
From nobody Wed Nov  1 00:40:43 2017
Return-Path: <zhencao.ietf@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 2E52713FAEE; Wed,  1 Nov 2017 00:40:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zhen Cao <zhencao.ietf@gmail.com>
To: <int-dir@ietf.org>
Cc: dhcwg@ietf.org, ietf@ietf.org, draft-ietf-dhc-rfc3315bis.all@ietf.org
Subject: Intdir early review of draft-ietf-dhc-rfc3315bis-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150952203714.25993.17333137226492207681@ietfa.amsl.com>
Date: Wed, 01 Nov 2017 00:40:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MWfsBpfpvnTnSNnQKZqavrenp8Q>
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, 01 Nov 2017 07:40:37 -0000

Reviewer: Zhen Cao
Review result: Ready with Issues

I am an assigned INT directorate reviewer for this draft. These
comments were written primarily for the benefit of the Internet Area
Directors. Document editors and shepherds should treat these comments
just like they would treat comments from any other IETF contributors
and resolve them along with any other Last Call comments that have
been received. For more details of the INT directorate, see
<http://www.ietf.org/iesg/directorate.html>.

This version is quite ready to go, with a small issue that I would like to
discussion:

In Section. 15 (Reliability of Client Initiated Message Exchanges), I strongly
recommend that implementation MUST NOT set both MRC or MRD to ZERO, which
attaches a possible risk that the client continues to send this message without
a stop.    So I would like to propose the following change:

s/
" If both MRC and MRD are zero, the client continues to transmit the
   message until it receives a response."
/
"The client must be informed with a limit of its retransmission behavior, and
MUST NOT set both MRC and MRD to zero"

-zhen



From nobody Wed Nov  1 01:13:13 2017
Return-Path: <prvs=1478feaab1=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 29C3D13FA0E for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 01:13:12 -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 b8SuFEhxwT-Q for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 01:13:10 -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 92A3A13F71F for <ietf@ietf.org>; Wed,  1 Nov 2017 01:13:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1509523989; x=1510128789; 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=TlVtjscR7Q7BpyWhmnflwW6Hy EP8YRQs4qS/vmssiQA=; b=gUKv7DCZjqB7P7PnhLa9yGNFNgn1uxfpNyL89edxo XVpyhn9jdE97rUP05Lh+jYAkZiqFR7ymHh9P5NSIzIyc3KjAR2/ShMFfGQ3GN7F5 wxxWP4C/5grfEN91tPMZVtjevCx+g4HyvRc8PAGK+Kfjlc31FwA+ij8yhI3JsXqj mA=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=davFlMF+sTBF4O3yGqcM5IYwXxzyQxKE+iusYxXp5YhK5BQFYalZdx5/Dhc9 2K1MOuBj59rAUB2owJm7TbW47m6SFlmWS4I5HMvv3lYaWUsQpmn5evvme y+KnrKdgtYotemBYyq2bCfCmtUHADdBjE6jL+EGACtKACHypW49I/M=;
X-MDAV-Processed: mail.consulintel.es, Wed, 01 Nov 2017 09:13:09 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 01 Nov 2017 09:13:06 +0100
Received: from [10.10.10.134] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005612282.msg for <ietf@ietf.org>; Wed, 01 Nov 2017 09:13:05 +0100
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:171101:md50005612282::inP6jkZJjDk9DLkX:00002PRO
X-Return-Path: prvs=1478feaab1=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Wed, 01 Nov 2017 09:13:02 +0100
Subject: Re: Proposal to revise ISOC's mission statement
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <5C4CF892-0D9E-4ECB-8B7B-F9385A8B1716@consulintel.es>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <20171030153844.GA19771@faui40p.informatik.uni-erlangen.de> <6.2.5.6.2.20171030121653.140878d8@elandnews.com> <1400E235-C322-42A0-8EEC-93D515EA95B6@consulintel.es> <53977630-3257-4CB9-8BED-DDAE5DD786B8@network-heretics.com> <25B4D3A1-721C-45DA-B6A8-EACADC7ECC9D@consulintel.es> <6.2.5.6.2.20171031162340.1250f1d0@elandnews.com> <C7DBB239-8912-420E-AB4C-E4A99BB81A9C@fugue.com>
In-Reply-To: <C7DBB239-8912-420E-AB4C-E4A99BB81A9C@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/P2pCnpTH1JOTOz3VwWBjn8U2PxM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 08:13:12 -0000

We aren=E2=80=99t talking here about leaders suppressing speech, if the cou=
ntry has split power, what I=E2=80=99m talking is about courts acting indep=
endently of the government to apply laws. In this specific case, it was tha=
t way: Court order not Government.

Again, take the example of the child pornography. A court order bans it. Is=
 that against freedom of speech? Is ISOC going to say that?

Here we have a similar case. Let me copy the text I responded in private to=
 someone else:

=E2=80=9CNo, what I=E2=80=99m arguing is that ISOC trust .CAT folks and not=
 having talked with the other Spanish ISOC chapters to verify it, instead o=
f going to read the court order.

My point here is not the Catalonia problem, is a general statement to make =
in the ISOC =E2=80=9Crules=E2=80=9D that ISOC MUST not interfere with court=
 orders, unless they can verify what is being said at the court order.

In this case, the court order indicated a list of very specific unlawful si=
tes, but ISOC published that it was a global order to .cat to ban any polit=
ical sites. It is a big difference. Our constitution doesn=E2=80=99t enable=
 splitting the country and consequently a voting on that, was declared agai=
nst law by our constitutional court, which ordered the police to avoid it (=
same way the police must avoid any other criminal or unlawful act, is their=
 duty). Our constitution allows to be amended, but Catalonia Government don=
=E2=80=99t want that, they want to make sure they split and do at their own=
 way, regardless only 25% of the Catalonian want that (which is only 5% of =
the total country population!).

Not sure if that's clearer.=E2=80=9D

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, 1 de noviembre de 2017, 2:18
Para: S Moonesamy <sm+ietf@elandsys.com>
CC: <ietf@ietf.org>, <jordi.palet@consulintel.es>
Asunto: Re: Proposal to revise ISOC's mission statement

    On Oct 31, 2017, at 8:47 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
    In other words, the society will only comment on law orders in "undemoc=
ratic countries".  Isn't it up to the society's Board of Trustees to decide=
 about that?
   =20
   =20
   =20
   =20
   =20
    No, as I said earlier (perhaps it's futile to repeat, but wth), democra=
cy depends on the ability of the electorate to speak about and understand t=
he issues being decided.   So when a nominally democratic country attempts =
to censor the internet, it makes sense to protest.   This is the whole poin=
t of having laws, and particularly laws that protect freedom of speech.   I=
t's quite commonplace for democratically elected leaders to attempt to supp=
ress speech, because it is often inconvenient for them.   This is normal.  =
 If we were to not protest when such attempts at suppression occurred, it w=
ould be normal for them to succeed.   That is why it makes sense to protest=
.
   =20
    Protesting an attempt to suppress speech is not something that only nee=
ds to be done un non-democratic countries; indeed, in non-democratic countr=
ies, it's somewhat futile.
   =20



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

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Wed Nov  1 01:20:05 2017
Return-Path: <prvs=1478feaab1=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 A761213F569 for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 01:20:03 -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 7krNmraM2jXt for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 01:20:00 -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 D81B213B138 for <ietf@ietf.org>; Wed,  1 Nov 2017 01:19:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1509524398; x=1510129198; 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=Rd0TNLeBhCwt2ByMRnWc04okQ lDlC9yCjxbWb/hlBxg=; b=JQ7H4pUoV7joPl2fpiRFMzJj5bmGAxLiBLY3DThEf oMiRmzkji1rY4btWuBLDgGfn3+Zc1bY6nIpZ5TliW1xr2+UX723MchTOdJpsSHUG riOP9ml21RWi37P/pq30Nt11hptirTt1FmqggyzHCNRHO+BexRA0EeHXexd7Dsst sQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=mgiBE2B6bMoZAkrSFuhjw/9DcOkQn+ozs6mhk3fsRtItZrmjapTaWxKyVgoa NvDlg4Q2q6c5NyHwbAzsUhe6ZvKiGKaazHRBoNCd+EloPP8lkyZE3dm13 suxqVPIo6aRGuVG8/vCq7Hqtb8Cegwa3chxrkFx1oAf9x3/n4whAxQ=;
X-MDAV-Processed: mail.consulintel.es, Wed, 01 Nov 2017 09:19:58 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 01 Nov 2017 09:19:56 +0100
Received: from [10.10.10.134] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005612287.msg for <ietf@ietf.org>; Wed, 01 Nov 2017 09:19:56 +0100
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:171101:md50005612287::jYd2S4DB7VR3hFwA:00003F+z
X-Return-Path: prvs=1478feaab1=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Wed, 01 Nov 2017 09:19:52 +0100
Subject: Re: Proposal to revise ISOC's mission statement
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <A0291665-ED5A-4627-8353-BD1B11A0945E@consulintel.es>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <20AAE687-BBEE-4990-8D6B-7E97EDB76F70@consulintel.es> <e236016d-71a8-d647-6734-417d032311ba@ericsson.com>
In-Reply-To: <e236016d-71a8-d647-6734-417d032311ba@ericsson.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/Wjrn3O7RL_r9GHywo6dfvc19uwU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 08:20:03 -0000

I missed this email a few days ago =E2=80=A6 Very short answer:

Agree that ISOC should not take political sides: That=E2=80=99s what they d=
id here, unfortunately.

What ISOC is missing here, in my opinion, is a very clear apologize for the=
 first post. I will love the ISOC board to take a position here to mandate =
that apologize. 45 million citizens have been insulted by ISOC staff by pub=
lishing false accusations, instead of having waited to read the court order=
 and consulted the rest of the Spanish chapters BEFORE the post.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Gonzalo Camarillo <Gonzalo.Ca=
marillo@ericsson.com>
Responder a: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Fecha: viernes, 27 de octubre de 2017, 9:34
Para: <jordi.palet@consulintel.es>, <ietf@ietf.org>
Asunto: Re: Proposal to revise ISOC's mission statement

    Hi Jordi,
   =20
    thanks for all the input!
   =20
    With respect to ISOC commenting on political issues, Frederic's
    clarifying statement (which was issued after the first one) said:
   =20
    > There are many other stakeholders who are much better positioned
    > than the Internet Society to deal with and comment on these
    > political aspects.
   =20
    So, yes, ISOC's role in those cases is not to take political sides but
    to comment on technical issues.
   =20
    With respect to your other comments, as you point out they are more
    about concrete activities than mission-level comments. I will relay
    them to those in ISOC dealing with those areas. In any case, you can
    find my brief initial comments below:
   =20
    1) ISOC has programs that bring "technical" and "policy" people to the
    IETF. In addition, we have received requests from the chapters
    community to have ISOC provide grants to support more-experienced IETF
    participants. One example given was, indeed, to have ISOC cover the
    registration fee for a few participants who meet some given criteria.
   =20
    As I mentioned in a previous email, we are going to also
    get the opinion of the IETF leadership about what is the best way to
    help the IETF in that area. So, in short, we are currently looking
    into this.
   =20
    2) How to have IoT deployments with better  security and resilience
    was discussed in a plenary a few IETF meetings ago, IIRC. In addition
    to having governments regulate such deployments, self-regulation by
    the industry is another alternative that is often discussed. ISOC's
    policy people are looking into that as well.
   =20
    Again, thanks for the comments, Jordi!
   =20
    Cheers,
   =20
    Gonzalo
   =20
   =20
    On 26/10/2017 4:30 PM, JORDI PALET MARTINEZ wrote:
    > Hi Gonzalo,
    >=20
    > I will suggest that we have a clear text (may be in the mission state=
ment) that avoids ISOC (and staff) to get involved into courts decisions in=
 democratic countries and even comment them unless they have documents that=
 demonstrate what they are saying. The recent happenings in Catalonia and t=
he lies that ISOC staff has communicated, are not only illegal but also lie=
s, and can bring legal consequences to ISOC & staff as a Spanish prosecutor=
 is already looking into that. I=E2=80=99m not going to repeat myself on th=
is, this is explained at:
    >=20
    > http://www.circleid.com/posts/20170926_catalonian_matter_law_order_de=
mocracy_freedom_of_speech_censorship/
    > and the continuation at:
    > https://jordipalet.blogspot.co.uk/2017/09/isoc-against-its-own-princi=
ples-acting.html
    >=20
    > Also, after reading your email, and according to the highlighted acti=
vities I will like to bring a couple of possible more concrete actions.
    >=20
    > 1) As one of the proposed activities is =E2=80=9CFacilitates open dev=
elopment of standards, protocols, administration, and the technical infrast=
ructure of the Internet=E2=80=9D, and this is clearly referring, at least i=
n part, to IETF, considering increase in the revenue that you mention, I th=
ink it will be very relevant to understand that many frequent and active pa=
rticipants are contributing from their own pockets, which our own personal =
time. So, I think we should consider that those not backed by big companies=
, could get some funding at least to cover their registration fee. I=E2=80=
=99m not sure if also traveling expenses, but I guess increasing the ISOC c=
ontribution to IETF, to make the registration fee free for those that need =
that support, will not mean a very high cost for ISOC and for many of us it=
 is over 2.000 USD per year.
    > 2) I=E2=80=99m missing highlighting very concrete activities regardin=
g =E2=80=9Cglobally-connected, and secure=E2=80=9D. Let me explain what I t=
hink are relevant actions that can be taken here in the next paragraphs.
    >=20
    > I=E2=80=99ve been tracking personally the problem of spam for several=
 years, and precisely we had a discussion with some folks on this yesterday=
 night. I=E2=80=99m clear that it requires some investigators, and I=E2=80=
=99m not talking only about =E2=80=9Cnetwork=E2=80=9D research, but also la=
wyers. I=E2=80=99m convinced that whois privacy is a big problem, as it hid=
es criminals, and we should get involved in making sure that ICANN understa=
nds it.
    >=20
    > My few resources to investigate this, brought me to the conviction (I=
=E2=80=99m not saying that it was not clear for me before, but now I=E2=80=
=99ve evidences) that there are some criminal organizations using spam for =
many other criminal actions. They create user databases (at least with emai=
ls, but possibly other personal data), and they are at the minimum, selling=
 or hiring those databases to another kind of =E2=80=9Clegal=E2=80=9D but i=
n my personal view, also criminal organizations which call themselves =E2=
=80=9Cemail marketing companies=E2=80=9D. Nobody, in general provides his/h=
er email for receiving spam, and in many countries, this is forbidden, and =
is even against the law, to have registered you email (despite what the =E2=
=80=9Cform=E2=80=9D said), and use it for a different =E2=80=9Cad campaign=
=E2=80=9D. In many countries every spam sender, requires a previous and exp=
licit acceptance from the email owner, but this is never respected.
    >=20
    > I=E2=80=99ve got threatened by several of those organizations when I=
=E2=80=99ve tried to act against them, and unfortunately, I don=E2=80=99t s=
ee data protection agencies and governments taking a strong position/action=
 on this, so Internet citizens are not protected.
    >=20
    > I think ISOC could invest in doing a good investigation on this (I=E2=
=80=99m happy to help, I=E2=80=99ve even a law proposal for governments to =
be able to fine/punish organizations hiring those illegal =E2=80=9Cspam=E2=
=80=9D services), bring this data to lawyers, and start a few suites agains=
t those criminal organizations, so governments actually see the problem, ma=
ke strong rules and enforce them.
    >=20
    > In summary, in my opinion =E2=80=9Cemail marketing=E2=80=9D should be=
 only used for a company to advertise their *own* products to their *own* c=
ustomers or interested ones that have explicitly agreed on that (which is w=
hat the law say in many countries, but is not getting enforced).
    >=20
    > I=E2=80=99m talking about spam, but the implications of what I explai=
ned above are related to security in general in the network, intrusion in o=
ur =E2=80=9Cown=E2=80=9D devices and apps, and all kind of related cybercri=
mes, and in the near future, if we don=E2=80=99t act now, it will also have=
 very serious implications in IoT and new developments.
    >=20
    > This week, during the RIPE meeting in Dubai, I learnt from ISOC staff=
 about the OTA (https://otalliance.org/), which is now an ISOC activity. Th=
is is one of the topics I believe ISOC should invest. My view has two sides=
:
    > a) The use of clouds is good (I don=E2=80=99t think is technically ne=
cessary with IPv6), but it requires SDOs, governments and industry to agree=
 in ways to protect consumers. Short explanation. You by a device, it works=
 only (or many of the best features) thru a cloud. Vendor goes to bankrupt,=
 you throw away the device, even if it costed several hundred dollars. Poss=
ible solution, governments have laws (as in any other field, FCC, EC, UL, e=
tc.), that mandate that every device being imported in a territory, either =
is not using cloud, or it has open and standard APIs so instead of using on=
ly the vendor =E2=80=9Cfree=E2=80=9D cloud can be attached/used to other on=
es without losing functionalities.
    > b) Security of those devices. Any Internet or IoT device, must pass (=
the same as FCC, EC, etc.), minimum security testing to allow to be upgrade=
d when security bugs are found, to avoid easily being hacked, etc. I recall=
 when we had modems, that need to pass specific regulations, and you can=E2=
=80=99t bring them to your country is they don=E2=80=99t have got the certi=
fication number. Nothing new here, just a different way to =E2=80=9Cconnect=
=E2=80=9D (it was RJ45 before, now is IP).
    >=20
    > A possible path for both areas is having the same organizations doing=
 those FCC, EC, UL, etc., testing, increasing their test, with the support =
from IETF or other SDOs when applicable, and making sure that governments a=
nd industry get together in supporting it and not allowing non-compliance d=
evices to be in the market. I believe that having the same =E2=80=9Ccertifi=
cation=E2=80=9D authorities, will not increase the =E2=80=9Ctesting=E2=80=
=9D cost, neither the =E2=80=9Cenforcement=E2=80=9D cost (same border contr=
ols in customs when importing products), and vendors will have an =E2=80=9C=
easy=E2=80=9D way to follow those specs if we work together.
    >=20
    > In my opinion ISOC has the power and budget to do that, and again, I=
=E2=80=99m happy to work on this area and specially contribute to the discu=
ssion of possible paths.
    >=20
    > Regards,
    > Jordi
    > =20
    >=20
    > -----Mensaje original-----
    > De: ietf <ietf-bounces@ietf.org> en nombre de Gonzalo Camarillo <Gonz=
alo.Camarillo@ericsson.com>
    > Responder a: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
    > Fecha: jueves, 26 de octubre de 2017, 11:21
    > Para: <ietf@ietf.org>
    > Asunto: Proposal to revise ISOC's mission statement
    >=20
    >     Hi,
    >    =20
    >     the board of trustees of the Internet Society (ISOC) plans to rev=
ise
    >     ISOC's mission statement. We would like to get your comments on t=
he
    >     proposal we include below. This email discusses the reasons for t=
he
    >     proposed change, the process we have followed so far to put toget=
her
    >     the current proposal, and the next steps in the process.
    >    =20
    >     ISOC's current vision and mission statements were developed aroun=
d
    >     2005 and are available at ISOC's web page:
    >    =20
    >     https://www.internetsociety.org/mission/
    >    =20
    >     These statements have provided ISOC with a clear direction for ma=
ny
    >     years and have been a useful tool for the community.
    >    =20
    >     What ISOC does in practice to fulfill its vision has evolved over
    >     time.  Looking at the environment in which ISOC operates, there h=
ave
    >     been important changes (some external and some internal to ISOC) =
that
    >     make it desirable to revise those statements at this point.
    >    =20
    >     Externally, the current Internet environment is different from wh=
at it
    >     was when the current statements were developed: regional needs ar=
e
    >     different, communication patterns are different, and the
    >     standardization landscape is different. Internet users and, thus,=
 also
    >     ISOC's chapters and members are more international and many of th=
em
    >     come from developing countries.
    >    =20
    >     Internally, ISOC's revenue sources have increased significantly f=
rom
    >     2005 until present. This means that ISOC's potential to realize i=
ts
    >     vision through activities has increased substantially and may sti=
ll
    >     continue to increase in the near term. The board considers that s=
imply
    >     increasing linearly everything ISOC does today would not be a via=
ble
    >     or desirable approach. Building a large reserve without further
    >     advancing ISOC's social goals is not a good option either. Instea=
d,
    >     ISOC will strengthen some of its current areas of engagement and,=
 when
    >     appropriate, engage in new impactful activities in new areas.
    >    =20
    >     Our goal is to bring more focus into the organization. The idea i=
s to
    >     avoid spreading ourselves too thin and, instead, increase ISOC's =
focus
    >     on activities that make a difference.
    >    =20
    >     In order to make those key decisions, staff, the board, and the
    >     community need to be on the same page regarding ISOC's vision and
    >     mission, and their underlying meaning. Given that many members of
    >     staff, the board, and the community were not around when the curr=
ent
    >     statements were developed back in 2005, revising them with their
    >     involvement was considered to be a necessary exercise so that
    >     everybody feels them as their own. Getting a common sense of owne=
rship
    >     is one of our main goals.
    >    =20
    >     In order to have a fresh look at our vision and mission, a set of
    >     workshops involving the whole staff were organized.  Using an
    >     iterative process and taking the input from those workshops into
    >     consideration, further workshops involving the board and ISOC's s=
enior
    >     management were organized with the help of a facilitator. Some of=
 the
    >     workshops were virtual and some of them were face-to-face.
    >    =20
    >     The board had a face-to-face retreat where, based on all the work
    >     above, revised draft statements were generated. Those draft state=
ments
    >     were sent to parts of the community (including IETF leadership, I=
SOC's
    >     emeriti trustees, and chapter and org members) to get initial
    >     comments. After gathering a good amount of initial community feed=
back,
    >     the board generated new proposed statements addressing the commen=
ts
    >     received. With the process above the board aimed to ensure that t=
he
    >     revised statements take into account the perspectives of staff as=
 well
    >     as our wider community.
    >    =20
    >     The resulting proposed statements (included below) are now ready =
to be
    >     sent to our whole community.
    >    =20
    >     During the process above, we agreed that ISOC's current vision an=
d
    >     mission are still as valid as ever. With respect to the *statemen=
ts*
    >     that capture the spirit of the vision and mission, we do not prop=
ose
    >     any changes to the vision statement.
    >    =20
    >     With respect to the mission statement, we propose to update it.  =
One
    >     of the goals with the new statement is that it is both concise an=
d
    >     memorable.  Consequently, the mission is stated at a higher
    >     abstraction level and contains fewer points.
    >    =20
    >     The current mission statement included a list of activities ISOC
    >     performs to help achieve our mission. While it seems that list wa=
s not
    >     approved as part of the mission statement back in the day, the in=
itial
    >     feedback we have gotten from the community clearly indicates that=
 many
    >     consider capturing the list in an official way important. Therefo=
re,
    >     we propose to keep those bullets as highlights of activities.
    >    =20
    >     It is worthwhile noting that, regardless of the outcome in the fo=
rm of
    >     a revised mission statement, this process is being very useful in
    >     itself. It has clearly helped getting a better understanding abou=
t
    >     ISOC's purpose among everybody involved.
    >    =20
    >     Please, find the proposed statements below and share your comment=
s
    >     with us on this list. Thanks!
    >    =20
    >     Cheers,
    >    =20
    >     Gonzalo Camarillo (for the board)
    >     Chair - ISOC Board of Trustees
    >    =20
    >    =20
    >     --- Proposal ---
    >    =20
    >     Vision:
    >     -------
    >    =20
    >       The Internet is for everyone.
    >    =20
    >     Mission:
    >     --------
    >    =20
    >       The Internet Society champions the development of the Internet =
as a
    >       global technical infrastructure, a resource to enrich people's
    >       lives, and a force for good in society.
    >    =20
    >       We work with the worldwide Internet community for an Internet t=
hat
    >       is open, globally-connected, and secure.
    >    =20
    >       Together, we focus on:
    >    =20
    >       - Building and supporting the communities that make the Interne=
t work;
    >    =20
    >       - Advancing the development of Internet infrastructure,
    >         technologies, and open standards; and
    >    =20
    >       - Advocating for sound Internet policy around the world.
    >    =20
    >     Highlights of Activities:
    >     -------------------------
    >    =20
    >       To help achieve our mission, the Internet Society:
    >    =20
    >       - Facilitates open development of standards, protocols,
    >         administration, and the technical infrastructure of the Inter=
net.
    >    =20
    >       - Supports education in developing countries specifically, and
    >         wherever the need exists.
    >    =20
    >       - Promotes professional development and builds community to fos=
ter
    >         participation and leadership in areas important to the evolut=
ion
    >         of the Internet.
    >    =20
    >       - Provides reliable information about the Internet.
    >    =20
    >       - Provides forums for discussion of issues that affect Internet
    >         evolution, development and use in technical, commercial, soci=
etal,
    >         and other contexts.
    >    =20
    >       - Fosters an environment for international cooperation, communi=
ty,
    >         and a culture that enables self-governance to work.
    >    =20
    >       - Serves as a focal point for cooperative efforts to promote th=
e
    >         Internet as a positive tool to benefit all people throughout =
the
    >         world.
    >    =20
    >       - Provides management and coordination for on-strategy initiati=
ves
    >         and outreach efforts in humanitarian, educational, societal, =
and
    >         other contexts.
    >    =20
    >     --- End of Proposal ---
    >    =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 exclusive use of=
 the individual(s) named above and further non-explicilty authorized disclo=
sure, copying, distribution or use of the contents of this information, eve=
n if partially, including attached files, is strictly prohibited and will b=
e considered a criminal offense. If you are not the intended recipient be a=
ware that any disclosure, copying, distribution or use of the contents of t=
his information, even if partially, including attached files, is strictly p=
rohibited, will be considered a criminal offense, so you must reply to the =
original sender to inform about this communication and delete it.
    >=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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Wed Nov  1 02:35:04 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3616F13F66D for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 02:35:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=Y9JyiDJK; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=w9UZgpU6
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7-8qRtVFyhDf for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 02:35:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F68113F666 for <ietf@ietf.org>; Wed,  1 Nov 2017 02:35:01 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.146.205]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA19YcIP023015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Nov 2017 02:34:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1509528890; x=1509615290; bh=XgF5LQ5s3IYtzOiPQacvd1m7hMa0J5ygi77czWiDXfs=; h=Date:To:From:Subject:In-Reply-To:References; b=Y9JyiDJK6vBZvy7R5LG2NmlLAi8WijuoLVF/uKJeFfmuCuug/y3iXv9Lb1adMGpfo 5Wpihr6R7rU2zZ1QPGo0GKdYvOqhsC0zjW4Z65EadMo2LCrYIKfZcIEuo6tefhqgPm TUayljOi1F0zty1I2CU6YBsSFOCs9ShBYYnrcaUw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1509528890; x=1509615290; i=@elandsys.com; bh=XgF5LQ5s3IYtzOiPQacvd1m7hMa0J5ygi77czWiDXfs=; h=Date:To:From:Subject:In-Reply-To:References; b=w9UZgpU64ZgahOyCNoUme84A/pUcBbGFeNs/xy4gBYBF+P1WPAYM6pvYWDQbU8Fz4 zjcYxcDXWdJanYRmlEoJ5nFn6E00TBfQ9h9Z5pu/UQag9ttzm959+TBU4qPlOx+mkh bJlX1acuS5Kg6NeY5dlN43zpUFH/3v8uC/wB27BY=
Message-Id: <6.2.5.6.2.20171101014511.1299be30@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Nov 2017 02:20:36 -0700
To: jordi.palet@consulintel.es, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Proposal to revise ISOC's mission statement
In-Reply-To: <5C4CF892-0D9E-4ECB-8B7B-F9385A8B1716@consulintel.es>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <20171030153844.GA19771@faui40p.informatik.uni-erlangen.de> <6.2.5.6.2.20171030121653.140878d8@elandnews.com> <1400E235-C322-42A0-8EEC-93D515EA95B6@consulintel.es> <53977630-3257-4CB9-8BED-DDAE5DD786B8@network-heretics.com> <25B4D3A1-721C-45DA-B6A8-EACADC7ECC9D@consulintel.es> <6.2.5.6.2.20171031162340.1250f1d0@elandnews.com> <C7DBB239-8912-420E-AB4C-E4A99BB81A9C@fugue.com> <5C4CF892-0D9E-4ECB-8B7B-F9385A8B1716@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DdyAd8n2mgOawroh-OWXMlhXAug>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 09:35:02 -0000

Hi Jordi,
At 01:13 AM 01-11-2017, JORDI PALET MARTINEZ wrote:
>No, what I'm arguing is that ISOC trust .CAT folks and not having 
>talked with the other Spanish ISOC chapters to verify it, instead of 
>going to read the court order.
>
>My point here is not the Catalonia problem, is a general statement 
>to make in the ISOC "rules" that ISOC MUST not interfere with court 
>orders, unless they can verify what is being said at the court order.
>
>In this case, the court order indicated a list of very specific 
>unlawful sites, but ISOC published that it was a global order to 
>.cat to ban any political sites. It is a big difference. Our 
>constitution doesn't enable splitting the country and consequently

As I see it, something went wrong [1].  What you are asking is for 
the Internet Society's Board of Trustee to set a policy so that the 
Internet Society does not make any statement related to a country 
without verifying the facts.

Regards,
S. Moonesamy

1. The word "wrong" is used for simplicity instead of accuracy. 


From nobody Wed Nov  1 03:49:24 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 3F66113A66B for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 03:49:23 -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 f21TbUeu7E6b for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 03:49:21 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c: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 118DE139428 for <ietf@ietf.org>; Wed,  1 Nov 2017 03:49:21 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id b189so3924243wmd.4 for <ietf@ietf.org>; Wed, 01 Nov 2017 03:49:20 -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:content-language; bh=ehDjb8eKWkqm17M9qjk5i3v3EATD1UipDJaT2J7U4cI=; b=ewKZIunAgNKWwtZULzp4yePsXmG1Xr/bhJScq9DKahlrltUHuAcfXP2p12PBBw7ZEM qaJnMig+lmId8ReGVa7vUi/wvFijZ4CvUf19M13Dzq2ZTFEekbernBM9E4+8t8PbGbbl Xx5WXUC4iWCpX+TiNTnpOjz7i+tvwCRQMI2vLwlxXypl41k8b30yISylxvTIEvbEnWI5 bzaMnpi0gdGyAZUhwF84bJWkvlSpfFEqJjZaEdhqmEBfgKWiz/J6kZ5Xz/KdKxaUNYpW 1aAvhvDLdBc2jMODaf7gv5ukF89XDhxtms74LAUp/VD9GdAQ4dBJLHC4GaDWiYVPEgoI f3sA==
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 :content-language; bh=ehDjb8eKWkqm17M9qjk5i3v3EATD1UipDJaT2J7U4cI=; b=PMxojeqluVC1wyJet5iMVuoXE5EVNEUytossg8k64+OdI7no38np61IRi+cdPlFbmS XY2OmpGwTpGK3HKdy+nFKahmXtfcr1hQhNzonoPsoPfvwjGel0WNar46VtGEHoq2EbT8 qLmF3GvSXKasPE0LAo35W1euBXpCOjcLBb4MKJhUnfjOee0yRAOWL2r56RqIgbuqo2og /Ro81GSjy7V3auhPtaqDFr+Zy4z/LxyDv+zprx/OOJ2JpQmdWcyeABEQl+5798baoKim KjNcvySPwhYsockLoqnFuCCmupWtT6zj3ZFJN6M2N7FnSjvFKarJCgyEa/n8gP4SpWpI d//g==
X-Gm-Message-State: AMCzsaURkOLmL1+tNzs8ef5kOsHFNK4gyoUk1/ki5r8Bw12TiRHuxEGU Y/htNe7m5zaY1Gu1N3n786g7RE/5
X-Google-Smtp-Source: ABhQp+TYkRtiS05SQ6OlaQAkDZrUTKvxY9YXKBzlaloWSDSlFpuo6eqLXn3Yyf2SPjij8fttIlBEgQ==
X-Received: by 10.28.54.154 with SMTP id y26mr4717076wmh.15.1509533359117; Wed, 01 Nov 2017 03:49:19 -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 141sm1143937wmr.45.2017.11.01.03.49.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Nov 2017 03:49:18 -0700 (PDT)
Subject: Re: IETF Website Status Update
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <545156e4-144f-6519-0f93-b4d2fa0f6789@gmail.com>
Date: Wed, 1 Nov 2017 10:49:16 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dHE5dq81QoGHL05wGnnJ9mWkkuk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 10:49:23 -0000

Hi Russ,

I must say I still prefer the original in terms of utility, clarity and 
information density.

I am not sure if the font being used is mandated, but I find it far less 
crisp, almost blurry compared to the smaller font of the original. I 
find such lack of crispness on web pages irritating and when I see it I 
am distracted by wondering if there is a technical failure in my system. 
People like 4K for a reason, and I see no reason why this preference 
would not be carried over to web pages.

Whilst I understand the need to provide an accessible interface I don't 
see why there cannot simply be a parallel high efficiency interface as 
well.

A useful addition to both the original and to this would be a direct 
link to id-nits right next to (well right before) the submit tag.

- Stewart


On 31/10/2017 21:36, Russ Housley wrote:
> I want to share an update on progress on the IETF website revamp project. In particular I’d like to highlight what has been done to respond to feedback from the IETF community received around IETF 99.
>
> A. Provide a landing page dedicated to current IETF participants
>
> A draft is currently posted at https://beta.ietf.org/links/
>
> That page includes links to:
> - items on the left-side at www.ietf.org (or a subset thereof)
> - information about the next IETF meeting
> - links to functions at datatracker.ietf.org
>
> The goal is to make this page:
> - viewable in a single screen on a desktop/laptop display
> - reachable via a short, memorable URL
>
> The current content includes changes implemented based on suggestions received via email after IETF 99. Of course, this page will be updated further based on input from the community.
>
> B. Ensure WCAG 2.0 compliance
>
> Since IETF 99, we have worked with the website developer to improve compliance. This is a requirement of the Statement of Work (https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf). We believe that has been accomplished. However, ensuring and improving accessibility must be part of ongoing editorial practices, so it will continue to be an area of focus for the website.
>
> C. Conduct review with other key audiences, especially potential participants and non-participants
>
> Additional interviews with members of the key audiences have been conducted to gather input. In general, response to the beta.ietf.org site was positive.  IETF newcomers say that the new site makes it easier to understand what the IETF is all about. Some specific suggestions have been incorporated into the project, and they are included at https://github.com/ietf/www.ietf.org/issues
>
> D. Improve data use and load times
>
> Since IETF 99, the beta.ietf.org site was placed behind the Cloudflare CDN. This has significantly improved load times. Of note, in interviews (see item C above), new or non-IETF participants located in Latin America and Africa did not report load time as a significant issue. However, as the new site moves to production, the editorial process will continue to fine tune how images and other elements are handled to further improve performance.
>
> Next steps:
>
> We are continuing to fine tune content and are aiming to move to production after IETF 100. One significant task remaining is to ensure continuity for important URLs, as specified in the Statement of Work. We expect to tackle that after IETF 100.
>
> We welcome input and suggestions. We held "office hours" at IETF 98 and IETF 99, and we will hold "office hours” at IETF 100.  If you will be in Singapore, please take this opportunity to share feedback in person. Details will be posted on a sign around the IETF meeting registration desk. And, of course, questions or issues can always be raised at https://github.com/ietf/www.ietf.org/issues
>
> Sincerely,
>    Russ Housley
>    IETF Website Revamp Project Manager


From nobody Wed Nov  1 04:15:29 2017
Return-Path: <prvs=1478feaab1=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 6F150139B9F for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 04:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 aPTA2ThU0DEI for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 04:15:25 -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 C376A13968C for <ietf@ietf.org>; Wed,  1 Nov 2017 04:15:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1509534922; x=1510139722; 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=BnzNGcisTEuf5cfBCs3MxIxRh AWJomio/HbJctvGy0E=; b=Z/muhkBZoMV9VgUWUoRU0GQhJgAYHpDnWpCG8C+tZ XhGjSXopImOOMpJNcxhtPc5QK6GiUs1493VB9TBQcGvXHLBYb2OENUNaDKzqwftA 4u98ACH+/idoWrG+zoIhzFZSohlxzZ/t6Td3uKL4yDqMauNJcr5T4GGkv/8V2NlF 90=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=U8a2OvwxQSFMOt01cmVSGPnDfNCMfVCfU4a/XIdvpSsEJwOeJ/M6D5RSuUQ/ BAH+zyT7x9OJEqauOKYRiolIUYU/RsqkLezTe/0TQMwHjE9oPr1rskMeO +5q7UWX3LpkHUpDdcBHw9TEGafkWmTnjj5PTKoJLnuZuYjnt2B+d2c=;
X-MDAV-Processed: mail.consulintel.es, Wed, 01 Nov 2017 12:15:21 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 01 Nov 2017 12:15:18 +0100
Received: from [10.10.10.134] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005612421.msg for <ietf@ietf.org>; Wed, 01 Nov 2017 12:15:17 +0100
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:171101:md50005612421::bzum/jRBC2xhQT7y:0000AD/c
X-Return-Path: prvs=1478feaab1=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Wed, 01 Nov 2017 12:14:57 +0100
Subject: Re: Proposal to revise ISOC's mission statement
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <C5A15CE2-D403-46AC-8287-48F5CEFF3991@consulintel.es>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <20171030153844.GA19771@faui40p.informatik.uni-erlangen.de> <6.2.5.6.2.20171030121653.140878d8@elandnews.com> <1400E235-C322-42A0-8EEC-93D515EA95B6@consulintel.es> <53977630-3257-4CB9-8BED-DDAE5DD786B8@network-heretics.com> <25B4D3A1-721C-45DA-B6A8-EACADC7ECC9D@consulintel.es> <6.2.5.6.2.20171031162340.1250f1d0@elandnews.com> <C7DBB239-8912-420E-AB4C-E4A99BB81A9C@fugue.com> <5C4CF892-0D9E-4ECB-8B7B-F9385A8B1716@consulintel.es> <6.2.5.6.2.20171101014511.1299be30@elandnews.com>
In-Reply-To: <6.2.5.6.2.20171101014511.1299be30@elandnews.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/-rvJ0k--GRRVjwAZ8Q8anxu8Sxo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 11:15:27 -0000

Exactly!

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de S Moonesamy <sm+ietf@elandsys=
.com>
Responder a: <sm+ietf@elandsys.com>
Fecha: mi=C3=A9rcoles, 1 de noviembre de 2017, 10:35
Para: <jordi.palet@consulintel.es>, <ietf@ietf.org>
Asunto: Re: Proposal to revise ISOC's mission statement

    Hi Jordi,
    At 01:13 AM 01-11-2017, JORDI PALET MARTINEZ wrote:
    >No, what I'm arguing is that ISOC trust .CAT folks and not having=20
    >talked with the other Spanish ISOC chapters to verify it, instead of=
=20
    >going to read the court order.
    >
    >My point here is not the Catalonia problem, is a general statement=20
    >to make in the ISOC "rules" that ISOC MUST not interfere with court=20
    >orders, unless they can verify what is being said at the court order.
    >
    >In this case, the court order indicated a list of very specific=20
    >unlawful sites, but ISOC published that it was a global order to=20
    >.cat to ban any political sites. It is a big difference. Our=20
    >constitution doesn't enable splitting the country and consequently
   =20
    As I see it, something went wrong [1].  What you are asking is for=20
    the Internet Society's Board of Trustee to set a policy so that the=20
    Internet Society does not make any statement related to a country=20
    without verifying the facts.
   =20
    Regards,
    S. Moonesamy
   =20
    1. The word "wrong" is used for simplicity instead of accuracy.=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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Wed Nov  1 05:44:50 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 E7E4B13F60D for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 05:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Qo4Sor0rPEkv for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 05:44:46 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0060.outbound.protection.outlook.com [104.47.34.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D944113A1FA for <ietf@ietf.org>; Wed,  1 Nov 2017 05:44:45 -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=Ro09bIwok0Gz5FglARV1yrpT9ZjrqXq/L2nMFav0nCM=; b=AJzGkUB2mG4HUM+uSDpDdNgiZ8C5B+33E/JE3HiDGdr81eAvmYp8wMDBE+gPDBRgrJU823nh6NXSwuKoWmV3qi1lMAX6FNQAcHP4qrBKrbWxvmDaE2cuRHdCkdqfjJrSQ8aim6p6iukV1XLOI/C1d+/N4An069k08AnjSTSXP/Y=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ford@isoc.org; 
Received: from [IPv6:2001:8b0:dcb:7d85:8d8e:681e:4800:915f] (2001:8b0:dcb:7d85:8d8e:681e:4800:915f) by BL2PR06MB2209.namprd06.prod.outlook.com (2a01:111:e400:c751::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.197.13; Wed, 1 Nov 2017 12:44:43 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\))
Subject: Re: Call for Nominations: 2018 Applied Networking Research Prize (ANRP)
From: Matthew Ford <ford@isoc.org>
In-Reply-To: <634C14EC-4C3B-49AB-8DA0-F12AAEBB3A2B@isoc.org>
Date: Wed, 1 Nov 2017 12:44:31 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC757668-322D-4E6F-B52A-D33BA67BA93E@isoc.org>
References: <634C14EC-4C3B-49AB-8DA0-F12AAEBB3A2B@isoc.org>
To: irtf-announce@irtf.org, irtf-discuss@irtf.org, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.3445.1.7)
X-Originating-IP: [2001:8b0:dcb:7d85:8d8e:681e:4800:915f]
X-ClientProxiedBy: AM5P194CA0011.EURP194.PROD.OUTLOOK.COM (2603:10a6:203:8f::21) To BL2PR06MB2209.namprd06.prod.outlook.com (2a01:111:e400:c751::23)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 633c78f3-e3e3-453d-d973-08d5212653d8
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(2017052603199); SRVR:BL2PR06MB2209; 
X-Microsoft-Exchange-Diagnostics: 1; BL2PR06MB2209; 3:79YwvsFXNQn83opILPd530DsBK39GA44VIh40XsT8OxaS8WxYdpUIJQzGgiGL+nY0pJqVklyj2/0DYF3oh+ymgxGU46cbG4OAQ6ejCCsTBSlEcuhGyxQ3XB/gl1CwS4HcCePHqBlesnFHScQggwZU4m8tegmsoOf9cNqoCgnt9/EeCySEuy3Z6K8w0Lhh+CZSQX9TaSz3Rpa/fGJCYVbptBmIFJFST2uhVdDIB755UrVkFBgM8rUBi27Wr4+LcWd; 25:CoNvXSABHJFoig62+UdQ7LDIa5HxUhVqfncY+KAU32+5IKHHMIHMI++1YHSY84Fkcny0CM1OJNRjT5IoUGYkKc4Wx0/cWnwyTCsB+VA6VT/IIGWSqvltXjfUj0u8jmSU/tCWrRmtQJrPoaafveyZUZBDg4pmtvYlQ6h4p7K73FEjHBCFGWyR2Hm1QhB7H9VGZwRT7x9fdngA4V9szYCxwnv8/YkAQ1Q5Bm7YnOD4tq5u+105eBqUBXCIYaWGqpZhoXsmF/HzR7LxduxD79Ip0uuBjvezbxsbwqBUHgeto6/lJNjjcznp5Cy+2Ex/JGM+uIWxcl9qlRzw7RiXxDMCVQ==; 31:zzw+IQot4/u05jCIwnFm7Yl+TfT0UzDg14Hu8IP4VywDvqcQXazaINSiYEAO/FeO3qdyHQMwoxVaTerIGgL5nypzJNiy5TPz2byttpwF3Kub8j1XzuZlDV8dq1gfPrgmWlXtLUTUHki+nNq12FbxwFPjM+iEKB0cQAy9g1V74SBC3CgQSFIkGH601nQNA9pGqhw4736aNH/6uy597NiwU1g4E9waZ1AQajsdpswup20=
X-MS-TrafficTypeDiagnostic: BL2PR06MB2209:
X-Microsoft-Exchange-Diagnostics: 1; BL2PR06MB2209; 20:z32yreV+E0PAqCiyu2d9nd84WG4S8ma/3Je7j6j/Sp0OZqfKgSA0CeGj+1xQgWj2cT4xlb8jRvIqHTxliEYxSCu1yQIWep+Yl+LtdUL9STkiMD3proApY2nCrxjv2ijqJ3nT527D/6RlOgbE+D34Jj7RdceV6yqZt3kaD9+WglosALVEQR2ZesGTD/U1AVVSeg7N5/1n3PcbUbyQTeeWRtC2O/eDMUCVtjldNNljdcaWq6/Pp+xf+2KLhkJUMcZVaFq467tX/Ywil9GUU4HnbcozARJUxNAKFf0fSQudNk6yIawTy9+vwwwX+5k28hzEe/DUefWZscEZQi8261gGX0YjwMmriEw9Az5inJV50cIG77OsWtKJ1SIr7ovN8mc7jJEjHsaV/CCUJGFM4zdJYR//i5esjnJ2OkiSa4spMChD/lSll7ICh2/fefnUfsNCQilCOqSwu6rDRn0KYzT5gqavZguOa0Ns/6Tm0S2XM60uuD2a8kqyoMSlilrcFKgm; 4:uvWvHVLarOYN4xR5eAoMpk3W/BugJ413VQqwqvUpyb+fsIzG5KlqXz++i5+rL2PyGHN+7x7HcP0Wd+a9rToaVsLtYUIoRuRhfmiabjn/0ObUOV6Yh07RDYdY7LPNQ0fxAQaUc/zrEnIDVXRa9Q2G8rRv6ptNeJ+KjnKKF6yumLYvRAiyUzrAefEyUVS1BCg8hgLN2D/uz6w8X8k+xKy62VXbZB7rS7f6+1t88IP4WdqS7KzXQTcrytXtw7yqaaXITq9WP0cfUROXOtHJNJ7a2BYHGZTViYyajFyrKFQa+8n+2VT7pcyJRvARgaufAiKI4tpx/7Q/RxDpNt1BCwf5cyCIJ74fwZhN9NkdmLIGfDs=
X-Exchange-Antispam-Report-Test: UriScan:(278428928389397)(192374486261705);
X-Microsoft-Antispam-PRVS: <BL2PR06MB2209BB43B28FC3957216FCF4A75F0@BL2PR06MB2209.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(3231020)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(3002001)(6041248)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123558100)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BL2PR06MB2209; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BL2PR06MB2209; 
X-Forefront-PRVS: 0478C23FE0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(979002)(6009001)(39830400002)(376002)(346002)(189002)(199003)(24454002)(47776003)(33656002)(76176999)(50986999)(478600001)(81166006)(2906002)(229853002)(5660300001)(106356001)(6486002)(81156014)(105586002)(2950100002)(101416001)(6916009)(8936002)(8746002)(6666003)(1706002)(7736002)(189998001)(83716003)(97736004)(53936002)(6116002)(6246003)(6306002)(82746002)(57306001)(86362001)(8676002)(966005)(68736007)(53546010)(25786009)(305945005)(316002)(36756003)(50226002)(50466002)(23676003)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BL2PR06MB2209; H:[IPv6:2001:8b0:dcb:7d85:8d8e:681e:4800:915f]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTDJQUjA2TUIyMjA5OzIzOnhtNWdkUW1EVy9IcWhYejBDeE1La21WWTdU?= =?utf-8?B?WHdFYWF5dWNKbFFtRmR0U1YzaEZMem5XQ3U0K0liM3M4cU9XZU9YZ21WOU1n?= =?utf-8?B?elQvZFZYZXprTit2ck02SEZLdi9TME9HblMyQkFld2FXWmtyWmRVOVM2dmdR?= =?utf-8?B?Qmd0dUJBeitxZHJJdlo3VVpYbkF2ZUFqTTE4ck5ZaFRvdVB3ai95dHFwUGdX?= =?utf-8?B?NXErSERMOTRJd2R1YVZaajUvUitvS3A0bUs0b1VldHFOWi9wbXd1a01JNmxw?= =?utf-8?B?YXp5M09WM0o1ZjhldGxUc1ZGMUYxeHZQckUyU0NYcnFDQW0xckRtNi9UbllU?= =?utf-8?B?MSt3VTNlbmh1WWV6clVDemZCb3hWdUFNdkJwY2YzZlVKQWpFeHRUcUFxbTY3?= =?utf-8?B?MnptYXJ4TmJtS0p0L08wT21zYmhubjNYSlkxNTVub3JpMXBhZytpSUc3dW5q?= =?utf-8?B?WnlDYkZtQUt6UjhUUW1IR3dmTGJrTHZvcDJSbllkYVMwRk42TytuV05KbGVr?= =?utf-8?B?cTVucThadnE5akdlM2s5VkFPY0FxQ1RBSjNDbzdVSFo4M0VaSmRFNy8vb2Js?= =?utf-8?B?SDU1N3RpYmVYNTFJenRGeDJ3TncxSWV4T3ByOUMrQk4rNUdZUHhIZkp2bVhL?= =?utf-8?B?dmZ1KzVFQ2lCRXliQ0pXajNpZVd6WFRCUGwyeGNHWFlYdXhpcmlaejNJRkN3?= =?utf-8?B?b1RGN0VSMzdsTC91bUs0N0FndlMxNHlUTjR5L3JLbTJtZ0k5NXJFNW5wL0F0?= =?utf-8?B?cUlMdGZLTkNpLzQyQUlCUTcrWEwrbWgvYVpydzFBZHh0Y2p1TzNid1oraVJr?= =?utf-8?B?OC9LamFVVkZrV1NuWWJuc2xOZ1Y0Z3RyRWZpeGVsOG9PMlhWdXNSTlczaXYv?= =?utf-8?B?enkwTk5lMVdlMXBYTlpQRkU5UW5FT25oVDY3VTBrL2FPWEFxOXpaOGl1NTd1?= =?utf-8?B?NVFHcEE4QWtraGF4WE1YUFc4OFZwTWtjdGltYnM2WHAwcEs0QUN6U0RvS3g3?= =?utf-8?B?Q1dNNUdJTktHT1VoQ25qUWZVNGl4amZxZnUyUElUSGcyMHlGQUhSTGdaejFl?= =?utf-8?B?Ly95cTRRR1BPclRwVzdGcGZnay93ZFZGZzVyY0RFVkptQi9uL1VSM0svWjhu?= =?utf-8?B?b3U2TWN1ZTkzK1ZRMnJ0dWJJYWQzMUh0TnpmUGdwV1Y0RmM5dDBSTkVOblB3?= =?utf-8?B?UzJOWVp5elUzbFBMYWVWeU9pZUlHOGc0RkJsTHBLdlhLcXN6UXpaZC9NdnJU?= =?utf-8?B?QzQ1U3hvR0dmSEFTZXF3R0xIUnVsWU1jcGN4ZDdQS0ttQ2xoNCtjT1F4VFFO?= =?utf-8?B?VjYzaG0vSUR3N0hzTG42c0ovalNKRmhvc0w4OFZ3eSt0WmZpWnFXZktHUlBZ?= =?utf-8?B?dTFTT0pSQTJrR20rdGpqbkJaVFFHaXI1UHkxSy80Q0pTbzEyNnZWQjRORGlN?= =?utf-8?B?c09CbFV6QzRJR2UzSVJ4VngxWUNndU1LRWdUdkdOdHora2RFclpkcjl2UFJP?= =?utf-8?B?cE9QcENhMHV5M2RoMUpoT2NVbzRjalRXSytKRHVVcHZNcDlsM0VaTXFKTUZt?= =?utf-8?B?ZXpCM1o2V1RUNEdQTGhBQjlvZzlsUGNDd0E3M0hoN1QxZVBmSFovYkVxeDRL?= =?utf-8?B?YlA3ZlJVOVpDeUVhVWFqS0tYaHZOeloxOCtHM3RvQkxhdE42NnBheXlEaCtT?= =?utf-8?Q?yBTSZhB/My6ZcbWjM8=3D?=
X-Microsoft-Exchange-Diagnostics: 1; BL2PR06MB2209; 6:Q6KElJST1V6Rcf5R2YtvlIe/mrdfdTmCttNyAN71Mi6ACMyUNfWtbHHtpPTlS2/CPUO5sgiiv8mmYUFcxVoAIXCicgwHvmLkmD49vZ9ZykWB89TTk8z0lTZx4NSN3/qceywgB0etutWZf3930KEJsHb/CtJA23/1Px6cJkd/ie8BnNksluoy28slEgZLLdbMLS4+Fbqb3Yua2bzp2W+/akJxO2Dd4nCvTwibRAAyHpZ6HY83nVjMQ01CS21xewlTkU8pWAMoeNU7tIujw9QWdUSbD4LccLFJNWjzrPRIPbsrBUBB5/UZAmbjYXObyxOQGqQM+vDL3EFUnBFrJwMxgLFf74owxFYz122rO9fmbGs=; 5:uuj69OFRl2VVLfj23s7po44Ft8+NTgmwjI3YIikCNwLWPAos5zbJ6w31H/2cyvA5qXf7FEuCx98uCTK4pVQLEgjw0B+ZDgLV+aUDnTPzoRKVCFvsgcm7EQZY9JMKmZX7A3UNF+EjwUDa2e0CBr1ZuwZZNSJhlvbNzN1kE3xr8Fk=; 24:WnufGwxvEc2wTMoGCbyz8aTDKlAjpQpkUhs59pt1t68lweKfsSJFe1VausJphlQlxIz1PRzqOAwrfGQh3Lloz29TgnD1T/jJ3XiE3N1wrzk=; 7:w6LvVOp4GTJm+EasLhLRM8LgKrndmgxtmpe8fvhdzTn+ovAzobvbbSy+oQKH8Y+3wJ3m6/ub+Xy486TfliGm31weKumyZdgIxW5H0lvHR3zfTqIP6BU0Pq43HewyOtwaQljD+dUT2l7nO5wwq9gVMC3U7F3ZgwxehVhTr1YDdziSvkkIHVG8NOQ+p5rzlNF1X3JpZOka1MTPkpFru3cEPL/qY80QZXAtOoGFoG5tbFpx++tGCltbVB9G15qXKTOF
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Nov 2017 12:44:43.3706 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 633c78f3-e3e3-453d-d973-08d5212653d8
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR06MB2209
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/igtPC11TJzNzasOMTj7OmZgttmg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 12:44:49 -0000

** NB. DEADLINE FOR NOMINATIONS : NOVEMBER 5 **

> On 4 Oct 2017, at 10:16, Matthew Ford <ford@isoc.org> wrote:
>=20
>                   CALL FOR NOMINATIONS:
>=20
>         APPLIED NETWORKING RESEARCH PRIZE (ANRP) 2018
>=20
>                    https://irtf.org/anrp
>=20
> ********************************************************************
> ***     Submit nominations for the 2018 award period of the      ***
> ***  Applied Networking Research Prize until November 5, 2017!   ***
> ***                                                              ***
> ***    (Please share this announcement with your colleagues.)    ***
> ********************************************************************
>=20
> The Applied Networking Research Prize (ANRP) is awarded for recent
> results in applied networking research that are relevant for
> transitioning into shipping Internet products and related
> standardization efforts. Researchers with relevant, recent results are
> encouraged to apply for this prize, which will offer them the
> opportunity to present and discuss their work with the engineers,
> network operators, policy makers and scientists that participate in
> the Internet Engineering Task Force (IETF) and its research arm, the
> Internet Research Task Force (IRTF). Third-party nominations for this
> prize are also encouraged. The goal of the Applied Networking Research
> Prize is to recognize the best new ideas in networking, and bring them
> to the IETF and IRTF especially in cases where they would not
> otherwise see much exposure or discussion.
>=20
> The Applied Networking Research Prize (ANRP) consists of:
>=20
> =E2=80=A2 invited talk at the IRTF Open Meeting
> =E2=80=A2 travel grant to attend a week-long IETF meeting (airfare, =
hotel,
> registration, stipend)
> =E2=80=A2 cash prize of $1000 (USD)
> =E2=80=A2 recognition at the IETF plenary
> =E2=80=A2 invitation to related social activities
> =E2=80=A2 potential for additional travel grants to future IETF =
meetings,
> based on community feedback
>=20
> The Applied Networking Research Prize will be awarded once per
> calendar year. Each year, several winners will be chosen and invited
> to present their work at one of the three IETF meetings during the
> year.
>=20
>=20
> HOW TO NOMINATE
>=20
> Only a single person can be nominated for the award. The basis of the
> nomination is a peer-reviewed, original journal, conference or
> workshop paper they authored, which was recently published or accepted
> for publication. The nominee must be one of the main authors of the
> nominated paper. Both self-nominations (nominating one=E2=80=99s own =
paper)
> and third-party nominations (nominating someone else=E2=80=99s paper) =
are
> encouraged.
>=20
> The nominated paper should provide a scientific foundation for
> possible future IETF engineering work or IRTF research and
> experimentation, analyze the behavior of Internet protocols in
> operational deployments or realistic testbeds, make an important
> contribution to the understanding of Internet scalability,
> performance, reliability, security or capability, or otherwise be of
> relevance to ongoing or future IETF or IRTF activities.
>=20
> Applicants must briefly describe how the nominated paper relates to
> these goals, and are encouraged to describe how a presentation of
> these research results would foster their transition into new IETF
> engineering or IRTF experimentation, or otherwise seed new activities
> that will have an impact on the real-world Internet.
>=20
> The goal of the Applied Networking Research Prize (ANRP) is to foster
> the transitioning of research results into real-world benefits for the
> Internet. Therefore, applicants must indicate that they (or the
> nominee, in case of third-party nominations) are available to attend
> at least one of the year=E2=80=99s IETF meetings in person and in its
> entirety.
>=20
> Nominations must include:
>=20
> =E2=80=A2 the name and email address of the nominee
> =E2=80=A2 a bibliographic reference to the published (or accepted)
> nominated paper
> =E2=80=A2 a PDF copy of the nominated paper
> =E2=80=A2 a statement that describes how the nominated paper fulfills =
the
> goals of the award
> =E2=80=A2 a statement about which of the year=E2=80=99s IETF meetings =
the nominee
> would be available to attend in person and in its entirety
> =E2=80=A2 a brief biography or CV of the nominee
> =E2=80=A2 optionally, any other supporting information (link to =
nominee=E2=80=99s
> web site, etc.)
>=20
> Nominations are submitted via the submission site at
> https://irtf.org/anrp/2018/. In exceptional cases, nominations may =
also
> be submitted by email to anrp@irtf.org.
>=20
>=20
> IMPORTANT DATES
>=20
> Applications close: November 5, 2017 (hard)
> Notifications:      December 7, 2017
>=20
>=20
> SPONSORS
>=20
> The Applied Networking Research Prize (ANRP) is supported by the
> Internet Society (ISOC) in coordination with the Internet Research =
Task Force
> (IRTF).
>=20
>=20
> HELP PUBLICIZE THE ANRP
>=20
> If you would like to help publicize the ANRP within your
> organization, you are welcome to print and use the flyer at
> https://irtf.org/anrp-2018-flyer.pdf
>=20
>=20


From nobody Wed Nov  1 06:27:25 2017
Return-Path: <volz@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 8AC6313F87C; Wed,  1 Nov 2017 06:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 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, 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 SzlW7gHbgUyc; Wed,  1 Nov 2017 06:27:16 -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 D957713942F; Wed,  1 Nov 2017 06:27:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2227; q=dns/txt; s=iport; t=1509542836; x=1510752436; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=FUU2GCXSXhlfDSwfF7kRLUFw4wxQT5goZWOA4I9l0jc=; b=CCwad0F6rYYJ3vJeiJ+0fPRHgYlN5kCynMwl9yV6qN8gEm60KpYJy//k TxFTHP/v6UphElAjv2gTowpHvhVoqOTRiMWjXjnDSpMwLIO9THNpWqNdV NA0qLeAEo76EIAiK286ApT/2WL4dnSssD3kc28vUGxHQ3GpvTJJ8I0q7S I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CcAAB0yvlZ/4gNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzEuZG4nB44VjxiBfJZEghEKGAuFGAKEfD8YAQIBAQEBAQEBayi?= =?us-ascii?q?FHQEBAQQBATg0CwwEAgEIEQQBAR8JBycLFAkIAgQBDQUIAYoaEKpmixABAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEdgy6CB4ZmgyKBSRBIhUQFogoClHGTOZVmAhEZAYE?= =?us-ascii?q?4AR84gWx6FUmCZAmEVncBik2BMgGBEAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.44,327,1505779200"; d="scan'208";a="24666129"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Nov 2017 13:27:15 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id vA1DRFOA023005 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 1 Nov 2017 13:27:15 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 1 Nov 2017 08:27:14 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1320.000; Wed, 1 Nov 2017 08:27:14 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Zhen Cao <zhencao.ietf@gmail.com>, "int-dir@ietf.org" <int-dir@ietf.org>
CC: "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-rfc3315bis.all@ietf.org" <draft-ietf-dhc-rfc3315bis.all@ietf.org>
Subject: RE: [Int-dir] Intdir early review of draft-ietf-dhc-rfc3315bis-10
Thread-Topic: [Int-dir] Intdir early review of draft-ietf-dhc-rfc3315bis-10
Thread-Index: AQHTUuS5t0NJ+fIQ4E2BcQoavKk7AqL/glXQ
Date: Wed, 1 Nov 2017 13:27:14 +0000
Message-ID: <1cfea94b1690409595b243f014083bf1@XCH-ALN-003.cisco.com>
References: <150952203714.25993.17333137226492207681@ietfa.amsl.com>
In-Reply-To: <150952203714.25993.17333137226492207681@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: [161.44.67.109]
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/C-BMplnmK6s74Dm3y5_p7LBJp4Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 13:27:18 -0000

Hi Zhen:

First, thanks for the Int-Dir review.

Regarding your comment, the cases where both MRC and MRD are zero is for a =
Solicit and Information-Request. And, for those particular cases, the clien=
t should probably retransmit "forever" at a hopefully low rate (SOL_MAX_RT =
and INF_MAX_RT are 3600 seconds*) to locate a  DHCP server. This of course =
depends on the RA M & O bits (indicating a DHCP server is available) or the=
 manual configuration of the client (to explicitly run DHCP).

* - RFC 3315 used 120 seconds for these values, but that was updated by RFC=
 7083.

- Bernie

-----Original Message-----
From: Int-dir [mailto:int-dir-bounces@ietf.org] On Behalf Of Zhen Cao
Sent: Wednesday, November 01, 2017 3:41 AM
To: int-dir@ietf.org
Cc: dhcwg@ietf.org; ietf@ietf.org; draft-ietf-dhc-rfc3315bis.all@ietf.org
Subject: [Int-dir] Intdir early review of draft-ietf-dhc-rfc3315bis-10

Reviewer: Zhen Cao
Review result: Ready with Issues

I am an assigned INT directorate reviewer for this draft. These comments we=
re written primarily for the benefit of the Internet Area Directors. Docume=
nt editors and shepherds should treat these comments just like they would t=
reat comments from any other IETF contributors and resolve them along with =
any other Last Call comments that have been received. For more details of t=
he INT directorate, see <http://www.ietf.org/iesg/directorate.html>.

This version is quite ready to go, with a small issue that I would like to
discussion:

In Section. 15 (Reliability of Client Initiated Message Exchanges), I stron=
gly recommend that implementation MUST NOT set both MRC or MRD to ZERO, whi=
ch attaches a possible risk that the client continues to send this message =
without
a stop.    So I would like to propose the following change:

s/
" If both MRC and MRD are zero, the client continues to transmit the
   message until it receives a response."
/
"The client must be informed with a limit of its retransmission behavior, a=
nd MUST NOT set both MRC and MRD to zero"

-zhen


_______________________________________________
Int-dir mailing list
Int-dir@ietf.org
https://www.ietf.org/mailman/listinfo/int-dir


From nobody Wed Nov  1 09:17:10 2017
Return-Path: <mfidelman@meetinghouse.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 B3D0F13FE57 for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 09:17: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEfKztyHaXFV for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 09:17:07 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id B100E13FE7F for <ietf@ietf.org>; Wed,  1 Nov 2017 09:14:45 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id A9459CC04B for <ietf@ietf.org>; Wed,  1 Nov 2017 12:14:44 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UwJwQRfi8hs8 for <ietf@ietf.org>; Wed,  1 Nov 2017 12:14:43 -0400 (EDT)
Received: from Miless-MBP.fios-router.home (pool-100-0-27-219.bstnma.fios.verizon.net [100.0.27.219]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 861CECC044 for <ietf@ietf.org>; Wed,  1 Nov 2017 12:14:43 -0400 (EDT)
Subject: Re: letting IETF build on top of Open Source technology
To: ietf@ietf.org
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <E6ED7F15-8855-45B6-A42E-707E32966CFA@network-heretics.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <5f97884c-9af4-6496-54a6-93cfac7a6705@meetinghouse.net>
Date: Wed, 1 Nov 2017 12:14:42 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <E6ED7F15-8855-45B6-A42E-707E32966CFA@network-heretics.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k5wvIvRky9o7fNgzB37FVJ3dIhw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 16:17:09 -0000

Let us not forget that a number of significant Internet protocols are 
based on open-source work (though not always called that).

We can start with the early TCP/IP reference implementations.  And then 
there's the web - HTTP pretty much co-evolved with early browsers & daemons.

Isn't the issue more one of underlying design philosophy & intent?  
Which comes first - the architecture & the protocol or the software?

Personally, I don't think it's an issue of the IETF "building on top of 
Open Source technology," it's a matter of educating developers to think 
in terms of protocol architectures & standards. (Something that I think 
we, as network & protocol developers have woefully failed to do - and 
that our professional organizations, like ISOC, should be doing more of.)

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Wed Nov  1 09:33:19 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 547E213F7B9 for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 09:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juAOnuPsHqZX for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 09:33:15 -0700 (PDT)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::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 E08AF13F7A3 for <ietf@ietf.org>; Wed,  1 Nov 2017 09:33:14 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id z55so2440460wrz.1 for <ietf@ietf.org>; Wed, 01 Nov 2017 09:33:14 -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=mJmBQ7j2vb4iLGelyXOegmz3FGjDv0lxRcWbvev4qSQ=; b=PnOCHX057iu04l22guzKA+UKqsQAk3bcc1DgENCjxzda0wk+GVcfws5cJodrF3ivga 49ZGEQoxcE1u1hjR3Zw1DQ57BYtgNfrOgz0gpzpLhIglxbgOCYYW1LSgKccaWLQKx+bL AbpSfqTEB7jZR9gQnXUPa5cHB+dGHoToo/98bpysIGVBGSL9wlLVEMgs38qunqP6ehHc rNo2wfOfFWsXqQ/bYJaoX54DLC8+XN8Rgl9n6QTkHepm4jHNb3dbzGx22HURbL5w6If1 td0RKYgz0/54khqAwHZ5p1gOmQFYky9w7A+AMUxjPacjjpOSMHMYwbkYmwRBKA3CfZBN Hsig==
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=mJmBQ7j2vb4iLGelyXOegmz3FGjDv0lxRcWbvev4qSQ=; b=IDRg6zgYAc5G/tp+BSJPENKqygF///U/JCPqFordNmW7rBHdNjFs70WV/ZEm/hF/ri r7NAyXbyFNBOyCBShity8bUndoYhFWs/8SJB2R3212qZf7Ug4DGhMgpXo9wCvo19BVsb 2lCNpVw7uirSR6YvHThYTE1ln/26+Hqm35n64w933xH1CPlMcbVD3s/NQMAlAd7TVEnr B/8t6UyLnPUFTjeC4b7fIYJIvTsiU/NVE344DfXd9qDIxbBXSa2sKRGgaV79kq4uXyvV 8jCpJarPd9FXGeKhbC3N4XXsSRx1TfOVugfN3dXiLNGMOOZLoMKWfBIGB48fYTRyuTwq Ao3g==
X-Gm-Message-State: AMCzsaX+uO7AmHJqVqINnAtayBgC8fnfie5NRvzKxGsJUF8C9RciNGrx o8QM+MIltPe+C13fAFPPYQKbKub202+/KqvcNO0=
X-Google-Smtp-Source: ABhQp+Tf4VdHGHovVinpECxazlZBN4Zsz4qo/hwZgl0PXsCm2yElfqFBBhUoLK8S775xeGMzJmE5nTibtdjEtT/1LsI=
X-Received: by 10.223.151.51 with SMTP id r48mr336830wrb.164.1509553993293; Wed, 01 Nov 2017 09:33:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.177.221 with HTTP; Wed, 1 Nov 2017 09:33:12 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <CAG4d1reoiMjiuY6m6fHj3QyZf5jF-4aZh4r+CK4fTg8kOWx-Jw@mail.gmail.com>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <CABkgnnWzJr_n4qLnJsu=mvBLjHwCH2LdbbjNGENaavVX357NpQ@mail.gmail.com> <CAG4d1regBTXfK798D0_hunWbC5beiWFsN_uR2q3vWyhwcmZ6vA@mail.gmail.com> <CABkgnnUoBBdUBiFMzD964eSpDkouaNSfUhvCKnBkSg87me9EFQ@mail.gmail.com> <79eaeafe-a35d-8342-4b6a-7413b4309ed9@gmail.com> <023a01d35262$1ee47e40$5cad7ac0$@gmail.com> <CAG4d1rfQvVjyd_cTj3V5jEqceiq1GZLPWO9gQfFdg89iAheZMQ@mail.gmail.com> <027c01d3526b$b6bcef50$2436cdf0$@gmail.com> <CAG4d1reoiMjiuY6m6fHj3QyZf5jF-4aZh4r+CK4fTg8kOWx-Jw@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Wed, 1 Nov 2017 11:33:12 -0500
Message-ID: <CAC8QAcc5H21xKtEoBB4f3jv03JUUHxRvUxxRga=MshEisucpeg@mail.gmail.com>
Subject: Re: letting IETF build on top of Open Source technology
To: Alia Atlas <akatlas@gmail.com>
Cc: Mehmet Ersue <mersue@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f4fde8a2602055cee6d9f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/V3yvuVY-Jl8LNcEBIqnpZNBCqyM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 16:33:17 -0000

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

Hi Alia,

One member mentioned that the open source code does serve as the protocol
description and hence it could be referenced as dependency in RFCs.
I think we should question that.

I worked many years on formal description techniques for protocols. I think
that such specs could serve as a reference.
Source code in some specific programming language is very long and
difficult to follow for someone interested in a high level view of the
protocol.
Also many people do not know the specific programming language it was
written.

My 2 cents.

Regards,
Behcet

On Tue, Oct 31, 2017 at 1:29 PM, Alia Atlas <akatlas@gmail.com> wrote:

> Hi Mehemet:
>
> below in-line
>
> On Tue, Oct 31, 2017 at 1:14 PM, Mehmet Ersue <mersue@gmail.com> wrote:
>
>> See ME:
>>
>>
>>
>> Thanks,
>>
>> Mehmet
>>
>>
>>
>> *From:* Alia Atlas [mailto:akatlas@gmail.com]
>> *Sent:* Tuesday, October 31, 2017 5:13 PM
>> *To:* Mehmet Ersue <mersue@gmail.com>
>> *Cc:* Brian E Carpenter <brian.e.carpenter@gmail.com>; Martin Thomson <
>> martin.thomson@gmail.com>; IETF Discussion Mailing List <ietf@ietf.org>
>> *Subject:* Re: letting IETF build on top of Open Source technology
>>
>>
>>
>> Hi Mehmet,
>>
>>
>>
>> On Tue, Oct 31, 2017 at 12:05 PM, Mehmet Ersue <mersue@gmail.com> wrote:
>>
>> Hi Alia,
>>
>> > >  1.  Is it stable, mature, and immutable (except for errata)?
>> >
>> > Those are not well known characteristics of open source projects.
>> > Even if we tie a reference down to a very specific version, I'm unclea=
r
>> how
>> > that can truly act as a stable reference. It may be stable in a
>> mathematical
>> > sense, but it may also be seven years behind deployed reality.
>>
>> I agree with Brian. There are different type of non-SDO organizations
>> having documents with diverse maturity levels and stability. Many of the=
m
>> don't qualify as normative references.
>>
>>
>>
>> Of course - and that's why it is necessary for the item to meet the
>> questions posed in the draft - which are the requirements (and we'll
>> rephrase more clearly as Russ suggested).
>>
>>
>>
>> Obvious examples for normative references are usually from well-known
>> SDOs like IEEE or W3C where the new standard-track RFC uses it as its ba=
sis
>> or builds on-top of it (e.g.  [W3C.REC-xml-20001006])
>>
>> I also don't see an issue with MD5 and HMAC as these are Informational
>> RFCs at IETF with a well-known stability.
>>
>>
>>
>> Sure - and that was one of the motivations for RFC 3967.
>>
>>
>>
>> Looking at section 1.1. of RFC 3967 and the statement: "a normative
>> reference specifies a document that must be read to fully understand or
>> implement the subject matter in the new RFC, or whose contents are
>> effectively part of the new RFC, as its omission would leave the new RFC
>> incompletely specified",
>> can you please give examples of external documents from non-DOSs, which
>> clearly qualify as normative references for a standard-track RFC at IETF=
?
>> I think primarily on non-SDO documents where the new RFC would build
>> on-top of it.
>>
>>
>>
>> An example would be potentially thrift, I think, for protocol encodings.
>> I have to hunt down the detailed reference for it.
>>
>> I know that protobufs have good documentation also.  I am sure that ther=
e
>> are others and would be happy to hear folks chime in with more.
>>
>>
>>
>> It's unclear whether there is a set of requirements acceptable to the
>> IETF Community that would work for WHATWG work.
>>
>>
>>
>> Is your concern that you don't see useful open source work that would be
>> suitable to reference? Or that none would meet our set of requirements?
>>
>> Or that it is risky to consider referencing non-SDO external work?
>>
>>
>>
>> ME: Generally I don=E2=80=99t see an issue with referencing useful open =
source
>> work. Though only in rare cases an IETF RFC has a dependency on or build=
s
>> indeed on-top of such a document normatively. I think the main criteria =
for
>> a normative reference is still based on the quoted text from RFC 3967 ab=
ove.
>>
>>
>
> [Alia] Agreed - and I pulled the requirements around stability, maturity,
> confidentiality, and IPR considerations largely from 2026.
> My question is whether it is rare than an IETF RFC builds on top of open
> source work because the path to do so is seen as too
> challenging/long/expensive or simply not relevant. This draft is proposin=
g
> a policy assuming the former applies at least some of the time.
>
>
>> I believe use cases and examples will help to define concrete
>> requirements.
>>
>> Once we have the requirements together such documents need to be looked
>> at in a case by case basis and taken over into a registry.
>>
>
> The requirements, I think, stem from our (the IETF community's)
> understanding of what is necessary for a dependency of a standards-track
> RFC and I am not proposing that those should change.  I'm trying to captu=
re
> what they are and how to evaluate a piece of work.
>
> Rather than looking at the set of documents and creating a registry, the
> draft suggests that when a WG wants to use such an item as a dependency,
> then after that use has IESG Approval, then the item can be added to a
> registry - so other WGs and other documents in that WG can benefit from t=
he
> evaluation that was done and feel more confident about using it.
>
> Regards,
> Alia
>
>
>> Regards,
>>
>> Alia
>>
>>
>>
>>
>>
>> Thanks,
>> Mehmet
>>
>>
>> > -----Original Message-----
>> > From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Brian E
>> Carpenter
>> > Sent: Monday, October 30, 2017 4:49 AM
>> > To: Martin Thomson <martin.thomson@gmail.com>; Alia Atlas
>> > <akatlas@gmail.com>
>> > Cc: IETF Discussion Mailing List <ietf@ietf.org>
>> > Subject: Re: letting IETF build on top of Open Source technology
>> >
>> > On 30/10/2017 16:27, Martin Thomson wrote:
>> > > On Mon, Oct 30, 2017 at 2:18 PM, Alia Atlas <akatlas@gmail.com>
>> wrote:
>> > >> The existing downref process (RFC 3967) doesn't apply. That is to
>> > >> handle references to an RFC that is at a lower maturity - such as a
>> > >> normative reference to an Informational or Experimental RFC - or fr=
om
>> > >> an Internet Standard to a Proposed Standard.
>> > >
>> > > I couldn't find anything in 3967 to support that view (other than th=
e
>> > > parenthetical in the abstract).  Maybe it's implicit.
>> >
>> > The quote from RFC2026 in section 1 of RFC3967 is pretty unambiguous
>> when
>> > read in context - throughout RFC2026, "standards track" refers to the
>> IETF
>> > standards track, and "standards track specifications"
>> > refers to IETF documents. And in any case the Abstract of RFC3967 sets
>> the
>> > scope thus: "Exceptions to this rule are sometimes needed as the IETF
>> uses
>> > informational RFCs to describe non-IETF standards or IETF-specific
>> modes of
>> > use of such standards."
>> >
>> > My main concern with the new proposal is other:
>> >
>> > >  1.  Is it stable, mature, and immutable (except for errata)?
>> >
>> > Those are not well known characteristics of open source projects.
>> > Even if we tie a reference down to a very specific version, I'm unclea=
r
>> how
>> > that can truly act as a stable reference. It may be stable in a
>> mathematical
>> > sense, but it may also be seven years behind deployed reality.
>> >
>> >     Brian
>>
>>
>>
>
>

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

<div dir=3D"ltr"><div><div><div><div><div><div><div><div>Hi Alia,<br><br></=
div>One member mentioned that the open source code does serve as the protoc=
ol description and hence it could be referenced as dependency in RFCs.<br><=
/div>I think we should question that.<br><br></div>I worked many years on f=
ormal description techniques for protocols. I think that such specs could s=
erve as a reference.<br></div>Source code in some specific programming lang=
uage is very long and difficult to follow for someone interested in a high =
level view of the protocol.<br></div>Also many people do not know the speci=
fic programming language it was written.<br><br></div>My 2 cents.<br><br></=
div>Regards,<br></div>Behcet<br></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Tue, Oct 31, 2017 at 1:29 PM, Alia Atlas <span dir=
=3D"ltr">&lt;<a href=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas=
@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"><div dir=
=3D"ltr">Hi Mehemet:<div><br></div><div>below in-line=C2=A0</div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote"><div><div class=3D"h5">On T=
ue, Oct 31, 2017 at 1:14 PM, Mehmet Ersue <span dir=3D"ltr">&lt;<a href=3D"=
mailto:mersue@gmail.com" target=3D"_blank">mersue@gmail.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple=
" lang=3D"EN-US"><div class=3D"m_5438088832007708087m_-2988931429681717626W=
ordSection1"><p class=3D"MsoNormal"><span style=3D"color:#0000cc">See ME:<u=
></u><u></u></span></p><p class=3D"MsoNormal"><span style=3D"color:#0000cc"=
><u></u>=C2=A0<u></u></span></p><p class=3D"MsoNormal"><span style=3D"color=
:#0000cc">Thanks,<u></u><u></u></span></p><p class=3D"MsoNormal"><span styl=
e=3D"color:#0000cc">Mehmet<u></u><u></u></span></p><p class=3D"MsoNormal"><=
span style=3D"color:#0000cc"><u></u>=C2=A0<u></u></span></p><div style=3D"b=
order:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><di=
v style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0cm 0cm=
 0cm"><p class=3D"MsoNormal"><b>From:</b> Alia Atlas [mailto:<a href=3D"mai=
lto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail.com</a>] <br><b>Sent=
:</b> Tuesday, October 31, 2017 5:13 PM<br><b>To:</b> Mehmet Ersue &lt;<a h=
ref=3D"mailto:mersue@gmail.com" target=3D"_blank">mersue@gmail.com</a>&gt;<=
br><b>Cc:</b> Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gma=
il.com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;; Martin Thoms=
on &lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin=
.thomson@gmail.com</a>&gt;; IETF Discussion Mailing List &lt;<a href=3D"mai=
lto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt;<span><br><b>Subj=
ect:</b> Re: letting IETF build on top of Open Source technology<u></u><u><=
/u></span></p></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><d=
iv><p class=3D"MsoNormal">Hi Mehmet,<u></u><u></u></p><div><p class=3D"MsoN=
ormal"><u></u>=C2=A0<u></u></p><div><span><p class=3D"MsoNormal">On Tue, Oc=
t 31, 2017 at 12:05 PM, Mehmet Ersue &lt;<a href=3D"mailto:mersue@gmail.com=
" target=3D"_blank">mersue@gmail.com</a>&gt; wrote:<u></u><u></u></p><block=
quote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm =
0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom=
:5.0pt"><p class=3D"MsoNormal">Hi Alia,<br><br>&gt; &gt;=C2=A0 1.=C2=A0 Is =
it stable, mature, and immutable (except for errata)?<br>&gt;<br>&gt; Those=
 are not well known characteristics of open source projects.<br>&gt; Even i=
f we tie a reference down to a very specific version, I&#39;m unclear how<b=
r>&gt; that can truly act as a stable reference. It may be stable in a math=
ematical<br>&gt; sense, but it may also be seven years behind deployed real=
ity.<br><br>I agree with Brian. There are different type of non-SDO organiz=
ations having documents with diverse maturity levels and stability. Many of=
 them don&#39;t qualify as normative references.<u></u><u></u></p></blockqu=
ote><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p class=
=3D"MsoNormal">Of course - and that&#39;s why it is necessary for the item =
to meet the questions posed in the draft - which are the requirements (and =
we&#39;ll rephrase more clearly as Russ suggested).=C2=A0<u></u><u></u></p>=
</div><div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p></div><blockquote=
 style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6=
.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0p=
t"><p class=3D"MsoNormal">Obvious examples for normative references are usu=
ally from well-known SDOs like IEEE or W3C where the new standard-track RFC=
 uses it as its basis or builds on-top of it (e.g.=C2=A0 [W3C.REC-xml-20001=
006])<br><br>I also don&#39;t see an issue with MD5 and HMAC as these are I=
nformational RFCs at IETF with a well-known stability.<u></u><u></u></p></b=
lockquote><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p=
 class=3D"MsoNormal">Sure - and that was one of the motivations for RFC 396=
7.<u></u><u></u></p></div><div><p class=3D"MsoNormal">=C2=A0<u></u><u></u><=
/p></div><blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;p=
adding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0c=
m;margin-bottom:5.0pt"><p class=3D"MsoNormal">Looking at section 1.1. of RF=
C 3967 and the statement: &quot;a normative reference specifies a document =
that must be read to fully understand or implement the subject matter in th=
e new RFC, or whose contents are effectively part of the new RFC, as its om=
ission would leave the new RFC incompletely specified&quot;,<br>can you ple=
ase give examples of external documents from non-DOSs, which clearly qualif=
y as normative references for a standard-track RFC at IETF?<br>I think prim=
arily on non-SDO documents where the new RFC would build on-top of it.<u></=
u><u></u></p></blockquote><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u><=
/p></div><div><p class=3D"MsoNormal">An example would be potentially thrift=
, I think, for protocol encodings. I have to hunt down the detailed referen=
ce for it.<u></u><u></u></p></div><div><p class=3D"MsoNormal">I know that p=
rotobufs have good documentation also.=C2=A0 I am sure that there are other=
s and would be happy to hear folks chime in with more.<u></u><u></u></p></d=
iv><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p class=
=3D"MsoNormal">It&#39;s unclear whether there is a set of requirements acce=
ptable to the IETF Community that would work for WHATWG work.<u></u><u></u>=
</p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div><div><p=
 class=3D"MsoNormal">Is your concern that you don&#39;t see useful open sou=
rce work that would be suitable to reference? Or that none would meet our s=
et of requirements?<u></u><u></u></p></div><div><p class=3D"MsoNormal">Or t=
hat it is risky to consider referencing non-SDO external work?<u></u><u></u=
></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></span><div><p cl=
ass=3D"MsoNormal"><span style=3D"color:#0070c0">ME: Generally I don=E2=80=
=99t see an issue with referencing useful open source work. Though only in =
rare cases an IETF RFC has a dependency on or builds indeed on-top of such =
a document normatively. I think the main criteria for a normative reference=
 is still based on the quoted text from RFC 3967 above.</span><span style=
=3D"color:rgb(0,112,192)">=C2=A0</span></p></div></div></div></div></div></=
div></div></blockquote><div><br></div></div></div><div>[Alia] Agreed - and =
I pulled the requirements around stability, maturity, confidentiality, and =
IPR considerations largely from 2026.</div><div>My question is whether it i=
s rare than an IETF RFC builds on top of open source work because the path =
to do so is seen as too challenging/long/expensive or simply not relevant. =
This draft is proposing a policy assuming the former applies at least some =
of the time.</div><span class=3D""><div>=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div class=3D"m_=
5438088832007708087m_-2988931429681717626WordSection1"><div style=3D"border=
:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><p class=3D"M=
soNormal"><span style=3D"color:#0070c0"><u></u></span></p><p class=3D"MsoNo=
rmal"><span style=3D"color:#0070c0">I believe use cases and examples will h=
elp to define concrete requirements.<u></u><u></u></span></p><p class=3D"Ms=
oNormal"><span style=3D"color:#0070c0">Once we have the requirements togeth=
er such documents need to be looked at in a case by case basis and taken ov=
er into a registry.</span></p></div></div></div></blockquote><div><br></div=
></span><div>The requirements, I think, stem from our (the IETF community&#=
39;s) understanding of what is necessary for a dependency of a standards-tr=
ack RFC and I am not proposing that those should change.=C2=A0 I&#39;m tryi=
ng to capture what they are and how to evaluate a piece of work.</div><div>=
<br></div><div>Rather than looking at the set of documents and creating a r=
egistry, the draft suggests that when a WG wants to use such an item as a d=
ependency, then after that use has IESG Approval, then the item can be adde=
d to a registry - so other WGs and other documents in that WG can benefit f=
rom the evaluation that was done and feel more confident about using it.</d=
iv><div><br></div><div>Regards,</div><div>Alia</div><div><div class=3D"h5">=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D=
"purple" lang=3D"EN-US"><div class=3D"m_5438088832007708087m_-2988931429681=
717626WordSection1"><div style=3D"border:none;border-left:solid blue 1.5pt;=
padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p class=3D"MsoNormal"><u></=
u></p></div><div><div class=3D"m_5438088832007708087h5"><div><p class=3D"Ms=
oNormal">Regards,<u></u><u></u></p></div><div><p class=3D"MsoNormal">Alia<u=
></u><u></u></p></div><div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><=
/div><div><p class=3D"MsoNormal">=C2=A0<u></u><u></u></p></div><blockquote =
style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.=
0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt=
"><p class=3D"MsoNormal">Thanks,<br>Mehmet<u></u><u></u></p><div><div><p cl=
ass=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>&gt; -----Original Mes=
sage-----<br>&gt; From: ietf [mailto:<a href=3D"mailto:ietf-bounces@ietf.or=
g" target=3D"_blank">ietf-bounces@ietf.org</a>] On Behalf Of Brian E Carpen=
ter<br>&gt; Sent: Monday, October 30, 2017 4:49 AM<br>&gt; To: Martin Thoms=
on &lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin=
.thomson@gmail.com</a>&gt;; Alia Atlas<br>&gt; &lt;<a href=3D"mailto:akatla=
s@gmail.com" target=3D"_blank">akatlas@gmail.com</a>&gt;<br>&gt; Cc: IETF D=
iscussion Mailing List &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blan=
k">ietf@ietf.org</a>&gt;<br>&gt; Subject: Re: letting IETF build on top of =
Open Source technology<br>&gt;<br>&gt; On 30/10/2017 16:27, Martin Thomson =
wrote:<br>&gt; &gt; On Mon, Oct 30, 2017 at 2:18 PM, Alia Atlas &lt;<a href=
=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail.com</a>&gt; w=
rote:<br>&gt; &gt;&gt; The existing downref process (RFC 3967) doesn&#39;t =
apply. That is to<br>&gt; &gt;&gt; handle references to an RFC that is at a=
 lower maturity - such as a<br>&gt; &gt;&gt; normative reference to an Info=
rmational or Experimental RFC - or from<br>&gt; &gt;&gt; an Internet Standa=
rd to a Proposed Standard.<br>&gt; &gt;<br>&gt; &gt; I couldn&#39;t find an=
ything in 3967 to support that view (other than the<br>&gt; &gt; parentheti=
cal in the abstract).=C2=A0 Maybe it&#39;s implicit.<br>&gt;<br>&gt; The qu=
ote from RFC2026 in section 1 of RFC3967 is pretty unambiguous when<br>&gt;=
 read in context - throughout RFC2026, &quot;standards track&quot; refers t=
o the IETF<br>&gt; standards track, and &quot;standards track specification=
s&quot;<br>&gt; refers to IETF documents. And in any case the Abstract of R=
FC3967 sets the<br>&gt; scope thus: &quot;Exceptions to this rule are somet=
imes needed as the IETF uses<br>&gt; informational RFCs to describe non-IET=
F standards or IETF-specific modes of<br>&gt; use of such standards.&quot;<=
br>&gt;<br>&gt; My main concern with the new proposal is other:<br>&gt;<br>=
&gt; &gt;=C2=A0 1.=C2=A0 Is it stable, mature, and immutable (except for er=
rata)?<br>&gt;<br>&gt; Those are not well known characteristics of open sou=
rce projects.<br>&gt; Even if we tie a reference down to a very specific ve=
rsion, I&#39;m unclear how<br>&gt; that can truly act as a stable reference=
. It may be stable in a mathematical<br>&gt; sense, but it may also be seve=
n years behind deployed reality.<br>&gt;<br>&gt;=C2=A0 =C2=A0 =C2=A0Brian<b=
r><br><u></u><u></u></p></div></div></blockquote></div></div></div><p class=
=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></div></div></div></div></bloc=
kquote></div></div></div><br></div></div>
</blockquote></div><br></div>

--f403045f4fde8a2602055cee6d9f--


From nobody Wed Nov  1 09:52:17 2017
Return-Path: <ott@in.tum.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 0180413F662; Wed,  1 Nov 2017 09:52:16 -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 qyBTqDMHKLJW; Wed,  1 Nov 2017 09:52:14 -0700 (PDT)
Received: from mail-out1.informatik.tu-muenchen.de (mail-out1.informatik.tu-muenchen.de [131.159.0.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7424713F839; Wed,  1 Nov 2017 09:52:12 -0700 (PDT)
Received: by mail.in.tum.de (Postfix, from userid 107) id 9E2F11C2A1E; Wed,  1 Nov 2017 17:52:10 +0100 (CET)
Received: (Authenticated sender: ott) by mail.in.tum.de (Postfix) with ESMTPSA id 747FB1C1350; Wed,  1 Nov 2017 17:52:06 +0100 (CET) (Extended-Queue-bit tech_aqhjx@fff.in.tum.de)
From: Joerg Ott <ott@in.tum.de>
Subject: TSV-ART review of draft-ietf-dhc-relay-port-06
To: draft-ietf-dhc-relay-port@tools.ietf.org, tsv-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, dhcwg@ietf.org
Message-ID: <28cf5d0f-091c-c917-a6ea-06a2262cd7fc@in.tum.de>
Date: Wed, 1 Nov 2017 17:52:06 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
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/MLqfdatWpTTTHnRiiDc5Iyk1FiE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 16:52:16 -0000

Hi,

I’ve reviewed this document as part of the transport area review team'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.

Jörg


Summary:
This draft is essentially ready.  I do not see any transport-specific
issues.

Comments:
It seems that in a few places, the document does not use RFC 2119
keywords where they could/should be used.  For example, in the
introduction paragraph to section 4 and in section 5.2 (right after the
enumeration).  Not sure if the non-use was intentional or an oversight.

Nit:
p.3: This is a standards track document, so the language could be
stronger.

OLD:
This document proposes an extension to relax the fixed UDP source

NEW:
This document defines an extension to relax the fixed UDP source




From nobody Wed Nov  1 10:22:10 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 8AA1013F9AA; Wed,  1 Nov 2017 10:21:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 FDvC12faLQUP; Wed,  1 Nov 2017 10:21:51 -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 4905C13F991; Wed,  1 Nov 2017 10:21:51 -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 5560358C4F6; Wed,  1 Nov 2017 18:21:46 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 405ABB0D054; Wed,  1 Nov 2017 18:21:46 +0100 (CET)
Date: Wed, 1 Nov 2017 18:21:46 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Christian Huitema <huitema@huitema.net>
Cc: Padma Pillay-Esnault <padma.ietf@gmail.com>, "ideas@ietf.org" <ideas@ietf.org>, "lisp@ietf.org list" <lisp@ietf.org>, Dino Farinacci <farinacci@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Ideas] [lisp]  WG Review: IDentity Enabled Networks (ideas)
Message-ID: <20171101172146.GA12437@faui40p.informatik.uni-erlangen.de>
References: <CALx6S370-TuoUicWep5vV2NjLPS4d-HP1qVxW_nGrxhBLw6Eug@mail.gmail.com> <8kd5pq.oxb4pv.rtlo8t-qmf@mercury.scss.tcd.ie> <644DA50AFA8C314EA9BDDAC83BD38A2E0EAA7204@sjceml521-mbx.china.huawei.com> <dd2c3bd5-dd37-109b-2e81-0327db4daa09@cs.tcd.ie> <0BA14206-DC82-49EF-A625-B2425FA396F6@gmail.com> <1f254140-1340-6c7d-9c73-e7137562c685@gmail.com> <fa644cc2-161f-8884-3445-2b50d2c2ad23@htt-consult.com> <cf2ca920-f2d2-b65e-05eb-ebe3c30b76d1@huitema.net> <CAG-CQxrdS9L+2+bN=1NcPGuztn4U4OwSWUiNaVcS9Bsm2mtpfA@mail.gmail.com> <b18459d1-7ce1-b83d-787d-9066267d584b@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b18459d1-7ce1-b83d-787d-9066267d584b@huitema.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/anHReSuj0UjN8H9R-m3fnLN2rFo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 17:21:55 -0000

On Wed, Oct 11, 2017 at 12:34:19PM -0700, Christian Huitema wrote:
> Some thing you should be hearing is that "long term identity of device"
> has almost the same privacy properties as "long term identity of the
> device's owner". You may think that identifying a random piece of
> hardware is no big deal, but it turns out that the network activity and
> network locations of that piece of hardware can be associated to those
> of its human owner. So you need the same kind of protection for these
> device identifiers as for human identifiers.

Sure, but i don't think it can be generalized:

There will be more and more non-individually owned nodes in public and
corporate infrastructures where requirements will be quite different
from those derived from individual human privacy.

If lets say those long term identifiers do not provide good human
privacy protection but good communications security properties and
managed transpacency for regulators then they could still be a great
benefit for those class of nodes.

[rant]

Trying to get more privacy into network layer is like making
tobacco more organic. You can get buried in the organic section
of the graveyard after you die of lung cancer. Great success!

Aka: Where is the IETF on any warnings, architectures or recommendations
on the actual application layer:

"Inhaling of this web page / IoT device will expose your personal
 activities related to it, social security number and credit card
 information to a "trusted set" of 1000 collaborating web services
 companies of which 10 at least have already been fined several times
 for leaking your information - and then made even more money out of it"

(sorry, just can't get beyond the fact that equifax is not making
 money out of their leakage...)

Should come with every mayor web page and IoT device.

[/rant]

Venting aside, i'd actually love to understand better if/what IETF
does for privacy inside eg: a TLS payload, besides sipbrandy/dprive/perc ?

Cheers
    Toerless

> -- 
> Christian Huitema
> 

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


From nobody Wed Nov  1 11:14:55 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 815E613FE60 for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 11:14:53 -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.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 dBxLL_kHGUuP for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 11:14:52 -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 EA0A813F3FE for <ietf@ietf.org>; Wed,  1 Nov 2017 11:14:51 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id m198so5822055oig.5 for <ietf@ietf.org>; Wed, 01 Nov 2017 11:14:51 -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=abOQTea5Qv/9+B4WEr1zj3khX+9SqxH7mV9MNphqxnc=; b=BF1Z2M7oNL7PMan0mn1jELZ7o4mBP7M1wejIY3aKzKcyCjzD6d+qbOurRKA6gpiDvv xEhPnGsD5XhEFo4vjp7q6WAhlfb2z/+jOSknNB3x1+i16PxrbLntzYffiHwzX+IH5vKJ eWC4VD/R552HNlQxjPPDRfnVGeO8Wt2F2sCRfraOZbKBZStywV+bvMa+7EqSsXV6jvV/ H8o1jhR3OWno3SCsqbMTKtFsEpuJdcQLq1LL7jdxIREYUqexjoTEfE9s8NaYRlk5cMcC awWPAJ3ZYXlOqPDb8Pmws01hxHpVUZzO3w63tO80bWIryeXGdxl4t0QxE7yAZYxzJbad 3PWQ==
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=abOQTea5Qv/9+B4WEr1zj3khX+9SqxH7mV9MNphqxnc=; b=q9BUvVlAMScFFtfECT71wtzqktFm43x76L6hIPIuupKOybKbTrbUTxrQLkxaEhCj2G imUkRBXdNQrFKACSGDqXyb1590yX2LmFgvUPgSNEC8rSFQp0BQpzm2pB25IScQ+A2I6A L5j+NeTUdFIlQMy8rrpxFCR7Ty7C6H+yfalKwzlDbgiFYSWgLFQFqdPh2+IgdFdXhMhl h4b23xQDW1KDMae3TjjfKBPHxtpByhULRQRcQ2rZ3P++z+z+J9ORiOVgIRNH3hnh1vQB NWtuP1y0Lw/n6sPt+deqtIcXRHN9jN8meZv3I6hNGNnoIngXCN4QqGTXNMh61NoW5EjF J7Sg==
X-Gm-Message-State: AMCzsaXXG5lEh2yNKvcQA2i12nXeV4R5Jz3/tAlHWQEUeneJ9eESiLAH bb9TR+YXeXja6mZis6bmtwadsChD24PUwNS8Z3o=
X-Google-Smtp-Source: ABhQp+QWGFN3t/c5eQJSR3v5Pqf+DFPKgMnW2zLjRWFD/VAEF0F62NDLqLux5zwHOpmcGfwwC0qE+DSoDx3j2bQ0QnU=
X-Received: by 10.202.172.85 with SMTP id v82mr414169oie.432.1509560091134; Wed, 01 Nov 2017 11:14:51 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.80.42 with HTTP; Wed, 1 Nov 2017 11:14:49 -0700 (PDT)
In-Reply-To: <0997d8de-bf01-f9f5-fc32-031ad44402f0@google.com>
References: <20171029003141.27C58CC43B@server1.neighborhoods.net> <AB7003B1-6F78-444F-9852-DF5B46A6C542@shockey.us> <CAMm+LwgDcsUF=QXuM0xgMP=1brSGzwn-g_g+25ViA79SHWFktw@mail.gmail.com> <0997d8de-bf01-f9f5-fc32-031ad44402f0@google.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 1 Nov 2017 14:14:49 -0400
X-Google-Sender-Auth: b1xknbuF2_nqhHeEd9B-NotTwNM
Message-ID: <CAMm+Lwi8iiZVCiZ12RmYGCBHUzvAjBTs6a7pahRcF3oVD0tkLQ@mail.gmail.com>
Subject: Re: Proposal to revise ISOC's mission statement
To: james woodyatt <jhw@google.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P7hXcJSPAZQUNnB5pfs8BtZeKUE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 18:14:53 -0000

On Tue, Oct 31, 2017 at 5:44 PM, james woodyatt <jhw@google.com> wrote:
> On 10/31/2017 05:20 AM, Phillip Hallam-Baker wrote:
>>
>> [...] it is the casual negligence many of the technologists show when it
>> comes to security risks.
>>
>> The question I see is who is going to be in control. Will it be the user
>> or someone else.
>> [...]
>
> I think you've already answer that question for yourself in the excerpt
> below.
>
>> We have to have a plan to make the Internet safe for users, yes. But what
>> we also need at this point is a plan to protect society from the Internet
>> itself. [...]
>
> According to that view, it will be someone else, unless "our" plan to
> protect "society" from the criminal users of the Internet is adequate.
>
> Absolutely speaking *only* for myself here, but I view talking about plans
> "to protect society from the Internet itself" like a pretty much straight up
> attack on the fundamental idea of an Internet Society as a thing worthy of
> that name.

Not at all. Much of the problem of 'Internet crime' has nothing to do
with the Internet.

Until 1995, almost no critical infrastructures were designed with the
expectation that they would be connected to a global network and need
a security model to meet that attack model. The principle exception
being the Internet which very few people understood to be critical.

Phishing is not a problem of Internet insecurity, the fundamental
security problem is that the credit card security model is based on a
password printed on the front of every card.

Advance fee fraud is not a problem of Internet security, it is
primarily a problem caused by unscrupulous people being able to
efficiently contact hundreds millions of people and then deceive a
small fraction (less than 0.1%) whose behavior is frequently explained
by dementia.

The fact that we now have SCADA attacks on a regular basis is not a
problem of Internet security, it is primarily caused by the fact that
the protocols they use today were designed 40 years ago and have no
inbuilt security.


Your response here is the response typical of many technologists,
'nothing to do with me'. Having been involved in national politics in
multiple countries, I can tell you that approach is not going to be
remotely acceptable to elected representatives whose constituents rely
on them.

Congressional, EU action is inevitable, in fact it has already begun.
The question is one of framing. Right now, the Internet is seen as the
problem because it was the new factor that was introduced and
invalidated the assumptions that the legacy infrastructures depended
on. If we don't want to get regulated to heck and back, we have to
change the conversation so that policy makers understand that the
Internet is the one infrastructure that was originally designed with
the understanding that every device would be connected to every other
device and that this would create a new set of security requirements.


> Instead, it seems to me that we have a philosophical tussle between A)
> people who think of the Internet firstly as a command and telemetry system
> for political and economic data, to be policed by and subservient to state
> power, used mainly as a tool for governing the populace, and B) people who
> think of the Internet firstly as an open standard communication technology
> to which justice demands that everyone is recognized to have an equal right
> to lawfully regulated use for any public or private purpose.
>
> How you think about security risks, it seems to me, depends on which side of
> this philosophical debate you align. Accusing the other side of "casual
> negligence," when it's actually the case that the other side has set
> different priorities, is probably not the best way to facilitate better
> mutual understanding.

The reason I am presenting these issues here is precisely the fact
that they are dismissed out of hand as you do here while making a plea
for seeing both sides!

I am currently writing an infrastructure that makes open end-to-end
secure messaging as easy to use as regular email despite the express
opposition to this idea from my own government expressed repeatedly by
the Prime Minister and Home Secretary. So I think it is pretty clear
which side I sit on. But that does not mean I reject the other side
out of hand.

Closing his plenary address to the first Web conference, Tim
Berners-Lee described the Web as 'building a whole new world'. Well we
have built a whole new world and it has replaced the old one. And a
lot of people are rather upset with us as a result even as they spend
their time venting their rage at what we have wrought on Facebook and
Twitter.


From nobody Wed Nov  1 11:53:45 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 BE743139612; Wed,  1 Nov 2017 11:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 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, 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 eAl4xu1SgK1K; Wed,  1 Nov 2017 11:53:40 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E7C813F87C; Wed,  1 Nov 2017 11:53:40 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id vA1IrcjI004391; Wed, 1 Nov 2017 18:53:38 GMT
Received: from 950129200 (254.196.113.87.dyn.plus.net [87.113.196.254]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id vA1Ira6R004372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Nov 2017 18:53:37 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <rtg-ads@ietf.org>
Cc: <draft-ietf-opsawg-mud@ietf.org>, <ietf@ietf.org>, <rtg-dir@ietf.org>
Subject: RTG-DIR review of draft-ietf-opsawg-mud-13
Date: Wed, 1 Nov 2017 18:53:35 -0000
Message-ID: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AdNTQrIO97lGRZjDTByyHTzDwLaeVQ==
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23434.002
X-TM-AS-Result: No--17.531-10.0-31-10
X-imss-scan-details: No--17.531-10.0-31-10
X-TMASE-MatchedRID: mKQO0h0Bck5tcr/uuDMv3m7hbmASKcrpQPCWRE0Lo8LIvQIyugvKdVjt prj9/vncRTpdHYygurQZwn7DIQtGC+4dcT3ZaToc+L2GsArAgtofXzVgO0hVqhW4PjzZ50/jMtY +alBD5ALetqCOhM9ls/thAPwiumCncVcsgVCVf8Vdxv5RmV3KC23eqxoVjgMEHWNaMBkegSfJTt eBOzpbgvD2wbKkvoqCr7t6OWlLJrw3IAlnCz/XMYdlc1JaOB1TkUtSee+57IH2Jzqp3fkNE3ory 7LEZ/71w/o6/kyrembJp2D4aumo7Lsl8Gv1eXkKRAvohSJUpI9RwfT2oEaYdGsTVziYHlSa9dB3 QPuA1xWs5qWj5r/l1zf9o2/0YdMdBYAV6EZJorJo2fKvznNZwMd5cqtswikAqpNaTZ0S3FoezV0 lIgz9uiTACfrZ6hofAGNtSDyz8sYqACWCM+FilqOuVibdZNTvveCbyZ3xax52iqcE/RbrKLE+hk hRyJ1V4nlXq9Sz6hQ9dnB5Mf9Aa6Yy2qfD59i787gU9YZmSw/vkROLxAaM3KBp/T5dSs2Tgo4eB 1LnWgiI7qXZddSBHfhwH/7pGOPdgtJ1kfzs6mBlI0vGyCjKv1Nn42YjbyMpStZtgyGdXLP31pa3 bg57F/53mchhBKw5YpDBQqe7Xi8yCh7sleAnD+XP7JqXOmP+ftnnpG0AB3WPcd2jEAJg7URdSGQ iaJZz8azB+j7c5JQZNgTPgsbY9S2DV9S/r9yeSxG/I0MjmF5zmB71otxffKkZyr3BN6qIcKcH6d pKXP0zDwDbj/+DgoS+UIhwPrWIJa+FAG1BTBOeAiCmPx4NwLTrdaH1ZWqCHOI0tZ7A+B36C0ePs 7A07QKmARN5PTKc
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S-dDsFs6RDcgQTQdaFhmvKaNynY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 18:53:44 -0000

Hello, 

I have been selected as the Routing Directorate reviewer for this draft. The
Routing Directorate seeks to review all routing or routing-related drafts as
they pass through IETF last call and IESG review, and sometimes on special
request. The purpose of the review is to provide assistance to the Routing ADs.
For more information about the Routing Directorate, please see
http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir 

Although these comments are primarily for the use of the Routing ADs, it would
be helpful if you could consider them along with any other IETF Last Call
comments that you receive, and strive to resolve them through discussion or by
updating the draft. 

Document: draft-ietf-opsawg-mud-13.txt
   Reviewer: Adrian Farrel 
   Review Date: 1 November 2017
   IETF LC End Date: 7 November 2017
   Intended Status: Standard Track

Overview

   Manufacturer Usage Descriptions (MUD) provide a means for elements of
   an IoT network to indicate what sorts of access and network 
   functionality they require in order to function properly.  The 
   emphasis of this document is on access control although the authors 
   envision future extensions for "other aspects".

   The document is a collection of bits and pieces to enable MUD: two
   YANG modules, IPv4 and IPv6 DHCP options, an LLDP TLV, a URL suffix
   specification, an X.509 certificate extension, and a means to sign and
   verify the descriptions.

   Some future work is listed, but I see no evidence that this work is 
   actually anything more than a possibility: there are no drafts that 
   appear to cover any additional MUD specifications.
   
Summary: 

I have some minor concerns about this document that I think should be
resolved before publication. I have flagged one of these as a more
serious issue, although I think it may be possible to solve with some
2119 language that governs expectations on implementations.

The document was easy to read although the number of minor issues and
nits in the early section suggests that the late-stage reviews were more
focused on the YANG than the text.

Adrian

===

Major Issues: 

I know I ranted about privacy before and the authors took some text I wrote as
the basis of the privacy considerations, but I'm still worried that the default
will be that devices are MUD-enabled (good) and that users will not be
protected. It would be sad if the user's only option is to reject MUD devices
(especially as they might not even know that the devices are MUD-enabled). More
burble below, but it seems to me that we should make privacy-supporting modes of
operation at least the default, but possibly the only approach.

Section 15 has...

   The release of a MUD URL by a Thing reveals what the Thing is, and
   provides an attacker with guidance on what vulnerabilities may be
   present.

Pleased to see this text: it was a security concern I had. Good to have
it flagged. However, the mitigation suggested 2 paragraphs later is a
bit thin and sounds rather optional. I see how an implementer might
take action, but what can a user do to protect their device? 

Similarly,

   While the MUD URL itself is not intended to be unique to a specific
   Thing, the release of the URL may aid an observer in identifying
   individuals when combined with other information.  This is a privacy
   consideration.

This is not the only privacy issue since once a location or individual
has been identified, the release of MUD URLs announce things about the
location (such as what valuable Things are present and even what 
security devices are in use). Furthermore, the picture of an individual
built up by knowing what Things they have is a substantial concern.

At least in the first case the implementer has an interest in applying
the protection, but the only person who cares about my privacy is me.
What options do I have to protect myself (except not purchasing MUD-
enabled devices which is presumably not the objective we want to 
pursue)?


===

Minor Issues: 


The last call indicated a Downref to draft-ietf-netmod-acl-model. All well and
good.

idnits reports RFC 2818 as a Downref as well, but didn't appear in the last
call.

---

Abstract
   Referring to "Things" is cute, but actually doesn't help the reader.
   Could you give a clue or two?

BTW, the definition in 1.6 is a little thin and circular. A Thing is 
something to which you apply MUD, but what is it actually?

---

The Abstract says...

   The initial focus is on access control.

But the Introduction says...

   Although this memo may seem to stress
   access requirements, usage intent also consists of quality of service
   needs a device may have.

Please decide which you mean.

---

Introduction

OLD
   The Internet has largely been constructed on general purpose
   computers, those devices that may be used for a purpose that is
   specified by those who buy the device.
NEW
   The Internet is largely constructed from general purpose computers.
   These are devices that may be used for a purpose that is specified by
   those who buy the device.

Although this is ambiguous and probably wrong: I think routers and 
switches probably form a part of the Internet, and I suspect they are
somewhat specific to their use.

---

Introduction

   In the context of a smarter
   device that has a built in Linux stack, it might be an integrator of
   that device.

Is there something special about Linux?

---

1.5
This section introduces the "MUD controller." It's unexplained.
It could be helpful to pull section 1.6 up perhaps to 1.3.

---

There seems to be some overlap of terms and definitions in 1.5 and 1.6.

---

1.7 has a nice picture, thanks.

But I note that the text describes a "web site" while the picture shows
a "file server".

Similarly, the text has "network management system" while the picture
has "MUD controller".

---

3.3 makes reference to "is supported" and 3.4 gives clarity to what 
that means.  Shouldn't this section also describe the meaning of this
object when the Thang isn't supported?

---

3.5 has me confused. Looks like a fine idea, but how does it work? A
Thing reports the MUD URL, and the file that is pulled contains the
systeminfo URL, and the info that is pulled contains the localised info.
Have I got that right?

That means that the MUD URL has to include the correct systeminfo for
the locality.  Presumably we're interested in the locality of the MUD
controller.

The MUD controller knows its locality.  Is it supposed to tell the 
web server?  How else does the right systeminfo URL get provided, or
the URL get mapped to the right localised information?

---

16.2

Something messed up here.

We have

   The IANA has allocated option 161 in the Dynamic Host Configuration
   Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters registry
   for the MUD DHCPv4 option.

   IANA is requested to allocated the DHCPv4 and v6 options as specified
   in Section 9.

But section 9 has 161 and 112 explicitly mentioned.

116 is already in the registry, but presumably you have an IANA action
to update the reference to this document when it becomes an RFC.

112 is also already in the DHCPv6 options registry.
So you probably want to point at that instead of the current 2nd para.

====     

Nits: 

Introduction

   Please do NOT use random uppercase words in your text.  There's NO
   need: the readers are no more stupid than the average reader of an
   RFC.

Ditto 3.4, 3.6

---

Introduction

   The key points are that the device itself is expected
   to serve a limited purpose,

I think you mean s/expected/intended/

---

Introduction

   The intent of MUD is to solve for the following problems:

d/for/

Although the list that follows is not a list of problems. So, perhaps,

   The intent of MUD is to provide the following function:

---

Introduction

   o  Provide for a means to scale network policies to the ever-
      increasing number types of devices in the network.

d/for/
s/types/of types/

---

Introduction

      Provide a means to address at least some vulnerabilities in a way
      that is faster than it might take to update systems.

s/than/than the time/

---

Introduction

   o  A classifier that a device emits that can be used to locate a
      description;

Classifier or classification?

---

OLD
1.1.  What MUD doesn't do
NEW
1.1.  What MUD Doesn't Do

---

Section 1.1

   No matter how good a MUD-enabled network is, it will never replace
   the need for manufacturers to patch vulnerabilities.  It may,
   however, provide network administrators with some additional
   protection when those vulnerabilities exist.

Does this paragraph belong in this section? Seems to say what MUD does,
not what MUD doesn't do.

Maybe flip the order of presentation?...

   MUD may provide network administrators with some protection when
   vulnerabilities exist, however, no matter how good a MUD-enabled 
   network is, it will never replace the need for manufacturers to 
   patch vulnerabilities. 

---

1.2

s/an app on smart phone/an application on a smart phone/

---

1.4 para 2
Might be worth splitting this into bullets

---

1.5
s/configuration of is/configuration is/

---

2.

s/only"accept"/only "accept"/

---

I think [I-D.ietf-netmod-rfc6087bis] may be used in a normative way to
explain the notation used in this document.

---

3.
   Note that in this section, when we use the term "match" we are
   referring to the ACL model "matches" node, and thus returns positive
   such that an action should be applied.

Is that English? I know what it means, but not what it says.

---

3.1

s/containers indicate/containers indicates/

---

3.1

   [I-D.ietf-netmod-acl-model] describes access-lists but does not
   attempt to indicate where they are applied as that is handled
   elsewhere in a configuration

"a configuration file?" "operation"? "in configuration information"?

---

3.8

Say that this is a null-valued node

---

3.11
s/mud/MUD/


From nobody Wed Nov  1 12:41:27 2017
Return-Path: <mersue@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 AA6A213FE82 for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 12:41:26 -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 MWw0JpjlBxhy for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 12:41:23 -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 08BAA13F651 for <ietf@ietf.org>; Wed,  1 Nov 2017 12:41:23 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id r68so6941195wmr.3 for <ietf@ietf.org>; Wed, 01 Nov 2017 12:41:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=otiZ5DqZ92HkDRPmcpwauWMWCHFq2m3DJKw/31mAYgg=; b=ittrPvQFNWMgmBVT1iqwIcET2lcquom2gMT0qS8A5F0Y+GyHjH2MPB7RscF1MPBU+J JbbS7xNCcoqSaV2YE1b0U5UApw5IQ7xkrf57zz38d0xpC8cAycgcscRplx2uNnSraIkM yGH7KFv/AjAOPbReyp0dZWC/tTqosshF1rS8S6YodHshuA7GIO0OAKiHXEjkTT2d4sdV Osh033M95ux/O1wYCwRw7EzKrI+Ylu9GhbuMaZrcAJ1E2mSwHp7nqqn+7IMnTVGvHDAV O33h74zyvKgmtnXBC8NjpTXAPFYmUXvU+CY+blWLM/JY+0RQ8ojF0FvBR0pTl+vP9C6p yKbQ==
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:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=otiZ5DqZ92HkDRPmcpwauWMWCHFq2m3DJKw/31mAYgg=; b=FhsYtiVjRvm5ZlmVLBEPw/3cEofwRZrPlg5crG1uA2gD23behKwNrJf4kW48Up8bjw j3x77cC6JkBICxKvNnog6nNnBvhbxUuQ6Wkr0y/Vm45eAnhBCUpV9USfm4/FmTowPQ4r PehWqQvU4Z+Q4uYG13U9C88w0TD32LLfSCpS6ngQ/sRr4Ct2aE2bi0Us+B1g+/shityT yUUcPexRKsEcmzAd0DlthiJs3UGsD6g20z6QLQnMbdc8augcInPuvKHQnkiMIfdRV7sB IkwJCdC7lFfRe1CV5jj7tZLOxp4+grul5k7H2kNdnyqiGjvlR7RLCSj/jCW5h3t7VyQs LZfA==
X-Gm-Message-State: AMCzsaU4sVRMDC4nJYaAUQvR71lrVbYKnXWXAoMBjfp5WLyzf0yDY86P XfZL/DeBBJEJhpzYtYzvlTV+34+K
X-Google-Smtp-Source: ABhQp+QuRoc+e9LNop0ldtBSJNYwEpgBz6OmBGf6ZPWQSW7UKWeLAH+uT5I9rfeFzB1JMF2KqpAB1Q==
X-Received: by 10.28.16.149 with SMTP id 143mr1116503wmq.62.1509565281424; Wed, 01 Nov 2017 12:41:21 -0700 (PDT)
Received: from DESKTOPFLHJVQJ (200116b826ddae0065f1aa2df4e9c0e1.dip.versatel-1u1.de. [2001:16b8:26dd:ae00:65f1:aa2d:f4e9:c0e1]) by smtp.gmail.com with ESMTPSA id x189sm1044546wmf.10.2017.11.01.12.41.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Nov 2017 12:41:20 -0700 (PDT)
From: "Mehmet Ersue" <mersue@gmail.com>
To: <sarikaya@ieee.org>, "'Alia Atlas'" <akatlas@gmail.com>
Cc: "'IETF Discussion Mailing List'" <ietf@ietf.org>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <CABkgnnWzJr_n4qLnJsu=mvBLjHwCH2LdbbjNGENaavVX357NpQ@mail.gmail.com> <CAG4d1regBTXfK798D0_hunWbC5beiWFsN_uR2q3vWyhwcmZ6vA@mail.gmail.com> <CABkgnnUoBBdUBiFMzD964eSpDkouaNSfUhvCKnBkSg87me9EFQ@mail.gmail.com> <79eaeafe-a35d-8342-4b6a-7413b4309ed9@gmail.com> <023a01d35262$1ee47e40$5cad7ac0$@gmail.com> <CAG4d1rfQvVjyd_cTj3V5jEqceiq1GZLPWO9gQfFdg89iAheZMQ@mail.gmail.com> <027c01d3526b$b6bcef50$2436cdf0$@gmail.com> <CAG4d1reoiMjiuY6m6fHj3QyZf5jF-4aZh4r+CK4fTg8kOWx-Jw@mail.gmail.com> <CAC8QAcc5H21xKtEoBB4f3jv03JUUHxRvUxxRga=MshEisucpeg@mail.gmail.com>
In-Reply-To: <CAC8QAcc5H21xKtEoBB4f3jv03JUUHxRvUxxRga=MshEisucpeg@mail.gmail.com>
Subject: RE: letting IETF build on top of Open Source technology
Date: Wed, 1 Nov 2017 20:41:19 +0100
Message-ID: <016901d35349$64791050$2d6b30f0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_016A_01D35351.C6420C30"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJMytRldqlLDabFYqOPiwW6BFd4uQGoqZ32AlrbQ3YCjDF0VwLYUQsFAeHRWJYCnvXQCAFi46dmAkUTsGsDcQSw2KFk6oOg
Content-Language: de
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GMScL5P2hR-K_y8wqrfZChFKCII>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 19:41:26 -0000

This is a multipart message in MIME format.

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

Hi Alia, All,

=20

during the discussion it kind of gets lost what kind of reference is =
sufficient and whether a normative reference is explicitly required.

If possible we should avoid such external dependency.

=20

IMO only in very rare cases an IETF RFC would use an external document =
normatively (i.e. use the external document as its basis or build on-top =
of it) and a normative reference would be required.

=20

To be able to understand in which cases a normative reference is =
imperative I think the requirements should be discussed and specified =
clearly giving real-life use cases.

=20

Mehmet

=20

From: Behcet Sarikaya [mailto:sarikaya2012@gmail.com]=20
Sent: Wednesday, November 1, 2017 5:33 PM
To: Alia Atlas <akatlas@gmail.com>
Cc: Mehmet Ersue <mersue@gmail.com>; IETF Discussion Mailing List =
<ietf@ietf.org>
Subject: Re: letting IETF build on top of Open Source technology

=20

Hi Alia,

One member mentioned that the open source code does serve as the =
protocol description and hence it could be referenced as dependency in =
RFCs.

I think we should question that.

I worked many years on formal description techniques for protocols. I =
think that such specs could serve as a reference.

Source code in some specific programming language is very long and =
difficult to follow for someone interested in a high level view of the =
protocol.

Also many people do not know the specific programming language it was =
written.

My 2 cents.

Regards,

Behcet

=20

On Tue, Oct 31, 2017 at 1:29 PM, Alia Atlas <akatlas@gmail.com =
<mailto:akatlas@gmail.com> > wrote:

Hi Mehemet:

=20

below in-line=20

=20

On Tue, Oct 31, 2017 at 1:14 PM, Mehmet Ersue <mersue@gmail.com =
<mailto:mersue@gmail.com> > wrote:

See ME:

=20

Thanks,

Mehmet

=20

From: Alia Atlas [mailto:akatlas@gmail.com <mailto:akatlas@gmail.com> ]=20
Sent: Tuesday, October 31, 2017 5:13 PM
To: Mehmet Ersue <mersue@gmail.com <mailto:mersue@gmail.com> >
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com =
<mailto:brian.e.carpenter@gmail.com> >; Martin Thomson =
<martin.thomson@gmail.com <mailto:martin.thomson@gmail.com> >; IETF =
Discussion Mailing List <ietf@ietf.org <mailto:ietf@ietf.org> >
Subject: Re: letting IETF build on top of Open Source technology

=20

Hi Mehmet,

=20

On Tue, Oct 31, 2017 at 12:05 PM, Mehmet Ersue <mersue@gmail.com =
<mailto:mersue@gmail.com> > wrote:

Hi Alia,

> >  1.  Is it stable, mature, and immutable (except for errata)?
>
> Those are not well known characteristics of open source projects.
> Even if we tie a reference down to a very specific version, I'm =
unclear how
> that can truly act as a stable reference. It may be stable in a =
mathematical
> sense, but it may also be seven years behind deployed reality.

I agree with Brian. There are different type of non-SDO organizations =
having documents with diverse maturity levels and stability. Many of =
them don't qualify as normative references.

=20

Of course - and that's why it is necessary for the item to meet the =
questions posed in the draft - which are the requirements (and we'll =
rephrase more clearly as Russ suggested).=20

=20

Obvious examples for normative references are usually from well-known =
SDOs like IEEE or W3C where the new standard-track RFC uses it as its =
basis or builds on-top of it (e.g.  [W3C.REC-xml-20001006])

I also don't see an issue with MD5 and HMAC as these are Informational =
RFCs at IETF with a well-known stability.

=20

Sure - and that was one of the motivations for RFC 3967.

=20

Looking at section 1.1. of RFC 3967 and the statement: "a normative =
reference specifies a document that must be read to fully understand or =
implement the subject matter in the new RFC, or whose contents are =
effectively part of the new RFC, as its omission would leave the new RFC =
incompletely specified",
can you please give examples of external documents from non-DOSs, which =
clearly qualify as normative references for a standard-track RFC at =
IETF?
I think primarily on non-SDO documents where the new RFC would build =
on-top of it.

=20

An example would be potentially thrift, I think, for protocol encodings. =
I have to hunt down the detailed reference for it.

I know that protobufs have good documentation also.  I am sure that =
there are others and would be happy to hear folks chime in with more.

=20

It's unclear whether there is a set of requirements acceptable to the =
IETF Community that would work for WHATWG work.

=20

Is your concern that you don't see useful open source work that would be =
suitable to reference? Or that none would meet our set of requirements?

Or that it is risky to consider referencing non-SDO external work?

=20

ME: Generally I don=E2=80=99t see an issue with referencing useful open =
source work. Though only in rare cases an IETF RFC has a dependency on =
or builds indeed on-top of such a document normatively. I think the main =
criteria for a normative reference is still based on the quoted text =
from RFC 3967 above.=20

=20

[Alia] Agreed - and I pulled the requirements around stability, =
maturity, confidentiality, and IPR considerations largely from 2026.

My question is whether it is rare than an IETF RFC builds on top of open =
source work because the path to do so is seen as too =
challenging/long/expensive or simply not relevant. This draft is =
proposing a policy assuming the former applies at least some of the =
time.

=20

I believe use cases and examples will help to define concrete =
requirements.

Once we have the requirements together such documents need to be looked =
at in a case by case basis and taken over into a registry.

=20

The requirements, I think, stem from our (the IETF community's) =
understanding of what is necessary for a dependency of a standards-track =
RFC and I am not proposing that those should change.  I'm trying to =
capture what they are and how to evaluate a piece of work.

=20

Rather than looking at the set of documents and creating a registry, the =
draft suggests that when a WG wants to use such an item as a dependency, =
then after that use has IESG Approval, then the item can be added to a =
registry - so other WGs and other documents in that WG can benefit from =
the evaluation that was done and feel more confident about using it.

=20

Regards,

Alia

=20

Regards,

Alia

=20

=20

Thanks,
Mehmet


> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org =
<mailto:ietf-bounces@ietf.org> ] On Behalf Of Brian E Carpenter
> Sent: Monday, October 30, 2017 4:49 AM
> To: Martin Thomson <martin.thomson@gmail.com =
<mailto:martin.thomson@gmail.com> >; Alia Atlas
> <akatlas@gmail.com <mailto:akatlas@gmail.com> >
> Cc: IETF Discussion Mailing List <ietf@ietf.org <mailto:ietf@ietf.org> =
>
> Subject: Re: letting IETF build on top of Open Source technology
>
> On 30/10/2017 16:27, Martin Thomson wrote:
> > On Mon, Oct 30, 2017 at 2:18 PM, Alia Atlas <akatlas@gmail.com =
<mailto:akatlas@gmail.com> > wrote:
> >> The existing downref process (RFC 3967) doesn't apply. That is to
> >> handle references to an RFC that is at a lower maturity - such as a
> >> normative reference to an Informational or Experimental RFC - or =
from
> >> an Internet Standard to a Proposed Standard.
> >
> > I couldn't find anything in 3967 to support that view (other than =
the
> > parenthetical in the abstract).  Maybe it's implicit.
>
> The quote from RFC2026 in section 1 of RFC3967 is pretty unambiguous =
when
> read in context - throughout RFC2026, "standards track" refers to the =
IETF
> standards track, and "standards track specifications"
> refers to IETF documents. And in any case the Abstract of RFC3967 sets =
the
> scope thus: "Exceptions to this rule are sometimes needed as the IETF =
uses
> informational RFCs to describe non-IETF standards or IETF-specific =
modes of
> use of such standards."
>
> My main concern with the new proposal is other:
>
> >  1.  Is it stable, mature, and immutable (except for errata)?
>
> Those are not well known characteristics of open source projects.
> Even if we tie a reference down to a very specific version, I'm =
unclear how
> that can truly act as a stable reference. It may be stable in a =
mathematical
> sense, but it may also be seven years behind deployed reality.
>
>     Brian

=20

=20

=20


------=_NextPart_000_016A_01D35351.C6420C30
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#0000CC;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:#0000CC;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#0000CC'>Hi Alia, All,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>during the discussion it =
kind of gets lost what kind of reference is sufficient and whether a =
normative reference is explicitly required.<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>If possible we should =
avoid such external dependency.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>IMO only in very rare =
cases an IETF RFC would use an external document normatively (i.e. use =
the external document as its basis or build on-top of it) and a =
normative reference would be required.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#0000CC'>To be able to understand =
in which cases a normative reference is imperative I think the =
requirements should be discussed and specified clearly giving real-life =
use cases.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'>Mehmet<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#0000CC'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b>From:</b> =
Behcet Sarikaya [mailto:sarikaya2012@gmail.com] <br><b>Sent:</b> =
Wednesday, November 1, 2017 5:33 PM<br><b>To:</b> Alia Atlas =
&lt;akatlas@gmail.com&gt;<br><b>Cc:</b> Mehmet Ersue =
&lt;mersue@gmail.com&gt;; IETF Discussion Mailing List =
&lt;ietf@ietf.org&gt;<br><b>Subject:</b> Re: letting IETF build on top =
of Open Source technology<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><div><div><div><div=
><div><div><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Hi =
Alia,<o:p></o:p></p></div><p class=3DMsoNormal>One member mentioned that =
the open source code does serve as the protocol description and hence it =
could be referenced as dependency in RFCs.<o:p></o:p></p></div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>I think we should =
question that.<o:p></o:p></p></div><p class=3DMsoNormal>I worked many =
years on formal description techniques for protocols. I think that such =
specs could serve as a reference.<o:p></o:p></p></div><p =
class=3DMsoNormal>Source code in some specific programming language is =
very long and difficult to follow for someone interested in a high level =
view of the protocol.<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Also many people do not know the specific =
programming language it was written.<o:p></o:p></p></div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>My 2 =
cents.<o:p></o:p></p></div><p =
class=3DMsoNormal>Regards,<o:p></o:p></p></div><p =
class=3DMsoNormal>Behcet<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>On Tue, =
Oct 31, 2017 at 1:29 PM, Alia Atlas &lt;<a =
href=3D"mailto:akatlas@gmail.com" =
target=3D"_blank">akatlas@gmail.com</a>&gt; =
wrote:<o:p></o:p></p><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><div><p class=3DMsoNormal>Hi Mehemet:<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>below in-line&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><div><p =
class=3DMsoNormal>On Tue, Oct 31, 2017 at 1:14 PM, Mehmet Ersue &lt;<a =
href=3D"mailto:mersue@gmail.com" =
target=3D"_blank">mersue@gmail.com</a>&gt; =
wrote:<o:p></o:p></p><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0000CC'>See ME:</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0000CC'>&nbsp;</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0000CC'>Thanks,</span><o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0000CC'>Mehmet</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0000CC'>&nbsp;</span><o:p></o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b>From:</b>=
 Alia Atlas [mailto:<a href=3D"mailto:akatlas@gmail.com" =
target=3D"_blank">akatlas@gmail.com</a>] <br><b>Sent:</b> Tuesday, =
October 31, 2017 5:13 PM<br><b>To:</b> Mehmet Ersue &lt;<a =
href=3D"mailto:mersue@gmail.com" =
target=3D"_blank">mersue@gmail.com</a>&gt;<br><b>Cc:</b> Brian E =
Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" =
target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;; Martin Thomson =
&lt;<a href=3D"mailto:martin.thomson@gmail.com" =
target=3D"_blank">martin.thomson@gmail.com</a>&gt;; IETF Discussion =
Mailing List &lt;<a href=3D"mailto:ietf@ietf.org" =
target=3D"_blank">ietf@ietf.org</a>&gt;<br><b>Subject:</b> Re: letting =
IETF build on top of Open Source technology<o:p></o:p></p></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi =
Mehmet,<o:p></o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>On Tue, Oct =
31, 2017 at 12:05 PM, Mehmet Ersue &lt;<a =
href=3D"mailto:mersue@gmail.com" =
target=3D"_blank">mersue@gmail.com</a>&gt; =
wrote:<o:p></o:p></p><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Hi =
Alia,<br><br>&gt; &gt;&nbsp; 1.&nbsp; Is it stable, mature, and =
immutable (except for errata)?<br>&gt;<br>&gt; Those are not well known =
characteristics of open source projects.<br>&gt; Even if we tie a =
reference down to a very specific version, I'm unclear how<br>&gt; that =
can truly act as a stable reference. It may be stable in a =
mathematical<br>&gt; sense, but it may also be seven years behind =
deployed reality.<br><br>I agree with Brian. There are different type of =
non-SDO organizations having documents with diverse maturity levels and =
stability. Many of them don't qualify as normative =
references.<o:p></o:p></p></blockquote><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Of course - =
and that's why it is necessary for the item to meet the questions posed =
in the draft - which are the requirements (and we'll rephrase more =
clearly as Russ suggested).&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Obvious =
examples for normative references are usually from well-known SDOs like =
IEEE or W3C where the new standard-track RFC uses it as its basis or =
builds on-top of it (e.g.&nbsp; [W3C.REC-xml-20001006])<br><br>I also =
don't see an issue with MD5 and HMAC as these are Informational RFCs at =
IETF with a well-known stability.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Sure - and =
that was one of the motivations for RFC =
3967.<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Looking at =
section 1.1. of RFC 3967 and the statement: &quot;a normative reference =
specifies a document that must be read to fully understand or implement =
the subject matter in the new RFC, or whose contents are effectively =
part of the new RFC, as its omission would leave the new RFC =
incompletely specified&quot;,<br>can you please give examples of =
external documents from non-DOSs, which clearly qualify as normative =
references for a standard-track RFC at IETF?<br>I think primarily on =
non-SDO documents where the new RFC would build on-top of =
it.<o:p></o:p></p></blockquote><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>An example =
would be potentially thrift, I think, for protocol encodings. I have to =
hunt down the detailed reference for it.<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>I know that =
protobufs have good documentation also.&nbsp; I am sure that there are =
others and would be happy to hear folks chime in with =
more.<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>It's =
unclear whether there is a set of requirements acceptable to the IETF =
Community that would work for WHATWG work.<o:p></o:p></p></div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Is your =
concern that you don't see useful open source work that would be =
suitable to reference? Or that none would meet our set of =
requirements?<o:p></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Or that it =
is risky to consider referencing non-SDO external work?<o:p></o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0070C0'>ME: Generally I don=E2=80=99t see an issue with =
referencing useful open source work. Though only in rare cases an IETF =
RFC has a dependency on or builds indeed on-top of such a document =
normatively. I think the main criteria for a normative reference is =
still based on the quoted text from RFC 3967 =
above.&nbsp;</span><o:p></o:p></p></div></div></div></div></div></div></d=
iv></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div><div><p =
class=3DMsoNormal>[Alia] Agreed - and I pulled the requirements around =
stability, maturity, confidentiality, and IPR considerations largely =
from 2026.<o:p></o:p></p></div><div><p class=3DMsoNormal>My question is =
whether it is rare than an IETF RFC builds on top of open source work =
because the path to do so is seen as too challenging/long/expensive or =
simply not relevant. This draft is proposing a policy assuming the =
former applies at least some of the time.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><div><div><div style=3D'border:none;border-left:solid blue =
1.5pt;padding:0cm 0cm 0cm 4.0pt'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0070C0'>I believe use cases and examples will help to =
define concrete requirements.</span><o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
style=3D'color:#0070C0'>Once we have the requirements together such =
documents need to be looked at in a case by case basis and taken over =
into a =
registry.</span><o:p></o:p></p></div></div></div></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The requirements, I think, stem from our (the IETF =
community's) understanding of what is necessary for a dependency of a =
standards-track RFC and I am not proposing that those should =
change.&nbsp; I'm trying to capture what they are and how to evaluate a =
piece of work.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Rather than looking at the set of documents and =
creating a registry, the draft suggests that when a WG wants to use such =
an item as a dependency, then after that use has IESG Approval, then the =
item can be added to a registry - so other WGs and other documents in =
that WG can benefit from the evaluation that was done and feel more =
confident about using it.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Regards,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Alia<o:p></o:p></p></div><div><div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><div><div><div style=3D'border:none;border-left:solid blue =
1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div><div><div><div><div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Regards,<o:p=
></o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Alia<o:p></o=
:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5=
.0pt'><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>Thanks,<br>M=
ehmet<o:p></o:p></p><div><div><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><br>&gt; =
-----Original Message-----<br>&gt; From: ietf [mailto:<a =
href=3D"mailto:ietf-bounces@ietf.org" =
target=3D"_blank">ietf-bounces@ietf.org</a>] On Behalf Of Brian E =
Carpenter<br>&gt; Sent: Monday, October 30, 2017 4:49 AM<br>&gt; To: =
Martin Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com" =
target=3D"_blank">martin.thomson@gmail.com</a>&gt;; Alia Atlas<br>&gt; =
&lt;<a href=3D"mailto:akatlas@gmail.com" =
target=3D"_blank">akatlas@gmail.com</a>&gt;<br>&gt; Cc: IETF Discussion =
Mailing List &lt;<a href=3D"mailto:ietf@ietf.org" =
target=3D"_blank">ietf@ietf.org</a>&gt;<br>&gt; Subject: Re: letting =
IETF build on top of Open Source technology<br>&gt;<br>&gt; On =
30/10/2017 16:27, Martin Thomson wrote:<br>&gt; &gt; On Mon, Oct 30, =
2017 at 2:18 PM, Alia Atlas &lt;<a href=3D"mailto:akatlas@gmail.com" =
target=3D"_blank">akatlas@gmail.com</a>&gt; wrote:<br>&gt; &gt;&gt; The =
existing downref process (RFC 3967) doesn't apply. That is to<br>&gt; =
&gt;&gt; handle references to an RFC that is at a lower maturity - such =
as a<br>&gt; &gt;&gt; normative reference to an Informational or =
Experimental RFC - or from<br>&gt; &gt;&gt; an Internet Standard to a =
Proposed Standard.<br>&gt; &gt;<br>&gt; &gt; I couldn't find anything in =
3967 to support that view (other than the<br>&gt; &gt; parenthetical in =
the abstract).&nbsp; Maybe it's implicit.<br>&gt;<br>&gt; The quote from =
RFC2026 in section 1 of RFC3967 is pretty unambiguous when<br>&gt; read =
in context - throughout RFC2026, &quot;standards track&quot; refers to =
the IETF<br>&gt; standards track, and &quot;standards track =
specifications&quot;<br>&gt; refers to IETF documents. And in any case =
the Abstract of RFC3967 sets the<br>&gt; scope thus: &quot;Exceptions to =
this rule are sometimes needed as the IETF uses<br>&gt; informational =
RFCs to describe non-IETF standards or IETF-specific modes of<br>&gt; =
use of such standards.&quot;<br>&gt;<br>&gt; My main concern with the =
new proposal is other:<br>&gt;<br>&gt; &gt;&nbsp; 1.&nbsp; Is it stable, =
mature, and immutable (except for errata)?<br>&gt;<br>&gt; Those are not =
well known characteristics of open source projects.<br>&gt; Even if we =
tie a reference down to a very specific version, I'm unclear how<br>&gt; =
that can truly act as a stable reference. It may be stable in a =
mathematical<br>&gt; sense, but it may also be seven years behind =
deployed reality.<br>&gt;<br>&gt;&nbsp; &nbsp; =
&nbsp;Brian<o:p></o:p></p></div></div></blockquote></div></div></div><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'>&nbsp;<o:p><=
/o:p></p></div></div></div></div></div></blockquote></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_016A_01D35351.C6420C30--


From nobody Wed Nov  1 13:26:08 2017
Return-Path: <carlosm3011@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 D6E4C13F54D for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 13:26:06 -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 ZoVM6Rp630UI for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 13:26:05 -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 7EA7D13836B for <ietf@ietf.org>; Wed,  1 Nov 2017 13:26:05 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id d9so4235793qtd.7 for <ietf@ietf.org>; Wed, 01 Nov 2017 13:26:05 -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:content-transfer-encoding; bh=TiPxU/0J5iEil/hLC8wW3dfkTh0bImkhcgKwJWqPDB8=; b=pXAbwXON4XMDozEmd68lVVY2xMf7MiIlfV+7tkjYbaeTbivm8OJbMDkZ+Kd0J/AZcz a7HUyhd9IPQCY1+eESMzOA2lb1nNcOXVCMYPGO5kAWVbnqhIorbJIdcxtLnk/T09S9WL Wj70AZ7Aw+Gbx+w4nFA4oy+n7G1yBCbjMQN25yWcATIscEm/OvJG7rKnz3XrBEEvh48b Tfu0ajHHWMNaZN9fF2YEDShkVt7wkU+5J805/CzN6AzAFgzxaW/pX+684v3X/CjuUZ4h 4AIO8ygxFXXWlHFW79Vl7b4inH1R0Vg5OAS7LYKVNnLUCJkY3JzBjEOyBk5pITbTvckM E7tw==
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:content-transfer-encoding; bh=TiPxU/0J5iEil/hLC8wW3dfkTh0bImkhcgKwJWqPDB8=; b=dDb8wcppW97vDWVXm3B322P7c051xHRFsCaad8qaSiheQZ8rbJBkEO56mkyNIfCXNQ vJihbMswGoJepnc9XGwqe8u5YSqjNbCvyipN76rtEwb+CX4uvQf92nT2hVTux/iW82nt uZHSIdYNMwddorlKHldXhj4wi63kyXLWzN4+1K+hB8yWV594FH286uwSoxFUNBI8N7y7 iXj5mtrbXKCsdn5fMzZYsU119rWn1NrXBI774hzOsoXEO1qMxgD++CTKVDMqOhkjTVra hF7hHOdWGYspDBeDpp2C4T9KfwqZ62GfMTM2ugRopQ4kKADXM7pDn/cP36s3nFtODCPL rmqA==
X-Gm-Message-State: AMCzsaV3Btg2Sq6QoRSVt0kICFCKZDffAWB5dkLNfsOOnqSc5QGmDh9K YlZIGfE1ypV0ZyuSqL2wVoM=
X-Google-Smtp-Source: ABhQp+Qo2VxLmYPuniyXihi0lapBUda6Stimn/RmDU4L257ZLr32VlPPhzTGoKT+if2s77xjhCddGg==
X-Received: by 10.200.45.28 with SMTP id n28mr1860767qta.100.1509567964570; Wed, 01 Nov 2017 13:26:04 -0700 (PDT)
Received: from [200.7.87.58] ([2001:13c7:7001:7000:e9e4:cd45:62a8:db1d]) by smtp.gmail.com with ESMTPSA id g81sm1017020qkh.24.2017.11.01.13.26.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Nov 2017 13:26:03 -0700 (PDT)
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
To: "Paul Wouters" <paul@nohats.ca>
Cc: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: IP's for point-to-point and loopbacks
Date: Wed, 01 Nov 2017 17:25:59 -0300
Message-ID: <8BC77937-BBB0-4DC7-997D-09A1138691F3@gmail.com>
In-Reply-To: <B7EE2A70-3433-4030-A01A-EC871C78E68E@nohats.ca>
References: <000801d34f23$63437010$29ca5030$@incert.com.br> <679E8589-F37E-4661-89FD-FF45EEB4AACF@sobco.com> <3a41b5f8-b711-cc27-d9ca-f75e7ba48da0@gmail.com> <B7EE2A70-3433-4030-A01A-EC871C78E68E@nohats.ca>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_C0544CC3-0CA9-4908-BAFA-8ACFD64A408D_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.7r5425)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pPphdbv_EhJIg0wuUpSonuWlC3c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 20:26:07 -0000

--=_MailMate_C0544CC3-0CA9-4908-BAFA-8ACFD64A408D_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

Hi!

On 27 Oct 2017, at 16:54, Paul Wouters wrote:

> However, there is a lot of unused multicast and reserved space left to 
> do assignments from. I’m not sure why we haven’t started nibbling 
> on those yet, other then wanting to promote ipv6?

It’s been said around that those ranges would present problems if used 
on the public Internet. Namely, there is zero guarantee that they will 
be widely routable.

Now, if we were to carve blocks for p2p and loopbacks from them _under 
the assumption that they are_ a kind “extended/special use” private 
space, maybe it’s not such a bad idea.




--=_MailMate_C0544CC3-0CA9-4908-BAFA-8ACFD64A408D_=
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"=
>
<style>
div.markdown { white-space: normal; }
body { font-family: sans-serif; }
h1 { font-size: 1.4em; }
h2 { font-size: 1.2em; }
h3 { font-size: 1.1em; }
blockquote { margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #=
777777; color: #777777; }
blockquote blockquote { border-left-color: #999999; color: #999999; }
blockquote blockquote blockquote { border-left-color: #BBBBBB; color: #BB=
BBBB; }
blockquote a { color: #777777; }
blockquote blockquote a { color: #999999; }
blockquote blockquote blockquote a { color: #BBBBBB; }
math[display=3D"inline"] > mrow { padding:5px; }
div.footnotes li p { margin: 0.2em 0; }
</style>
</head>
<body>
<div class=3D"markdown">
<p dir=3D"auto">Hi!</p>

<p dir=3D"auto">On 27 Oct 2017, at 16:54, Paul Wouters wrote:</p>

<blockquote>
<p dir=3D"auto">However, there is a lot of unused multicast and reserved =
space left to do assignments from. I=E2=80=99m not sure why we haven=E2=80=
=99t started nibbling on those yet, other then wanting to promote ipv6?</=
p>
</blockquote>

<p dir=3D"auto">It=E2=80=99s been said around that those ranges would pre=
sent problems if used on the public Internet. Namely, there is zero guara=
ntee that they will be widely routable.</p>

<p dir=3D"auto">Now, if we were to carve blocks for p2p and loopbacks fro=
m them <em>under the assumption that they are</em> a kind =E2=80=9Cextend=
ed/special use=E2=80=9D private space, maybe it=E2=80=99s not such a bad =
idea.</p>
</div>

</body>
</html>

--=_MailMate_C0544CC3-0CA9-4908-BAFA-8ACFD64A408D_=--


From nobody Wed Nov  1 13:26:32 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 B3C3A13836B for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 13:26:30 -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, 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=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 r4y8x4ldBYNS for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 13:26:28 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002: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 1F38113FE8B for <ietf@ietf.org>; Wed,  1 Nov 2017 13:26:27 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id y75so2922711ywg.0 for <ietf@ietf.org>; Wed, 01 Nov 2017 13:26:27 -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=s+lvSn61UIT03T0rux5wXRlUSi2zDM2B4e+0+u3YPR0=; b=zXGzRplxWoULmaEGtO8bimSZqXeMRsll7f0uPEqtC3t3jvA6g5UQhzw4lknKzzV1VO 1m1maSP7MvAOAhi5SUe219tfm1pthr2qm+LObwu0oltDDb1s+y9QIzhGemFk6AwZlFVX 1/4tSNfMzreMdt8kXXQ1LGAVip2l0jMN3nUqDjL/S1ruDOSycpcXmPoS8SsLReLNukWA q+pjx/GE3ddnoamxEdQ8N+2cPeZ8QHBR9BFD4sAvB9UoXM9z19dx1NWOw9ZODJsKKxzg r89dfrXD4qTuPqPzuavKYs9BtW0mg2VOsuurBLMsD178BtxowXEesK6Uwl5lbT16bveZ E3lg==
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=s+lvSn61UIT03T0rux5wXRlUSi2zDM2B4e+0+u3YPR0=; b=dvdClUM0gZ57noRc3nDm0rHPOyCNgQty+c+UmxRFGaPGWJP20EIAzwvRJWw0bb7rua dxSU7puDRc5Q/D5cMaX9klNJKCeP/hbudZ7wTC/HTTOwqUD0QHxrRddQ3/qEXmwsOfh0 iOfDc47vIj5pMUCb3b9VP6CFNsnhepMPxkgW+uv8jDtUvhAd/fTfv+sJm4uLKYg0EGDa Hf4oG81wA254KfWcUsjeVQqtlX7HTxb39y2glUaiAplsIvpwTusk5Y9/VhYSsGdUrSru 3rFTDcE08vsp6Sg4wXyxjCOj35KBZx5smJUuWCV3rKiUMNV8jPqC8d0JZHYjBMjQq1FM lsgg==
X-Gm-Message-State: AMCzsaV3mEpN8BsIREPQDzYMPcloTV2vXAAS3ssB9yDe6yVOFKF/ebvB MnZyvuBTHP2VGVcdrN/ZonFxl6DS47zGeg==
X-Google-Smtp-Source: ABhQp+Qc4F2RJ4+bUpjT/y8faC23FtDRh+RVYOdCKOhLz0Z9JerPQKetlaUNNhlAN/Mn+hvnF1NCdw==
X-Received: by 10.37.135.18 with SMTP id a18mr759762ybl.166.1509567986193; Wed, 01 Nov 2017 13:26:26 -0700 (PDT)
Received: from [172.20.0.195] ([206.121.8.178]) by smtp.gmail.com with ESMTPSA id 130sm623018yws.104.2017.11.01.13.26.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Nov 2017 13:26:25 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <8D0320DC-3B44-4206-8C87-3C8E27D6FEA0@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F779CF60-EAF9-40EE-85AD-1B67D7E647C9"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Proposal to revise ISOC's mission statement
Date: Wed, 1 Nov 2017 16:26:21 -0400
In-Reply-To: <5C4CF892-0D9E-4ECB-8B7B-F9385A8B1716@consulintel.es>
Cc: ietf@ietf.org
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <20171030153844.GA19771@faui40p.informatik.uni-erlangen.de> <6.2.5.6.2.20171030121653.140878d8@elandnews.com> <1400E235-C322-42A0-8EEC-93D515EA95B6@consulintel.es> <53977630-3257-4CB9-8BED-DDAE5DD786B8@network-heretics.com> <25B4D3A1-721C-45DA-B6A8-EACADC7ECC9D@consulintel.es> <6.2.5.6.2.20171031162340.1250f1d0@elandnews.com> <C7DBB239-8912-420E-AB4C-E4A99BB81A9C@fugue.com> <5C4CF892-0D9E-4ECB-8B7B-F9385A8B1716@consulintel.es>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dEYpk5VVfj9RVLCa3zf3wEviRpk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 20:26:31 -0000

--Apple-Mail=_F779CF60-EAF9-40EE-85AD-1B67D7E647C9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Nov 1, 2017, at 4:13 AM, JORDI PALET MARTINEZ =
<jordi.palet@consulintel.es> wrote:
> My point here is not the Catalonia problem, is a general statement to =
make in the ISOC =E2=80=9Crules=E2=80=9D that ISOC MUST not interfere =
with court orders, unless they can verify what is being said at the =
court order.
>=20
> In this case, the court order indicated a list of very specific =
unlawful sites, but ISOC published that it was a global order to .cat to =
ban any political sites. It is a big difference. Our constitution =
doesn=E2=80=99t enable splitting the country and consequently a voting =
on that, was declared against law by our constitutional court, which =
ordered the police to avoid it (same way the police must avoid any other =
criminal or unlawful act, is their duty). Our constitution allows to be =
amended, but Catalonia Government don=E2=80=99t want that, they want to =
make sure they split and do at their own way, regardless only 25% of the =
Catalonian want that (which is only 5% of the total country =
population!).

I haven't seen the court order, but I agree that it's important to get =
the facts straight before making a statement, and this is a good example =
of a set of facts that, had they been gotten straight, would have =
resulted in a clearer and more effective message.


--Apple-Mail=_F779CF60-EAF9-40EE-85AD-1B67D7E647C9
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 Nov 1, 2017, at 4:13 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"">My point here is not the Catalonia =
problem, is a general statement to make in the ISOC =E2=80=9Crules=E2=80=9D=
 that ISOC MUST not interfere with court orders, unless they can verify =
what is being said at the court order.</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""><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""><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"">In this case, the court order indicated a list =
of very specific unlawful sites, but ISOC published that it was a global =
order to .cat to ban any political sites. It is a big difference. Our =
constitution doesn=E2=80=99t enable splitting the country and =
consequently a voting on that, was declared against law by our =
constitutional court, which ordered the police to avoid it (same way the =
police must avoid any other criminal or unlawful act, is their duty). =
Our constitution allows to be amended, but Catalonia Government don=E2=80=99=
t want that, they want to make sure they split and do at their own way, =
regardless only 25% of the Catalonian want that (which is only 5% of the =
total country population!).</span></div></blockquote></div><br =
class=3D""><div class=3D"">I haven't seen the court order, but I agree =
that it's important to get the facts straight before making a statement, =
and this is a good example of a set of facts that, had they been gotten =
straight, would have resulted in a clearer and more effective =
message.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_F779CF60-EAF9-40EE-85AD-1B67D7E647C9--


From nobody Wed Nov  1 13:36:18 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7103113FEBF for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 13:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=SEGoAOHI; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=pXEpjW+j
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DVRnh-9zX8PH for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 13:36:08 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A8A4713FEBE for <ietf@ietf.org>; Wed,  1 Nov 2017 13:36:08 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.35.139]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA1KZrF3011524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Nov 2017 13:36:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1509568563; x=1509654963; bh=8c5/QO64mXfva45QvGgfrNcO+2/YZ78+PGND4IZKJeA=; h=Date:To:From:Subject:In-Reply-To:References; b=SEGoAOHIRTnBAurvDVzBU3LOYO15cHSvSewbn30eEBYL9x+7Uw3FwV+XACkP777au gIjEqIGP7kyQtcpt+5Om2Knf10fDEi/v4AxA4rz8A1NWBDePyoEW7Hc8asEytFJ3ri +/5F0jMw2JZeCxvtbXp/rBuze6yocb+2g325qxfI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1509568563; x=1509654963; i=@elandsys.com; bh=8c5/QO64mXfva45QvGgfrNcO+2/YZ78+PGND4IZKJeA=; h=Date:To:From:Subject:In-Reply-To:References; b=pXEpjW+jb4a7Ee74qthorjTtemQJ8RU8GYDN+cMnTkCJFaBla80Jhv22jPQOYxlhZ 6Nd9fC7KPmNu1Z98onZ0fV3fOCG2kQhu2lAhuixex9CtMCV7i6tMNvXTbE7K8cJtGh Y+6BNJwV0Wvf1RzTZ+m8m6Mgemg2nTZ8bF9AFOV4=
Message-Id: <6.2.5.6.2.20171101132245.10d04f48@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Nov 2017 13:34:55 -0700
To: Alia Atlas <akatlas@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: letting IETF build on top of Open Source technology
In-Reply-To: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.g mail.com>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qMiYqo8Pz5bFS1wmYunZmTJbnfg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 20:36:09 -0000

Hi Alia,
At 08:02 PM 29-10-2017, Alia Atlas wrote:
>After some discussion, my co-authors and I have written down a 
>proposed policy that would clearly and specifically allow 
>standards-track RFCs to have external non-SDO normative 
>references.  It's not disallowed now - but determining early when it 
>is ok is unclear.

I read draft-atlas-external-normref-00.  "Opus" was an exception.  I 
don't think that it is a good example of referencing external code.

What is an "Open Source Organization"?  Are there examples of such 
organizations documenting IPR?

Regards,
S. Moonesamy 


From nobody Wed Nov  1 13:46:22 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 73B7413F5FE; Wed,  1 Nov 2017 13:46:16 -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 7JgJ2RsuOOTP; Wed,  1 Nov 2017 13:46:15 -0700 (PDT)
Received: from thornhill.mtv.corp.google.com (unknown [IPv6:2620:0:1000:4200:6ace:bd71:da72:3b5f]) (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 A3EDF139059; Wed,  1 Nov 2017 13:46:15 -0700 (PDT)
To: ietf-announce@ietf.org, ietf@ietf.org
From: IAB Chair <iab-chair@iab.org>
Subject: Appointment of the RFC Series Editor
Message-ID: <cf3558d9-b4db-5ba8-2f6b-c84d5d7c0c4b@iab.org>
Date: Wed, 1 Nov 2017 13:46:15 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zDTBrBdHj7FyRkHV_YFSZhDuPak>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 20:46:16 -0000

The IAB is pleased to announce the re-appointment of Heather Flanagan to 
the position of RFC Series Editor.  The RSOC's recommendation of Heather 
noted her experience, education, skill, and the energy she brings to her 
position; the full IAB is happy to concur.

This appointment is for two years, with options for a further two 
years.  The IAB looks forward to continuing to work with Heather. We 
would also like to thank the RSOC for their work in conducting the 
search and the IAOC for finalizing the contractual details.

regards,

Ted Hardie
for the IAB


From nobody Wed Nov  1 14:14:17 2017
Return-Path: <akatlas@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 A045613F7C1 for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 14:14:15 -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 nDLal2uWL_OD for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 14:14:14 -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 AD6B413F715 for <ietf@ietf.org>; Wed,  1 Nov 2017 14:14:13 -0700 (PDT)
Received: by mail-wm0-x22b.google.com with SMTP id r68so7336470wmr.3 for <ietf@ietf.org>; Wed, 01 Nov 2017 14:14:13 -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=araV9/2km2xeu/J1D17b54YWuC2eW2ZXgPBrCV0tdjU=; b=dOCsloiAGFe4NendB18WRvdi6M97+sazECrxE4BCP8Rw8MrVcuJmsjjox9cuhwNoAG v3zbQfZJneE8amN2g+7q12fyqYEOi88RbNVxMIcwqr3UyR2g6lMfzWvXqdgQIoejvmnY nRSRqUeltS8XmJnCuYFwFajtHfjOYe3BKxLdsfrbtHuY3be4aQrC6OwR0XuMH8u8PT2y 2if5lLjHjMHUFQtW41GsdEyw+PDBQehwxyHsouqlD7LyvZg6gTVcVvDk3xto6+NBGXbZ HSckQitdXDtufG2tGjz6U5rs05MkJGNOabZLBOJG2S9MgOaPPTQHqpihWZ1pLktZeFLi hj1A==
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=araV9/2km2xeu/J1D17b54YWuC2eW2ZXgPBrCV0tdjU=; b=i5OPCRF4m51BPhvbhs8jupMPxECHXJQYsTyTTfkdhZMZi9mBhi8HinTqvHKfUcctqo X7F7j5laNMn8z1ovHtcx9lXkemyJqOc+AiMBk/czy9zFud0vqyISWu3peNctXIOA2eOH IyJyWprZKrlpxpr+Q+nLAYydwyLgtNuufNlg+Rhrzt26Xc06DrdaWOk8upuL4VxWxxqb OkDO/PTyVZjsZbNkKNoFi/AGZG5k+r9osk5XT/+52rC4wZxa76q7gIxoEIDUVQBFEdJd 172PxQ1AtcQy/CmlL0ztvPDcNsuSPU7lqNiKpMCPkhVXEG++kSKZwDr8MTeanFWthb4y nGtw==
X-Gm-Message-State: AMCzsaWVzn0CMYUFfXl31DYJoRMUMpMZ0UOk+zbPdEqfdLnbmf9B6qaX w0H4G04h5GEhaPwz7u0saEVHk5hxBDTL1CSjItVaorRI
X-Google-Smtp-Source: ABhQp+QvV0OC2U+6x6+4nbt+in7krdoIt3lOhU/aTAo4mdSEczRXiiMBX3fpsp7w/lWempPHnYSgigeK+xwfG6+2JNA=
X-Received: by 10.28.178.81 with SMTP id b78mr1158247wmf.157.1509570851965; Wed, 01 Nov 2017 14:14:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.150.10 with HTTP; Wed, 1 Nov 2017 14:14:11 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20171101132245.10d04f48@elandnews.com>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <6.2.5.6.2.20171101132245.10d04f48@elandnews.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, 1 Nov 2017 17:14:11 -0400
Message-ID: <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com>
Subject: Re: letting IETF build on top of Open Source technology
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11443e36651956055cf25ab0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KSQWzTGrHXGYy9mT1XONTwsMdPY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 21:14:15 -0000

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

Hi S.

On Wed, Nov 1, 2017 at 4:34 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Alia,
> At 08:02 PM 29-10-2017, Alia Atlas wrote:
>
>> After some discussion, my co-authors and I have written down a proposed
>> policy that would clearly and specifically allow standards-track RFCs to
>> have external non-SDO normative references.  It's not disallowed now - but
>> determining early when it is ok is unclear.
>>
>
> I read draft-atlas-external-normref-00.  "Opus" was an exception.  I
> don't think that it is a good example of referencing external code.
>

Agreed - the point was supposed to be that while referencing external code
might be reasonable in extremely limited situations (an algorithm or codec
and Opus was such an example), usually a clear specification is needed.

What is an "Open Source Organization"?  Are there examples of such
> organizations documenting IPR?
>

There are a number of projects under the Linux Foundation.  Taking a quick
glance at OpenNFV, I find
https://www.opnfv.org/about/bylaws-and-policies/ip-policy
which binds contributions to the Apache License.

While the motivation that I see for this proposed policy is to help make it
easier for the IETF and Open Source to collaboration, nothing in the policy
is intended to be restricted to Open Source Organizations or require a
clear definition of one.

Thanks for reading the draft!  I really do appreciate all the feedback :-)

Cheers,
Alia

Regards,
> S. Moonesamy
>

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

<div dir=3D"ltr">Hi S.<br><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Wed, Nov 1, 2017 at 4:34 PM, S Moonesamy <span dir=3D"ltr">&lt;=
<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf@elandsys.=
com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex">Hi Alia,<span class=3D"gmail-"><br>
At 08:02 PM 29-10-2017, Alia Atlas 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">
After some discussion, my co-authors and I have written down a proposed pol=
icy that would clearly and specifically allow standards-track RFCs to have =
external non-SDO normative references.=C2=A0 It&#39;s not disallowed now - =
but determining early when it is ok is unclear.<br>
</blockquote>
<br></span>
I read draft-atlas-external-normref-0<wbr>0.=C2=A0 &quot;Opus&quot; was an =
exception.=C2=A0 I don&#39;t think that it is a good example of referencing=
 external code.<br></blockquote><div><br></div><div>Agreed - the point was =
supposed to be that while referencing external code might be reasonable in =
extremely limited situations (an algorithm or codec and Opus was such an ex=
ample), usually a clear specification is needed.</div><div><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">
What is an &quot;Open Source Organization&quot;?=C2=A0 Are there examples o=
f such organizations documenting IPR?<br></blockquote><div><br></div><div>T=
here are a number of projects under the Linux Foundation.=C2=A0 Taking a qu=
ick glance at OpenNFV, I find</div><div><a href=3D"https://www.opnfv.org/ab=
out/bylaws-and-policies/ip-policy">https://www.opnfv.org/about/bylaws-and-p=
olicies/ip-policy</a><br></div><div>which binds contributions to the Apache=
 License.</div><div><br></div><div>While the motivation that I see for this=
 proposed policy is to help make it easier for the IETF and Open Source to =
collaboration, nothing in the policy is intended to be restricted to Open S=
ource Organizations or require a clear definition of one.</div><div><br></d=
iv><div>Thanks for reading the draft!=C2=A0 I really do appreciate all the =
feedback :-)</div><div><br></div><div>Cheers,</div><div>Alia=C2=A0</div><di=
v><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Regards,<br>
S. Moonesamy <br>
</blockquote></div><br></div></div>

--001a11443e36651956055cf25ab0--


From nobody Wed Nov  1 15:39:13 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 052E913F754; Wed,  1 Nov 2017 15:39:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level: 
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 jy2cHpstj7zQ; Wed,  1 Nov 2017 15:39:08 -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 A6CBB13F70B; Wed,  1 Nov 2017 15:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=34101; q=dns/txt; s=iport; t=1509575947; x=1510785547; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=ba78W3jvLhiuEwOKsmkJAEOmxHlAXunPfB9tdbHA1AM=; b=UMilimePh3iR0G/aRl29NbxLOLY1nd7AJnB223lVTeqYeUaHXUU6JPms DYZs8FL75GVCotDN/D2nUEC9WmtqQ+lAHClc7j1ne1S80WdGJmjhajm/Q f0kM+kBHhq4dqZ9K3w79+Uwpb7a9FDOoXhaRA8f8tYJUqHBsaZyNvzB+f s=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BUAwCYS/pZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzGBEjk1JwGDfIofdI96Jn2VR4IRBwMjhRgChT8YAQIBAQEBAQE?= =?us-ascii?q?BayiFHQEBAQECARoJUQUFCwsUBCAKAgJXBwwIAQGKFwgQqQGCJyaKbAEBAQEBB?= =?us-ascii?q?QEBAQEBAQEBARAPgy6BZRGDTSkLgkE1gyKBSAsGNoJ1gmEFijKOUokGhEKCI4E?= =?us-ascii?q?Bg2eJL4IVXoUjg2AkhxaKLII0iTOBOR84gWw0IQgdFUmCZQiCToIJQDeKMYJEA?= =?us-ascii?q?QEB?=
X-IronPort-AV: E=Sophos;i="5.44,331,1505779200";  d="asc'?scan'208,217";a="656716634"
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; 01 Nov 2017 22:39:01 +0000
Received: from [10.61.88.6] (ams3-vpn-dhcp6151.cisco.com [10.61.88.6]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id vA1Md1UR009293; Wed, 1 Nov 2017 22:39:01 GMT
Subject: Re: RTG-DIR review of draft-ietf-opsawg-mud-13
To: adrian@olddog.co.uk, rtg-ads@ietf.org
Cc: draft-ietf-opsawg-mud@ietf.org, ietf@ietf.org, rtg-dir@ietf.org
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk>
From: Eliot Lear <lear@cisco.com>
Message-ID: <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com>
Date: Wed, 1 Nov 2017 23:38:44 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="g6mCCiTVt5WPhsPjOOLc6hgOeukasiFBk"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ykSvI0anv3K8aldMQqWepgSe0Ew>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Nov 2017 22:39:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--g6mCCiTVt5WPhsPjOOLc6hgOeukasiFBk
Content-Type: multipart/mixed; boundary="O1CPM3d39gi4k7gq6Jj1Q2Q6wKg51CA9I";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: adrian@olddog.co.uk, rtg-ads@ietf.org
Cc: draft-ietf-opsawg-mud@ietf.org, ietf@ietf.org, rtg-dir@ietf.org
Message-ID: <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com>
Subject: Re: RTG-DIR review of draft-ietf-opsawg-mud-13
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk>
In-Reply-To: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk>

--O1CPM3d39gi4k7gq6Jj1Q2Q6wKg51CA9I
Content-Type: multipart/alternative;
 boundary="------------C2FA02EB029D14B419DF936D"
Content-Language: en-US

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

Hello Adrian,

Thanks again for your highly detailed review.=C2=A0 Please see below:


On 11/1/17 7:53 PM, Adrian Farrel wrote:
> Hello,=20
>
> I have been selected as the Routing Directorate reviewer for this draft=
=2E The
> Routing Directorate seeks to review all routing or routing-related draf=
ts as
> they pass through IETF last call and IESG review, and sometimes on spec=
ial
> request. The purpose of the review is to provide assistance to the Rout=
ing ADs.
> For more information about the Routing Directorate, please see
> http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir=20
>
> Although these comments are primarily for the use of the Routing ADs, i=
t would
> be helpful if you could consider them along with any other IETF Last Ca=
ll
> comments that you receive, and strive to resolve them through discussio=
n or by
> updating the draft.=20
>
> Document: draft-ietf-opsawg-mud-13.txt
>    Reviewer: Adrian Farrel=20
>    Review Date: 1 November 2017
>    IETF LC End Date: 7 November 2017
>    Intended Status: Standard Track
>
> Overview
>
>    Manufacturer Usage Descriptions (MUD) provide a means for elements o=
f
>    an IoT network to indicate what sorts of access and network=20
>    functionality they require in order to function properly.  The=20
>    emphasis of this document is on access control although the authors =

>    envision future extensions for "other aspects".
>
>    The document is a collection of bits and pieces to enable MUD: two
>    YANG modules, IPv4 and IPv6 DHCP options, an LLDP TLV, a URL suffix
>    specification, an X.509 certificate extension, and a means to sign a=
nd
>    verify the descriptions.
>
>    Some future work is listed, but I see no evidence that this work is =

>    actually anything more than a possibility: there are no drafts that =

>    appear to cover any additional MUD specifications.
>   =20
> Summary:=20
>
> I have some minor concerns about this document that I think should be
> resolved before publication. I have flagged one of these as a more
> serious issue, although I think it may be possible to solve with some
> 2119 language that governs expectations on implementations.
>
> The document was easy to read although the number of minor issues and
> nits in the early section suggests that the late-stage reviews were mor=
e
> focused on the YANG than the text.
>
> Adrian
>
> =3D=3D=3D
>
> Major Issues:=20
>
> I know I ranted about privacy before and the authors took some text I w=
rote as
> the basis of the privacy considerations, but I'm still worried that the=
 default
> will be that devices are MUD-enabled (good) and that users will not be
> protected. It would be sad if the user's only option is to reject MUD d=
evices
> (especially as they might not even know that the devices are MUD-enable=
d). More
> burble below, but it seems to me that we should make privacy-supporting=
 modes of
> operation at least the default, but possibly the only approach.

>
> Section 15 has...
>
>    The release of a MUD URL by a Thing reveals what the Thing is, and
>    provides an attacker with guidance on what vulnerabilities may be
>    present.
>
> Pleased to see this text: it was a security concern I had. Good to have=

> it flagged. However, the mitigation suggested 2 paragraphs later is a
> bit thin and sounds rather optional. I see how an implementer might
> take action, but what can a user do to protect their device? [...]


While this may not be a *perfect* solve for all of your concerns, I hope
you will find=C2=A0 the proposal below Good Enough.=C2=A0 Keep in mind th=
at we are
attempting to address a very broad set of devices with a large variety
of capabilities, from energy-harvesting devices that may never encrypt
(think a wall switch) to devices that have heaps of power and memory
(think robots).=C2=A0 Many of the devices have very limited privacy conce=
rns,
while others will have quite a few.=C2=A0 In addition, whatever capabilit=
ies
the device has must intersect the capabilities found in deployments.

With all that in mind, what I propose is the following:

  * Add text that RECOMMENDs that devices make use of TEAP when there
    may be privacy concerns and when it is available; and
  * In other cases where privacy may be a concern, we should RECOMMEND
    that a configuration option be provided, particularly when devices
    are designed to be mobile, which is where I think most of your
    concerns stem from.

At the moment, you should also consider that devices leak like sieves.=C2=
=A0
Bad guys can do a very good job of mapping devices they are looking for,
and aggregating that information.=C2=A0 So before you go reaching for tha=
t
button, get hold of WireShark :-(

And as you consider this as an issue, also consider the threat that you
face at home.=C2=A0 Every single one of those devices, if hacked, will
absolutely violate your privacy, to say the least.=C2=A0 The goal here is=
 to
stop that.


>
>
> =3D=3D=3D
>
> Minor Issues:=20
>
>
> The last call indicated a Downref to draft-ietf-netmod-acl-model. All w=
ell and
> good.
>
> idnits reports RFC 2818 as a Downref as well, but didn't appear in the =
last
> call.

It's on the right list.

>
> ---
>
> Abstract
>    Referring to "Things" is cute, but actually doesn't help the reader.=

>    Could you give a clue or two?
>
> BTW, the definition in 1.6 is a little thin and circular. A Thing is=20
> something to which you apply MUD, but what is it actually?

This is addressed, I think, in response to mnot's review.

>
> ---
>
> The Abstract says...
>
>    The initial focus is on access control.
>
> But the Introduction says...
>
>    Although this memo may seem to stress
>    access requirements, usage intent also consists of quality of servic=
e
>    needs a device may have.
>
> Please decide which you mean.

Right.=C2=A0 Mark caught this as well.
> ---
>
> Introduction
>
> OLD
>    The Internet has largely been constructed on general purpose
>    computers, those devices that may be used for a purpose that is
>    specified by those who buy the device.
> NEW
>    The Internet is largely constructed from general purpose computers.
>    These are devices that may be used for a purpose that is specified b=
y
>    those who buy the device.
>
> Although this is ambiguous and probably wrong: I think routers and=20
> switches probably form a part of the Internet, and I suspect they are
> somewhat specific to their use.

I think the participle we are looking for is "for".=C2=A0 Propose to chan=
ge
to that.

>
> ---
>
> Introduction
>
>    In the context of a smarter
>    device that has a built in Linux stack, it might be an integrator of=

>    that device.
>
> Is there something special about Linux?

That's meant as an example, nothing more.=C2=A0 To clarify, I propose to =
add
"For example" in the previous sentence.
>
> ---
>
> 1.5
> This section introduces the "MUD controller." It's unexplained.
> It could be helpful to pull section 1.6 up perhaps to 1.3.

Ok.

> ---
>
> There seems to be some overlap of terms and definitions in 1.5 and 1.6.=


Can you be more specific?

>
> ---
>
> 1.7 has a nice picture, thanks.
>
> But I note that the text describes a "web site" while the picture shows=

> a "file server".
>
> Similarly, the text has "network management system" while the picture
> has "MUD controller".

What I propose is to make the terms consistent, but added parentheticals
to remind people what those terms mean.
>
> ---
>
> 3.3 makes reference to "is supported" and 3.4 gives clarity to what=20
> that means.  Shouldn't this section also describe the meaning of this
> object when the Thang isn't supported?

That is actually discussed in Section 3.4 (these are short sections).

>
> ---
>
> 3.5 has me confused. Looks like a fine idea, but how does it work? A
> Thing reports the MUD URL, and the file that is pulled contains the
> systeminfo URL, and the info that is pulled contains the localised info=
=2E
> Have I got that right?
Yes.
>
> That means that the MUD URL has to include the correct systeminfo for
> the locality.  Presumably we're interested in the locality of the MUD
> controller.

The intent here is basically to allow for language tags to do their
thing through one level of indirection.=C2=A0 That doesn't require any
specific change to the URL itself.=C2=A0 I've included some text in respo=
nse
to Mark, but that text may further shift based on other suggestions Mark
may have.


>
> ---
>
> 16.2
>
> Something messed up here.
>
> We have
>
>    The IANA has allocated option 161 in the Dynamic Host Configuration
>    Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters registry
>    for the MUD DHCPv4 option.
>
>    IANA is requested to allocated the DHCPv4 and v6 options as specifie=
d
>    in Section 9.
>
> But section 9 has 161 and 112 explicitly mentioned.
>
> 116 is already in the registry, but presumably you have an IANA action
> to update the reference to this document when it becomes an RFC.
>
> 112 is also already in the DHCPv6 options registry.
> So you probably want to point at that instead of the current 2nd para.

Yes.=C2=A0 Bad edit.=C2=A0 Thanks.

>
> =3D=3D=3D=3D    =20
>
> Nits:=20
>
> Introduction
>
>    Please do NOT use random uppercase words in your text.  There's NO
>    need: the readers are no more stupid than the average reader of an
>    RFC.
>
> Ditto 3.4, 3.6

Sorry- I didn't parse this.
>
> ---
>
> Introduction
>
>    The key points are that the device itself is expected
>    to serve a limited purpose,
>
> I think you mean s/expected/intended/

How about "assumed"?

> ---
>
> Introduction
>
>    The intent of MUD is to solve for the following problems:
>
> d/for/
>
> Although the list that follows is not a list of problems. So, perhaps,
>
>    The intent of MUD is to provide the following function:

s/following function/following/ ?
>
> ---
>
> Introduction
>
>    o  Provide for a means to scale network policies to the ever-
>       increasing number types of devices in the network.
>
> d/for/

ok

> s/types/of types/

right.

>
> ---
>
> Introduction
>
>       Provide a means to address at least some vulnerabilities in a way=

>       that is faster than it might take to update systems.
>
> s/than/than the time/
>
> ---
>
> Introduction
>
>    o  A classifier that a device emits that can be used to locate a
>       description;
>
> Classifier or classification?

Classifier.
>
> ---
>
> OLD
> 1.1.  What MUD doesn't do
> NEW
> 1.1.  What MUD Doesn't Do

ok
>
> ---
>
> Section 1.1
>
>    No matter how good a MUD-enabled network is, it will never replace
>    the need for manufacturers to patch vulnerabilities.  It may,
>    however, provide network administrators with some additional
>    protection when those vulnerabilities exist.
>
> Does this paragraph belong in this section? Seems to say what MUD does,=

> not what MUD doesn't do.
>
> Maybe flip the order of presentation?...
>
>    MUD may provide network administrators with some protection when
>    vulnerabilities exist, however, no matter how good a MUD-enabled=20
>    network is, it will never replace the need for manufacturers to=20
>    patch vulnerabilities.=20

How about:

Although MUD can provide network administrators with some additional
protection when=C2=A0=C2=A0=C2=A0 device vulnerabilities exist, it will n=
ever replace the
need for manufacturers to patch vulnerabilities.
>
> ---
>
> 1.2
>
> s/an app on smart phone/an application on a smart phone/

ok
> ---
>
> 1.4 para 2
> Might be worth splitting this into bullets

ok
>
> ---
>
> 1.5
> s/configuration of is/configuration is/

ok
>
> ---
>
> 2.
>
> s/only"accept"/only "accept"/

ok
>
> ---
>
> I think [I-D.ietf-netmod-rfc6087bis] may be used in a normative way to
> explain the notation used in this document.

I think this is broken off to another draft
(draft-ietf-netmod-yang-tree-diagrams).

>
> ---
>
> 3.
>    Note that in this section, when we use the term "match" we are
>    referring to the ACL model "matches" node, and thus returns positive=

>    such that an action should be applied.
>
> Is that English? I know what it means, but not what it says.

New text in response to review.=C2=A0 I don't think it's English either.=C2=
=A0 I
think a line was clipped accidentally.=C2=A0 I propose to delete everythi=
ng
after the comma.

>
> ---
>
> 3.1
>
> s/containers indicate/containers indicates/

Good catch.

> ---
>
> 3.1
>
>    [I-D.ietf-netmod-acl-model] describes access-lists but does not
>    attempt to indicate where they are applied as that is handled
>    elsewhere in a configuration
>
> "a configuration file?" "operation"? "in configuration information"?

This text requires a small change, anyway.

>
> ---
>
> 3.8
>
> Say that this is a null-valued node
ok
> ---
>
> 3.11
> s/mud/MUD/
>
>

Ok.


And thanks again!

Eliot

--------------C2FA02EB029D14B419DF936D
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=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hello Adrian,</p>
    <p>Thanks again for your highly detailed review.=C2=A0 Please see bel=
ow:<br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">On 11/1/17 7:53 PM, Adrian Farrel
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">Hello,=20

I have been selected as the Routing Directorate reviewer for this draft. =
The
Routing Directorate seeks to review all routing or routing-related drafts=
 as
they pass through IETF last call and IESG review, and sometimes on specia=
l
request. The purpose of the review is to provide assistance to the Routin=
g ADs.
For more information about the Routing Directorate, please see
<a class=3D"moz-txt-link-freetext" href=3D"http://trac.tools.ietf.org/are=
a/rtg/trac/wiki/RtgDir">http://trac.tools.ietf.org/area/rtg/trac/wiki/Rtg=
Dir</a>=20

Although these comments are primarily for the use of the Routing ADs, it =
would
be helpful if you could consider them along with any other IETF Last Call=

comments that you receive, and strive to resolve them through discussion =
or by
updating the draft.=20

Document: draft-ietf-opsawg-mud-13.txt
   Reviewer: Adrian Farrel=20
   Review Date: 1 November 2017
   IETF LC End Date: 7 November 2017
   Intended Status: Standard Track

Overview

   Manufacturer Usage Descriptions (MUD) provide a means for elements of
   an IoT network to indicate what sorts of access and network=20
   functionality they require in order to function properly.  The=20
   emphasis of this document is on access control although the authors=20
   envision future extensions for "other aspects".

   The document is a collection of bits and pieces to enable MUD: two
   YANG modules, IPv4 and IPv6 DHCP options, an LLDP TLV, a URL suffix
   specification, an X.509 certificate extension, and a means to sign and=

   verify the descriptions.

   Some future work is listed, but I see no evidence that this work is=20
   actually anything more than a possibility: there are no drafts that=20
   appear to cover any additional MUD specifications.
  =20
Summary:=20

I have some minor concerns about this document that I think should be
resolved before publication. I have flagged one of these as a more
serious issue, although I think it may be possible to solve with some
2119 language that governs expectations on implementations.

The document was easy to read although the number of minor issues and
nits in the early section suggests that the late-stage reviews were more
focused on the YANG than the text.

Adrian

=3D=3D=3D

Major Issues:=20

I know I ranted about privacy before and the authors took some text I wro=
te as
the basis of the privacy considerations, but I'm still worried that the d=
efault
will be that devices are MUD-enabled (good) and that users will not be
protected. It would be sad if the user's only option is to reject MUD dev=
ices
(especially as they might not even know that the devices are MUD-enabled)=
=2E More
burble below, but it seems to me that we should make privacy-supporting m=
odes of
operation at least the default, but possibly the only approach.</pre>
    </blockquote>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

Section 15 has...

   The release of a MUD URL by a Thing reveals what the Thing is, and
   provides an attacker with guidance on what vulnerabilities may be
   present.

Pleased to see this text: it was a security concern I had. Good to have
it flagged. However, the mitigation suggested 2 paragraphs later is a
bit thin and sounds rather optional. I see how an implementer might
take action, but what can a user do to protect their device? [...]</pre>
    </blockquote>
    <br>
    <br>
    While this may not be a *perfect* solve for all of your concerns, I
    hope you will find=C2=A0 the proposal below Good Enough.=C2=A0 Keep i=
n mind
    that we are attempting to address a very broad set of devices with a
    large variety of capabilities, from energy-harvesting devices that
    may never encrypt (think a wall switch) to devices that have heaps
    of power and memory (think robots).=C2=A0 Many of the devices have ve=
ry
    limited privacy concerns, while others will have quite a few.=C2=A0 I=
n
    addition, whatever capabilities the device has must intersect the
    capabilities found in deployments.<br>
    <br>
    With all that in mind, what I propose is the following:<br>
    <ul>
      <li>Add text that RECOMMENDs that devices make use of TEAP when
        there may be privacy concerns and when it is available; and</li>
      <li>In other cases where privacy may be a concern, we should
        RECOMMEND that a configuration option be provided, particularly
        when devices are designed to be mobile, which is where I think
        most of your concerns stem from.</li>
    </ul>
    <p>At the moment, you should also consider that devices leak like
      sieves.=C2=A0 Bad guys can do a very good job of mapping devices th=
ey
      are looking for, and aggregating that information.=C2=A0 So before =
you
      go reaching for that button, get hold of WireShark :-(<br>
    </p>
    <p>And as you consider this as an issue, also consider the threat
      that you face at home.=C2=A0 Every single one of those devices, if
      hacked, will absolutely violate your privacy, to say the least.=C2=A0=

      The goal here is to stop that.<br>
    </p>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">


=3D=3D=3D

Minor Issues:=20


The last call indicated a Downref to draft-ietf-netmod-acl-model. All wel=
l and
good.

idnits reports RFC 2818 as a Downref as well, but didn't appear in the la=
st
call.</pre>
    </blockquote>
    <br>
    It's on the right list.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

Abstract
   Referring to "Things" is cute, but actually doesn't help the reader.
   Could you give a clue or two?

BTW, the definition in 1.6 is a little thin and circular. A Thing is=20
something to which you apply MUD, but what is it actually?</pre>
    </blockquote>
    <br>
    This is addressed, I think, in response to mnot's review.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

The Abstract says...

   The initial focus is on access control.

But the Introduction says...

   Although this memo may seem to stress
   access requirements, usage intent also consists of quality of service
   needs a device may have.

Please decide which you mean.
</pre>
    </blockquote>
    <br>
    Right.=C2=A0 Mark caught this as well.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">
---

Introduction

OLD
   The Internet has largely been constructed on general purpose
   computers, those devices that may be used for a purpose that is
   specified by those who buy the device.
NEW
   The Internet is largely constructed from general purpose computers.
   These are devices that may be used for a purpose that is specified by
   those who buy the device.

Although this is ambiguous and probably wrong: I think routers and=20
switches probably form a part of the Internet, and I suspect they are
somewhat specific to their use.</pre>
    </blockquote>
    <br>
    I think the participle we are looking for is "for".=C2=A0 Propose to
    change to that.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

Introduction

   In the context of a smarter
   device that has a built in Linux stack, it might be an integrator of
   that device.

Is there something special about Linux?</pre>
    </blockquote>
    <br>
    That's meant as an example, nothing more.=C2=A0 To clarify, I propose=
 to
    add "For example" in the previous sentence.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

1.5
This section introduces the "MUD controller." It's unexplained.
It could be helpful to pull section 1.6 up perhaps to 1.3.
</pre>
    </blockquote>
    <br>
    Ok. <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">
---

There seems to be some overlap of terms and definitions in 1.5 and 1.6.</=
pre>
    </blockquote>
    <br>
    Can you be more specific?<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

1.7 has a nice picture, thanks.

But I note that the text describes a "web site" while the picture shows
a "file server".

Similarly, the text has "network management system" while the picture
has "MUD controller".</pre>
    </blockquote>
    <br>
    What I propose is to make the terms consistent, but added
    parentheticals to remind people what those terms mean.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

3.3 makes reference to "is supported" and 3.4 gives clarity to what=20
that means.  Shouldn't this section also describe the meaning of this
object when the Thang isn't supported?</pre>
    </blockquote>
    <br>
    That is actually discussed in Section 3.4 (these are short
    sections).<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

3.5 has me confused. Looks like a fine idea, but how does it work? A
Thing reports the MUD URL, and the file that is pulled contains the
systeminfo URL, and the info that is pulled contains the localised info.
Have I got that right?</pre>
    </blockquote>
    Yes.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

That means that the MUD URL has to include the correct systeminfo for
the locality.  Presumably we're interested in the locality of the MUD
controller.</pre>
    </blockquote>
    <br>
    The intent here is basically to allow for language tags to do their
    thing through one level of indirection.=C2=A0 That doesn't require an=
y
    specific change to the URL itself.=C2=A0 I've included some text in
    response to Mark, but that text may further shift based on other
    suggestions Mark may have.<br>
    <br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

16.2

Something messed up here.

We have

   The IANA has allocated option 161 in the Dynamic Host Configuration
   Protocol (DHCP) and Bootstrap Protocol (BOOTP) Parameters registry
   for the MUD DHCPv4 option.

   IANA is requested to allocated the DHCPv4 and v6 options as specified
   in Section 9.

But section 9 has 161 and 112 explicitly mentioned.

116 is already in the registry, but presumably you have an IANA action
to update the reference to this document when it becomes an RFC.

112 is also already in the DHCPv6 options registry.
So you probably want to point at that instead of the current 2nd para.</p=
re>
    </blockquote>
    <br>
    Yes.=C2=A0 Bad edit.=C2=A0 Thanks.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

=3D=3D=3D=3D    =20

Nits:=20

Introduction

   Please do NOT use random uppercase words in your text.  There's NO
   need: the readers are no more stupid than the average reader of an
   RFC.

Ditto 3.4, 3.6</pre>
    </blockquote>
    <br>
    Sorry- I didn't parse this.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

Introduction

   The key points are that the device itself is expected
   to serve a limited purpose,

I think you mean s/expected/intended/
</pre>
    </blockquote>
    <br>
    How about "assumed"?<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">
---

Introduction

   The intent of MUD is to solve for the following problems:

d/for/</pre>
    </blockquote>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

Although the list that follows is not a list of problems. So, perhaps,

   The intent of MUD is to provide the following function:</pre>
    </blockquote>
    <br>
    s/following function/following/ ?<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

Introduction

   o  Provide for a means to scale network policies to the ever-
      increasing number types of devices in the network.

d/for/</pre>
    </blockquote>
    <br>
    ok<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">
s/types/of types/</pre>
    </blockquote>
    <br>
    right.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

Introduction

      Provide a means to address at least some vulnerabilities in a way
      that is faster than it might take to update systems.

s/than/than the time/

---

Introduction

   o  A classifier that a device emits that can be used to locate a
      description;

Classifier or classification?</pre>
    </blockquote>
    <br>
    Classifier.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

OLD
1.1.  What MUD doesn't do
NEW
1.1.  What MUD Doesn't Do</pre>
    </blockquote>
    <br>
    ok<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

Section 1.1

   No matter how good a MUD-enabled network is, it will never replace
   the need for manufacturers to patch vulnerabilities.  It may,
   however, provide network administrators with some additional
   protection when those vulnerabilities exist.

Does this paragraph belong in this section? Seems to say what MUD does,
not what MUD doesn't do.

Maybe flip the order of presentation?...

   MUD may provide network administrators with some protection when
   vulnerabilities exist, however, no matter how good a MUD-enabled=20
   network is, it will never replace the need for manufacturers to=20
   patch vulnerabilities. </pre>
    </blockquote>
    <br>
    How about:<br>
    <br>
    Although MUD can provide network administrators with some additional<=
br>
    protection when=C2=A0=C2=A0=C2=A0 device vulnerabilities exist, it wi=
ll never
    replace the<br>
    need for manufacturers to patch vulnerabilities.<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

1.2

s/an app on smart phone/an application on a smart phone/
</pre>
    </blockquote>
    <br>
    ok<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">
---

1.4 para 2
Might be worth splitting this into bullets</pre>
    </blockquote>
    <br>
    ok<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

1.5
s/configuration of is/configuration is/</pre>
    </blockquote>
    <br>
    ok<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

2.

s/only"accept"/only "accept"/</pre>
    </blockquote>
    <br>
    ok<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

I think [I-D.ietf-netmod-rfc6087bis] may be used in a normative way to
explain the notation used in this document.</pre>
    </blockquote>
    <br>
    I think this is broken off to another draft
    (draft-ietf-netmod-yang-tree-diagrams).<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

3.
   Note that in this section, when we use the term "match" we are
   referring to the ACL model "matches" node, and thus returns positive
   such that an action should be applied.

Is that English? I know what it means, but not what it says.</pre>
    </blockquote>
    <br>
    New text in response to review.=C2=A0 I don't think it's English eith=
er.=C2=A0
    I think a line was clipped accidentally.=C2=A0 I propose to delete
    everything after the comma.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

3.1

s/containers indicate/containers indicates/
</pre>
    </blockquote>
    <br>
    Good catch.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">
---

3.1

   [I-D.ietf-netmod-acl-model] describes access-lists but does not
   attempt to indicate where they are applied as that is handled
   elsewhere in a configuration

"a configuration file?" "operation"? "in configuration information"?</pre=
>
    </blockquote>
    <br>
    This text requires a small change, anyway.<br>
    <br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">

---

3.8

Say that this is a null-valued node
</pre>
    </blockquote>
    ok<br>
    <blockquote type=3D"cite"
      cite=3D"mid:01d501d35342$b90d7450$2b285cf0$@olddog.co.uk">
      <pre wrap=3D"">
---

3.11
s/mud/MUD/


</pre>
    </blockquote>
    <br>
    Ok.<br>
    <br>
    <br>
    And thanks again!<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------C2FA02EB029D14B419DF936D--

--O1CPM3d39gi4k7gq6Jj1Q2Q6wKg51CA9I--

--g6mCCiTVt5WPhsPjOOLc6hgOeukasiFBk
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

iQEcBAEBCAAGBQJZ+kz1AAoJEIe2a0bZ0nozgsIIAMGFZv6gq/PhWas3++8eNwZ6
GrujALFjPA8ZexSjL1olgGK/ewLZ9uXRV8rEyVrNTEUB1NEq1ZQq+bL+RndkzMfK
VrLHZcFayFZ/YUy1Et6/8DkvbHW4CeVHdRtDEpE++hmCFRoF8WwpImtNK4r9FLJV
HQxlw5SEKF+BzfL9xnpxbuoHh2z7yMMFUcv5lb6gxptQLr/e5FbKAcn2w4axpZC3
s63tiCA16Ai7dYx/7NpxDxv8orrCoKjtB/ChOWrHZzPj0q3KjPQWDPYWUGo0/9p4
AWABI4cfb5NkmtaoptugVaPKzeuqG71ikCI9ojT2y6uwozwaZ+4D6yzrIl5e+hY=
=6LS+
-----END PGP SIGNATURE-----

--g6mCCiTVt5WPhsPjOOLc6hgOeukasiFBk--


From nobody Wed Nov  1 17:02:14 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 A077C13FB8A; Wed,  1 Nov 2017 17:02:12 -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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-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 sdlSc3-Me2HJ; Wed,  1 Nov 2017 17:02:10 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 046A8138BD6; Wed,  1 Nov 2017 17:02:09 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id vA2025eS005850; Thu, 2 Nov 2017 00:02:05 GMT
Received: from 950129200 (254.196.113.87.dyn.plus.net [87.113.196.254]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id vA201v2T005817 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Nov 2017 00:02:04 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Eliot Lear'" <lear@cisco.com>, <rtg-ads@ietf.org>
Cc: <draft-ietf-opsawg-mud@ietf.org>, <ietf@ietf.org>, <rtg-dir@ietf.org>
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk> <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com>
In-Reply-To: <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com>
Subject: RE: RTG-DIR review of draft-ietf-opsawg-mud-13
Date: Thu, 2 Nov 2017 00:01:55 -0000
Message-ID: <022901d3536d$d01d7b10$70587130$@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
Content-Language: en-gb
Thread-Index: AQHbXiOVWYUGr+virfAy7t490kIJlgFDRd+PouXvjKA=
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23434.003
X-TM-AS-Result: No--25.587-10.0-31-10
X-imss-scan-details: No--25.587-10.0-31-10
X-TMASE-MatchedRID: yebcs53SkkCnykMun0J1wj4PYxsTKj6OPllq4+7Psp9LjXXGQy6nlCU7 43HF3fJ1O2sF32mXbnzfneWgb0wCfhvMQPGNwEh5nbUZkYTzXIZT4DtiSkMnWHe9QDr8+LTcLHN FiwmJRq9g9QVv4yJoozMqW8WukwCx6xj9tplxe1otR8fVMTBo3eBgp+G3IXxrasEfs27jsmF33U cFnsV9K2Aa4EJHd+lhy2r0pKo9mL2BmL85GH6eoJU7Bltw5qVLLi2dwKiMR9zoN8DSoota+bJVv 13dZNfHed0d4sqKDsNW6DYmWGhh3b0LBwJblWbCiFoorQjboWkt9SM1xCCZI9qqof+gfD6RXdBQ Y13RVu+fHoYNv/tRVd0iK4aOzykGr4Tjl93LJlctMfCdg6KRDdSqEluSYtV7ZD2MRV9hScnGdRf PKx6LHGd012aNXJXONuVfhyZ1UoR/mtiXLG/iqwArNgt5xpQYQPCPzycuBFNrH7R0RhorDICjHI wimOiw41ajEsPwj9r4L3Nr51seQUHQ/pYAwhs64NAJeq9IDSxBAihwNc9u51c/CedjlcvkkJfLp HarHP0ExaFjjiqBlEBd8jXb7PkJVOdT7lcCJT6VSBCoZUyqbEH7wsB5444wGNAPebYwJ/v9aPr9 xdwJWeRMOKt5mOY0mpwWqsTbqy9EbxUbCvHWy7xygpRxo469xNK79ogfIKlO2MZoFipNWxB3/5R 3B1LBPDsVTI/DsCqZ+/AHXHSuX98B+f+wv7x4et6HZsHsM79G/JUd7BvSQp3BT+pdjEe8wr3tCV Ik66rR8zboG6RI6n0EqyYQ2mty6fLaoi+ilkSeAiCmPx4NwFkMvWAuahr8+gD2vYtOFhgqtq5d3 cxkNQP90fJP9eHt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nf3g65lYDyi0UMcvmpIyoQd2hgw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 00:02:13 -0000

This looks really good, Eliot. Thanks for being so responsive and =
positive to my peculiar brand of paranoia and pedantry.

Just a few bits of discussion remain...

>> I know I ranted about privacy before and the authors took some text I =
wrote
>> as the basis of the privacy considerations, but I'm still worried =
that the default
>> will be that devices are MUD-enabled (good) and that users will not =
be
>> protected. It would be sad if the user's only option is to reject MUD =
devices
>> (especially as they might not even know that the devices are =
MUD-enabled).
>> More burble below, but it seems to me that we should make =
privacy-supporting
>> modes of operation at least the default, but possibly the only =
approach.
>>
>> Section 15 has...
>>
>>   The release of a MUD URL by a Thing reveals what the Thing is, and
>>   provides an attacker with guidance on what vulnerabilities may be
>>   present.
>>
>> Pleased to see this text: it was a security concern I had. Good to =
have
>> it flagged. However, the mitigation suggested 2 paragraphs later is a
>> bit thin and sounds rather optional. I see how an implementer might
>> take action, but what can a user do to protect their device? [...]
>
> While this may not be a *perfect* solve for all of your concerns, I =
hope
> you will find  the proposal below Good Enough.  Keep in mind that we
> are attempting to address a very broad set of devices with a large =
variety
> of capabilities, from energy-harvesting devices that may never encrypt
> (think a wall switch) to devices that have heaps of power and memory
> (think robots).  Many of the devices have very limited privacy =
concerns,
> while others will have quite a few.  In addition, whatever =
capabilities the
> device has must intersect the capabilities found in deployments.
>
> With all that in mind, what I propose is the following:
> =E2=80=A2 Add text that RECOMMENDs that devices make use of TEAP when =
there
>     may be privacy concerns and when it is available; and
> =E2=80=A2 In other cases where privacy may be a concern, we should =
RECOMMEND
>    that a configuration option be provided, particularly when devices =
are
>    designed to be mobile, which is where I think most of your concerns
>    stem from.

This is getting gooder. Thanks.
Even when the MUD controller is on the premises (the not mobile case), =
it contacts
an offsite file server, and that act is visible.
Suppose my Hi-Fi uses MUD - now you know that my house is worth robbing.
Suppose my intruder alarm uses MUD - now you know what security system I =
have.

Of course, when the MUD controller is remote (the mobile case), it's all =
even more worrying.

I know you are trying to trade between perfect and getting something =
that will be implemented and so make the world a somewhat better place. =
But just recall that someone implemented those devices that "leak like =
sieves" and those folk are unlikely to see a Recommendation as anything =
like a strong hint.

Well, I'm not in a position to block the whole effort, and I'm not =
enough of an expert to suggest a solution to my concern that works for =
all types of device.

>> There seems to be some overlap of terms and definitions in 1.5 and =
1.6.
>
> Can you be more specific?

1.5 and 1.6 both have "manufacturer".
1.5 has "controller" and 1.6 has "MUD controller".
The definitions don't match.

>> 3.5 has me confused. Looks like a fine idea, but how does it work? A
>> Thing reports the MUD URL, and the file that is pulled contains the
>> systeminfo URL, and the info that is pulled contains the localised =
info.
>> Have I got that right?
> Yes.
>
>> That means that the MUD URL has to include the correct systeminfo for
>> the locality.  Presumably we're interested in the locality of the MUD
>> controller.
>
> The intent here is basically to allow for language tags to do their =
thing
> through one level of indirection.  That doesn't require any specific =
change
> to the URL itself.  I've included some text in response to Mark, but =
that
> text may further shift based on other suggestions Mark may have.

I'm missing something, but that's OK, I don't have to understand =
something for it to be right :-)

So long as it is possible for the MUD Controller to be in one locale and =
the MUD Server in another and all the bits to work right, I'm happy.

>> Introduction
>>
>>   Please do NOT use random uppercase words in your text.  There's NO
>>   need: the readers are no more stupid than the average reader of an
>>   RFC.
>>
>> Ditto 3.4, 3.6
>
> Sorry- I didn't parse this.

Sorry I'm being sassy.

I mean, please don't capitalise for emphasis. Just limit yourself to =
2119 capitalisation.

>> Introduction
>>
>>   The key points are that the device itself is expected
>>   to serve a limited purpose,
>>
>> I think you mean s/expected/intended/
>
> How about "assumed"?

We're both being overly passive. Who has the =
expectation/intention/assumption?

By "intended" I meant "intended by the manufacturer".
So, actually, any one of the three words is fine, if you can attribute =
the verb to someone.

>> Introduction
>>
>>   o  A classifier that a device emits that can be used to locate a
>>      description;
>>
>> Classifier or classification?
>
> Classifier.

Oh.

A "classifier" is a person or thing that classifies.
I don't think the device emits a thing or a person :-)
I think it emits a piece of information that allows the device to be =
classified.=20


Cheers,
Adrian


From nobody Wed Nov  1 19:35:13 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 88ADF13F81E for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 19:35:11 -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.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 nsdlGeKS8MaG for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 19:35:09 -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 BC8AE13F570 for <ietf@ietf.org>; Wed,  1 Nov 2017 19:35:09 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id n82so7256281oig.3 for <ietf@ietf.org>; Wed, 01 Nov 2017 19:35:09 -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=NhLO3OuSB2lBLYDxQ/l2bB2OAAwUxZTx9aFNhb5bhak=; b=j/1kJso5dKeRfEyYjHJJwSwAU9f+dJF6av/v5NCd8X+vhDuOiHVZoNalFbmbfAza9I H3445mbmOyYPoyyLiKOAD4rLPvh9vadgCSIi4ry2eGVDBA9BLB/c5mZa7R24GjegbHD1 +EKRZtFSkuImlVGum6ZENW4NO+YB57NX/b0nut/2tbtD/NlX18j1LrUK8U/Pcexp+sdA iNVqAgAOyBMbKDrJgGmAnpSFhXgGFl0Q5jP/uaMnmPhLq3YmqY6QZzl3DPo4Kp8QGqeB 1DiFvQB15AFKm+n43qSa+vql4+fo5+0WyEs/wwwNNushcMjdeFABrTwlft9yBUaU/7uS wEpQ==
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=NhLO3OuSB2lBLYDxQ/l2bB2OAAwUxZTx9aFNhb5bhak=; b=B1jUtU9k+7yxb8Hhqqd+vk/yOEBzG7jcEBZuoNwCXFJFzKD8Fyy+EiFvSSuTGD/V2S 016iJECGe/Y05BmTq1kCNS9ux2d0l2H8qjA38j/oiN3ecS331fB2g5E1Kh7+fq1GaGJH qm9evIjrIhMtdZzMg4MEzakDGpoSM9+AEIVO+AvtjHMuZwxZK4TOdTEyJ1l7tXFAI/fF qdauwPm7FZQz4KP4iEsF+znL/AtU2LwNJzFJByA9jzGX76sjd4ksTBNWSo4Gg4ILYdQz 7fcktyXun8yYH1UofVzJ6LBRNWiczB8edE5yh42HZjeK+qfK6QOqIsbwfsNkKMz4twWG rQnQ==
X-Gm-Message-State: AMCzsaVh2CQjvGimcu1Z+KZ5MPG+nqQ//5FxYVR9Qn2p/NzF619gI67G Fx5Uk1BhePkAeitVj1X1cQIkGEicm3WbfZADphk=
X-Google-Smtp-Source: ABhQp+QfdlzkLkfRNzvHyPbtCfHIBT9Nu4L40bBSvtbRKlO4V5oCklcZA2yfvX8itlrqZDukyl6DFUE9u8SgQLXfdYM=
X-Received: by 10.202.172.85 with SMTP id v82mr1105676oie.432.1509590109034; Wed, 01 Nov 2017 19:35:09 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.80.42 with HTTP; Wed, 1 Nov 2017 19:35:08 -0700 (PDT)
In-Reply-To: <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <6.2.5.6.2.20171101132245.10d04f48@elandnews.com> <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 1 Nov 2017 22:35:08 -0400
X-Google-Sender-Auth: oMW09Nn6b_Df3vFxcGyGUsvC_PY
Message-ID: <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com>
Subject: Re: letting IETF build on top of Open Source technology
To: Alia Atlas <akatlas@gmail.com>
Cc: S Moonesamy <sm+ietf@elandsys.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5UzMFLHEr6Q09H2HXRBmsS0ZOgw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 02:35:11 -0000

My specifications are my code.

If you look at any of the protocol specifications for the Mesh, you
will find a reference section in the back that is generated directly
from the schema and examples taken from running code generated from
the same schema. And the running code used to generate the examples is
the same as the reference code.

http://www.prismproof.org/Resources/

The tool set is also open source though documenting this has been a
lower priority for me than finishing the Mesh.

http://www.prismproof.org/Code/standard/html/12cd4543-7aeb-41b3-81cf-4f828b2f76d7.htm

The original point of doing this was accuracy rather than saving time.
But it certainly saves me a lot of time now I have the system working.
I am currently working on generating examples for the Web site as
well.

At present, the code generators create C# code but they have generated
C in the past. I will probably return to that after the current code
set is complete.


From nobody Wed Nov  1 20:30:16 2017
Return-Path: <zhencao.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 6AF4A13F843; Wed,  1 Nov 2017 20:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 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, GB_AFFORDABLE=1, 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 P06Rev-XI3NW; Wed,  1 Nov 2017 20:30:06 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c: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 B751C13F418; Wed,  1 Nov 2017 20:30:03 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id x65so2735150vkx.1; Wed, 01 Nov 2017 20:30:03 -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=pXOw+4Uqi6ETPPK9U3k/sT7pL+6pMIiyLGqr93kd0m8=; b=O8C36P1lX6bZQ/SdyKS4y8punv7tpUr45DCC7nV5H5Lo4XaLUBQicIv2KgTq4PnHNt ZhcYJAx8QdX5IjmKB225BBX132TBcJ1IxtjNSEeBuQnsIcyJU8QTzXq99HRIk0rfA5Vi 6XKAosJxGrY1eW4btN/eXfqA7pBQ5Wbluht2Ffqr5+Qg8wjsuitZdFbneumx61L1o8hU XfydIcL5VTG2Ryg4R0w+UjDWBc/9T+1c1bOayPVu877QzKrW47ML+wDHUsA/OpNsqgr7 SCn+g0S3X5XPGrYUcCK6cjOAkHtxziS0vAcE1FSRrQZpuHDd8ZEiJfHyItvM0QD6tjiU rtPw==
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=pXOw+4Uqi6ETPPK9U3k/sT7pL+6pMIiyLGqr93kd0m8=; b=cSYtG6V+vUk1P4QS/Oz4mwnjK//w+kKgmpTibB9AfYDy0DTnj5r1JrdXVssaxtVf4W TGyvBZ4DNVoEg30nCTE+944Z6alGQBypB+E6hBbfoMgOYR3gp8/fAAFOT9I9KaPpXWYT kejLawPbG3oSU+wJmSwm4jnLvQ1PF4Gn3YLptR72XW9m8KwiNpez5rS7klVfsSqfmhzg ARdMDe1tbWCqbe7V9iB5GyT9hbh2FIEK0H1EzEF+0P6duy+C1SJ3kgyg0BMoA+pL1LrV 501SQrYeu4Xy/+b96RWxLO5xcaf5cg6h5JiirqqhPUScp+IYEMoF5ZHp1LYolsJu/56d LEsA==
X-Gm-Message-State: AMCzsaVGyfihT1VwcPw+Lx23FBef64MOc7dBd6DnNzCOQGCe+D1afk/8 ypulp2YMnLjJWJR83HS+8eX/q81jiP1hKF3GmCA=
X-Google-Smtp-Source: ABhQp+Th8aEdcDAh/sEokSu62Tg/rMOEz38CHmDIJV+yE+Fwzr3k8E6hZJS4eGANwN1/Krp43i3NChuRJLh9dRYLS4E=
X-Received: by 10.31.70.133 with SMTP id t127mr1787975vka.100.1509593402646; Wed, 01 Nov 2017 20:30:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.84.143 with HTTP; Wed, 1 Nov 2017 20:30:02 -0700 (PDT)
In-Reply-To: <1cfea94b1690409595b243f014083bf1@XCH-ALN-003.cisco.com>
References: <150952203714.25993.17333137226492207681@ietfa.amsl.com> <1cfea94b1690409595b243f014083bf1@XCH-ALN-003.cisco.com>
From: Zhen Cao <zhencao.ietf@gmail.com>
Date: Thu, 2 Nov 2017 11:30:02 +0800
Message-ID: <CAFxP68xsGG1K4Q0qfQL6VG4Qmth+GVv7qdDWcTjP20K9y9tehg@mail.gmail.com>
Subject: Re: [Int-dir] Intdir early review of draft-ietf-dhc-rfc3315bis-10
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: "int-dir@ietf.org" <int-dir@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-rfc3315bis.all@ietf.org" <draft-ietf-dhc-rfc3315bis.all@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SAZ0I5O2jZpjE9swMgTJkL7vNY0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 03:30:08 -0000

Hi Bernie,

> First, thanks for the Int-Dir review.
My pleasure as always.

>
> Regarding your comment, the cases where both MRC and MRD are zero is for =
a Solicit and Information-Request. And, for those particular cases, the cli=
ent should probably retransmit "forever" at a hopefully low rate (SOL_MAX_R=
T and INF_MAX_RT are 3600 seconds*) to locate a  DHCP server. This of cours=
e depends on the RA M & O bits (indicating a DHCP server is available) or t=
he manual configuration of the client (to explicitly run DHCP).

Then depending on this information, it is up to you to see if there is
a need of an affordable better description than the current text.

Cheers,
zhen

>
> * - RFC 3315 used 120 seconds for these values, but that was updated by R=
FC 7083.
>
> - Bernie
>
> -----Original Message-----
> From: Int-dir [mailto:int-dir-bounces@ietf.org] On Behalf Of Zhen Cao
> Sent: Wednesday, November 01, 2017 3:41 AM
> To: int-dir@ietf.org
> Cc: dhcwg@ietf.org; ietf@ietf.org; draft-ietf-dhc-rfc3315bis.all@ietf.org
> Subject: [Int-dir] Intdir early review of draft-ietf-dhc-rfc3315bis-10
>
> Reviewer: Zhen Cao
> Review result: Ready with Issues
>
> I am an assigned INT directorate reviewer for this draft. These comments =
were written primarily for the benefit of the Internet Area Directors. Docu=
ment editors and shepherds should treat these comments just like they would=
 treat comments from any other IETF contributors and resolve them along wit=
h any other Last Call comments that have been received. For more details of=
 the INT directorate, see <http://www.ietf.org/iesg/directorate.html>.
>
> This version is quite ready to go, with a small issue that I would like t=
o
> discussion:
>
> In Section. 15 (Reliability of Client Initiated Message Exchanges), I str=
ongly recommend that implementation MUST NOT set both MRC or MRD to ZERO, w=
hich attaches a possible risk that the client continues to send this messag=
e without
> a stop.    So I would like to propose the following change:
>
> s/
> " If both MRC and MRD are zero, the client continues to transmit the
>    message until it receives a response."
> /
> "The client must be informed with a limit of its retransmission behavior,=
 and MUST NOT set both MRC and MRD to zero"
>
> -zhen
>
>
> _______________________________________________
> Int-dir mailing list
> Int-dir@ietf.org
> https://www.ietf.org/mailman/listinfo/int-dir


From nobody Wed Nov  1 23:01:32 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 1424413F58D for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 23:01:31 -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] 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 yeD6uWsXE_jk for <ietf@ietfa.amsl.com>; Wed,  1 Nov 2017 23:01:28 -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 A006713F866 for <ietf@ietf.org>; Wed,  1 Nov 2017 23:01:28 -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 E243358C4FC; Thu,  2 Nov 2017 07:01:23 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id C72D0B0D039; Thu,  2 Nov 2017 07:01:23 +0100 (CET)
Date: Thu, 2 Nov 2017 07:01:23 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Alia Atlas <akatlas@gmail.com>, S Moonesamy <sm+ietf@elandsys.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: letting IETF build on top of Open Source technology
Message-ID: <20171102060123.GA25640@faui40p.informatik.uni-erlangen.de>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <6.2.5.6.2.20171101132245.10d04f48@elandnews.com> <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com> <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7d1SQQZCR3hk4yxlNiDM-ekVRxI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 06:01:31 -0000

How do i know which behavior of your code is a bug and which behavior is a feature ?

On Wed, Nov 01, 2017 at 10:35:08PM -0400, Phillip Hallam-Baker wrote:
> My specifications are my code.
> 
> If you look at any of the protocol specifications for the Mesh, you
> will find a reference section in the back that is generated directly
> from the schema and examples taken from running code generated from
> the same schema. And the running code used to generate the examples is
> the same as the reference code.
> 
> http://www.prismproof.org/Resources/
> 
> The tool set is also open source though documenting this has been a
> lower priority for me than finishing the Mesh.
> 
> http://www.prismproof.org/Code/standard/html/12cd4543-7aeb-41b3-81cf-4f828b2f76d7.htm
> 
> The original point of doing this was accuracy rather than saving time.
> But it certainly saves me a lot of time now I have the system working.
> I am currently working on generating examples for the Web site as
> well.
> 
> At present, the code generators create C# code but they have generated
> C in the past. I will probably return to that after the current code
> set is complete.


From nobody Thu Nov  2 00:31:02 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D5B13FA1E for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 00:31:01 -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=opendkim.org header.b=ZzuTW7bc; dkim=pass (1024-bit key) header.d=elandsys.com header.b=hbk2Yl2C
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlW_kUJeJc5K for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 00:31:00 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 13B9913F9DF for <ietf@ietf.org>; Thu,  2 Nov 2017 00:31:00 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.35.139]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA27Ui9C013599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Nov 2017 00:30:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1509607858; x=1509694258; bh=c0LfVSzejW14oX1yYvywibeYiDNO4oyhpJS+sbkjRAQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZzuTW7bcpFUnfQsC0rlolgauoHAFu357O9V+2v8oV7HugM2YGF/HMBfAYv22zRmsM OVGDs1z2rsQ/SgBnX4so/PvnzHQBLRBMZhBL3E84RKbQ+U1GwXqghD77FJx4+pXgyY jSrQ6HsO+Tkv/IvjvwHv1uSln4tHEMmoovPYyvmA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1509607858; x=1509694258; i=@elandsys.com; bh=c0LfVSzejW14oX1yYvywibeYiDNO4oyhpJS+sbkjRAQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hbk2Yl2CbwfIzJZjsSM7vThI9l6y/K4sD/Ps4ZJSxvD9XdFQSJYQxI5THZ7os6Bz0 Vs+Y1udpYaLXUgbMlvukK4irer6N2nFK1XsaZ1Li6jIe85cNeGQGbYam/r6qxj0L65 Kwpjrz90gOKgbVczEeTDA6EEV/VH8JYbVmrAbQDM=
Message-Id: <6.2.5.6.2.20171101232739.100f49c8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 Nov 2017 00:28:24 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Responses to questions about the new IETF privacy statement
Cc: "John R Levine" <johnl@taugh.com>
In-Reply-To: <alpine.OSX.2.21.1710191805520.71205@ary.qy>
References: <alpine.OSX.2.21.1710191805520.71205@ary.qy>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kcMHfm-tFH9YL-Yh2iIN-FkO748>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 07:31:01 -0000

Hello,
At 03:08 PM 19-10-2017, John R Levine wrote:
>The IAOC published a new privacy statement last month, which is now 
>available at
>https://iaoc.ietf.org/documents/IETFPrivacyStatement2017-07-12.pdf
>
>We got a few questions on the draft version.

The initial request for comments about the privacy statement was in 
February 2015.  The responses to the questions cannot be described as 
timely [1].

There was a comment from the current IETF Chair about retention 
policies.  The latest version of the privacy statement does not say 
anything about that.

What information is shared with the Internet Society for marketing purposes?

There is the following on Page 2: "If you provide Personal Data to 
the Parties, you acknowledge and agree that such Personal Data may be 
transferred from your current location to others in any country in 
the world".  Who are those "others"?

Regards,
S. Moonesamy

1. I don't think that John is responsible for that. 


From nobody Thu Nov  2 01:46:49 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 B98A913FA89; Thu,  2 Nov 2017 01:46:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 Wb0FoDqDv2wo; Thu,  2 Nov 2017 01:46:45 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D2D3013FA8A; Thu,  2 Nov 2017 01:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8583; q=dns/txt; s=iport; t=1509612405; x=1510822005; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=7Op2zRXxlJPtHz74lS2s7/XhudF61wwsLu8m5guZ+Wc=; b=NsH0BPYBfcAd21rvkhu4UVANPtdW3hgW///IzKIVg0HoQOZO1/1Rj89Z 6TG9iRhdLaetZzEZvYUmqX1L9RNUSv4f+IXNIqdqa1wfJu6vS9r/riZcd //TtdKcuVpSFUUCkfIWoF64FXmOYJDBQS5aglkqqnU5dZ9Hz7/aY9pyYm 0=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0COAABL2vpZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhQaEJIofdJAifZVIghEHA4U7AoVGGAEBAQEBAQEBAWsohR0BAQE?= =?us-ascii?q?BAgEjSA4FCwsYKgICVwcMCAEBF4oACKhfgieLFwEBAQEBBQEBAQEBFA+DLoFlg?= =?us-ascii?q?14pgXRYNYRqAQoGgyuCYgWKMo5UiQeEQoIjjheCFYYDg2CHOpYWgTkfOIFsNCE?= =?us-ascii?q?IHRWDLoRfQIpbASaCHQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.44,333,1505779200"; d="asc'?scan'208";a="5942"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Nov 2017 08:46:42 +0000
Received: from [10.61.88.6] (ams3-vpn-dhcp6151.cisco.com [10.61.88.6]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id vA28kgOg027478; Thu, 2 Nov 2017 08:46:42 GMT
Subject: Re: RTG-DIR review of draft-ietf-opsawg-mud-13
To: adrian@olddog.co.uk, rtg-ads@ietf.org
Cc: draft-ietf-opsawg-mud@ietf.org, ietf@ietf.org, rtg-dir@ietf.org
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk> <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com> <022901d3536d$d01d7b10$70587130$@olddog.co.uk>
From: Eliot Lear <lear@cisco.com>
Message-ID: <44f7279c-aef8-b8ab-dfb5-a941f52e7899@cisco.com>
Date: Thu, 2 Nov 2017 09:46:07 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <022901d3536d$d01d7b10$70587130$@olddog.co.uk>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HEOxsNcAnkXKsqEoJd8GewcDbWwqEGnID"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aAcJvLQOyUkX8LOITrD1b9awZXA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 08:46:48 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--HEOxsNcAnkXKsqEoJd8GewcDbWwqEGnID
Content-Type: multipart/mixed; boundary="THoqLSCOu4COKf0mml9UH2EslJFO3lqsx";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: adrian@olddog.co.uk, rtg-ads@ietf.org
Cc: draft-ietf-opsawg-mud@ietf.org, ietf@ietf.org, rtg-dir@ietf.org
Message-ID: <44f7279c-aef8-b8ab-dfb5-a941f52e7899@cisco.com>
Subject: Re: RTG-DIR review of draft-ietf-opsawg-mud-13
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk>
 <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com>
 <022901d3536d$d01d7b10$70587130$@olddog.co.uk>
In-Reply-To: <022901d3536d$d01d7b10$70587130$@olddog.co.uk>

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

Hi Adrian,


On 11/2/17 1:01 AM, Adrian Farrel wrote:
> This looks really good, Eliot. Thanks for being so responsive and posit=
ive to my peculiar brand of paranoia and pedantry.

Not at all, and thanks for improving the work.
> Just a few bits of discussion remain...
>
>>> I know I ranted about privacy before and the authors took some text I=
 wrote
>>> as the basis of the privacy considerations, but I'm still worried tha=
t the default
>>> will be that devices are MUD-enabled (good) and that users will not b=
e
>>> protected. It would be sad if the user's only option is to reject MUD=
 devices
>>> (especially as they might not even know that the devices are MUD-enab=
led).
>>> More burble below, but it seems to me that we should make privacy-sup=
porting
>>> modes of operation at least the default, but possibly the only approa=
ch.
>>>
>>> Section 15 has...
>>>
>>>   The release of a MUD URL by a Thing reveals what the Thing is, and
>>>   provides an attacker with guidance on what vulnerabilities may be
>>>   present.
>>>
>>> Pleased to see this text: it was a security concern I had. Good to ha=
ve
>>> it flagged. However, the mitigation suggested 2 paragraphs later is a=

>>> bit thin and sounds rather optional. I see how an implementer might
>>> take action, but what can a user do to protect their device? [...]
>> While this may not be a *perfect* solve for all of your concerns, I ho=
pe
>> you will find  the proposal below Good Enough.  Keep in mind that we
>> are attempting to address a very broad set of devices with a large var=
iety
>> of capabilities, from energy-harvesting devices that may never encrypt=

>> (think a wall switch) to devices that have heaps of power and memory
>> (think robots).  Many of the devices have very limited privacy concern=
s,
>> while others will have quite a few.  In addition, whatever capabilitie=
s the
>> device has must intersect the capabilities found in deployments.
>>
>> With all that in mind, what I propose is the following:
>> =E2=80=A2 Add text that RECOMMENDs that devices make use of TEAP when =
there
>>     may be privacy concerns and when it is available; and
>> =E2=80=A2 In other cases where privacy may be a concern, we should REC=
OMMEND
>>    that a configuration option be provided, particularly when devices =
are
>>    designed to be mobile, which is where I think most of your concerns=

>>    stem from.
> This is getting gooder. Thanks.
> Even when the MUD controller is on the premises (the not mobile case), =
it contacts
> an offsite file server, and that act is visible.
> Suppose my Hi-Fi uses MUD - now you know that my house is worth robbing=
=2E
> Suppose my intruder alarm uses MUD - now you know what security system =
I have.

Here, I think you have some cause for hope, because on the whole, in the
home, wireless encryption is generally used.=C2=A0 It's not perfect but w=
ould
address the point you make above.

> Of course, when the MUD controller is remote (the mobile case), it's al=
l even more worrying.

Yes, and to that end I propose to highlight a particular warning for
open networks (this would be one amongst many that developers should
heed with regard to open networks).

>
> I know you are trying to trade between perfect and getting something th=
at will be implemented and so make the world a somewhat better place. But=
 just recall that someone implemented those devices that "leak like sieve=
s" and those folk are unlikely to see a Recommendation as anything like a=
 strong hint.

My hope is that this problem will abate over time, but I really cannot
say.=C2=A0 My guess is that the same who are unlikely to heed such a
recommendation are also highly unlikely to implement MUD in the first pla=
ce.

>
> Well, I'm not in a position to block the whole effort, and I'm not enou=
gh of an expert to suggest a solution to my concern that works for all ty=
pes of device.
>
>>> There seems to be some overlap of terms and definitions in 1.5 and 1.=
6.
>> Can you be more specific?
> 1.5 and 1.6 both have "manufacturer".
> 1.5 has "controller" and 1.6 has "MUD controller".
> The definitions don't match.

Ah- that is because they are being used in different contexts.=C2=A0 One =
is
intended as a YANG node and the other really means those people who
build the thing.
>
>>> 3.5 has me confused. Looks like a fine idea, but how does it work? A
>>> Thing reports the MUD URL, and the file that is pulled contains the
>>> systeminfo URL, and the info that is pulled contains the localised in=
fo.
>>> Have I got that right?
>> Yes.
>>
>>> That means that the MUD URL has to include the correct systeminfo for=

>>> the locality.  Presumably we're interested in the locality of the MUD=

>>> controller.
>> The intent here is basically to allow for language tags to do their th=
ing
>> through one level of indirection.  That doesn't require any specific c=
hange
>> to the URL itself.  I've included some text in response to Mark, but t=
hat
>> text may further shift based on other suggestions Mark may have.
> I'm missing something, but that's OK, I don't have to understand someth=
ing for it to be right :-)
>
> So long as it is possible for the MUD Controller to be in one locale an=
d the MUD Server in another and all the bits to work right, I'm happy.
>
>>> Introduction
>>>
>>>   Please do NOT use random uppercase words in your text.  There's NO
>>>   need: the readers are no more stupid than the average reader of an
>>>   RFC.
>>>
>>> Ditto 3.4, 3.6
>> Sorry- I didn't parse this.
> Sorry I'm being sassy.
>
> I mean, please don't capitalise for emphasis. Just limit yourself to 21=
19 capitalisation.

Got it.

>
>>> Introduction
>>>
>>>   The key points are that the device itself is expected
>>>   to serve a limited purpose,
>>>
>>> I think you mean s/expected/intended/
>> How about "assumed"?
> We're both being overly passive. Who has the expectation/intention/assu=
mption.
>
> By "intended" I meant "intended by the manufacturer".
> So, actually, any one of the three words is fine, if you can attribute =
the verb to someone.

Ok, I think we might have to disagree.=C2=A0 The use of passive in this c=
ase
is appropriate because the assumption is general and not attached to a
single party.=C2=A0 Also, the following phrase =E2=80=93 and the rest of =
the document
=E2=80=93 make clear who is doing what.

>
>>> Introduction
>>>
>>>   o  A classifier that a device emits that can be used to locate a
>>>      description;
>>>
>>> Classifier or classification?
>> Classifier.
> Oh.
>
> A "classifier" is a person or thing that classifies.
> I don't think the device emits a thing or a person :-)
> I think it emits a piece of information that allows the device to be cl=
assified.

Means of classification?

Eliot



--THoqLSCOu4COKf0mml9UH2EslJFO3lqsx--

--HEOxsNcAnkXKsqEoJd8GewcDbWwqEGnID
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

iQEcBAEBCAAGBQJZ+ttQAAoJEIe2a0bZ0nozDdMIAJV3mFDhMVhjRPWEroPyK9yx
e0pWfTWboTow4jcOkNJrMl7wZ2avp86sbmA1qw8TAfR6dVm0TSfBvhi23c9ixc1y
MQKRL4FG8I6QzvL/GG8r06hihDQmPsmi1pL4O3Z/tyAc2UlzSeFa9pWOUy7o/d0J
+DixpL9Z0amg2hPXsqljrveA/9TyEQM1TaeZ1vtWL4mtlk43Fo61sQUlwhH/uFjS
zWa/31hQTbtAfmN4BHGBZ3aTk8PgnoPU+ROf1RP3pWnbnmjWaf0KE+PI5V9WpixS
bO2wi2f5xAeKkYo4ioJ4SMX6DMdsq6zKZMS1bMDWSqDgmwpc7MYNsgFtDVVnPkA=
=Eq7T
-----END PGP SIGNATURE-----

--HEOxsNcAnkXKsqEoJd8GewcDbWwqEGnID--


From nobody Thu Nov  2 04:14:30 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 28BEA139982; Thu,  2 Nov 2017 04:14: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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-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 4fWKHgBzrrZx; Thu,  2 Nov 2017 04:14:21 -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 D8E2713F4CB; Thu,  2 Nov 2017 04:14:19 -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 vA2BEDR7012431; Thu, 2 Nov 2017 11:14:13 GMT
Received: from 950129200 (254.196.113.87.dyn.plus.net [87.113.196.254]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id vA2BECCn012405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Nov 2017 11:14:13 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Eliot Lear'" <lear@cisco.com>, <rtg-ads@ietf.org>
Cc: <draft-ietf-opsawg-mud@ietf.org>, <ietf@ietf.org>, <rtg-dir@ietf.org>
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk> <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com> <022901d3536d$d01d7b10$70587130$@olddog.co.uk> <44f7279c-aef8-b8ab-dfb5-a941f52e7899@cisco.com>
In-Reply-To: <44f7279c-aef8-b8ab-dfb5-a941f52e7899@cisco.com>
Subject: RE: RTG-DIR review of draft-ietf-opsawg-mud-13
Date: Thu, 2 Nov 2017 11:14:09 -0000
Message-ID: <02b901d353cb$b54a7aa0$1fdf6fe0$@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
Content-Language: en-gb
Thread-Index: AQHbXiOVWYUGr+virfAy7t490kIJlgFDRd+PAaRHM/gA4lCt+aLSgX2g
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23434.005
X-TM-AS-Result: No--19.810-10.0-31-10
X-imss-scan-details: No--19.810-10.0-31-10
X-TMASE-MatchedRID: Kx0w2sAofbsRqNE+xcwLcPHkpkyUphL9/NqdnmyTYHNcKZwALwMGswPa oyNK+Jv3xILoPou7rqmZ5rXmZbU9pX8RWuGQxsOi081phgl5F/lReWnUUdhI9a2PbheqHTJct/b KbgYFIpodfitjgIfGwGuQ7Ro4lHrcGBntNyPrRBurfZ+usyeESClayzmQ9QV0h868MqJkrtyTqM woXHwYFHF6xI97o6MHAhPLyEMdtHermmW6xY+ZmNh3b7/zBhN10Wobj8GkNVrKY//WmIj/ofi0j vfWRgUfPOeTGEP3OBanQTgw3dez4gjgWUfbdVp/z5rIW0RbS5h9SoM2kg9cUvYnOqnd+Q0TkGYM 14lC/DWhY1RK7RrSZ/H58jGrRTfoNA4kPXMXcBLYxkZC4pzxSEbxaqRa2zEnh8BhJvgqWBlY9QW glzfLgd9J2PHe9WriZ1cUcXza30wWFyz6902fByQIIQf/f8GJRvyVHewb0kKdwU/qXYxHvGeO90 L8tOZ6jF6wvhtRU7eILExmshQCk/l9KkqHi12rcFEiuPxHjsWLB4sTRpOnCes6rusujBXfdodzZ VKMVFxhYIpB42crUu9EJt2F5Oksv1l2Uvx6idpWdFebWIc3VsRB0bsfrpPI6T/LTDsmJmg=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r58zFR7eDSV8FxwWbM49V2GUsCg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 11:14:23 -0000

Getting close.

> >> With all that in mind, what I propose is the following:
> >> =E2=80=A2 Add text that RECOMMENDs that devices make use of TEAP =
when there
> >>     may be privacy concerns and when it is available; and
> >> =E2=80=A2 In other cases where privacy may be a concern, we should =
RECOMMEND
> >>    that a configuration option be provided, particularly when =
devices are
> >>    designed to be mobile, which is where I think most of your =
concerns
> >>    stem from.
> > This is getting gooder. Thanks.
> > Even when the MUD controller is on the premises (the not mobile =
case), it
> > contacts an offsite file server, and that act is visible.
> > Suppose my Hi-Fi uses MUD - now you know that my house is worth =
robbing.
> > Suppose my intruder alarm uses MUD - now you know what security =
system I
> > have.
>=20
> Here, I think you have some cause for hope, because on the whole, in =
the
> home, wireless encryption is generally used.  It's not perfect but =
would
> address the point you make above.

Yes. This addresses communications between device and router, and =
between router and MUD controller.
Of course, there are some issues with the use of wireless encryption in =
the home (like security concerns) added to the fact that far fewer =
people use wireless security than you might think given that you hang =
out with technology-aware folk. But that's OK because (nominally) we =
have a protection mechanism.

But when the home-based MUD controller uses a URL to access a MUD =
server, isn't that pretty visible and associated with the home (via the =
IP address)?

> > Of course, when the MUD controller is remote (the mobile case), it's =
all even
> > more worrying.
>=20
> Yes, and to that end I propose to highlight a particular warning for
> open networks (this would be one amongst many that developers should
> heed with regard to open networks).

OK. That works.

> > I know you are trying to trade between perfect and getting something =
that will
> > be implemented and so make the world a somewhat better place. But =
just recall
> > that someone implemented those devices that "leak like sieves" and =
those folk
> > are unlikely to see a Recommendation as anything like a strong hint.
>=20
> My hope is that this problem will abate over time, but I really cannot
> say.  My guess is that the same who are unlikely to heed such a
> recommendation are also highly unlikely to implement MUD in the first =
place.

Yeah, you're right.

I assume you have already written the paper titled "As Clear As MUD".

> >>> There seems to be some overlap of terms and definitions in 1.5 and =
1.6.
> >> Can you be more specific?
> > 1.5 and 1.6 both have "manufacturer".
> > 1.5 has "controller" and 1.6 has "MUD controller".
> > The definitions don't match.
>=20
> Ah- that is because they are being used in different contexts.  One is
> intended as a YANG node and the other really means those people who
> build the thing.

Yeah, got that. But isn't the YANG node supposed to encode the =
information about the real things?

Well, if everyone else thinks this is clear.

> >>> Introduction
> >>>
> >>>   The key points are that the device itself is expected
> >>>   to serve a limited purpose,
> >>>
> >>> I think you mean s/expected/intended/
> >> How about "assumed"?
> > We're both being overly passive. Who has the
> > expectation/intention/assumption.
> >
> > By "intended" I meant "intended by the manufacturer".
> > So, actually, any one of the three words is fine, if you can =
attribute the verb to
> > someone.
>=20
> Ok, I think we might have to disagree.  The use of passive in this =
case
> is appropriate because the assumption is general and not attached to a
> single party.  Also, the following phrase =E2=80=93 and the rest of =
the document
> =E2=80=93 make clear who is doing what.

Sigh. You'll not convince me that passive voice is ever a good thing in =
a spec.=20
A general assumption is pretty risky. It's a second order assumption: =
you're assuming that I assume. I'm reminded that the US has actually =
written laws about "intended use" because those assumptions were not =
necessarily shared.

Maybe it's just writing style.

Thanks,
Adrian


From nobody Thu Nov  2 06:34:08 2017
Return-Path: <volz@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 5632913F65E; Thu,  2 Nov 2017 06:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.521
X-Spam-Level: 
X-Spam-Status: No, score=-13.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_AFFORDABLE=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Q6OR5WG4Txg5; Thu,  2 Nov 2017 06:34:04 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 697781397F9; Thu,  2 Nov 2017 06:33:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4270; q=dns/txt; s=iport; t=1509629634; x=1510839234; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=V0AyTB2x4N1XrZ7RBQHl9kFtz7pvxGuXe19bySC3QWc=; b=VzaU4y487kNTOtCEuqkxQ0sxs0TkmTPOJ7pCLg6KGu/Pd0jWkevq/xp2 r6ugkw6eUIebTHg0XU4AKJepYeSOeBiiirGPcrRlpMoyMzCwsPNtxCuVc AXUuR/rE0mzPAR9dtcMkrsxuELVVmpJ2c+n1Zj+W0AWAI2g51SPTZ+zj8 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CdAACCHftZ/5FdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgwYuZG4nB4N2ih+PG4F8iFCNdYIRChgLhRgCGoQ0PxgBAQEBAQE?= =?us-ascii?q?BAQFrKIUdAQEBAwEBASEROgsFBwQCAQgRBAEBAwIjAwICAh8GCxQBCAgCBA4FC?= =?us-ascii?q?AGKAgMNCBCob4Inh0INg0gBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQ+CH4IHhma?= =?us-ascii?q?CajiBSRAtgn6CYgWhUTwCkAGEcJM7jRqITwIRGQGBOAEfOIFsehVJgmQJglMcg?= =?us-ascii?q?Wd3AYp/gTKBEQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.44,334,1505779200"; d="scan'208";a="25187865"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Nov 2017 13:33:53 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id vA2DXrCu032058 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 2 Nov 2017 13:33:53 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 2 Nov 2017 08:33:52 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1320.000; Thu, 2 Nov 2017 08:33:52 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Zhen Cao <zhencao.ietf@gmail.com>
CC: "int-dir@ietf.org" <int-dir@ietf.org>, "dhcwg@ietf.org" <dhcwg@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-rfc3315bis.all@ietf.org" <draft-ietf-dhc-rfc3315bis.all@ietf.org>
Subject: RE: [Int-dir] Intdir early review of draft-ietf-dhc-rfc3315bis-10
Thread-Topic: [Int-dir] Intdir early review of draft-ietf-dhc-rfc3315bis-10
Thread-Index: AQHTUuS5t0NJ+fIQ4E2BcQoavKk7AqL/glXQgAFBbwCAAFPdUA==
Date: Thu, 2 Nov 2017 13:33:52 +0000
Message-ID: <f2419bc5d0ff40eb950ae8eb613367b0@XCH-ALN-003.cisco.com>
References: <150952203714.25993.17333137226492207681@ietfa.amsl.com> <1cfea94b1690409595b243f014083bf1@XCH-ALN-003.cisco.com> <CAFxP68xsGG1K4Q0qfQL6VG4Qmth+GVv7qdDWcTjP20K9y9tehg@mail.gmail.com>
In-Reply-To: <CAFxP68xsGG1K4Q0qfQL6VG4Qmth+GVv7qdDWcTjP20K9y9tehg@mail.gmail.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.98.1.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q97aZzjQg4YU24DE-a87xPUl6-I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 13:34:06 -0000

SGk6DQoNCkkgdGhpbmsgdGhpcyB0ZXh0IGlzIGZpbmUgYXMgaXMuIEl0IGlzIGFsc28gdGV4dCB0
aGF0IHdhcyBtb3ZlZCBmcm9tIFJGQyAzMzE1IChsYXN0IHBhcmFncmFwaCBvZiBTZWN0aW9uIDE0
KSBhbmQgaGFzIGNhdXNlZCBubyBpc3N1ZXMgKHdlbGwsIGl0IGRpZCByZXN1bHQgaW4gUkZDNzA4
MyB0byBjaGFuZ2UgU09MX01BWF9SVCBhbmQgSU5GX01BWF9SVCBkZWZhdWx0cyB0byByZWR1Y2Ug
dGhlIGZyZXF1ZW5jeSBvZiByZXRyYW5zbWlzc2lvbnMgLS0gc28gcGVyaGFwcyB3ZSBjYW4gY29u
c2lkZXIgdGhhdCB0byBoYXZlIGFkZHJlc3NlZCB0aGUgaXNzdWU/KS4NCg0KLSBCZXJuaWUNCg0K
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFpoZW4gQ2FvIFttYWlsdG86emhlbmNh
by5pZXRmQGdtYWlsLmNvbV0gDQpTZW50OiBXZWRuZXNkYXksIE5vdmVtYmVyIDAxLCAyMDE3IDEx
OjMwIFBNDQpUbzogQmVybmllIFZvbHogKHZvbHopIDx2b2x6QGNpc2NvLmNvbT4NCkNjOiBpbnQt
ZGlyQGlldGYub3JnOyBkaGN3Z0BpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1k
aGMtcmZjMzMxNWJpcy5hbGxAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbSW50LWRpcl0gSW50ZGly
IGVhcmx5IHJldmlldyBvZiBkcmFmdC1pZXRmLWRoYy1yZmMzMzE1YmlzLTEwDQoNCkhpIEJlcm5p
ZSwNCg0KPiBGaXJzdCwgdGhhbmtzIGZvciB0aGUgSW50LURpciByZXZpZXcuDQpNeSBwbGVhc3Vy
ZSBhcyBhbHdheXMuDQoNCj4NCj4gUmVnYXJkaW5nIHlvdXIgY29tbWVudCwgdGhlIGNhc2VzIHdo
ZXJlIGJvdGggTVJDIGFuZCBNUkQgYXJlIHplcm8gaXMgZm9yIGEgU29saWNpdCBhbmQgSW5mb3Jt
YXRpb24tUmVxdWVzdC4gQW5kLCBmb3IgdGhvc2UgcGFydGljdWxhciBjYXNlcywgdGhlIGNsaWVu
dCBzaG91bGQgcHJvYmFibHkgcmV0cmFuc21pdCAiZm9yZXZlciIgYXQgYSBob3BlZnVsbHkgbG93
IHJhdGUgKFNPTF9NQVhfUlQgYW5kIElORl9NQVhfUlQgYXJlIDM2MDAgc2Vjb25kcyopIHRvIGxv
Y2F0ZSBhICBESENQIHNlcnZlci4gVGhpcyBvZiBjb3Vyc2UgZGVwZW5kcyBvbiB0aGUgUkEgTSAm
IE8gYml0cyAoaW5kaWNhdGluZyBhIERIQ1Agc2VydmVyIGlzIGF2YWlsYWJsZSkgb3IgdGhlIG1h
bnVhbCBjb25maWd1cmF0aW9uIG9mIHRoZSBjbGllbnQgKHRvIGV4cGxpY2l0bHkgcnVuIERIQ1Ap
Lg0KDQpUaGVuIGRlcGVuZGluZyBvbiB0aGlzIGluZm9ybWF0aW9uLCBpdCBpcyB1cCB0byB5b3Ug
dG8gc2VlIGlmIHRoZXJlIGlzIGEgbmVlZCBvZiBhbiBhZmZvcmRhYmxlIGJldHRlciBkZXNjcmlw
dGlvbiB0aGFuIHRoZSBjdXJyZW50IHRleHQuDQoNCkNoZWVycywNCnpoZW4NCg0KPg0KPiAqIC0g
UkZDIDMzMTUgdXNlZCAxMjAgc2Vjb25kcyBmb3IgdGhlc2UgdmFsdWVzLCBidXQgdGhhdCB3YXMg
dXBkYXRlZCBieSBSRkMgNzA4My4NCj4NCj4gLSBCZXJuaWUNCj4NCj4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gRnJvbTogSW50LWRpciBbbWFpbHRvOmludC1kaXItYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mIFpoZW4gQ2FvDQo+IFNlbnQ6IFdlZG5lc2RheSwgTm92ZW1iZXIg
MDEsIDIwMTcgMzo0MSBBTQ0KPiBUbzogaW50LWRpckBpZXRmLm9yZw0KPiBDYzogZGhjd2dAaWV0
Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IA0KPiBkcmFmdC1pZXRmLWRoYy1yZmMzMzE1YmlzLmFsbEBp
ZXRmLm9yZw0KPiBTdWJqZWN0OiBbSW50LWRpcl0gSW50ZGlyIGVhcmx5IHJldmlldyBvZiBkcmFm
dC1pZXRmLWRoYy1yZmMzMzE1YmlzLTEwDQo+DQo+IFJldmlld2VyOiBaaGVuIENhbw0KPiBSZXZp
ZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPg0KPiBJIGFtIGFuIGFzc2lnbmVkIElOVCBk
aXJlY3RvcmF0ZSByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlc2UgY29tbWVudHMgd2VyZSB3
cml0dGVuIHByaW1hcmlseSBmb3IgdGhlIGJlbmVmaXQgb2YgdGhlIEludGVybmV0IEFyZWEgRGly
ZWN0b3JzLiBEb2N1bWVudCBlZGl0b3JzIGFuZCBzaGVwaGVyZHMgc2hvdWxkIHRyZWF0IHRoZXNl
IGNvbW1lbnRzIGp1c3QgbGlrZSB0aGV5IHdvdWxkIHRyZWF0IGNvbW1lbnRzIGZyb20gYW55IG90
aGVyIElFVEYgY29udHJpYnV0b3JzIGFuZCByZXNvbHZlIHRoZW0gYWxvbmcgd2l0aCBhbnkgb3Ro
ZXIgTGFzdCBDYWxsIGNvbW1lbnRzIHRoYXQgaGF2ZSBiZWVuIHJlY2VpdmVkLiBGb3IgbW9yZSBk
ZXRhaWxzIG9mIHRoZSBJTlQgZGlyZWN0b3JhdGUsIHNlZSA8aHR0cDovL3d3dy5pZXRmLm9yZy9p
ZXNnL2RpcmVjdG9yYXRlLmh0bWw+Lg0KPg0KPiBUaGlzIHZlcnNpb24gaXMgcXVpdGUgcmVhZHkg
dG8gZ28sIHdpdGggYSBzbWFsbCBpc3N1ZSB0aGF0IEkgd291bGQgDQo+IGxpa2UgdG8NCj4gZGlz
Y3Vzc2lvbjoNCj4NCj4gSW4gU2VjdGlvbi4gMTUgKFJlbGlhYmlsaXR5IG9mIENsaWVudCBJbml0
aWF0ZWQgTWVzc2FnZSBFeGNoYW5nZXMpLCBJIHN0cm9uZ2x5IHJlY29tbWVuZCB0aGF0IGltcGxl
bWVudGF0aW9uIE1VU1QgTk9UIHNldCBib3RoIE1SQyBvciBNUkQgdG8gWkVSTywgd2hpY2ggYXR0
YWNoZXMgYSBwb3NzaWJsZSByaXNrIHRoYXQgdGhlIGNsaWVudCBjb250aW51ZXMgdG8gc2VuZCB0
aGlzIG1lc3NhZ2Ugd2l0aG91dA0KPiBhIHN0b3AuICAgIFNvIEkgd291bGQgbGlrZSB0byBwcm9w
b3NlIHRoZSBmb2xsb3dpbmcgY2hhbmdlOg0KPg0KPiBzLw0KPiAiIElmIGJvdGggTVJDIGFuZCBN
UkQgYXJlIHplcm8sIHRoZSBjbGllbnQgY29udGludWVzIHRvIHRyYW5zbWl0IHRoZQ0KPiAgICBt
ZXNzYWdlIHVudGlsIGl0IHJlY2VpdmVzIGEgcmVzcG9uc2UuIg0KPiAvDQo+ICJUaGUgY2xpZW50
IG11c3QgYmUgaW5mb3JtZWQgd2l0aCBhIGxpbWl0IG9mIGl0cyByZXRyYW5zbWlzc2lvbiBiZWhh
dmlvciwgYW5kIE1VU1QgTk9UIHNldCBib3RoIE1SQyBhbmQgTVJEIHRvIHplcm8iDQo+DQo+IC16
aGVuDQo+DQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+IEludC1kaXIgbWFpbGluZyBsaXN0DQo+IEludC1kaXJAaWV0Zi5vcmcNCj4gaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnQtZGlyDQo=


From nobody Thu Nov  2 08:02:04 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 B08EA13F66C; Thu,  2 Nov 2017 08:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 m0i3TjjMfdTk; Thu,  2 Nov 2017 08:01:51 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB0D013FA9C; Thu,  2 Nov 2017 08:01:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2582; q=dns/txt; s=iport; t=1509634911; x=1510844511; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=fv49HHpLt6JYCysPAP5w6KAgOv3qYU4OQfjMeUAbkII=; b=PEeC1xG2KM2td27HgzLm3XdGSnXDRXhtNPLD3wuDOVmNJNJacAiGVoNY laqeRwkhhzfV4Sh3XdGt0El9+nl2SnscVl8pN8PkOhSqQh2Rpohf4fMOE ASngvBh1t5XqnGvGGmPojAaRNUCysKdFAYndMQLXz3XlPWZtwZK5jpdFY g=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0COAADXMvtZ/xbLJq1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBhQaEJIofdJAjlkUQggEHA4U7AoUOGAEBAQEBAQEBAWsohR4BBSN?= =?us-ascii?q?WEAsYKgICVwcMCAEBih+ofYInixcBAQEBAQUBAQEBARQPgy6FbIMBhFUmgyuCY?= =?us-ascii?q?gWZBokHhEKCI44Xi3iHOpYWgTkfOIFsNCEIHRWDLoRfQI15AQEB?=
X-IronPort-AV: E=Sophos;i="5.44,334,1505779200"; d="asc'?scan'208";a="15242"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Nov 2017 15:01:49 +0000
Received: from [10.61.88.6] (ams3-vpn-dhcp6151.cisco.com [10.61.88.6]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id vA2F1moe014382; Thu, 2 Nov 2017 15:01:48 GMT
Subject: Re: RTG-DIR review of draft-ietf-opsawg-mud-13
To: adrian@olddog.co.uk, rtg-ads@ietf.org
Cc: draft-ietf-opsawg-mud@ietf.org, ietf@ietf.org, rtg-dir@ietf.org
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk> <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com> <022901d3536d$d01d7b10$70587130$@olddog.co.uk> <44f7279c-aef8-b8ab-dfb5-a941f52e7899@cisco.com> <02b901d353cb$b54a7aa0$1fdf6fe0$@olddog.co.uk>
From: Eliot Lear <lear@cisco.com>
Message-ID: <73c3c46a-46ae-2d41-a6d0-b6c41a1365cf@cisco.com>
Date: Thu, 2 Nov 2017 16:00:57 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <02b901d353cb$b54a7aa0$1fdf6fe0$@olddog.co.uk>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tcWWjFJUoFA47HjVTekARctxTi3lWogUD"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/75N9Z87xGpjLVGItoC5csubPVHU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 15:01:58 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--tcWWjFJUoFA47HjVTekARctxTi3lWogUD
Content-Type: multipart/mixed; boundary="TCuBHosPCSvTVcadH51NI9p2w4rwSEhph";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: adrian@olddog.co.uk, rtg-ads@ietf.org
Cc: draft-ietf-opsawg-mud@ietf.org, ietf@ietf.org, rtg-dir@ietf.org
Message-ID: <73c3c46a-46ae-2d41-a6d0-b6c41a1365cf@cisco.com>
Subject: Re: RTG-DIR review of draft-ietf-opsawg-mud-13
References: <01d501d35342$b90d7450$2b285cf0$@olddog.co.uk>
 <5f1c796d-3700-cda3-0bce-f5c6e70ffc9a@cisco.com>
 <022901d3536d$d01d7b10$70587130$@olddog.co.uk>
 <44f7279c-aef8-b8ab-dfb5-a941f52e7899@cisco.com>
 <02b901d353cb$b54a7aa0$1fdf6fe0$@olddog.co.uk>
In-Reply-To: <02b901d353cb$b54a7aa0$1fdf6fe0$@olddog.co.uk>

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

Hi Adrian,

Trimming now.

On 11/2/17 12:14 PM, Adrian Farrel wrote:
> But when the home-based MUD controller uses a URL to access a MUD
> server, isn't that pretty visible and associated with the home (via
> the IP address)?

The communication occurs via TLS.=C2=A0 I just don't know how to do bette=
r.=C2=A0
Also, I perceive two additional mitigations, one something of a happy
accident: I expect that there will be providers that do MUD file
management and so many of these URLs will all likely be served from the
same places, and not necessarily give away what they are.=C2=A0 The secon=
d is
that much of this data will be served from commercial clouds for
reliability purposes.

Regarding passive tense let us take that as editorial and I will work
with you to find a form that fits.

AD and WG permitting of course.

Eliot


--TCuBHosPCSvTVcadH51NI9p2w4rwSEhph--

--tcWWjFJUoFA47HjVTekARctxTi3lWogUD
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

iQEcBAEBCAAGBQJZ+zMpAAoJEIe2a0bZ0nozYa0IAK35jQM99G03HkoIY9znyVw3
8FTIZKLQYieVuHU5GbGIkWn093mJY5WzXc9GQtpIncoyHyx3vanLF+ccLo6b3rSt
dUEAqYmfC1iiMHmp4gxMd/L5Zqm3+e1WbHelZ8IpoevEpyKTi2Ehae+10rYyY9Ad
hNiecuVEza/dhuGfVz6hSaTJznx1V0XyszFOpXEQVtP5SfjFO3maRu1FHVgPobso
Pb7yRia2AcbVvDlczck6aOrUGttSLn3t5kS5uNOZcORiM35pICw3WYbpaRckHGzl
XET1C2QJ5PrTNke3L6beiuUZmJJtmmTSM/EIWX4OKOV3+tQdPFw6NGytqjxB9CQ=
=utCP
-----END PGP SIGNATURE-----

--tcWWjFJUoFA47HjVTekARctxTi3lWogUD--


From nobody Thu Nov  2 08:30:24 2017
Return-Path: <tom@herbertland.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2559B139680 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 08:30:17 -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=herbertland-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqeJaLGttEQW for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 08:30:15 -0700 (PDT)
Received: from mail-ua0-x244.google.com (mail-ua0-x244.google.com [IPv6:2607:f8b0:400c:c08::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 89166136001 for <ietf@ietf.org>; Thu,  2 Nov 2017 08:30:12 -0700 (PDT)
Received: by mail-ua0-x244.google.com with SMTP id n22so4229246uaj.13 for <ietf@ietf.org>; Thu, 02 Nov 2017 08:30:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0YDnVodjsKJZ2cUlNPs3xCRZ2v1Gqd4oIuQfAYOb0UA=; b=aQP8Ld6FPuvOoizzw+kIms8wQEteGVMMoLsRFy2NgH/9zAG4fNj5cTBBz8iwgS5CMy FqZR2m9r3ZPYrFzKdcOPUgCU0K/M9lmF8G83O/s10V4JFcqzoykaFX4GCmVgj5xyEbn9 lk0cceqw9LBB8ZwbGL9JjSTZoJ4HM2WdhUjluwI8uVdqky7u7DHuoNnX3+ruIM9UUkwt UNBgJVt6KKSO0KbWhEbYERUmNzEpzIpiE11V2DTl3ZW69w/FMdWDsbDyvj7dZao119Eo pvL4JM/L+1Pp5tv786YrPidQsBFP/NfXNxGg7C0sTXMuvtSNAQVIE1x6k2j9lixm/OXa mHIQ==
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=0YDnVodjsKJZ2cUlNPs3xCRZ2v1Gqd4oIuQfAYOb0UA=; b=ccmhs1z+a9CkHcXljoQi1q1hFJarLSC+FrYr0TO6f0Enc1gnYBcGJ60iFI8C3CKjGQ XXfyYNoX9xlvg4yhkcVCtEDUfF71RYZ5DpFHb/m0NOkGUbDA6UHOOfoJN1wEFscYVGtM bbx0ylKCe+MnkwnoOo/6V0liRkWx0yNZKpvnK3NnSEYFTKNFIfXY41AYPAtk1LpDbBUA GUMvyiCV4T7neqNqGihiTneA5rCx4ryM1xzuVVwiKoPcmv+usTim2Syqt8ztP+z9E8qD mDSA2e+mKNZmVKqAGpxh1xXseA0IyFK8IbBXHjmusffBD7g+frm+GvdFVPwfZFmAupbO RJ+Q==
X-Gm-Message-State: AMCzsaVlAAylp7qEY1ezPE4VbQ3SUFlx3Y2l7QM2R4ZG+xm5X9izekZP dWh3dRwXitTfXgPgrliRVbh9kTL1LNHtgO4np0ozFA==
X-Google-Smtp-Source: ABhQp+SaVrAbsJKwiDzMP1+5KlJmpV1k4uBCkBZpvil031q2Iy+MRpGrmCvZ8oxQFGIW2i8WWmHjAxDaqOr8QxeJuLA=
X-Received: by 10.176.83.206 with SMTP id l14mr3297045uaa.167.1509636611570; Thu, 02 Nov 2017 08:30:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.69.4 with HTTP; Thu, 2 Nov 2017 08:30:11 -0700 (PDT)
In-Reply-To: <20171101172146.GA12437@faui40p.informatik.uni-erlangen.de>
References: <CALx6S370-TuoUicWep5vV2NjLPS4d-HP1qVxW_nGrxhBLw6Eug@mail.gmail.com> <8kd5pq.oxb4pv.rtlo8t-qmf@mercury.scss.tcd.ie> <644DA50AFA8C314EA9BDDAC83BD38A2E0EAA7204@sjceml521-mbx.china.huawei.com> <dd2c3bd5-dd37-109b-2e81-0327db4daa09@cs.tcd.ie> <0BA14206-DC82-49EF-A625-B2425FA396F6@gmail.com> <1f254140-1340-6c7d-9c73-e7137562c685@gmail.com> <fa644cc2-161f-8884-3445-2b50d2c2ad23@htt-consult.com> <cf2ca920-f2d2-b65e-05eb-ebe3c30b76d1@huitema.net> <CAG-CQxrdS9L+2+bN=1NcPGuztn4U4OwSWUiNaVcS9Bsm2mtpfA@mail.gmail.com> <b18459d1-7ce1-b83d-787d-9066267d584b@huitema.net> <20171101172146.GA12437@faui40p.informatik.uni-erlangen.de>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 2 Nov 2017 08:30:11 -0700
Message-ID: <CALx6S34Bkv4ipyA5si4KkW7VaYU6A=3=cPpRo_ss00H+vDms-w@mail.gmail.com>
Subject: Re: [Ideas] [lisp] WG Review: IDentity Enabled Networks (ideas)
To: Toerless Eckert <tte@cs.fau.de>
Cc: Christian Huitema <huitema@huitema.net>, Padma Pillay-Esnault <padma.ietf@gmail.com>,  "ietf@ietf.org" <ietf@ietf.org>, "ideas@ietf.org" <ideas@ietf.org>, Dino Farinacci <farinacci@gmail.com>, "lisp@ietf.org list" <lisp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rn72uTnSPJ0WrWwZ8WVK6HBAaGE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 15:30:17 -0000

On Wed, Nov 1, 2017 at 10:21 AM, Toerless Eckert <tte@cs.fau.de> wrote:
> On Wed, Oct 11, 2017 at 12:34:19PM -0700, Christian Huitema wrote:
>> Some thing you should be hearing is that "long term identity of device"
>> has almost the same privacy properties as "long term identity of the
>> device's owner". You may think that identifying a random piece of
>> hardware is no big deal, but it turns out that the network activity and
>> network locations of that piece of hardware can be associated to those
>> of its human owner. So you need the same kind of protection for these
>> device identifiers as for human identifiers.
>
> Sure, but i don't think it can be generalized:
>
> There will be more and more non-individually owned nodes in public and
> corporate infrastructures where requirements will be quite different
> from those derived from individual human privacy.
>
Toerless,

That maybe true, but personal devices, such as smart phones and cars
that are associated with individuals, are hardly going away anytime
soon. How addresses are assigned to these devices has a material
impact on individual privacy. Even right now there are two long
threads on v6ops right now that are delving precisely into privacy of
IPv6 addresses that may be relevant. This includes discussion about
CGNAT and efforts by some governments to illegalize it because the
privacy it gives is too strong for law enforcement.

> If lets say those long term identifiers do not provide good human
> privacy protection but good communications security properties and
> managed transpacency for regulators then they could still be a great
> benefit for those class of nodes.
>
> [rant]
>
> Trying to get more privacy into network layer is like making
> tobacco more organic. You can get buried in the organic section
> of the graveyard after you die of lung cancer. Great success!
>
> Aka: Where is the IETF on any warnings, architectures or recommendations
> on the actual application layer:
>
Maybe there should be something like that. But, not unlike security,
if the goal is to derive a system with good privacy characteristics
then privacy should be considered at every layer including the
networking layer.

Tom


From nobody Thu Nov  2 08:31:07 2017
Return-Path: <tjc@ecs.soton.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 7E68F13A2B8 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 08:31:05 -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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ptq-SRkJlFUs for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 08:30:59 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFE16136001 for <ietf@ietf.org>; Thu,  2 Nov 2017 08:30:58 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id vA2FUpVS019636; Thu, 2 Nov 2017 15:30:51 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk vA2FUpVS019636
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1509636651; bh=RA1DZbjP7/ZMeGb47cqcb+GO2tM=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=5XZQ/o4KfpMJSi7eqCB5gqNBnVrlglpXzu+a3fIUzi//tIIz4Buh4dWcIMKHZ3pHY hzbZ09+ZZ7IxyvLZay6Z0HRsAMn4MnXzeAwJ9CG1yvz6c5OD2AftLaP1Ri0U9OUwvV LdsEVJ8fHfzgxk+L2/CmTjkE2NXpFcGxCwxJgS/o=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id yA1FUp2053809759E5 ret-id none; Thu, 02 Nov 2017 15:30:51 +0000
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:347c:9966:7017:389f] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id vA2FUflR025007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Nov 2017 15:30:42 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: IETF Website Status Update
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <545156e4-144f-6519-0f93-b4d2fa0f6789@gmail.com>
Date: Thu, 2 Nov 2017 15:30:41 +0000
Cc: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f40e4b5c2fe25cda5a447a2cf2f47ba4yA1FUp03tjc|ecs.soton.ac.uk|61DA7F6E-0378-49FA-B1D5-AB5D8A31A0DB@ecs.soton.ac.uk>
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com> <545156e4-144f-6519-0f93-b4d2fa0f6789@gmail.com> <61DA7F6E-0378-49FA-B1D5-AB5D8A31A0DB@ecs.soton.ac.uk>
To: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ssss
X-smtpf-Report: sid=yA1FUp205380975900; tid=yA1FUp2053809759E5; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: vA2FUpVS019636
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WC5tpRlh0FK0NA6fkeZTmvQojko>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 15:31:05 -0000

Hi,

> On 1 Nov 2017, at 10:49, Stewart Bryant <stewart.bryant@gmail.com> =
wrote:
>=20
> Hi Russ,
>=20
> I must say I still prefer the original in terms of utility, clarity =
and information density.

I must say I agree. It certainly should be possible to lay out the links =
page so that you can see where to go at a glance, rather than feeling =
you have to read the page line by line.=20

> I am not sure if the font being used is mandated, but I find it far =
less crisp, almost blurry compared to the smaller font of the original. =
I find such lack of crispness on web pages irritating and when I see it =
I am distracted by wondering if there is a technical failure in my =
system. People like 4K for a reason, and I see no reason why this =
preference would not be carried over to web pages.
>=20
> Whilst I understand the need to provide an accessible interface I =
don't see why there cannot simply be a parallel high efficiency =
interface as well.

I would second this request. As per the discussion at IETF99, I accept =
that www.ietf.org is essentially conceded to IETF =E2=80=98comms and =
marketing=E2=80=99, but there=E2=80=99s no reason we can=E2=80=99t have =
alternative well-laid out index pages as well.

There=E2=80=99s much of course that can be done simply by only using the =
datatracker and tools pages, which have gone from strength to strength =
over recent years.

> A useful addition to both the original and to this would be a direct =
link to id-nits right next to (well right before) the submit tag.

One other point is that I don=E2=80=99t think I=E2=80=99ve yet seen what =
a meeting page would look like in the new =E2=80=9Cglossy" format.=20
Under the new system, what would =
https://www.ietf.org/meeting/100/index.html look like?  If it=E2=80=99s =
https://beta.ietf.org/how/meetings/upcoming/100/, that=E2=80=99s not =
really comparable, yet.
That=E2=80=99s a really useful, and clearly laid out, page for finding =
info at meetings.
I assume there=E2=80=99s a change coming, as meeting pages fall under =
www.ietf.org.

Thanks,
Tim

>=20
> - Stewart
>=20
>=20
> On 31/10/2017 21:36, Russ Housley wrote:
>> I want to share an update on progress on the IETF website revamp =
project. In particular I=E2=80=99d like to highlight what has been done =
to respond to feedback from the IETF community received around IETF 99.
>>=20
>> A. Provide a landing page dedicated to current IETF participants
>>=20
>> A draft is currently posted at https://beta.ietf.org/links/
>>=20
>> That page includes links to:
>> - items on the left-side at www.ietf.org (or a subset thereof)
>> - information about the next IETF meeting
>> - links to functions at datatracker.ietf.org
>>=20
>> The goal is to make this page:
>> - viewable in a single screen on a desktop/laptop display
>> - reachable via a short, memorable URL
>>=20
>> The current content includes changes implemented based on suggestions =
received via email after IETF 99. Of course, this page will be updated =
further based on input from the community.
>>=20
>> B. Ensure WCAG 2.0 compliance
>>=20
>> Since IETF 99, we have worked with the website developer to improve =
compliance. This is a requirement of the Statement of Work =
(https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf). =
We believe that has been accomplished. However, ensuring and improving =
accessibility must be part of ongoing editorial practices, so it will =
continue to be an area of focus for the website.
>>=20
>> C. Conduct review with other key audiences, especially potential =
participants and non-participants
>>=20
>> Additional interviews with members of the key audiences have been =
conducted to gather input. In general, response to the beta.ietf.org =
site was positive.  IETF newcomers say that the new site makes it easier =
to understand what the IETF is all about. Some specific suggestions have =
been incorporated into the project, and they are included at =
https://github.com/ietf/www.ietf.org/issues
>>=20
>> D. Improve data use and load times
>>=20
>> Since IETF 99, the beta.ietf.org site was placed behind the =
Cloudflare CDN. This has significantly improved load times. Of note, in =
interviews (see item C above), new or non-IETF participants located in =
Latin America and Africa did not report load time as a significant =
issue. However, as the new site moves to production, the editorial =
process will continue to fine tune how images and other elements are =
handled to further improve performance.
>>=20
>> Next steps:
>>=20
>> We are continuing to fine tune content and are aiming to move to =
production after IETF 100. One significant task remaining is to ensure =
continuity for important URLs, as specified in the Statement of Work. We =
expect to tackle that after IETF 100.
>>=20
>> We welcome input and suggestions. We held "office hours" at IETF 98 =
and IETF 99, and we will hold "office hours=E2=80=9D at IETF 100.  If =
you will be in Singapore, please take this opportunity to share feedback =
in person. Details will be posted on a sign around the IETF meeting =
registration desk. And, of course, questions or issues can always be =
raised at https://github.com/ietf/www.ietf.org/issues
>>=20
>> Sincerely,
>>   Russ Housley
>>   IETF Website Revamp Project Manager
>=20


From nobody Thu Nov  2 09:25:44 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 F3FFD13F736 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 09:25:42 -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.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 i2nswKatBh_C for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 09:25:41 -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 4F6D913F728 for <ietf@ietf.org>; Thu,  2 Nov 2017 09:25:41 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id r128so81104oig.9 for <ietf@ietf.org>; Thu, 02 Nov 2017 09:25: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=TioX9iaIms2ArdPwiHh4SLazuJVCeaBKVoloxcFNQ9Y=; b=Y2NvaocRXDN8QWye459SDqV9dSUKZm89Ba2GERc9uA80Uv8geImbGzoPXHtoCkTuTn PX6WwbWQWGy1h+tngDcqDNVcQdZx8dmmHZc8dCw1J+388rNuuPEoselVBL5BoD2quNit nWvbVv1UfwQdPUMquFhhXWiEvUvAZSvvfg9A3pvOM4uue0AFKBMfiiZhiuTcZ3qVlajE cgxWx1fIvGGqK86Ek2PHGc3Im3hIVW1Vdt4j3FBF/8XOUCSqGoifCHAtP8I9Ii5IGwj0 cH1RIq0ScRny3D7w3ed1P8m1ze1mPTa2TQpGs4JuV0JfJcpcs7djZQ0V6zxjhTlZi0RW 3zXw==
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=TioX9iaIms2ArdPwiHh4SLazuJVCeaBKVoloxcFNQ9Y=; b=lqCYj9KNT+9f6WuwivVC4vzQkcYBv7Zq4RVNRA705M9KS8Yb+bT0ZbuLiT7WiT+xD8 rfkRUH4gfjFeCDzuk7zWvrJexWuUeRPtjbzN80LTEsuP+tyjrz/Lp6MOaV9aMCzFQeah fh6jc3hQnFg6va1O6kcVyI4oirzzOWkdhXfyG/92vVkw/baKtSGty/73KBBkiy//RwUC W+w2lbRWOSkFkPZgFdnT0ppnNZWe1dcFmTIYElQmtAtNbTQuGVEagw7eZULt4+kyEsKu keuIYCJKXQkEvotjZjdOh1DuG8PWA+JyDZYMVVk5eP2FEi7dkstT7zWnVb/+ts8T4hfq zjCw==
X-Gm-Message-State: AMCzsaXcZXxLBbzt5PMWcYE58NcVaRHL3q3DtABMBMqmBcN2WaRTc212 3awJzf0V3kkjuOXApWdEOUDsIfG9WYlKZ99Uuq4=
X-Google-Smtp-Source: ABhQp+S83UUR5Z+u3xtRy9z0iFlqtXM1ppf4mWUSARG0xXDP5NKzYwY6FJAOjxPCiuhuLgE/jDd2z88D5JD+OK9cgns=
X-Received: by 10.202.206.196 with SMTP id e187mr2260604oig.349.1509639940622;  Thu, 02 Nov 2017 09:25:40 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.80.42 with HTTP; Thu, 2 Nov 2017 09:25:39 -0700 (PDT)
In-Reply-To: <20171102060123.GA25640@faui40p.informatik.uni-erlangen.de>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <6.2.5.6.2.20171101132245.10d04f48@elandnews.com> <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com> <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com> <20171102060123.GA25640@faui40p.informatik.uni-erlangen.de>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 2 Nov 2017 12:25:39 -0400
X-Google-Sender-Auth: u2laJKwQYBR1ZSy9Dnv_hEL49dQ
Message-ID: <CAMm+LwjixEd6xgSte+gYPx7ad9Oe0vs8DtOH3MD5ioV9csvvvw@mail.gmail.com>
Subject: Re: letting IETF build on top of Open Source technology
To: Toerless Eckert <tte@cs.fau.de>
Cc: Alia Atlas <akatlas@gmail.com>, S Moonesamy <sm+ietf@elandsys.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4S3Vk7JFHM0kMUaEI3sic0FGY_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: Thu, 02 Nov 2017 16:25:43 -0000

On Thu, Nov 2, 2017 at 2:01 AM, Toerless Eckert <tte@cs.fau.de> wrote:
> How do i know which behavior of your code is a bug and which behavior is a feature ?

The point of this exercise is to make the implementation and
specification match as closely as is feasible without the extreme
overhead of formal proof.

There is still the possibility/possibility that the specification is
broken. Hence the reason to participate in a standards review process.


From nobody Thu Nov  2 10:01:52 2017
Return-Path: <mfidelman@meetinghouse.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 4DEE313F765 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 10:01:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCvXoWNnmOeO for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 10:01:45 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2172713B262 for <ietf@ietf.org>; Thu,  2 Nov 2017 10:01:44 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 4BCD94D95E8 for <ietf@ietf.org>; Thu,  2 Nov 2017 13:01:43 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FYUvgyq0LVmS for <ietf@ietf.org>; Thu,  2 Nov 2017 13:01:27 -0400 (EDT)
Received: from Miless-MBP.fios-router.home (pool-100-0-27-219.bstnma.fios.verizon.net [100.0.27.219]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 6527D4D9577 for <ietf@ietf.org>; Thu,  2 Nov 2017 13:01:27 -0400 (EDT)
Subject: Re: letting IETF build on top of Open Source technology
To: ietf@ietf.org
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <6.2.5.6.2.20171101132245.10d04f48@elandnews.com> <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com> <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <a72fab79-1c5b-07a2-b21d-efe4491d9339@meetinghouse.net>
Date: Thu, 2 Nov 2017 13:01:26 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R76C_7HfnLiW0h1Mtlb7N_TVAt4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 17:01:46 -0000

On 11/1/17 10:35 PM, Phillip Hallam-Baker wrote:

> My specifications are my code.
>
> If you look at any of the protocol specifications for the Mesh, you
> will find a reference section in the back that is generated directly
> from the schema and examples taken from running code generated from
> the same schema. And the running code used to generate the examples is
> the same as the reference code.
>
That's a little bit disingenuous, isn't it - particularly since you've 
written quite a bit of documentation beyond your code.

Beyond that, the point of a specification is to DRIVE implementation & 
testing of multiple, interoperable implementations.  A reference 
implementation is one thing, but as soon as one specific piece of code 
(warts & all) becomes the "spec" - it's not really a specification anymore.

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Thu Nov  2 11:21:19 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 89F6513F7DD for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 11:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (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 SHIa6abb8mGZ for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 11:21:15 -0700 (PDT)
Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::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 8BF2513F7B7 for <ietf@ietf.org>; Thu,  2 Nov 2017 11:21:15 -0700 (PDT)
Received: by mail-pg0-x22a.google.com with SMTP id b192so331110pga.2 for <ietf@ietf.org>; Thu, 02 Nov 2017 11:21:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NGlVXBOYTXP7Ku4AEcSUnhIcpl+N4WQGo5FdeaG2+YI=; b=Bo/7axCicPrHSkaMVpywEKvX44TYHuT8QXVj6D1CxXaAmrkov2JzHGrBKBhkncNeRv M0SiuXYOWBSfPlnMlQ9KUspJJ3eKRogxzH4ap3N5cpWTJMXt1IISw+yAfqIN0y3kaUDT wn3YcIS/6dKlBoRkYgf7GSml/i85AEkbzRFCVccBwfxkXT/MPtCuqfj3qUR9RusqKhkg RHnXcP/G/XNH6MHRqswEf+R1XOqcbQPzjOG47KvkQLjl07nH3/aL2Ux6KVAxEQO+suIg rndWIBZYmR/6/qgqeFBpSCiHAzftGPUN/Z4SK+LAu6rA/f5s+t+Ig1PBrCVn4DZ5eHvI dPxg==
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=NGlVXBOYTXP7Ku4AEcSUnhIcpl+N4WQGo5FdeaG2+YI=; b=IgZBoCTyTTAa5uXCDrlOGdVYnWztgQ+fHEsMmfA23gIfnRjeYtPfAiIYI7MFjIs9/D F9N+y7mkbP2TmErUYHxccO0jX4GCNgTHrPx2kbWy5QxEbddSP8BO6ciWQpi8VF4w3rWK ptgE4VZp+3ZvLy1o9dhoEirYjIUXIu6Jk1YQqc3tRZ/gWVxL0I2Tag8BbqWiZ1xpWHcq 4M1a239bwepZAZrFY+n8bvGdD9q/0pI28vyikcdqJlAND4wvT71FYOL9Mc3VEJj2QB2j r8WSiCapLczFQ3V6iagjG4cA2qXbFvH0PHtp6nntxuO0qGCaFVq0pUd1RhcMbJnSZtw7 /l1A==
X-Gm-Message-State: AMCzsaV7nuipE5aJq3maIbPNTLki51nT15GniVylVnHpx809HTh64PZ2 XgPAVoI7uSwazPGTlXxuBVMGMw==
X-Google-Smtp-Source: ABhQp+RHd/EsBqkOzOP0q8yzGK1CE1wxbVrWnfZwknx55rmwY2B7XLzGiOtvx4qBm47R/+m0eHb6Zg==
X-Received: by 10.101.88.14 with SMTP id g14mr4584189pgr.412.1509646874551; Thu, 02 Nov 2017 11:21:14 -0700 (PDT)
Received: from ?IPv6:2620::10e7:10:3ccd:59e3:6241:9918? ([2620:0:10e7:10:3ccd:59e3:6241:9918]) by smtp.gmail.com with ESMTPSA id o128sm7164652pfg.118.2017.11.02.11.21.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Nov 2017 11:21:13 -0700 (PDT)
From: james woodyatt <jhw@google.com>
Message-Id: <DD29EFBB-F802-4B4F-8164-A39DDF3F009E@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7BFD4C26-CC74-4EC9-8164-EE2792DFC864"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Proposal to revise ISOC's mission statement
Date: Thu, 2 Nov 2017 11:21:12 -0700
In-Reply-To: <CAMm+Lwi8iiZVCiZ12RmYGCBHUzvAjBTs6a7pahRcF3oVD0tkLQ@mail.gmail.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
To: Phillip Hallam-Baker <phill@hallambaker.com>
References: <20171029003141.27C58CC43B@server1.neighborhoods.net> <AB7003B1-6F78-444F-9852-DF5B46A6C542@shockey.us> <CAMm+LwgDcsUF=QXuM0xgMP=1brSGzwn-g_g+25ViA79SHWFktw@mail.gmail.com> <0997d8de-bf01-f9f5-fc32-031ad44402f0@google.com> <CAMm+Lwi8iiZVCiZ12RmYGCBHUzvAjBTs6a7pahRcF3oVD0tkLQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wbpUIvx3TPZAoHNZhd0aHa-i5DA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 18:21:17 -0000

--Apple-Mail=_7BFD4C26-CC74-4EC9-8164-EE2792DFC864
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Nov 1, 2017, at 11:14, Phillip Hallam-Baker <phill@hallambaker.com> =
wrote:
> On Tue, Oct 31, 2017 at 5:44 PM, james woodyatt <jhw@google.com =
<mailto:jhw@google.com>> wrote:
>>=20
>>=20
>> According to that view, it will be someone else, unless "our" plan to
>> protect "society" from the criminal users of the Internet is =
adequate.
>>=20
>> Absolutely speaking *only* for myself here, but I view talking about =
plans
>> "to protect society from the Internet itself" like a pretty much =
straight up
>> attack on the fundamental idea of an Internet Society as a thing =
worthy of
>> that name.
>=20
> [=E2=80=A6]
> Your response here is the response typical of many technologists,
> 'nothing to do with me=E2=80=99.

I think you may have mischaracterized my response here. When I speak =
only for myself, I am disclaiming any representation of the entity that =
owns the domain name in my email address. I=E2=80=99m speaking as an =
individual and independent participant, and I think the Internet =
society, and the set of political, philosophical and economic problems =
it poses, has everything to do with me.

> Having been involved in national politics in
> multiple countries, I can tell you that approach is not going to be
> remotely acceptable to elected representatives whose constituents rely
> on them.
>=20
> Congressional, EU action is inevitable, in fact it has already begun.

I=E2=80=99m not taking "that approach=E2=80=9D at all. I=E2=80=99m =
trying to point out that a strong majority our elected representatives, =
particularly most of the ones who are powerful members of the ruling =
parties, view the fundamental concept of an Internet Society as =
essentially unacceptable. In that light, I think that revising the ISOC =
mission statement to align better with their view of the world would be =
to neuter the ISOC completely. I=E2=80=99m not sure that=E2=80=99s an =
outcome I would support, but I do think pretending that we aren=E2=80=99t =
doing that is a road to failure.

> The question is one of framing. Right now, the Internet is seen as the
> problem because it was the new factor that was introduced and
> invalidated the assumptions that the legacy infrastructures depended
> on. If we don't want to get regulated to heck and back, we have to
> change the conversation so that policy makers understand that the
> Internet is the one infrastructure that was originally designed with
> the understanding that every device would be connected to every other
> device and that this would create a new set of security requirements.

My sense of politics tell me that the pressure for the Internet to be =
=E2=80=9Cregulated to heck and back=E2=80=9D originates from sources =
across the full spectrum of politics. It=E2=80=99s an overwhelming and =
irresistible force. We *will* be regulated to heck and back, and =
moreover, maybe that=E2=80=99s a thing reasonable people can welcome.

The relevant question here, I believe, is whose political interests will =
be guarded by the inevitable new regulations, and whose political =
interests will be damaged in the construction of those guard towers, and =
I don=E2=80=99t agree there is anything to be gained by lecturing policy =
makers about how the original design of the Internet was expressly to =
create a whole new system of security requirements=E2=80=94 which, =
let=E2=80=99s be honest, they have spent the last several decades in a =
determined and furious effort to sweep those new security issues under a =
rug conveniently provided to them by technology industry lobbyists. =
They=E2=80=99re not likely to take that lecturing in the spirit in which =
we might hope to be seen giving it.

What I would say we should want is a voice that provides some kind of =
counterpoint to those voices with large sunk costs in the infrastructure =
that needs to be redesigned and reconstructed for the new world where =
there is an Internet. There are plenty of other organizations that can =
devote themselves to advocating for big technology companies, advocating =
for ordinary private individuals, advocating for returning to an old =
pre-Internet world, et cetera. Where the ISOC can help, I would say, is =
to be an otherwise neutral advocate for embracing the new Internet =
Society, which includes refactoring the world's legacy infrastructure =
for dealing with the new security requirements.

> [=E2=80=A6] Well we have built a whole new world and it has replaced =
the old one. And a lot of people are rather upset with us as a result =
[=E2=80=A6].


I know. Most days, lately, I am considering myself one of them. Which is =
why I am a member of other organizations dedicated, among other things, =
to regulating the Internet to heck and back. Note well: I am not =
advocating for ISOC to be yet another one of those organizations. Quite =
the opposite, actually, I kind of want the ISOC to be neutral about =
that.


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


--Apple-Mail=_7BFD4C26-CC74-4EC9-8164-EE2792DFC864
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 Nov 1, 2017, at 11:14, Phillip Hallam-Baker &lt;<a =
href=3D"mailto:phill@hallambaker.com" =
class=3D"">phill@hallambaker.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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"">On Tue, Oct 31, 2017 at 5:44 PM, james =
woodyatt &lt;</span><a href=3D"mailto:jhw@google.com" =
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-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">jhw@google.com</a><span style=3D"font-family: Menlo-Regular; =
font-size: 11px; 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"">&gt; wrote:</span><blockquote type=3D"cite"=
 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-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D""><br class=3D"">According to that view, it will be someone =
else, unless "our" plan to<br class=3D"">protect "society" from the =
criminal users of the Internet is adequate.<br class=3D""><br =
class=3D"">Absolutely speaking *only* for myself here, but I view =
talking about plans<br class=3D"">"to protect society from the Internet =
itself" like a pretty much straight up<br class=3D"">attack on the =
fundamental idea of an Internet Society as a thing worthy of<br =
class=3D"">that name.<br class=3D""></blockquote><br style=3D"font-family:=
 Menlo-Regular; font-size: 11px; 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""><font =
face=3D"Menlo-Regular" class=3D""><span style=3D"font-size: 11px;" =
class=3D"">[=E2=80=A6]</span></font><br style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; 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"">Your response here =
is the response typical of many technologists,</span><br =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; =
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"">'nothing to do with =
me=E2=80=99.</span></div></blockquote><div><br class=3D""></div><div>I =
think you may have mischaracterized my response here. When I speak only =
for myself, I am disclaiming any representation of the entity that owns =
the domain name in my email address. I=E2=80=99m speaking as an =
individual and independent participant, and I think the Internet =
society, and the set of political, philosophical and economic problems =
it poses, has everything to do with me.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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"">Having been involved in national politics =
in</span><br style=3D"font-family: Menlo-Regular; font-size: 11px; =
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: =
Menlo-Regular; font-size: 11px; 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"">multiple countries, I can tell you that =
approach is not going to be</span><br style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; 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"">remotely acceptable =
to elected representatives whose constituents rely</span><br =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; =
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"">on them.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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""><br =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; =
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"">Congressional, EU action is inevitable, in fact =
it has already begun.</span><br style=3D"font-family: Menlo-Regular; =
font-size: 11px; 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><div>I=E2=80=99m =
not taking "that approach=E2=80=9D at all. I=E2=80=99m trying to point =
out that a strong majority our elected representatives, particularly =
most of the ones who are powerful members of the ruling parties, view =
the fundamental concept of an Internet Society as essentially =
unacceptable. In that light, I think that revising the ISOC mission =
statement to align better with their view of the world would be to =
neuter the ISOC completely. I=E2=80=99m not sure that=E2=80=99s an =
outcome I would support, but I do think pretending that we aren=E2=80=99t =
doing that is a road to failure.</div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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"">The question is one of framing. Right =
now, the Internet is seen as the</span><br style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; 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"">problem because it =
was the new factor that was introduced and</span><br style=3D"font-family:=
 Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; 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"">invalidated the =
assumptions that the legacy infrastructures depended</span><br =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; =
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"">on. If we don't want to get regulated to heck =
and back, we have to</span><br style=3D"font-family: Menlo-Regular; =
font-size: 11px; 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: Menlo-Regular; font-size: 11px; 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"">change the =
conversation so that policy makers understand that the</span><br =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; =
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"">Internet is the one infrastructure that was =
originally designed with</span><br style=3D"font-family: Menlo-Regular; =
font-size: 11px; 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: Menlo-Regular; font-size: 11px; 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"">the understanding =
that every device would be connected to every other</span><br =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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: Menlo-Regular; font-size: 11px; =
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"">device and that this would create a new set of =
security requirements.</span><br style=3D"font-family: Menlo-Regular; =
font-size: 11px; 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><div>My sense of =
politics tell me that the pressure for the Internet to be =E2=80=9Cregulat=
ed to heck and back=E2=80=9D originates from sources across the full =
spectrum of politics. It=E2=80=99s an overwhelming and irresistible =
force. We *will* be regulated to heck and back, and moreover, maybe =
that=E2=80=99s a thing reasonable people can welcome.</div><div><br =
class=3D""></div><div>The relevant question here, I believe, is whose =
political interests will be guarded by the inevitable new regulations, =
and whose political interests will be damaged in the construction of =
those guard towers, and I don=E2=80=99t agree there is anything to be =
gained by lecturing policy makers about how the original design of the =
Internet was expressly to create a whole new system of security =
requirements=E2=80=94 which, let=E2=80=99s be honest, they have spent =
the last several decades in a determined and furious effort to sweep =
those new security issues under a rug conveniently provided to them by =
technology industry lobbyists. They=E2=80=99re not likely to take that =
lecturing in the spirit in which we might hope to be seen giving =
it.</div><div><br class=3D""></div><div>What I would say we should want =
is a voice that provides some kind of counterpoint to those voices with =
large sunk costs in the infrastructure that needs to be redesigned and =
reconstructed for the new world where there is an Internet. There are =
plenty of other organizations that can devote themselves to advocating =
for big technology companies, advocating for ordinary private =
individuals, advocating for returning to an old pre-Internet world, et =
cetera. Where the ISOC can help, I would say, is to be an otherwise =
neutral advocate for embracing the new Internet Society, which includes =
refactoring the world's legacy infrastructure for dealing with the new =
security requirements.</div><div><br class=3D""></div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 11px; 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"">[=E2=80=A6] Well we&nbsp;</span><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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"">have built a whole =
new world and it has replaced the old one. And a&nbsp;</span><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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"">lot of people are =
rather upset with us as a result [=E2=80=A6]</span><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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"">.</span></div></blockquote></div><div class=3D""><br =
class=3D""></div><div class=3D"">I know. Most days, lately, I am =
considering myself one of them. Which is why I am a member of other =
organizations dedicated, among other things, to regulating the Internet =
to heck and back. Note well: I am not advocating for ISOC to be yet =
another one of those organizations. Quite the opposite, actually, I kind =
of want the ISOC to be neutral about that.</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></div></body></html>=

--Apple-Mail=_7BFD4C26-CC74-4EC9-8164-EE2792DFC864--


From nobody Thu Nov  2 12:23:45 2017
Return-Path: <pat.thaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859FF13F5CA for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 12:23:43 -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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCPugbTObDxn for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 12:23:40 -0700 (PDT)
Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com [IPv6:2607:f8b0:400d: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 F218213F777 for <ietf@ietf.org>; Thu,  2 Nov 2017 12:23:39 -0700 (PDT)
Received: by mail-qk0-x22f.google.com with SMTP id l194so657502qke.13 for <ietf@ietf.org>; Thu, 02 Nov 2017 12:23:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=voUYRsJAmMJYImxXC5DBcFqCQqguBN55AskTIG/6xiI=; b=Mbhr/+/GlcIVXfjkWoRLFrKH2knmsonW7+rWEzyPSOmBh2vrlD3qXiTE481qD+SMl1 8f26ibWX/572prHBrJzVFNe5EITBaeBX60e+x8zqBwJ2O53wZwhux9l70S0oXzdJZI32 xx2yBOXjY/FF7ejpVvQvVtP7XSxjvL0vhTt3c=
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=voUYRsJAmMJYImxXC5DBcFqCQqguBN55AskTIG/6xiI=; b=mCCxI2gE/x9zQ0EcU2PvhhNtHyvCKKrlmAtgI8R0OrTYqPr/JUESggJTcmbysJnztc fp93652SD2H06InQph9jKnFYvmYdt+dP9AsPlZO5DhclQRJaMM72uGcZ1XUV1JxXAsmt T/cZGBK0MvyxhJmL10FZ5M073SSYyRueoFDRzKqTsSu4Mg+RIj6w0ynOZ4sp0C91cGDV /lFK8hZbZvkykmSMaA2x3ENuB/0Tm1pd6+BCvIYMhLHI2VWcF5HZ9811Ss21LMjeg3E/ kVqinUqkc30pkIIhvKY6PGo/yWaQP7Btas4q08YO3zEhHmkRHBQ//CSbvajUGD6M2sx9 AoKg==
X-Gm-Message-State: AMCzsaWxVh7O5cEZZb2uTsymueqLLDzO07+Z2X/LZZqZuk60Xin6zCYT 5e8xr1NRDB90QN7YFkS2BJAetw2wzHxt1HFpvdOpBg==
X-Google-Smtp-Source: ABhQp+QA9uQ7pblKHVopJqulIqUyHj7QVNrbcqQ8Owloq3d5zIdrVYsetVI4khTSMmPxPmQo9D68NBSWnYCRbCysMmA=
X-Received: by 10.55.121.194 with SMTP id u185mr6502041qkc.128.1509650617375;  Thu, 02 Nov 2017 12:23:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.85.99 with HTTP; Thu, 2 Nov 2017 12:23:36 -0700 (PDT)
In-Reply-To: <EMEW3|f40e4b5c2fe25cda5a447a2cf2f47ba4yA1FUp03tjc|ecs.soton.ac.uk|61DA7F6E-0378-49FA-B1D5-AB5D8A31A0DB@ecs.soton.ac.uk>
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com> <61DA7F6E-0378-49FA-B1D5-AB5D8A31A0DB@ecs.soton.ac.uk> <545156e4-144f-6519-0f93-b4d2fa0f6789@gmail.com> <EMEW3|f40e4b5c2fe25cda5a447a2cf2f47ba4yA1FUp03tjc|ecs.soton.ac.uk|61DA7F6E-0378-49FA-B1D5-AB5D8A31A0DB@ecs.soton.ac.uk>
From: Pat Thaler <pat.thaler@broadcom.com>
Date: Thu, 2 Nov 2017 12:23:36 -0700
Message-ID: <CAJt_5Eh8GDqTY5zTNCxqpxGZ6_40EvZkhq7vrrD=pOXfYjj6ZA@mail.gmail.com>
Subject: Re: IETF Website Status Update
To: Tim Chown <tjc@ecs.soton.ac.uk>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05a196c8d324055d04ec87"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H_zS8znNLDtjMgTGif5v73pPYwg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 19:23:43 -0000

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

On Thu, Nov 2, 2017 at 8:30 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> Hi,
>
> > On 1 Nov 2017, at 10:49, Stewart Bryant <stewart.bryant@gmail.com>
> wrote:
> >
> > Hi Russ,
> >
> > I must say I still prefer the original in terms of utility, clarity and
> information density.
>
> I must say I agree. It certainly should be possible to lay out the links
> page so that you can see where to go at a glance, rather than feeling you
> have to read the page line by line.
>

Agreed. One problem is the horizontal lists of items in a string. I find
the lists much easier to read if they are column lists where each item
starts on a new line. The string of items format makes one have to scan
across the whole list to find the item you want.

>
> > I am not sure if the font being used is mandated, but I find it far les=
s
> crisp, almost blurry compared to the smaller font of the original. I find
> such lack of crispness on web pages irritating and when I see it I am
> distracted by wondering if there is a technical failure in my system.
> People like 4K for a reason, and I see no reason why this preference woul=
d
> not be carried over to web pages.
> >
> > Whilst I understand the need to provide an accessible interface I don't
> see why there cannot simply be a parallel high efficiency interface as we=
ll.
>
> I would second this request. As per the discussion at IETF99, I accept
> that www.ietf.org is essentially conceded to IETF =E2=80=98comms and mark=
eting=E2=80=99,
> but there=E2=80=99s no reason we can=E2=80=99t have alternative well-laid=
 out index pages
> as well.
>
Agree. Also, is there going to be a link to this page from www.ietf.org?
There should be but there isn't one on the current beta top.

>
> There=E2=80=99s much of course that can be done simply by only using the
> datatracker and tools pages, which have gone from strength to strength ov=
er
> recent years.
>
> > A useful addition to both the original and to this would be a direct
> link to id-nits right next to (well right before) the submit tag.
>
> One other point is that I don=E2=80=99t think I=E2=80=99ve yet seen what =
a meeting page
> would look like in the new =E2=80=9Cglossy" format.
> Under the new system, what would https://www.ietf.org/meeting/
> 100/index.html look like?  If it=E2=80=99s https://beta.ietf.org/how/
> meetings/upcoming/100/, that=E2=80=99s not really comparable, yet.
> That=E2=80=99s a really useful, and clearly laid out, page for finding in=
fo at
> meetings.
> I assume there=E2=80=99s a change coming, as meeting pages fall under www=
.ietf.org
> .
>
> Thanks,
> Tim
>
> >
> > - Stewart
> >
> >
> > On 31/10/2017 21:36, Russ Housley wrote:
> >> I want to share an update on progress on the IETF website revamp
> project. In particular I=E2=80=99d like to highlight what has been done t=
o respond
> to feedback from the IETF community received around IETF 99.
> >>
> >> A. Provide a landing page dedicated to current IETF participants
> >>
> >> A draft is currently posted at https://beta.ietf.org/links/
> >>
> >> That page includes links to:
> >> - items on the left-side at www.ietf.org (or a subset thereof)
> >> - information about the next IETF meeting
> >> - links to functions at datatracker.ietf.org
> >>
> >> The goal is to make this page:
> >> - viewable in a single screen on a desktop/laptop display
> >> - reachable via a short, memorable URL
> >>
> >> The current content includes changes implemented based on suggestions
> received via email after IETF 99. Of course, this page will be updated
> further based on input from the community.
> >>
> >> B. Ensure WCAG 2.0 compliance
> >>
> >> Since IETF 99, we have worked with the website developer to improve
> compliance. This is a requirement of the Statement of Work (
> https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf). We
> believe that has been accomplished. However, ensuring and improving
> accessibility must be part of ongoing editorial practices, so it will
> continue to be an area of focus for the website.
> >>
> >> C. Conduct review with other key audiences, especially potential
> participants and non-participants
> >>
> >> Additional interviews with members of the key audiences have been
> conducted to gather input. In general, response to the beta.ietf.org site
> was positive.  IETF newcomers say that the new site makes it easier to
> understand what the IETF is all about. Some specific suggestions have bee=
n
> incorporated into the project, and they are included at
> https://github.com/ietf/www.ietf.org/issues
> >>
> >> D. Improve data use and load times
> >>
> >> Since IETF 99, the beta.ietf.org site was placed behind the Cloudflare
> CDN. This has significantly improved load times. Of note, in interviews
> (see item C above), new or non-IETF participants located in Latin America
> and Africa did not report load time as a significant issue. However, as t=
he
> new site moves to production, the editorial process will continue to fine
> tune how images and other elements are handled to further improve
> performance.
> >>
> >> Next steps:
> >>
> >> We are continuing to fine tune content and are aiming to move to
> production after IETF 100. One significant task remaining is to ensure
> continuity for important URLs, as specified in the Statement of Work. We
> expect to tackle that after IETF 100.
> >>
> >> We welcome input and suggestions. We held "office hours" at IETF 98 an=
d
> IETF 99, and we will hold "office hours=E2=80=9D at IETF 100.  If you wil=
l be in
> Singapore, please take this opportunity to share feedback in person.
> Details will be posted on a sign around the IETF meeting registration des=
k.
> And, of course, questions or issues can always be raised at
> https://github.com/ietf/www.ietf.org/issues
> >>
> >> Sincerely,
> >>   Russ Housley
> >>   IETF Website Revamp Project Manager
> >
>
>

--94eb2c05a196c8d324055d04ec87
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 Thu, Nov 2, 2017 at 8:30 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=
=3D"mailto:tjc@ecs.soton.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<span class=3D""><br>
&gt; On 1 Nov 2017, at 10:49, Stewart Bryant &lt;<a href=3D"mailto:stewart.=
bryant@gmail.com">stewart.bryant@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Russ,<br>
&gt;<br>
&gt; I must say I still prefer the original in terms of utility, clarity an=
d information density.<br>
<br>
</span>I must say I agree. It certainly should be possible to lay out the l=
inks page so that you can see where to go at a glance, rather than feeling =
you have to read the page line by line.<br></blockquote><div><br></div><div=
>Agreed. One problem is the horizontal lists of items in a string. I find t=
he lists much easier to read if they are column lists where each item start=
s on a new line. The string of items format makes one have to scan across t=
he whole list to find the item you want.=C2=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<span class=3D""><br>
&gt; I am not sure if the font being used is mandated, but I find it far le=
ss crisp, almost blurry compared to the smaller font of the original. I fin=
d such lack of crispness on web pages irritating and when I see it I am dis=
tracted by wondering if there is a technical failure in my system. People l=
ike 4K for a reason, and I see no reason why this preference would not be c=
arried over to web pages.<br>
&gt;<br>
&gt; Whilst I understand the need to provide an accessible interface I don&=
#39;t see why there cannot simply be a parallel high efficiency interface a=
s well.<br>
<br>
</span>I would second this request. As per the discussion at IETF99, I acce=
pt that <a href=3D"http://www.ietf.org" rel=3D"noreferrer" target=3D"_blank=
">www.ietf.org</a> is essentially conceded to IETF =E2=80=98comms and marke=
ting=E2=80=99, but there=E2=80=99s no reason we can=E2=80=99t have alternat=
ive well-laid out index pages as well.<br></blockquote><div>Agree. Also, is=
 there going to be a link to this page from <a href=3D"http://www.ietf.org"=
>www.ietf.org</a>? There should be but there isn&#39;t one on the current b=
eta top.=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
There=E2=80=99s much of course that can be done simply by only using the da=
tatracker and tools pages, which have gone from strength to strength over r=
ecent years.<br>
<span class=3D""><br>
&gt; A useful addition to both the original and to this would be a direct l=
ink to id-nits right next to (well right before) the submit tag.<br>
<br>
</span>One other point is that I don=E2=80=99t think I=E2=80=99ve yet seen =
what a meeting page would look like in the new =E2=80=9Cglossy&quot; format=
.<br>
Under the new system, what would <a href=3D"https://www.ietf.org/meeting/10=
0/index.html" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mee=
ting/<wbr>100/index.html</a> look like?=C2=A0 If it=E2=80=99s <a href=3D"ht=
tps://beta.ietf.org/how/meetings/upcoming/100/" rel=3D"noreferrer" target=
=3D"_blank">https://beta.ietf.org/how/<wbr>meetings/upcoming/100/</a>, that=
=E2=80=99s not really comparable, yet.<br>
That=E2=80=99s a really useful, and clearly laid out, page for finding info=
 at meetings.<br>
I assume there=E2=80=99s a change coming, as meeting pages fall under <a hr=
ef=3D"http://www.ietf.org" rel=3D"noreferrer" target=3D"_blank">www.ietf.or=
g</a>.<br>
<br>
Thanks,<br>
Tim<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt;<br>
&gt; - Stewart<br>
&gt;<br>
&gt;<br>
&gt; On 31/10/2017 21:36, Russ Housley wrote:<br>
&gt;&gt; I want to share an update on progress on the IETF website revamp p=
roject. In particular I=E2=80=99d like to highlight what has been done to r=
espond to feedback from the IETF community received around IETF 99.<br>
&gt;&gt;<br>
&gt;&gt; A. Provide a landing page dedicated to current IETF participants<b=
r>
&gt;&gt;<br>
&gt;&gt; A draft is currently posted at <a href=3D"https://beta.ietf.org/li=
nks/" rel=3D"noreferrer" target=3D"_blank">https://beta.ietf.org/links/</a>=
<br>
&gt;&gt;<br>
&gt;&gt; That page includes links to:<br>
&gt;&gt; - items on the left-side at <a href=3D"http://www.ietf.org" rel=3D=
"noreferrer" target=3D"_blank">www.ietf.org</a> (or a subset thereof)<br>
&gt;&gt; - information about the next IETF meeting<br>
&gt;&gt; - links to functions at <a href=3D"http://datatracker.ietf.org" re=
l=3D"noreferrer" target=3D"_blank">datatracker.ietf.org</a><br>
&gt;&gt;<br>
&gt;&gt; The goal is to make this page:<br>
&gt;&gt; - viewable in a single screen on a desktop/laptop display<br>
&gt;&gt; - reachable via a short, memorable URL<br>
&gt;&gt;<br>
&gt;&gt; The current content includes changes implemented based on suggesti=
ons received via email after IETF 99. Of course, this page will be updated =
further based on input from the community.<br>
&gt;&gt;<br>
&gt;&gt; B. Ensure WCAG 2.0 compliance<br>
&gt;&gt;<br>
&gt;&gt; Since IETF 99, we have worked with the website developer to improv=
e compliance. This is a requirement of the Statement of Work (<a href=3D"ht=
tps://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf" rel=3D"n=
oreferrer" target=3D"_blank">https://iaoc.ietf.org/<wbr>documents/IETF-Webs=
ite-SOW-<wbr>20140604-Final.pdf</a>). We believe that has been accomplished=
. However, ensuring and improving accessibility must be part of ongoing edi=
torial practices, so it will continue to be an area of focus for the websit=
e.<br>
&gt;&gt;<br>
&gt;&gt; C. Conduct review with other key audiences, especially potential p=
articipants and non-participants<br>
&gt;&gt;<br>
&gt;&gt; Additional interviews with members of the key audiences have been =
conducted to gather input. In general, response to the <a href=3D"http://be=
ta.ietf.org" rel=3D"noreferrer" target=3D"_blank">beta.ietf.org</a> site wa=
s positive.=C2=A0 IETF newcomers say that the new site makes it easier to u=
nderstand what the IETF is all about. Some specific suggestions have been i=
ncorporated into the project, and they are included at <a href=3D"https://g=
ithub.com/ietf/www.ietf.org/issues" rel=3D"noreferrer" target=3D"_blank">ht=
tps://github.com/ietf/www.<wbr>ietf.org/issues</a><br>
&gt;&gt;<br>
&gt;&gt; D. Improve data use and load times<br>
&gt;&gt;<br>
&gt;&gt; Since IETF 99, the <a href=3D"http://beta.ietf.org" rel=3D"norefer=
rer" target=3D"_blank">beta.ietf.org</a> site was placed behind the Cloudfl=
are CDN. This has significantly improved load times. Of note, in interviews=
 (see item C above), new or non-IETF participants located in Latin America =
and Africa did not report load time as a significant issue. However, as the=
 new site moves to production, the editorial process will continue to fine =
tune how images and other elements are handled to further improve performan=
ce.<br>
&gt;&gt;<br>
&gt;&gt; Next steps:<br>
&gt;&gt;<br>
&gt;&gt; We are continuing to fine tune content and are aiming to move to p=
roduction after IETF 100. One significant task remaining is to ensure conti=
nuity for important URLs, as specified in the Statement of Work. We expect =
to tackle that after IETF 100.<br>
&gt;&gt;<br>
&gt;&gt; We welcome input and suggestions. We held &quot;office hours&quot;=
 at IETF 98 and IETF 99, and we will hold &quot;office hours=E2=80=9D at IE=
TF 100.=C2=A0 If you will be in Singapore, please take this opportunity to =
share feedback in person. Details will be posted on a sign around the IETF =
meeting registration desk. And, of course, questions or issues can always b=
e raised at <a href=3D"https://github.com/ietf/www.ietf.org/issues" rel=3D"=
noreferrer" target=3D"_blank">https://github.com/ietf/www.<wbr>ietf.org/iss=
ues</a><br>
&gt;&gt;<br>
&gt;&gt; Sincerely,<br>
&gt;&gt;=C2=A0 =C2=A0Russ Housley<br>
&gt;&gt;=C2=A0 =C2=A0IETF Website Revamp Project Manager<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div></div>

--94eb2c05a196c8d324055d04ec87--


From nobody Thu Nov  2 13:07:57 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 5B8B413A1F4 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 13:07: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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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 Kel9CiCIGWEc for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 13:07:53 -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 0FA9D13F90B for <ietf@ietf.org>; Thu,  2 Nov 2017 13:07:51 -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 B6C7258C500; Thu,  2 Nov 2017 21:07:47 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id A1FDDB0D06C; Thu,  2 Nov 2017 21:07:47 +0100 (CET)
Date: Thu, 2 Nov 2017 21:07:47 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Russ Housley <housley@vigilsec.com>
Cc: IETF <ietf@ietf.org>
Subject: Re: IETF Website Status Update
Message-ID: <20171102200747.GA20936@faui40p.informatik.uni-erlangen.de>
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ertXc6IuO7dzB0LnrlDWiY5rfyU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 20:07:55 -0000

Russ,

Thanks for bringing this to ietf ML.

You are referring to feedback. Are there publically accessible written versions
of all that feedback so that i could read up on it ? So far i can only see
the github issues, but i guess that that is not the only or not even
primary feedback channel, or is it ?

I did post my opinion into github issue #95.

Cheers
    Toerless

On Tue, Oct 31, 2017 at 05:36:00PM -0400, Russ Housley wrote:
> I want to share an update on progress on the IETF website revamp project. In particular I???d like to highlight what has been done to respond to feedback from the IETF community received around IETF 99.
> 
> A. Provide a landing page dedicated to current IETF participants
> 
> A draft is currently posted at https://beta.ietf.org/links/
> 
> That page includes links to:
> - items on the left-side at www.ietf.org (or a subset thereof)
> - information about the next IETF meeting 
> - links to functions at datatracker.ietf.org 
> 
> The goal is to make this page:
> - viewable in a single screen on a desktop/laptop display
> - reachable via a short, memorable URL
> 
> The current content includes changes implemented based on suggestions received via email after IETF 99. Of course, this page will be updated further based on input from the community.
> 
> B. Ensure WCAG 2.0 compliance
> 
> Since IETF 99, we have worked with the website developer to improve compliance. This is a requirement of the Statement of Work (https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf). We believe that has been accomplished. However, ensuring and improving accessibility must be part of ongoing editorial practices, so it will continue to be an area of focus for the website.
> 
> C. Conduct review with other key audiences, especially potential participants and non-participants
> 
> Additional interviews with members of the key audiences have been conducted to gather input. In general, response to the beta.ietf.org site was positive.  IETF newcomers say that the new site makes it easier to understand what the IETF is all about. Some specific suggestions have been incorporated into the project, and they are included at https://github.com/ietf/www.ietf.org/issues  
> 
> D. Improve data use and load times
> 
> Since IETF 99, the beta.ietf.org site was placed behind the Cloudflare CDN. This has significantly improved load times. Of note, in interviews (see item C above), new or non-IETF participants located in Latin America and Africa did not report load time as a significant issue. However, as the new site moves to production, the editorial process will continue to fine tune how images and other elements are handled to further improve performance.  
> 
> Next steps:
> 
> We are continuing to fine tune content and are aiming to move to production after IETF 100. One significant task remaining is to ensure continuity for important URLs, as specified in the Statement of Work. We expect to tackle that after IETF 100.
> 
> We welcome input and suggestions. We held "office hours" at IETF 98 and IETF 99, and we will hold "office hours??? at IETF 100.  If you will be in Singapore, please take this opportunity to share feedback in person. Details will be posted on a sign around the IETF meeting registration desk. And, of course, questions or issues can always be raised at https://github.com/ietf/www.ietf.org/issues  
> 
> Sincerely,
>   Russ Housley
>   IETF Website Revamp Project Manager


From nobody Thu Nov  2 13:17:03 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 1A0B513F87D for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 13:17:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, 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 hNnyFjwKALAy for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 13:17:00 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::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 BB9C113F810 for <ietf@ietf.org>; Thu,  2 Nov 2017 13:17:00 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id v132so618176oie.1 for <ietf@ietf.org>; Thu, 02 Nov 2017 13:17:00 -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:content-transfer-encoding; bh=DldW1vosckFReb4hfVkBfbatr5gIKvsdCIKH9/jWSaI=; b=N/KR2Gp0Zn70opRRmpBgZURm7JW5gYafbi2cnvN4umaXzz9urTp2jy6ng+D5U1P1WK PwzQbYDB+/EiTSxJUgtA1DohOElu1dy92Z7kTIK//4zIH2ccvrid9VBqByUU/7xLAyqv afB552Er82yWcRRP7v5USbx1jQUDLuqE9lbn++h31AmGWVpgnt9Dn/YDzqZtbqoloooy hQsKphsEH2whcxmFPpOZs/x08DWNLOZ06BRivoWTj128INZz09D3+vnePWMct/y8yeAm 08f5RcRmSGXirHOyU75D+SErjP6VS8FuXnT6EYjb7XMoh0iMmCWyd1WStcTpzqnk6kRH 4fiQ==
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:content-transfer-encoding; bh=DldW1vosckFReb4hfVkBfbatr5gIKvsdCIKH9/jWSaI=; b=fsiZK/VaaZsCzM8gKTsqweh8Wr8tAUqMLzCiZUO/B9q6ziPcw6pkmqEv8tHDVfYpCF SYydsy6r6FMexfTyAjmwwEheHb3UMXNvJmifS9OsYhyi0Utc80lx1PxKavRiTrcHXwtv IogP2zuwla5AoDv31IJuDmkSlg7Wrl3K6xeBdzQyqaly5oa39WCSNf1YhzamZ1Ackh8g uuxovIM+Tj7cQqZ1qd1FowyentWouGrtbErBapJrWFShXvvUIgSYeRtIrc1YbMKiyJWg 7ceWASKlk+WRlJHMkpTxRP7SDG9I7gji1rju5/Yzh3yl/X3rw8rjWHbgUGO4DtzSFzkE xtpg==
X-Gm-Message-State: AMCzsaW+7d3p9Wn8f/n6Lbey7Wh101tkC5urYYtDyJnVgDxEAYb9mftj vLDBXYnAVja5l+vrgNg2dd7mYp0TgnSpSHxUWrE=
X-Google-Smtp-Source: ABhQp+T7hcFJjuR1mruvx4X8wyEczh9gLUH2Ka7CAQWg6w//FR8SMQAPDw5cnOzQ2CKTnLT5Vrthw3TqyruX2XAM9/I=
X-Received: by 10.202.206.196 with SMTP id e187mr2677921oig.349.1509653820108;  Thu, 02 Nov 2017 13:17:00 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.80.42 with HTTP; Thu, 2 Nov 2017 13:16:59 -0700 (PDT)
In-Reply-To: <DD29EFBB-F802-4B4F-8164-A39DDF3F009E@google.com>
References: <20171029003141.27C58CC43B@server1.neighborhoods.net> <AB7003B1-6F78-444F-9852-DF5B46A6C542@shockey.us> <CAMm+LwgDcsUF=QXuM0xgMP=1brSGzwn-g_g+25ViA79SHWFktw@mail.gmail.com> <0997d8de-bf01-f9f5-fc32-031ad44402f0@google.com> <CAMm+Lwi8iiZVCiZ12RmYGCBHUzvAjBTs6a7pahRcF3oVD0tkLQ@mail.gmail.com> <DD29EFBB-F802-4B4F-8164-A39DDF3F009E@google.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 2 Nov 2017 16:16:59 -0400
X-Google-Sender-Auth: byB0qhsvfntzl4iAeiFmWzVEAX0
Message-ID: <CAMm+LwiAorSF6VOsVCcky3tMGS9VCS89zi5WrS5XzTt=iW277Q@mail.gmail.com>
Subject: Re: Proposal to revise ISOC's mission statement
To: james woodyatt <jhw@google.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JJXdNv9yVCGw2yCkCtgYqnjje1o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Nov 2017 20:17:02 -0000

On Thu, Nov 2, 2017 at 2:21 PM, james woodyatt <jhw@google.com> wrote:

> I=E2=80=99m not taking "that approach=E2=80=9D at all. I=E2=80=99m trying=
 to point out that a strong
> majority our elected representatives, particularly most of the ones who a=
re
> powerful members of the ruling parties, view the fundamental concept of a=
n
> Internet Society as essentially unacceptable. In that light, I think that
> revising the ISOC mission statement to align better with their view of th=
e
> world would be to neuter the ISOC completely. I=E2=80=99m not sure that=
=E2=80=99s an outcome
> I would support, but I do think pretending that we aren=E2=80=99t doing t=
hat is a
> road to failure.

That is nonsense.

If you begin by assuming absolute bad faith on the part of all elected
representatives then yes, you are going to end up in the meat grinder
because you refuse to recognize any legitimacy to their concerns
whatsoever.

The pathology of US regulation is that industry assumes that all
regulation will be utterly unacceptable, resists all attempts to come
to any form of common understanding and eventually ends up being hit
by a series of punitive regulations that are then taken as evidence
that the system is broken.


From nobody Thu Nov  2 17:30:04 2017
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2438B13FAD6 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 17:30:02 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9zSbMLWy0By for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 17:30:00 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C55FF13FAD3 for <ietf@ietf.org>; Thu,  2 Nov 2017 17:30:00 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1886120CC2; Thu,  2 Nov 2017 20:30:00 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 02 Nov 2017 20:30:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=snkm27 H1a3gnZvONrYGIXqnMH/VmUM+kA8ERAbzal9Y=; b=cNP/2U2CWb7+2jsbiMpCbe +X6xGjNfmbHms8UOkBHW9PSBnO2YPSihN+dZyzqD8t56TuHs0aEpLfl5+YaX23We /AmG9WEcgvMkvNBVIIL4mSMjHp8vNPNEaaGmVXRigvU+x2zXBttdelK1zSApi2sA oE4mtUoezbLkVoWiceZyunL9Vkj96TWPtauwC3b5QGV+gPI5ydPHQNIGvahDnU8j sfB9dGFcjsgRmEoECRfZgmcF95Rqrfrh5yT3IJQn1KKWVTPVds2j/fd6ocGXb2D+ fyfc8AnZhlvyNdAqhrcvS2e0QGOgv5LELBzbpFPIdaiyhhFYCFrG5YWNPjMKIH0Q ==
X-ME-Sender: <xms:iLj7WbOEFYDczI8cMb-sBVOUCLVKIIIZyvXgPqC0LYHuHvX2Rc-e2A>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 9A51324311; Thu,  2 Nov 2017 20:29:59 -0400 (EDT)
Subject: Re: Proposal to revise ISOC's mission statement
To: ietf@ietf.org
References: <20171029003141.27C58CC43B@server1.neighborhoods.net> <AB7003B1-6F78-444F-9852-DF5B46A6C542@shockey.us> <CAMm+LwgDcsUF=QXuM0xgMP=1brSGzwn-g_g+25ViA79SHWFktw@mail.gmail.com> <0997d8de-bf01-f9f5-fc32-031ad44402f0@google.com> <CAMm+Lwi8iiZVCiZ12RmYGCBHUzvAjBTs6a7pahRcF3oVD0tkLQ@mail.gmail.com> <DD29EFBB-F802-4B4F-8164-A39DDF3F009E@google.com> <CAMm+LwiAorSF6VOsVCcky3tMGS9VCS89zi5WrS5XzTt=iW277Q@mail.gmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <a4e31c0b-941c-7bd2-183a-13ce6d41fb01@network-heretics.com>
Date: Thu, 2 Nov 2017 20:29:58 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAMm+LwiAorSF6VOsVCcky3tMGS9VCS89zi5WrS5XzTt=iW277Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NzU_-cKvJD1MCxgdZt7qUApgWtI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 00:30:02 -0000

On 11/02/2017 04:16 PM, Phillip Hallam-Baker wrote:

> On Thu, Nov 2, 2017 at 2:21 PM, james woodyatt <jhw@google.com> wrote:
>
>> I’m not taking "that approach” at all. I’m trying to point out that a strong
>> majority our elected representatives, particularly most of the ones who are
>> powerful members of the ruling parties, view the fundamental concept of an
>> Internet Society as essentially unacceptable. In that light, I think that
>> revising the ISOC mission statement to align better with their view of the
>> world would be to neuter the ISOC completely. I’m not sure that’s an outcome
>> I would support, but I do think pretending that we aren’t doing that is a
>> road to failure.
> That is nonsense.
>
> If you begin by assuming absolute bad faith on the part of all elected
> representatives

... you are not far from the truth.   Though the reality is somewhat 
closer to selfishness and desire for ego gratification rather than 
absolute bad faith, and nearly all elected representatives rather than 
absolutely all of them.   People do sometimes run for public office for 
unselfish reasons, but (a) the good ones tend to be weeded out by the 
system, and (b) those who aren't weeded out tend to be corrupted.

> The pathology of US regulation is that industry assumes that all
> regulation will be utterly unacceptable, resists all attempts to come
> to any form of common understanding and eventually ends up being hit
> by a series of punitive regulations that are then taken as evidence
> that the system is broken.

No, industry assumes that legislators can often be bought, and that the 
purpose of legislation is to tilt the playing field in the favor of the 
buyers.   Any meaningful regulation is therefore likely to be seen as an 
insult to people who paid good money to have things go their way.

Keith



From nobody Thu Nov  2 17:50:57 2017
Return-Path: <henry@callistohouse.club>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087BA13FAE8 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 17:50:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 pc38sRYecdTp for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 17:50:52 -0700 (PDT)
Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (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 D276313FAE1 for <ietf@ietf.org>; Thu,  2 Nov 2017 17:50:51 -0700 (PDT)
Date: Thu, 02 Nov 2017 20:50:45 -0400
Authentication-Results: mail1.protonmail.ch; dkim=none
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
From: henry <henry@callistohouse.club>
Reply-To: henry <henry@callistohouse.club>
Subject: Re: Proposal to revise ISOC's mission statement
Message-ID: <1femIsrSs9b1olFF69mFjFP8QPHQ0OxjY7ZXBbr2GUkYHoy-gUUHM98Fma5CE05wyWH-jnFnxrLGTzGo6y0TiYUHwmMRWkHyGB1iU27TPO8=@callistohouse.club>
In-Reply-To: <a4e31c0b-941c-7bd2-183a-13ce6d41fb01@network-heretics.com>
References: <20171029003141.27C58CC43B@server1.neighborhoods.net> <AB7003B1-6F78-444F-9852-DF5B46A6C542@shockey.us> <CAMm+LwgDcsUF=QXuM0xgMP=1brSGzwn-g_g+25ViA79SHWFktw@mail.gmail.com> <0997d8de-bf01-f9f5-fc32-031ad44402f0@google.com> <CAMm+Lwi8iiZVCiZ12RmYGCBHUzvAjBTs6a7pahRcF3oVD0tkLQ@mail.gmail.com> <DD29EFBB-F802-4B4F-8164-A39DDF3F009E@google.com> <CAMm+LwiAorSF6VOsVCcky3tMGS9VCS89zi5WrS5XzTt=iW277Q@mail.gmail.com> <a4e31c0b-941c-7bd2-183a-13ce6d41fb01@network-heretics.com>
Feedback-ID: vEY7k4yIhKH60ezyh_ewYb5cBh9lM6d5hXuAKmMcj-2yeFvumZUf2Q6AIaPs9viRuOL95Jg0-5_mTgpMVWHl3Q==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_aaf5027e4f5540c53d518987a16a5617"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Xzu-0D5pmTaMEkpfKPMzhYqAcTI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 00:50:56 -0000

This is a multi-part message in MIME format.

--b1_aaf5027e4f5540c53d518987a16a5617
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

U2VudCBmcm9tIFByb3Rvbk1haWwgTW9iaWxlCgpPbiBUaHUsIE5vdiAyLCAyMDE3IGF0IDIwOjI5
LCBLZWl0aCBNb29yZSA8bW9vcmVAbmV0d29yay1oZXJldGljcy5jb20+IHdyb3RlOgoKPiBPbiAx
MS8wMi8yMDE3IDA0OjE2IFBNLCBQaGlsbGlwIEhhbGxhbS1CYWtlciB3cm90ZTogPiBPbiBUaHUs
IE5vdiAyLCAyMDE3IGF0IDI6MjEgUE0sIGphbWVzIHdvb2R5YXR0IHdyb3RlOiA+ID4+IEnigJlt
IG5vdCB0YWtpbmcgInRoYXQgYXBwcm9hY2giIGF0IGFsbC4gSeKAmW0gdHJ5aW5nIHRvIHBvaW50
IG91dCB0aGF0IGEgc3Ryb25nID4+IG1ham9yaXR5IG91ciBlbGVjdGVkIHJlcHJlc2VudGF0aXZl
cywgcGFydGljdWxhcmx5IG1vc3Qgb2YgdGhlIG9uZXMgd2hvIGFyZSA+PiBwb3dlcmZ1bCBtZW1i
ZXJzIG9mIHRoZSBydWxpbmcgcGFydGllcywgdmlldyB0aGUgZnVuZGFtZW50YWwgY29uY2VwdCBv
ZiBhbiA+PiBJbnRlcm5ldCBTb2NpZXR5IGFzIGVzc2VudGlhbGx5IHVuYWNjZXB0YWJsZS4gSW4g
dGhhdCBsaWdodCwgSSB0aGluayB0aGF0ID4+IHJldmlzaW5nIHRoZSBJU09DIG1pc3Npb24gc3Rh
dGVtZW50IHRvIGFsaWduIGJldHRlciB3aXRoIHRoZWlyIHZpZXcgb2YgdGhlID4+IHdvcmxkIHdv
dWxkIGJlIHRvIG5ldXRlciB0aGUgSVNPQyBjb21wbGV0ZWx5LiBJ4oCZbSBub3Qgc3VyZSB0aGF0
4oCZcyBhbiBvdXRjb21lID4+IEkgd291bGQgc3VwcG9ydCwgYnV0IEkgZG8gdGhpbmsgcHJldGVu
ZGluZyB0aGF0IHdlIGFyZW7igJl0IGRvaW5nIHRoYXQgaXMgYSA+PiByb2FkIHRvIGZhaWx1cmUu
ID4gVGhhdCBpcyBub25zZW5zZS4gPiA+IElmIHlvdSBiZWdpbiBieSBhc3N1bWluZyBhYnNvbHV0
ZSBiYWQgZmFpdGggb24gdGhlIHBhcnQgb2YgYWxsIGVsZWN0ZWQgPiByZXByZXNlbnRhdGl2ZXMg
Li4uIHlvdSBhcmUgbm90IGZhciBmcm9tIHRoZSB0cnV0aC4gICBUaG91Z2ggdGhlIHJlYWxpdHkg
aXMgc29tZXdoYXQgY2xvc2VyIHRvIHNlbGZpc2huZXNzIGFuZCBkZXNpcmUgZm9yIGVnbyBncmF0
aWZpY2F0aW9uIHJhdGhlciB0aGFuIGFic29sdXRlIGJhZCBmYWl0aCwgQGdvb2dsZS5jb20+Cgo+
IEhIPiBUaGUgc3lzdGVtIGFuZCByZXNwb25zaWJpbGl0aWVzIHRvIGlubmVyIHN0YWtlaG9sZGVy
cyBmb3JjZXMgdGhlbSB0byBiZSBwb2xpdGljYWwgYW5kIHBvbGl0aWMuIFRoZSBzeXN0ZW0gZWxl
Y3RzIHJlcHJlc2VudGF0aXZlcyBvY2Nhc2lvbmFsbHkgd2hvIHZvdGUgY29udGludWFsbHksIGFz
IHByb3h5LiBXaXRoIHByZWRpY3Rpb24gbWFya2V0cywgY29udGludWFsIHZvdGluZyBvZiBldmVy
eW9uZSwgYWJzZW50IGEgcHJveHksIHByb3ZpZGVzIGRpc3NvbHV0aW9uIG9mIGdyYWIgd2hhdCB5
b3UgY2FuIHJlc3BvbnNpYmlsaXR5IHRvIGVkdWNhdGUgdGhlIHZvdGVycyBhbmQgY29vcmRpbmF0
ZSB2b3Rlcy4gVGhlIGlubmVyIHN0YWNraG9sZGVycyBub3cgbmVlZCBiZSBwb2xpdGljLiBDaGFu
Z2UgcmVwcmVzZW50YXRpdmUgZGVtb2NyYWN5IHRvIGFuIGFkdmlzb3J5IHJvbGUuIFRlY2hub2Ny
YXRzIGVkdWNhdGUgdGhlIHBvbGl0eS4gSGVyZeKAmXMgdGhlIGtleSBpdCBzZWVtcyB0byBtZSwg
aWxsdW1pbmF0ZWQgYnkgeW91ciBvd24gd29ya2luZyBncm91cHMsIGNvbWluZyBhbmQgZ29pbmcu
IFNwcmVhZCB0aGUgbWVtZSBvZiBkcmFmdGluZyBhbmQgZm9jdXMgZ3JvdXBzLiBXZSBzZWUgaG93
IHdlbGwgaXQgd29ya3MsIHJlYWNoaW5nIGNvbnNlbnN1cy4gU3BlYWsgYWJvdXQgaXQgcG9saXRp
Y2FsIGJleW9uZCB5b3VyIGRvbWluaW9uIGFuZCBnZXQgcG9saXRpYy4gSnVzdCBteSB3YXkgb2Yg
dGhpbmtpbmcuQGdvb2dsZS5jb20+Cgo+IGFuZCBuZWFybHkgYWxsIGVsZWN0ZWQgcmVwcmVzZW50
YXRpdmVzIHJhdGhlciB0aGFuIGFic29sdXRlbHkgYWxsIG9mIHRoZW0uICAgUGVvcGxlIGRvIHNv
bWV0aW1lcyBydW4gZm9yIHB1YmxpYyBvZmZpY2UgZm9yIHVuc2VsZmlzaCByZWFzb25zLCBidXQg
KGEpIHRoZSBnb29kIG9uZXMgdGVuZCB0byBiZSB3ZWVkZWQgb3V0IGJ5IHRoZSBzeXN0ZW0sIGFu
ZCAoYikgdGhvc2Ugd2hvIGFyZW4ndCB3ZWVkZWQgb3V0IHRlbmQgdG8gYmUgY29ycnVwdGVkLkBn
b29nbGUuY29tPgoKPiBISD4geW91IHNlZSwgdGhlIHN5c3RlbSBiaWFzZXMgdGhpcyBiZWhhdmlv
ci5AZ29vZ2xlLmNvbT4KCj4gQGdvb2dsZS5jb20+Cgo+IEBnb29nbGUuY29tPgoKPiBAZ29vZ2xl
LmNvbT4KCj4+IFRoZSBwYXRob2xvZ3kgb2YgVVMgcmVndWxhdGlvbiBpcyB0aGF0IGluZHVzdHJ5
IGFzc3VtZXMgdGhhdCBhbGwgPiByZWd1bGF0aW9uIHdpbGwgYmUgdXR0ZXJseSB1bmFjY2VwdGFi
bGUsIHJlc2lzdHMgYWxsIGF0dGVtcHRzIHRvIGNvbWUgPiB0byBhbnkgZm9ybSBvZiBjb21tb24g
dW5kZXJzdGFuZGluZyBhbmQgZXZlbnR1YWxseSBlbmRzIHVwIGJlaW5nIGhpdCA+IGJ5IGEgc2Vy
aWVzIG9mIHB1bml0aXZlIHJlZ3VsYXRpb25zIHRoYXQgYXJlIHRoZW4gdGFrZW4gYXMgZXZpZGVu
Y2UgPiB0aGF0IHRoZSBzeXN0ZW0gaXMgYnJva2VuLiBObywgaW5kdXN0cnkgYXNzdW1lcyB0aGF0
IGxlZ2lzbGF0b3JzIGNhbiBvZnRlbiBiZSBib3VnaHQsIGFuZCB0aGF0IHRoZSBwdXJwb3NlIG9m
IGxlZ2lzbGF0aW9uIGlzIHRvIHRpbHQgdGhlIHBsYXlpbmcgZmllbGQgaW4gdGhlIGZhdm9yIG9m
IHRoZSBidXllcnMuICAgQW55IG1lYW5pbmdmdWwgcmVndWxhdGlvbiBpcyB0aGVyZWZvcmUgbGlr
ZWx5IHRvIGJlIHNlZW4gYXMgYW4gaW5zdWx0IHRvIHBlb3BsZSB3aG8gcGFpZCBnb29kIG1vbmV5
IHRvIGhhdmUgdGhpbmdzIGdvIHRoZWlyIHdheS4gS2VpdGggQGdvb2dsZS5jb20+Cgo+IEhIPiBh
bGwgZHVlIHJlc3BlY3QgdG93YXJkcyB5b3VyIGFzc3VtcHRpb24gZmlsbGVkIHdpdGggY3luaWNh
bCBlc3RpbWF0aW9uIG9mIG90aGVycyBtb3RpdmF0aW9ucywgd2l0aCB0aGUgZHluYW1pYyBvZiBt
YWtpbmcgdGhpbmdzIGhhcHBlbiB3aXRoaW4gZWFjaCBDb3JwIEkgdGhpbmsgaXTigJlzIG1vcmUg
ImJlZyBmb3JnaXZlbmVzcyB0aGFuIGFzayBwZXJtaXNzaW9uIiBzb3J0IG9mIGxpbWVyaWNrIHdh
eS4gV2VyZSB5b3UgdG8gc2VlIHdoYXQgcGVyc3BlY3RpdmUgSSBvZmZlciBJIHdvdWxkIGJlIGdy
YXRlZnVsLgoKPiBSb2JlcnQ=


--b1_aaf5027e4f5540c53d518987a16a5617
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PGRpdj4KICAgIDxiciAvPgo8L2Rpdj4KPGRpdj4KICAgIDxiciAvPgo8L2Rpdj4KPGRpdiBpZD0i
cHJvdG9ubWFpbF9tb2JpbGVfc2lnbmF0dXJlX2Jsb2NrIj5TZW50IGZyb20gUHJvdG9uTWFpbCBN
b2JpbGU8L2Rpdj4KPGRpdj4KICAgIDxiciAvPgogICAgPGRpdj4KICAgICAgICA8ZGl2PgogICAg
ICAgICAgICA8YnIgLz4KICAgICAgICA8L2Rpdj5PbiBUaHUsIE5vdiAyLCAyMDE3IGF0IDIwOjI5
LCBLZWl0aCBNb29yZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1vb3JlQG5ldHdvcmstaGVyZXRpY3Mu
Y29tIiBjbGFzcz0iIj5tb29yZUBuZXR3b3JrLWhlcmV0aWNzLmNvbTwvYT4mZ3Q7IHdyb3RlOjwv
ZGl2PgogICAgPGJsb2NrcXVvdGUgY2xhc3M9InByb3Rvbm1haWxfcXVvdGUiIHR5cGU9ImNpdGUi
Pk9uIDExLzAyLzIwMTcgMDQ6MTYgUE0sIFBoaWxsaXAgSGFsbGFtLUJha2VyIHdyb3RlOiAmZ3Q7
IE9uIFRodSwgTm92IDIsIDIwMTcgYXQgMjoyMSBQTSwgamFtZXMgd29vZHlhdHQKICAgICAgICA8
amh3QGdvb2dsZS5jb20+d3JvdGU6ICZndDsgJmd0OyZndDsgSeKAmW0gbm90IHRha2luZyAidGhh
dCBhcHByb2FjaCIgYXQgYWxsLiBJ4oCZbSB0cnlpbmcgdG8gcG9pbnQgb3V0IHRoYXQgYSBzdHJv
bmcgJmd0OyZndDsgbWFqb3JpdHkgb3VyIGVsZWN0ZWQgcmVwcmVzZW50YXRpdmVzLCBwYXJ0aWN1
bGFybHkgbW9zdCBvZiB0aGUgb25lcyB3aG8gYXJlICZndDsmZ3Q7IHBvd2VyZnVsIG1lbWJlcnMg
b2YgdGhlIHJ1bGluZyBwYXJ0aWVzLCB2aWV3IHRoZSBmdW5kYW1lbnRhbAogICAgICAgICAgICBj
b25jZXB0IG9mIGFuICZndDsmZ3Q7IEludGVybmV0IFNvY2lldHkgYXMgZXNzZW50aWFsbHkgdW5h
Y2NlcHRhYmxlLiBJbiB0aGF0IGxpZ2h0LCBJIHRoaW5rIHRoYXQgJmd0OyZndDsgcmV2aXNpbmcg
dGhlIElTT0MgbWlzc2lvbiBzdGF0ZW1lbnQgdG8gYWxpZ24gYmV0dGVyIHdpdGggdGhlaXIgdmll
dyBvZiB0aGUgJmd0OyZndDsgd29ybGQgd291bGQgYmUgdG8gbmV1dGVyIHRoZSBJU09DIGNvbXBs
ZXRlbHkuIEnigJltCiAgICAgICAgICAgIG5vdCBzdXJlIHRoYXTigJlzIGFuIG91dGNvbWUgJmd0
OyZndDsgSSB3b3VsZCBzdXBwb3J0LCBidXQgSSBkbyB0aGluayBwcmV0ZW5kaW5nIHRoYXQgd2Ug
YXJlbuKAmXQgZG9pbmcgdGhhdCBpcyBhICZndDsmZ3Q7IHJvYWQgdG8gZmFpbHVyZS4gJmd0OyBU
aGF0IGlzIG5vbnNlbnNlLiAmZ3Q7ICZndDsgSWYgeW91IGJlZ2luIGJ5IGFzc3VtaW5nIGFic29s
dXRlIGJhZCBmYWl0aCBvbiB0aGUgcGFydCBvZiBhbGwgZWxlY3RlZAogICAgICAgICAgICAmZ3Q7
IHJlcHJlc2VudGF0aXZlcyAuLi4geW91IGFyZSBub3QgZmFyIGZyb20gdGhlIHRydXRoLiZuYnNw
OyZuYnNwOyBUaG91Z2ggdGhlIHJlYWxpdHkgaXMgc29tZXdoYXQgY2xvc2VyIHRvIHNlbGZpc2hu
ZXNzIGFuZCBkZXNpcmUgZm9yIGVnbyBncmF0aWZpY2F0aW9uIHJhdGhlciB0aGFuIGFic29sdXRl
IGJhZCBmYWl0aCwmbmJzcDs8L2pod0Bnb29nbGUuY29tPgogICAgPC9ibG9ja3F1b3RlPgogICAg
PGJsb2NrcXVvdGUgY2xhc3M9InByb3Rvbm1haWxfcXVvdGUiIHR5cGU9ImNpdGUiPgogICAgICAg
IDxqaHdAZ29vZ2xlLmNvbT5ISCZndDsmbmJzcDtUaGUgc3lzdGVtIGFuZCByZXNwb25zaWJpbGl0
aWVzIHRvIGlubmVyIHN0YWtlaG9sZGVycyBmb3JjZXMgdGhlbSB0byBiZSBwb2xpdGljYWwgYW5k
IHBvbGl0aWMuIFRoZSBzeXN0ZW0gZWxlY3RzIHJlcHJlc2VudGF0aXZlcyBvY2Nhc2lvbmFsbHkg
d2hvIHZvdGUgY29udGludWFsbHksIGFzIHByb3h5LiBXaXRoIHByZWRpY3Rpb24gbWFya2V0cywg
Y29udGludWFsIHZvdGluZyBvZiBldmVyeW9uZSwgYWJzZW50CiAgICAgICAgICAgIGEgcHJveHks
IHByb3ZpZGVzIGRpc3NvbHV0aW9uIG9mIGdyYWIgd2hhdCB5b3UgY2FuIHJlc3BvbnNpYmlsaXR5
IHRvIGVkdWNhdGUgdGhlIHZvdGVycyBhbmQgY29vcmRpbmF0ZSB2b3Rlcy4gVGhlIGlubmVyIHN0
YWNraG9sZGVycyBub3cgbmVlZCBiZSBwb2xpdGljLiBDaGFuZ2UgcmVwcmVzZW50YXRpdmUgZGVt
b2NyYWN5IHRvIGFuIGFkdmlzb3J5IHJvbGUuIFRlY2hub2NyYXRzIGVkdWNhdGUgdGhlIHBvbGl0
eS4KICAgICAgICAgICAgSGVyZeKAmXMgdGhlIGtleSBpdCBzZWVtcyB0byBtZSwgaWxsdW1pbmF0
ZWQgYnkgeW91ciBvd24gd29ya2luZyBncm91cHMsIGNvbWluZyBhbmQgZ29pbmcuIFNwcmVhZCB0
aGUgbWVtZSBvZiBkcmFmdGluZyBhbmQgZm9jdXMgZ3JvdXBzLiBXZSBzZWUgaG93IHdlbGwgaXQg
d29ya3MsIHJlYWNoaW5nIGNvbnNlbnN1cy4gU3BlYWsgYWJvdXQgaXQgcG9saXRpY2FsIGJleW9u
ZCB5b3VyIGRvbWluaW9uIGFuZCBnZXQgcG9saXRpYy4KICAgICAgICAgICAgSnVzdCBteSB3YXkg
b2YgdGhpbmtpbmcuPC9qaHdAZ29vZ2xlLmNvbT4KICAgIDwvYmxvY2txdW90ZT4KICAgIDxibG9j
a3F1b3RlIGNsYXNzPSJwcm90b25tYWlsX3F1b3RlIiB0eXBlPSJjaXRlIj4KICAgICAgICA8amh3
QGdvb2dsZS5jb20+YW5kIG5lYXJseSBhbGwgZWxlY3RlZCByZXByZXNlbnRhdGl2ZXMgcmF0aGVy
IHRoYW4gYWJzb2x1dGVseSBhbGwgb2YgdGhlbS4mbmJzcDsmbmJzcDsgUGVvcGxlIGRvIHNvbWV0
aW1lcyBydW4gZm9yIHB1YmxpYyBvZmZpY2UgZm9yIHVuc2VsZmlzaCByZWFzb25zLCBidXQgKGEp
IHRoZSBnb29kIG9uZXMgdGVuZCB0byBiZSB3ZWVkZWQgb3V0IGJ5IHRoZSBzeXN0ZW0sIGFuZCAo
YikgdGhvc2Ugd2hvIGFyZW4ndCB3ZWVkZWQKICAgICAgICAgICAgb3V0IHRlbmQgdG8gYmUgY29y
cnVwdGVkLjwvamh3QGdvb2dsZS5jb20+CiAgICA8L2Jsb2NrcXVvdGU+CiAgICA8YmxvY2txdW90
ZSBjbGFzcz0icHJvdG9ubWFpbF9xdW90ZSIgdHlwZT0iY2l0ZSI+CiAgICAgICAgPGpod0Bnb29n
bGUuY29tPkhIJmd0OyB5b3Ugc2VlLCB0aGUgc3lzdGVtIGJpYXNlcyB0aGlzIGJlaGF2aW9yLjwv
amh3QGdvb2dsZS5jb20+CiAgICA8L2Jsb2NrcXVvdGU+CiAgICA8YmxvY2txdW90ZSBjbGFzcz0i
cHJvdG9ubWFpbF9xdW90ZSIgdHlwZT0iY2l0ZSI+CiAgICAgICAgPGpod0Bnb29nbGUuY29tPgog
ICAgICAgICAgICA8YnIgLz4KICAgICAgICA8L2pod0Bnb29nbGUuY29tPgogICAgPC9ibG9ja3F1
b3RlPgogICAgPGJsb2NrcXVvdGUgY2xhc3M9InByb3Rvbm1haWxfcXVvdGUiIHR5cGU9ImNpdGUi
PgogICAgICAgIDxqaHdAZ29vZ2xlLmNvbT4KICAgICAgICAgICAgPGJyIC8+CiAgICAgICAgPC9q
aHdAZ29vZ2xlLmNvbT4KICAgIDwvYmxvY2txdW90ZT4KICAgIDxibG9ja3F1b3RlIGNsYXNzPSJw
cm90b25tYWlsX3F1b3RlIiB0eXBlPSJjaXRlIj4KICAgICAgICA8amh3QGdvb2dsZS5jb20+CiAg
ICAgICAgICAgIDxiciAvPgogICAgICAgIDwvamh3QGdvb2dsZS5jb20+CiAgICA8L2Jsb2NrcXVv
dGU+CiAgICA8YmxvY2txdW90ZSBjbGFzcz0icHJvdG9ubWFpbF9xdW90ZSIgdHlwZT0iY2l0ZSI+
CiAgICAgICAgPGpod0Bnb29nbGUuY29tPgoKICAgICAgICAgICAgJmd0OyBUaGUgcGF0aG9sb2d5
IG9mIFVTIHJlZ3VsYXRpb24gaXMgdGhhdCBpbmR1c3RyeSBhc3N1bWVzIHRoYXQgYWxsICZndDsg
cmVndWxhdGlvbiB3aWxsIGJlIHV0dGVybHkgdW5hY2NlcHRhYmxlLCByZXNpc3RzIGFsbCBhdHRl
bXB0cyB0byBjb21lICZndDsgdG8gYW55IGZvcm0gb2YgY29tbW9uIHVuZGVyc3RhbmRpbmcgYW5k
IGV2ZW50dWFsbHkgZW5kcyB1cCBiZWluZyBoaXQgJmd0OyBieSBhIHNlcmllcyBvZiBwdW5pdGl2
ZSByZWd1bGF0aW9ucwogICAgICAgICAgICB0aGF0IGFyZSB0aGVuIHRha2VuIGFzIGV2aWRlbmNl
ICZndDsgdGhhdCB0aGUgc3lzdGVtIGlzIGJyb2tlbi4gTm8sIGluZHVzdHJ5IGFzc3VtZXMgdGhh
dCBsZWdpc2xhdG9ycyBjYW4gb2Z0ZW4gYmUgYm91Z2h0LCBhbmQgdGhhdCB0aGUgcHVycG9zZSBv
ZiBsZWdpc2xhdGlvbiBpcyB0byB0aWx0IHRoZSBwbGF5aW5nIGZpZWxkIGluIHRoZSBmYXZvciBv
ZiB0aGUgYnV5ZXJzLiZuYnNwOyZuYnNwOyBBbnkgbWVhbmluZ2Z1bAogICAgICAgICAgICByZWd1
bGF0aW9uIGlzIHRoZXJlZm9yZSBsaWtlbHkgdG8gYmUgc2VlbiBhcyBhbiBpbnN1bHQgdG8gcGVv
cGxlIHdobyBwYWlkIGdvb2QgbW9uZXkgdG8gaGF2ZSB0aGluZ3MgZ28gdGhlaXIgd2F5LiBLZWl0
aAoKCiAgICAgICAgPC9qaHdAZ29vZ2xlLmNvbT4KICAgIDwvYmxvY2txdW90ZT4KICAgIDxibG9j
a3F1b3RlIGNsYXNzPSJwcm90b25tYWlsX3F1b3RlIiB0eXBlPSJjaXRlIj5ISCZndDsgYWxsIGR1
ZSByZXNwZWN0IHRvd2FyZHMgeW91ciBhc3N1bXB0aW9uIGZpbGxlZCB3aXRoIGN5bmljYWwgZXN0
aW1hdGlvbiBvZiBvdGhlcnMgbW90aXZhdGlvbnMsIHdpdGggdGhlIGR5bmFtaWMgb2YgbWFraW5n
IHRoaW5ncyBoYXBwZW4gd2l0aGluIGVhY2ggQ29ycCBJIHRoaW5rIGl04oCZcyBtb3JlICZxdW90
O2JlZyBmb3JnaXZlbmVzcyB0aGFuIGFzayBwZXJtaXNzaW9uJnF1b3Q7IHNvcnQgb2YgbGltZXJp
Y2sgd2F5LgogICAgICAgIFdlcmUgeW91IHRvIHNlZSB3aGF0IHBlcnNwZWN0aXZlIEkgb2ZmZXIg
SSB3b3VsZCBiZSBncmF0ZWZ1bC48L2Jsb2NrcXVvdGU+CiAgICA8YmxvY2txdW90ZSBjbGFzcz0i
cHJvdG9ubWFpbF9xdW90ZSIgdHlwZT0iY2l0ZSI+Um9iZXJ0PC9ibG9ja3F1b3RlPgo8L2Rpdj4=



--b1_aaf5027e4f5540c53d518987a16a5617--


From nobody Thu Nov  2 18:17:53 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 33B3913FAF6; Thu,  2 Nov 2017 18:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=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 Dui-r6WyFAH6; Thu,  2 Nov 2017 18:17:50 -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 1D84A13FAF0; Thu,  2 Nov 2017 18:17:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 48CEFBE50; Fri,  3 Nov 2017 01:17:48 +0000 (GMT)
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 TNf2jfJuVeT5; Fri,  3 Nov 2017 01:17:46 +0000 (GMT)
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 683D8BE49; Fri,  3 Nov 2017 01:17:46 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1509671866; bh=fH3b6k0sY/FouvsxrHblMklM2SP4WV+r2Lcm1OeXpZQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=UVO3EdrIxXIB57MaWCdRBmoBJlZhjg9UNCNCaK+7XQobxxArvuqQPuFoAOl67uJ37 bfnBArAdUwvJR+ddbR4ALp9cSAvn9WZJzEbY57LM1MXlLfltVCiEiS61Z7HYS79MjO /zCylTTTv32LpX8OXpmoiaRBNXBjgZnjN00jcHBI=
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
To: draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org
Cc: ietf@ietf.org, ben@nostrum.com, aallen@blackberry.com
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
Date: Fri, 3 Nov 2017 01:17:45 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PiJdQJc8BvpRK9G28wvr0JVAtmWNcJG7L"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LVj1sSrEPwE11q6yw-s7odfCnYs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 01:17:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PiJdQJc8BvpRK9G28wvr0JVAtmWNcJG7L
Content-Type: multipart/mixed; boundary="jDLrFp5QPaQ1V1hIsvu70UWIu42O4agpC";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org
Cc: ietf@ietf.org, ben@nostrum.com, aallen@blackberry.com
Message-ID: <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt>
 (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an
 Instance ID) to Informational RFC
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com>
In-Reply-To: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com>

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


Hiya,

I don't claim to fully understand the usage of this ID,
but I'm quite sure that I have no clue what this text
is supposed to mean (as a piece of specification):

  "In particular, the "sip.instance" media feature tag
   containing the 3GPP2 MEID URN MUST NOT be included in requests or
   responses intended to convey any level of anonymity, as this could
   violate the users privacy."

I guess this is either an existing problem with whatever
a "'sip.instance' media feature tag" really is or else this
draft creates a new problem, but the quoted text seems to
me to be non-deterministic impossible-to-program-for words
seemingly about (but not actually helping with) privacy.

Am I confused?

Cheers,
S.

On 02/11/17 22:43, The IESG wrote:
>=20
> The IESG has received a request from an individual submitter to conside=
r the
> following document: - 'Using the Mobile Equipment Identity (MEID) Unifo=
rm
> Resource Name (URN)
>    as an Instance ID'
>   <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> as Information=
al RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits f=
inal
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-12-08. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the beginn=
ing of
> the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    This specification specifies how the Uniform Resource Name (URN)
>    namespace reserved for the Third Generation Partnership Project 2
>    (3GPP2) identities and its Namespace Specific String (NSS) for the
>    Mobile Equipment Identity (MEID) can be used as an instance-id.  Its=

>    purpose is to fulfill the requirements for defining how a specific
>    URN needs to be constructed and used in the "+sip.instance" Contact
>    header field parameter for outbound behavior.
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as-ins=
tanceid/
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as-ins=
tanceid/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
>=20
>=20
>=20


--jDLrFp5QPaQ1V1hIsvu70UWIu42O4agpC--

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

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

iQEcBAEBCAAGBQJZ+8O5AAoJEC88hzaAX42iaPsH/1PvbGR+MCTZusBffFfjCKuX
fdayPH9Z8y5gPSOtTGldDp9fx256RUcyVSpQLBJNTMlfSd4YkJA8CVAx563oyp6g
kfBgGcCuvxYhbtYv3YVoPTQ2ZcMFe3hY6xvj1bIAy1K6HfxTt9I7hSNP+SD2HDeq
uEMe0rgfdj/VNaaC1tB4lJiu25oz5l+XZf03vG09rKGsbiUM3EYe96jpqz7tX2z4
vqU7SP0YCopGb67KwgSMO0TDJS7dpDEcOj/jsKUPrZE8HtRy86d+ks9LkC/Fzqjy
667la0r/Y6tC0xhhaHI6tp1LRyIz9QruARQPFjtBg9/kjABcCOvaYdueU9wDFMg=
=4qzY
-----END PGP SIGNATURE-----

--PiJdQJc8BvpRK9G28wvr0JVAtmWNcJG7L--


From nobody Thu Nov  2 18:20:00 2017
Return-Path: <henry@callistohouse.club>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC2313FAFB for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 18:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 22kaKr7E14Dd for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 18:19:56 -0700 (PDT)
Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (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 3873513FAE7 for <ietf@ietf.org>; Thu,  2 Nov 2017 18:19:56 -0700 (PDT)
Date: Thu, 02 Nov 2017 21:19:50 -0400
Authentication-Results: mail1.protonmail.ch; dkim=none
To: IETF <ietf@ietf.org>
From: henry <henry@callistohouse.club>
Reply-To: henry <henry@callistohouse.club>
Subject: [internet-draft-draft] ParrotTalk: Anonymous P2P encryption
Message-ID: <Jb3SNoewcUFcFYxHEzi3ZOZT2xxZHasZl6NK4K1TxNZsGZBbkmE2qBVV4YMMrquJl8adsKVEzZq-ULBsnUcYyheSYVfC9yGxp8xWWex4OJI=@callistohouse.club>
Feedback-ID: vEY7k4yIhKH60ezyh_ewYb5cBh9lM6d5hXuAKmMcj-2yeFvumZUf2Q6AIaPs9viRuOL95Jg0-5_mTgpMVWHl3Q==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_c295a202368d8437b1d0a449b365a2ae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vZAh1QTXOUWhEoAKAvCWP37CqiU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 01:19:58 -0000

This is a multi-part message in MIME format.

--b1_c295a202368d8437b1d0a449b365a2ae
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

SSBoYXZlIGRldmVsb3BlZCB0aGUgUGFycm90VGFsayBQcm90b2NvbCwgYW5kIGFtIHN0YXJ0aW5n
IGFuIGludGVybmV0IGRyYWZ0IGRvY3VtZW50IFsxXSBmb3Igc3VibWlzc2lvbiB0byB0aGUgcHJv
Y2VzcyBhdCBJRVRGLgoKUGFycm90VGFsayBQcm90b2NvbCBpcyBkb2N1bWVudGVkIGluIHBhcnQg
aGVyZVsxXSwgd2hpbGUgSSBoYXZlIHR3byBpbXBsZW1lbnRhdGlvbnM6IDEgaW4gU3F1ZWFrL1Bo
YXJvIFszIGEvYl0gYW5kIHRoZSBvdGhlciBpbiBKYXZhIFs0IGEvYl0uIFRoZSBwYXJ0aWN1bGFy
cyBvZiBNQUMga2V5IGFuZCBpdlNlcXVlbmNlIGRlcml2YXRpb24sIGFzIHdlbGwgYXMgY29uc3Ry
YWluZWQgdHJhZmZpYyBzaWduaW5nLCBhcmUgdGhlIGltcGxlbWVudGF0aW9ucywgeWV0IG1pc3Np
bmcgZnJvbSB0aGUgc3BlY2lmaWNhdGlvbi4gVGhleSB3aWxsIGJlIGFkZGVkIHRvIHRoZSBpbnRl
cm5ldC1kcmFmdC4KCkhvdyBkbyBJIGdvIGFib3V0IHN1Ym1pdHRpbmcgYSBzcGVjaWZpY2F0aW9u
IGZvciBQYXJyb3RUYWxrIGZvciBJRVRGIHJldmlldyBhbmQgY29uc2lkZXJhdGlvbj8KClRoYW5r
IHlvdS4KCi0gUm9iZXJ0CgpbMV0gSUVURiBJLUQgZHJhZnQgLSBodHRwOi8vam1wLnNoL1ZSZWpT
MmcKClsyXSBQYXJyb3RUYWxrIEZyYW1lIERlc2lnbiAtIGh0dHA6Ly9qbXAuc2gvT3FsWXB5ZwoK
WzMgYV0gU3F1ZWFrL1BoYXJvIENyeXB0b2dyYXBoeSBsaWJyYXJ5IC0gaHR0cDovL3d3dy5zcXVl
YWtzb3VyY2UuY29tL0NyeXB0b2dyYXBoeS9DcnlwdG9ncmFwaHktSGVucnlIb3VzZS4xMTMubWN6
ClszIGJdIFNxdWVhay9QaGFybyBQYXJyb3RUYWxrIHYzLjYgLSBodHRwOi8vd3d3LnNxdWVha3Nv
dXJjZS5jb20vQ3J5cHRvZ3JhcGh5L1BhcnJvdFRhbGstSGVucnlIb3VzZS45Lm1jegoKWzQgYV0g
SmF2YSBBU04xIGZyYW1ld29yayAtIGh0dHBzOi8vZ2l0aHViLmNvbS9aaXJvWmltYmFycmEvQVNO
MQpbNCBiXSBKYXZhIFBhcnJvdFRhbGsgdjMuNiAtIGh0dHBzOi8vZ2l0aHViLmNvbS9aaXJvWmlt
YmFycmEvUGFycm90VGFsaw==


--b1_c295a202368d8437b1d0a449b365a2ae
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PGRpdj5JCiBoYXZlIGRldmVsb3BlZCB0aGUgUGFycm90VGFsayBQcm90b2NvbCwgYW5kIGFtIHN0
YXJ0aW5nIGFuIGludGVybmV0IGRyYWZ0IGRvY3VtZW50IFsxXSBmb3Igc3VibWlzc2lvbiB0byB0
aGUgcHJvY2VzcyBhdCBJRVRGLjxicj48YnI+UGFycm90VGFsayBQcm90b2NvbCBpcyBkb2N1bWVu
dGVkIGluIHBhcnQgaGVyZVsxXSwgCndoaWxlIEkgaGF2ZSB0d28gaW1wbGVtZW50YXRpb25zOiAx
IGluIFNxdWVhay9QaGFybyBbMyBhL2JdJm5ic3A7YW5kIHRoZSAKb3RoZXIgaW4gSmF2YSBbNCBh
L2JdLiBUaGUgcGFydGljdWxhcnMgb2YgTUFDIGtleSBhbmQgaXZTZXF1ZW5jZSBkZXJpdmF0aW9u
LAogYXMgd2VsbCBhcyBjb25zdHJhaW5lZCZuYnNwO3RyYWZmaWMKICAgIHNpZ25pbmcsIGFyZSB0
aGUgaW1wbGVtZW50YXRpb25zLCB5ZXQgbWlzc2luZyBmcm9tIHRoZSBzcGVjaWZpY2F0aW9uLiBU
aGV5IHdpbGwgYmUgYWRkZWQgdG8gdGhlIGludGVybmV0LWRyYWZ0Ljxicj48L2Rpdj48ZGl2IGRh
dGEtaW5qZWN0LW1lc3NhZ2UtbWVkaWE9IiIgZGF0YS1lbWJlZGRlZC1pbWctbG9hZGVyPSIiIGNs
YXNzPSJmcmFtZSBtZXNzYWdlLWZyYW1lIj48ZGl2IGNsYXNzPSJib2R5RGVjcnlwdGVkIGVtYWls
IG1lc3NhZ2UtYm9keS1jb250YWluZXIiPjxkaXY+PGJyPjwvZGl2PjxkaXY+SG93IGRvIEkgZ28g
YWJvdXQgc3VibWl0dGluZyBhIHNwZWNpZmljYXRpb24gZm9yIFBhcnJvdFRhbGsgZm9yIElFVEYg
cmV2aWV3IGFuZCBjb25zaWRlcmF0aW9uPzxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PlRo
YW5rIHlvdS48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdiBjbGFzcz0icHJvdG9ubWFpbF9z
aWduYXR1cmVfYmxvY2siPi0gUm9iZXJ0PGJyPjwvZGl2PjxkaXYgY2xhc3M9InByb3Rvbm1haWxf
c2lnbmF0dXJlX2Jsb2NrIj48YnI+PC9kaXY+PGRpdiBjbGFzcz0icHJvdG9ubWFpbF9zaWduYXR1
cmVfYmxvY2siPlsxXSBJRVRGIEktRCBkcmFmdCAtIDxhIGhyZWY9Imh0dHA6Ly9qbXAuc2gvVlJl
alMyZyI+aHR0cDovL2ptcC5zaC9WUmVqUzJnPC9hPjxicj48L2Rpdj48ZGl2IGNsYXNzPSJwcm90
b25tYWlsX3NpZ25hdHVyZV9ibG9jayI+PGRpdj48YnI+PC9kaXY+PGRpdj5bMl0gUGFycm90VGFs
ayBGcmFtZSBEZXNpZ24gLSZuYnNwOzxhIHN0eWxlPSJmb250LXNpemU6IDFlbTsiIGhyZWY9Imh0
dHA6Ly9qbXAuc2gvT3FsWXB5ZyIgcmVsPSJub3JlZmVycmVyIG5vZm9sbG93IG5vb3BlbmVyIj5o
dHRwOi8vam1wLnNoL09xbFlweWc8L2E+PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+WzMg
YV0gU3F1ZWFrL1BoYXJvIENyeXB0b2dyYXBoeSBsaWJyYXJ5IC0mbmJzcDs8YSByZWw9Im5vcmVm
ZXJyZXIgbm9mb2xsb3cgbm9vcGVuZXIiIGhyZWY9Imh0dHA6Ly93d3cuc3F1ZWFrc291cmNlLmNv
bS9DcnlwdG9ncmFwaHkvQ3J5cHRvZ3JhcGh5LUhlbnJ5SG91c2UuMTEzLm1jeiIgc3R5bGU9ImZv
bnQtc2l6ZTogMWVtOyI+aHR0cDovL3d3dy5zcXVlYWtzb3VyY2UuY29tL0NyeXB0b2dyYXBoeS9D
cnlwdG9ncmFwaHktSGVucnlIb3VzZS4xMTMubWN6PC9hPjxicj48L2Rpdj48L2Rpdj48ZGl2IGNs
YXNzPSJwcm90b25tYWlsX3NpZ25hdHVyZV9ibG9jayI+WzMgYl0gU3F1ZWFrL1BoYXJvIFBhcnJv
dFRhbGsgdjMuNiAtJm5ic3A7PGEgcmVsPSJub3JlZmVycmVyIG5vZm9sbG93IG5vb3BlbmVyIiBo
cmVmPSJodHRwOi8vd3d3LnNxdWVha3NvdXJjZS5jb20vQ3J5cHRvZ3JhcGh5L1BhcnJvdFRhbGst
SGVucnlIb3VzZS45Lm1jeiIgc3R5bGU9ImZvbnQtc2l6ZTogMWVtOyI+aHR0cDovL3d3dy5zcXVl
YWtzb3VyY2UuY29tL0NyeXB0b2dyYXBoeS9QYXJyb3RUYWxrLUhlbnJ5SG91c2UuOS5tY3o8L2E+
PGJyPjwvZGl2PjxkaXYgY2xhc3M9InByb3Rvbm1haWxfc2lnbmF0dXJlX2Jsb2NrIj48YnI+PC9k
aXY+PGRpdiBjbGFzcz0icHJvdG9ubWFpbF9zaWduYXR1cmVfYmxvY2siPls0IGFdIEphdmEgQVNO
MSBmcmFtZXdvcmsgLSZuYnNwOzxhIHJlbD0ibm9yZWZlcnJlciBub2ZvbGxvdyBub29wZW5lciIg
aHJlZj0iaHR0cHM6Ly9naXRodWIuY29tL1ppcm9aaW1iYXJyYS9BU04xIiBzdHlsZT0iZm9udC1z
aXplOiAxZW07Ij5odHRwczovL2dpdGh1Yi5jb20vWmlyb1ppbWJhcnJhL0FTTjE8L2E+PGJyPjwv
ZGl2PjxkaXYgY2xhc3M9InByb3Rvbm1haWxfc2lnbmF0dXJlX2Jsb2NrIj5bNCBiXSBKYXZhIFBh
cnJvdFRhbGsgdjMuNiAtJm5ic3A7PGEgcmVsPSJub3JlZmVycmVyIG5vZm9sbG93IG5vb3BlbmVy
IiBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vWmlyb1ppbWJhcnJhL1BhcnJvdFRhbGsiIHN0eWxl
PSJmb250LXNpemU6IDFlbTsiPmh0dHBzOi8vZ2l0aHViLmNvbS9aaXJvWmltYmFycmEvUGFycm90
VGFsazwvYT48YnI+PC9kaXY+PC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+



--b1_c295a202368d8437b1d0a449b365a2ae--


From nobody Thu Nov  2 21:53:13 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 309B913FB78 for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 21:53:11 -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 Fy2Kh2IrqCkT for <ietf@ietfa.amsl.com>; Thu,  2 Nov 2017 21:53:08 -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 E997813FB76 for <ietf@ietf.org>; Thu,  2 Nov 2017 21:53:08 -0700 (PDT)
Received: from pps.filterd (m0098410.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vA34pkxX115728 for <ietf@ietf.org>; Fri, 3 Nov 2017 00:53:08 -0400
Received: from e19.ny.us.ibm.com (e19.ny.us.ibm.com [129.33.205.209]) by mx0a-001b2d01.pphosted.com with ESMTP id 2e0hh90sj7-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 03 Nov 2017 00:53:08 -0400
Received: from localhost by e19.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, 3 Nov 2017 00:53:07 -0400
Received: from b01cxnp22035.gho.pok.ibm.com (9.57.198.25) by e19.ny.us.ibm.com (146.89.104.206) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 Nov 2017 00:53:04 -0400
Received: from b01ledav001.gho.pok.ibm.com (b01ledav001.gho.pok.ibm.com [9.57.199.106]) by b01cxnp22035.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id vA34r4U949414220 for <ietf@ietf.org>; Fri, 3 Nov 2017 04:53:04 GMT
Received: from b01ledav001.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C70A62803E for <ietf@ietf.org>; Fri,  3 Nov 2017 00:52:56 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav001.gho.pok.ibm.com (Postfix) with ESMTPS id B43332803D for <ietf@ietf.org>; Fri,  3 Nov 2017 00:52:56 -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 vA34r3LO017790 for <ietf@ietf.org>; Fri, 3 Nov 2017 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id vA34r2AP017728 for ietf@ietf.org; Fri, 3 Nov 2017 00:53:02 -0400
From: narten@us.ibm.com
Date: Fri, 03 Nov 2017 00:53:02 -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: 17110304-0056-0000-0000-000003E3AEE7
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00008001; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000239; SDB=6.00940386; UDB=6.00474191; IPR=6.00720642;  BA=6.00005668; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00017842; XFM=3.00000015; UTC=2017-11-03 04:53:05
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17110304-0057-0000-0000-0000081AC28A
Message-Id: <201711030453.vA34r2AP017728@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-11-03_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=13 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-1707230000 definitions=main-1711030057
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/98AkVkOD5Cw5jH7ljbFfYhrFmVw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 04:53:11 -0000

Total of 166 messages in the last 7 days.
 
script run at: Fri Nov  3 00:53:02 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  0.60% |    1 | 28.43% |   804730 | bill.wu@huawei.com
  8.43% |   14 |  7.98% |   226037 | akatlas@gmail.com
  7.23% |   12 |  3.63% |   102677 | sm+ietf@elandsys.com
  5.42% |    9 |  4.93% |   139576 | lear@cisco.com
  6.02% |   10 |  3.49% |    98725 | moore@network-heretics.com
  5.42% |    9 |  3.04% |    86121 | tte@cs.fau.de
  3.61% |    6 |  3.07% |    86927 | jordi.palet@consulintel.es
  3.61% |    6 |  1.94% |    54952 | housley@vigilsec.com
  3.61% |    6 |  1.89% |    53599 | mfidelman@meetinghouse.net
  3.01% |    5 |  1.89% |    53480 | phill@hallambaker.com
  3.01% |    5 |  1.75% |    49644 | brian.e.carpenter@gmail.com
  3.01% |    5 |  1.58% |    44643 | martin.thomson@gmail.com
  1.81% |    3 |  2.68% |    75920 | mersue@gmail.com
  1.81% |    3 |  2.58% |    73066 | gonzalo.camarillo@ericsson.com
  2.41% |    4 |  1.79% |    50585 | mellon@fugue.com
  2.41% |    4 |  1.66% |    46919 | stephen.farrell@cs.tcd.ie
  2.41% |    4 |  1.38% |    39035 | john-ietf@jck.com
  1.81% |    3 |  1.56% |    44192 | richard@shockey.us
  1.81% |    3 |  1.52% |    43157 | adrian@olddog.co.uk
  1.20% |    2 |  1.56% |    44186 | jhw@google.com
  1.20% |    2 |  1.27% |    35998 | corazza@incert.com.br
  1.20% |    2 |  1.12% |    31810 | henry@callistohouse.club
  1.20% |    2 |  0.98% |    27685 | framefritti@gmail.com
  1.20% |    2 |  0.84% |    23862 | petithug@acm.org
  1.20% |    2 |  0.83% |    23402 | tjc@ecs.soton.ac.uk
  1.20% |    2 |  0.82% |    23335 | volz@cisco.com
  1.20% |    2 |  0.79% |    22249 | melinda.shore@gmail.com
  1.20% |    2 |  0.78% |    22178 | logan@hackers.mu
  1.20% |    2 |  0.72% |    20337 | stewart.bryant@gmail.com
  1.20% |    2 |  0.70% |    19941 | jmh@joelhalpern.com
  1.20% |    2 |  0.66% |    18658 | zhencao.ietf@gmail.com
  1.20% |    2 |  0.60% |    17070 | ajs@anvilwalrusden.com
  1.20% |    2 |  0.57% |    16037 | mcr+ietf@sandelman.ca
  1.20% |    2 |  0.52% |    14819 | rsk@gsp.org
  0.60% |    1 |  1.03% |    29285 | sarikaya2012@gmail.com
  0.60% |    1 |  1.00% |    28217 | pat.thaler@broadcom.com
  0.60% |    1 |  0.74% |    20981 | ford@isoc.org
  0.60% |    1 |  0.61% |    17345 | spencerdawkins.ietf@gmail.com
  0.60% |    1 |  0.59% |    16647 | daedulus@btconnect.com
  0.60% |    1 |  0.56% |    15933 | eckelcu@cisco.com
  0.60% |    1 |  0.51% |    14324 | sajassi@cisco.com
  0.60% |    1 |  0.47% |    13389 | narten@us.ibm.com
  0.60% |    1 |  0.40% |    11297 | carlosm3011@gmail.com
  0.60% |    1 |  0.40% |    11203 | tom@herbertland.com
  0.60% |    1 |  0.38% |    10828 | cabo@tzi.org
  0.60% |    1 |  0.36% |    10147 | ned+ietf@mauve.mrochek.com
  0.60% |    1 |  0.33% |     9349 | paul@nohats.ca
  0.60% |    1 |  0.33% |     9343 | jeanmichel.combes@gmail.com
  0.60% |    1 |  0.33% |     9227 | hartmans-ietf@mit.edu
  0.60% |    1 |  0.30% |     8447 | tim.chown@jisc.ac.uk
  0.60% |    1 |  0.29% |     8169 | dm-list-tcpcrypt@scs.stanford.edu
  0.60% |    1 |  0.28% |     8054 | johnl@taugh.com
  0.60% |    1 |  0.28% |     7959 | sob@sobco.com
  0.60% |    1 |  0.27% |     7722 | ott@in.tum.de
  0.60% |    1 |  0.25% |     7146 | nick@foobar.org
  0.60% |    1 |  0.25% |     7028 | amy.yemin@huawei.com
  0.60% |    1 |  0.24% |     6750 | adam.w.montville@gmail.com
  0.60% |    1 |  0.24% |     6689 | iab-chair@iab.org
--------+------+--------+----------+------------------------
100.00% |  166 |100.00% |  2831031 | Total


From nobody Thu Nov  2 22:05:42 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4401D13FB1B; Thu,  2 Nov 2017 22:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=pVPueEAV; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=1AJXaF0T
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbl2eepp5DCU; Thu,  2 Nov 2017 22:05:39 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B83013FB1A; Thu,  2 Nov 2017 22:05:39 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.34.249]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA355GtV007183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Nov 2017 22:05:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1509685529; x=1509771929; bh=A2KuY743w30IADtcq1MN4+lbBzew5E16TV0Na4GxuFM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pVPueEAVaVukyx6FSDxQJbKJkS9wBo1XTeevRkfoUILkxRL7Wbo1N5j+bo3g55a0J MDu0XLWacA119+LuBVDV5TReqAzn15LMOJt0Ig3j1mBus2ITZ0CFeJLQ8kJANMRW4x IDPCerQ9+HCvqiImnJDg9cm62ykZUZexqaFooToo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1509685529; x=1509771929; i=@elandsys.com; bh=A2KuY743w30IADtcq1MN4+lbBzew5E16TV0Na4GxuFM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1AJXaF0TYntIVSfRPRQ63w5PU0V6Zr2zNUQxu4XqU6OMeoKooe22ZAb4Y9cdoPctM gHynOCkzcUrUPNIfkA5eGtfo6PzcKvhv9xOTm5FGOzFzOlqbP9urkzyhLusQhMv9b9 lWFBnPQfKoJln382UkVomGpimDyBT+dcfbf0A5UM=
Message-Id: <6.2.5.6.2.20171102214547.110eda80@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 Nov 2017 22:04:52 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
Cc: ben@nostrum.com, ietf@ietf.org
In-Reply-To: <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com> <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qc-gZsr4BqDibL93vUnPj2p2XpI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 05:05:40 -0000

Hi Stephen,
At 06:17 PM 02-11-2017, Stephen Farrell wrote:
>I don't claim to fully understand the usage of this ID,
>but I'm quite sure that I have no clue what this text
>is supposed to mean (as a piece of specification):
>
>   "In particular, the "sip.instance" media feature tag
>    containing the 3GPP2 MEID URN MUST NOT be included in requests or
>    responses intended to convey any level of anonymity, as this could
>    violate the users privacy."
>
>I guess this is either an existing problem with whatever
>a "'sip.instance' media feature tag" really is or else this
>draft creates a new problem, but the quoted text seems to
>me to be non-deterministic impossible-to-program-for words
>seemingly about (but not actually helping with) privacy.
>
>Am I confused?

The text which you quoted above is similar to text which is found in 
RFC 7255.  Several years ago, there was a controversy about that document.

Regards,
S. Moonesamy 


From nobody Thu Nov  2 22:57:53 2017
Return-Path: <ben@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 CB5D613FBFE; Thu,  2 Nov 2017 22:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9Pu7vA_1B40u; Thu,  2 Nov 2017 22:57:48 -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 3332613FBF1; Thu,  2 Nov 2017 22:57:48 -0700 (PDT)
Received: from [10.0.1.82] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id vA35uQ3U049716 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 3 Nov 2017 00:56:27 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.82]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <039BDED8-AD0F-4AA2-8408-343D4D828751@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7D663C52-8B6F-479D-B6C0-3EB98F98161B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
Date: Fri, 3 Nov 2017 00:56:25 -0500
In-Reply-To: <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
Cc: draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org, ietf@ietf.org, aallen@blackberry.com
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com> <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/itF9SZDmiKzyKFA-4nZe6YYgR1A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 05:57:51 -0000

--Apple-Mail=_7D663C52-8B6F-479D-B6C0-3EB98F98161B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Nov 2, 2017, at 8:17 PM, Stephen Farrell =
<stephen.farrell@cs.tcd.ie> wrote:
>=20
>=20
> Hiya,
>=20
> I don't claim to fully understand the usage of this ID,
> but I'm quite sure that I have no clue what this text
> is supposed to mean (as a piece of specification):
>=20
>  "In particular, the "sip.instance" media feature tag
>   containing the 3GPP2 MEID URN MUST NOT be included in requests or
>   responses intended to convey any level of anonymity, as this could
>   violate the users privacy."
>=20
> I guess this is either an existing problem with whatever
> a "'sip.instance' media feature tag" really is or else this
> draft creates a new problem, but the quoted text seems to
> me to be non-deterministic impossible-to-program-for words
> seemingly about (but not actually helping with) privacy.
>=20
> Am I confused?

Possibly, but only because it=E2=80=99s confusing :-)

As S. Moonesamy pointed out separately, this draft borrows quite a bit =
of language from RFC 7255, which was pretty much the same things for =
IMEIs.

RFC 3261 (SIP) and a few related RFCs (especially 3323) talk about =
placing anonymous calls. The point here is that, when a user is trying =
to place an anonymous call, don=E2=80=99t screw up and stick identifying =
information somewhere else in the request.  I suspect (but do not know) =
that the language =E2=80=9Cany level of anonymity=E2=80=9D originally =
came from the distinction between  =E2=80=9Cuser-provided privacy=E2=80=9D=
 vs =E2=80=9Cnetwork-provided privacy=E2=80=9D discussed in RFC 3323.

The =E2=80=9Csip.instance=E2=80=9D media feature tag is defined in RFC =
5626. It carries a URL to persistently identify a specific SIP user =
agent. That RFC contains guidance to not use the sip.instance tag for =
anonymous requests or responses, i.e. when you don=E2=80=99t want to the =
UA to reveal its identity.

Would citations help?

(Authors, feel free to jump in).

Thanks!

Ben.


>=20
> Cheers,
> S.
>=20
> On 02/11/17 22:43, The IESG wrote:
>>=20
>> The IESG has received a request from an individual submitter to =
consider the
>> following document: - 'Using the Mobile Equipment Identity (MEID) =
Uniform
>> Resource Name (URN)
>>   as an Instance ID'
>>  <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> as =
Informational RFC
>>=20
>> 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-12-08. 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.
>>=20
>> Abstract
>>=20
>>=20
>>   This specification specifies how the Uniform Resource Name (URN)
>>   namespace reserved for the Third Generation Partnership Project 2
>>   (3GPP2) identities and its Namespace Specific String (NSS) for the
>>   Mobile Equipment Identity (MEID) can be used as an instance-id.  =
Its
>>   purpose is to fulfill the requirements for defining how a specific
>>   URN needs to be constructed and used in the "+sip.instance" Contact
>>   header field parameter for outbound behavior.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> =
https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as-instan=
ceid/
>>=20
>> IESG discussion can be tracked via
>> =
https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as-instan=
ceid/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>>=20
>>=20
>>=20
>=20


--Apple-Mail=_7D663C52-8B6F-479D-B6C0-3EB98F98161B
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAln8BQkACgkQgFZKbJXz
1A38YhAAoAgQjBlo2NUgktlmnV11zYG/oFRpfosYW1Cqm3zIpjS0Wy6Z9eeI6UPj
gnIbHjXPnI1PpvVQUW/Ssd5kPP1LrsK2KpUCERblXHHSpVGJ+ejhH+ZLWzpL42Mr
xhGyAoPu5VCWu+bn+l2pawykIaCNod5oKG3xo9BViKgSkRdFWAMcxNGjquTuAufo
JlynEdISp0yDkhxlU/Wop53iin6Ms2LzCdOKz4XNlm4Ibg1q11Qh6xoQzw8m/HCw
puv6Mvo9QmGfzaTv+o8Z3nXL+ODKXiInVkoNPd/oana1CSXC6lAY+ZUo87kZNBuK
qoZrv3bCf5IsqfGRr7dE3pgUIjmpb/ThNpOW7c3lYLn/QjtU8qjm/SRmCuhJRs+D
b+OIDAmJejsvJBi7mKd3KP2iNy2R448vmugUK2SqYhEBDG4LOEo2lZybuFIYVjlu
Jh9+lZP2VQGfz+d8akgdUjBZxnZpN5VCFtL/9kOTa/KM9an3Ecx2YB+kliGiJKWO
dRLmyp6ErzWqB0aS/cLzSZ6qGjpracIGoakaJic4Ycb8/ojbnHS7YpA/lVcBDgpM
8nVDdD6jFgQ2EETJGjuQnJ9CH8PxzhrOjjNto0WfcyDzMqgge5nkDZhRSbpn9Gbx
wEOs9gFtkJ442I7i/1lxC4OrTpBeEzlfsl6VSqpjcgPwZ7qbe9w=
=Fg72
-----END PGP SIGNATURE-----

--Apple-Mail=_7D663C52-8B6F-479D-B6C0-3EB98F98161B--


From nobody Fri Nov  3 05:07:18 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 022AD13FB1F for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 05:07:16 -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, 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 aImbUx7N72FY for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 05:07:09 -0700 (PDT)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::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 61D2213F963 for <ietf@ietf.org>; Fri,  3 Nov 2017 05:07:09 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id f66so1909454oib.2 for <ietf@ietf.org>; Fri, 03 Nov 2017 05:07:09 -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=QLBdzmsZzka8wlDqW7u7J6R2iXxF7LSoDdpWApJju2A=; b=LaPYmYvFlOgwCr57JRXdf4p5zrJeFruwM29z9nULZHjmDuQG+z14IEldni7pNJeaoX 0LJfT2pBQYXAve+r478SPS/9e+0spfe6je5I/epCfsk7FExh5XAu6jMkMDHxUM9DK6/r oDwk46OQo55QIje/c2QWF6LdiS/hb+ndF1Fldi0GUxQUha80OCQk9LONalXr84cNFy8l O4p9JhypiGk109GfjE+r60esxM8BLTaHPyCwcJid9RCZ+PAE0Bgrh1H+lJYBaPpgGQrk X7mydXpUuR9TfSLHTlBZuLAxnyjZkXcCbqHrk0vvCK4JPnwWhus9dLafJBx4lVrlx8qE pzww==
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=QLBdzmsZzka8wlDqW7u7J6R2iXxF7LSoDdpWApJju2A=; b=cY2l8Jh4HArNB6CO6yWnSoz2vdtwSo5b/OjvQzuHpDUA8mXpyGz5EUkX6IZLmDVsUx ARTfVp0M1Sh+ATEeWVmZu9YHdq8rh79xUYDL4kYKIybqH63Lm3b13zqhWAre9fAk+Ubl L2xzyWRsH/xSeX8p1eyA6VZJZXsVneKl3o4R2DURsBcu4DWR8TqXa1VRmKgsFofabKNX KcvdsNp7+EI9y99Srhgkr3oMf7OL2tXapQ0HvKtq0EqBVpxli+wEgW1pRQuKRRG5ijj/ rVuPM8oZYUk0xZZsycXRqzjkdMGXJ2MrF1T1U5Xm7EPd53MCfm65iGIHFKgL3COEJjcw 6YcA==
X-Gm-Message-State: AMCzsaVMePTLRR276wY6CarXN3vem+mMtSX0a4ASba8xM5xeTrjn3KRP lVQfq0yLpBpgxtwBaNOhdBt4P1NHcKFwdQ68CU4=
X-Google-Smtp-Source: ABhQp+TdOCGNqlOJf0sEGGlvrazi6bUm2hgdIA2WqY1qUjNn7wBYad1Xg4WLGzhXUiuNohOvox3sNNE8v1Ni5emTJZU=
X-Received: by 10.202.80.213 with SMTP id e204mr3919138oib.0.1509710828401; Fri, 03 Nov 2017 05:07:08 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.56.164 with HTTP; Fri, 3 Nov 2017 05:07:07 -0700 (PDT)
In-Reply-To: <a72fab79-1c5b-07a2-b21d-efe4491d9339@meetinghouse.net>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <6.2.5.6.2.20171101132245.10d04f48@elandnews.com> <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com> <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com> <a72fab79-1c5b-07a2-b21d-efe4491d9339@meetinghouse.net>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 3 Nov 2017 08:07:07 -0400
X-Google-Sender-Auth: 13feRugLFStwHJxkCLryWo_cnNM
Message-ID: <CAMm+Lwi-_sECr0Ls6fUk6VJTGovS4_zk-BO8_2gHWHS8P8+xbQ@mail.gmail.com>
Subject: Re: letting IETF build on top of Open Source technology
To: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/68whW5ch-bvWDL1QNGsti-2pwuQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 12:07:16 -0000

On Thu, Nov 2, 2017 at 1:01 PM, Miles Fidelman
<mfidelman@meetinghouse.net> wrote:
> On 11/1/17 10:35 PM, Phillip Hallam-Baker wrote:
>
>> My specifications are my code.
>>
>> If you look at any of the protocol specifications for the Mesh, you
>> will find a reference section in the back that is generated directly
>> from the schema and examples taken from running code generated from
>> the same schema. And the running code used to generate the examples is
>> the same as the reference code.
>>
> That's a little bit disingenuous, isn't it - particularly since you've
> written quite a bit of documentation beyond your code.

I did not say my code is my specification. Which is what a lot of
people have done in the past.

I develop the documentation and the code at the same time. Of course
there are parts of the documentation that are not code, the user
guide, requirements, etc. But every specification has normative and
non-normative sections.


> Beyond that, the point of a specification is to DRIVE implementation &
> testing of multiple, interoperable implementations.  A reference
> implementation is one thing, but as soon as one specific piece of code
> (warts & all) becomes the "spec" - it's not really a specification anymore.

Reference code is not necessarily the same as production. Production
code should be conservative in what it sends and liberal in what it
accepts. Reference code should be the other way round. It should
complain when the sender fails to abide by the strict specification.

We have always considered rough consensus and running code to be
important. Building code from specifications is the next logical step.


From nobody Fri Nov  3 07:24:32 2017
Return-Path: <ietf-secretariat@ietf.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 C9C8B13FC10; Fri,  3 Nov 2017 07:24:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: recentattendees@ietf.org, ietf@ietf.org, 100all@ietf.org
Subject: IETF 100 Early Bird Deadline Today!
X-Test-IDTracker: no
X-IETF-IDTracker: 6.64.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF Agenda <agenda@ietf.org>
Message-ID: <150971907077.29038.1461911075651754442.idtracker@ietfa.amsl.com>
Date: Fri, 03 Nov 2017 07:24:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9139B7a3g-zTxkyYmZq7Us4DIQ4>
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, 03 Nov 2017 14:24:31 -0000

IETF 100 
Singapore
November 11-17, 2017
Host: Cisco

IETF 100 Information: https://ietf.org/meeting/100/index.html

1. Early Bird Deadline
	The early bird deadline for registration is Friday, November 3rd.
	Be sure to register and pay before the deadline passes!

	Register online at: https://ietf.org/meeting/register.html

2. Thursday Speaker Series Topic — 3 years on: Open Standards, Open Source, Open Loop

	At IETF 91, many outrageous claims were emphatically made
	about the relationship between Open Standards and Open Source.
	Three years later, let’s take a look at how much progress has
	been made, if any; and discuss successes and failures.
	Communities of developers and engineers have fully formed Open
	Source efforts and are building large, effective communities
	without any documented standardization as a part of their
	strategy. How should SDOs interact with developers, communities
	and deployers of Open Source? There are claims and perhaps proof
	that Open Source now fully defines the industries "de facto
	Standards." Does the process of standardization and the contents
	and lifecycle of a standard need to fundamentally change?

	Logistics:
	• Room: Canning
	• Date: Thursday, November 16, 2017
	• Time: 12:30 – 13:15
	• Lunch will NOT be provided. 

	Speaker Biography:

	Dave Ward, Senior Vice President, Chief Architect & CTO - Engineering

	Dave is Chief Architect at Cisco Systems, responsible for
	architectural governance, defining strategy, development of new
	technology and leading use-inspired research. Working via tight
	partnerships with customers, partners, developers and academia he
	is also leading co-development and co-innovation initiatives. He
	has been the Routing Area Director at the IETF and chair of four
	Working Groups: IS-IS, HIP, BFD and Softwires and worked with the
	ITU-T, ONF and several Open Source consortia. David was also a
	Juniper Fellow and Chief Architect working on the operating
	system and next-generation routing systems. Dave has a small
	vineyard in the Santa Cruz Mountains and an heirloom tomato farm
	along the St. Croix River in Somerset, Wisconsin.

3. Code Sprint	

	The IETF 100 Code Sprint in Singapore will, as
	always, let you work on fixing those things about the datatracker
	which you most urgently desire to do something about.

	When: Saturday, November 11 from 09:30 to 18:00
	Where: Raffles City Convention Center, Room Ord
	Signup: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF100SprintSignUp
	More information: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF100Sprint

4. Hackathon
	
	The IETF is holding a Hackathon at IETF 100 to encourage
	developers to discuss, collaborate and develop utilities, ideas,
	sample code and solutions that show practical implementations of
	IETF standards.

	When: Saturday November 11 and Sunday November 12
	Where: Raffles City Convention Center, Room Moor/Morrison
	Signup: https://www.ietf.org/registration/ietf100/hackathonregistration.py
	More information: http://ietf.org/hackathon/100-hackathon.html 
	Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon

	The Hackathon is free to attend and open to all. Extend
	the invitation to colleagues outside the IETF!

	Descriptions and information regarding the technologies
	for the hackathon are located on the IETF 100 Meeting Wiki:
	https://www.ietf.org/registration/MeetingWiki/wiki/100hackathon

	Don’t see anything that interests you? Feel free to add
	your preferred technology to the list, sign up as its
	Champion and show up to work on it. Note: you must login to
	the wiki to add content. If you do add a new technology, we
	strongly suggest that you send an email to hackathon@ietf.org
	to let others know. You may generate interest in your
	technology, and find other people who want to contribute to
	it.

	To request a wiki account, please click on the “login”
	button on the bottom right corner of the page, and choose
	“register.” If you need a new password please click on the
	“login” button on the bottom right corner of the page and
	choose “Send new password.”

5. Side Meetings

	The IESG is continuing the side meeting experiment in
	Singapore with some slight modifications based on the comments
	received from the experiment in Prague. For IETF 100, two rooms
	are available for first-come first-served (FCFS) signup online.
	The larger of the two (Hullet) will hold approximately 40 people
	and will be configured with a U-shaped table. The smaller room
	(Butterworth) will be configured as a boardroom and will hold
	approximately 12 people; please note that this smaller room was
	previously the onsite signup room, so there will be no onsite
	signup room at IETF 100. Both Hullet and Butterworth rooms will
	have projectors.

	You can sign up for either room by visiting the IETF meeting
	wiki and navigating to Side Meetings via the Table of Contents.
	See:
	https://www.ietf.org/registration/MeetingWiki/wiki/ietf100# side_meetings 	
	You will need to login to the wiki in order to reserve a
	room. If you’ve registered for an IETF meeting in the recent
	past, an account has been automatically created for you. If you
	have trouble logging into the wiki, you can choose to reset your
	password.

	The coveted morning, lunch and evening slots are not
	currently available for reservation, but will be made available
	at the start of IETF 100.

	Please include your name, email and a short description of
	the meeting when reserving the room, and please limit yourself to
	no more than a total of three hours during the IETF meeting week.
	In addition, please remember that meetings held in these rooms
	are subject to the IETF Meeting Policy:
	https://www.ietf.org/meeting/meeting-rooms-policy.html.

Important Dates: https://ietf.org/meeting/important-dates.html#ietf100


From nobody Fri Nov  3 10:53:13 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 4B9C513FF0F; Fri,  3 Nov 2017 10:53:05 -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] 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 Zdsrjj_Hox1d; Fri,  3 Nov 2017 10:53:03 -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 3344C13FF0E; Fri,  3 Nov 2017 10:53:03 -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 0E70058C4B2; Fri,  3 Nov 2017 18:52:59 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id E996CB0D084; Fri,  3 Nov 2017 18:52:58 +0100 (CET)
Date: Fri, 3 Nov 2017 18:52:58 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Tom Herbert <tom@herbertland.com>
Cc: Christian Huitema <huitema@huitema.net>, Padma Pillay-Esnault <padma.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "ideas@ietf.org" <ideas@ietf.org>, Dino Farinacci <farinacci@gmail.com>, "lisp@ietf.org list" <lisp@ietf.org>
Subject: Re: [Ideas] [lisp] WG Review: IDentity Enabled Networks (ideas)
Message-ID: <20171103175258.GA6808@faui40p.informatik.uni-erlangen.de>
References: <644DA50AFA8C314EA9BDDAC83BD38A2E0EAA7204@sjceml521-mbx.china.huawei.com> <dd2c3bd5-dd37-109b-2e81-0327db4daa09@cs.tcd.ie> <0BA14206-DC82-49EF-A625-B2425FA396F6@gmail.com> <1f254140-1340-6c7d-9c73-e7137562c685@gmail.com> <fa644cc2-161f-8884-3445-2b50d2c2ad23@htt-consult.com> <cf2ca920-f2d2-b65e-05eb-ebe3c30b76d1@huitema.net> <CAG-CQxrdS9L+2+bN=1NcPGuztn4U4OwSWUiNaVcS9Bsm2mtpfA@mail.gmail.com> <b18459d1-7ce1-b83d-787d-9066267d584b@huitema.net> <20171101172146.GA12437@faui40p.informatik.uni-erlangen.de> <CALx6S34Bkv4ipyA5si4KkW7VaYU6A=3=cPpRo_ss00H+vDms-w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALx6S34Bkv4ipyA5si4KkW7VaYU6A=3=cPpRo_ss00H+vDms-w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/V5HfR8ZKQTQavSzlNe67cbtzV6k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 17:53:05 -0000

Thanks, Tom, inline

On Thu, Nov 02, 2017 at 08:30:11AM -0700, Tom Herbert wrote:
> Toerless,
> 
> That maybe true, but personal devices, such as smart phones and cars
> that are associated with individuals, are hardly going away anytime
> soon. How addresses are assigned to these devices has a material
> impact on individual privacy. Even right now there are two long
> threads on v6ops right now that are delving precisely into privacy of
> IPv6 addresses that may be relevant. This includes discussion about
> CGNAT and efforts by some governments to illegalize it because the
> privacy it gives is too strong for law enforcement.

Sure. All i was saying is that we should not dismiss solutions if they
do not help to improve privacy. It reminds me of the congestion control
principles and the fact that a lot of money is made with video in
controlled networks without congestion control. As in: "Sorry, we couldn't
build a great solution for sensor devices in manufacturing plants because
those solutions wouldn't pass the privacy bar".

I am not even aware if we have good characterizations of solutions
vs. privacy like IMHO we have for congestion control, but of course its
a more complex topic. (IMHO: lot more cases IMHO to distinguish).

That being said, i would of course love to see that we leverage IDEAs to
also create options that (could) enhance privacy, i just don't think that
we will make a lot of progress if we can not do this work in a WG but
if all the complex issues have to be resolved on pre-wg mailing lists before
even charters are accepted. This is part of whats wrong with the IETF
if i may say so.

For example, Christian contested that long lived identifiers help to
improve privacy (for device = individual case) and those arguments about
privacy had the IESG turn their opinions.

IMHO: The long-lived identifiers are meant to be functionally limited. You do
increase the bar of identifying an individual when you do this because the
web applications need to do more work to correlate application layer
information across multiple functional identifiers.

So, how & where do we even create a common understanding about the qualitative and
quantitative privacy benefits of technology options if not in a WG. Functional
identifiers just being one example. 

Even more fundamentally: If each individual application layer function requires
authentication via e.g.: government, google or facebook ID, and all those
web services are free to correlate their information in the backend, any
network layer privacy work is just like growing organic tobacco.

Which is why i really would like to know what the state of requirements/BCP etc.
is re. privacy at app layer in the IETF, because without that knowledge, i can
only define the privacy benefits of a network layer enhancement under the
ASSUMPTION of particular application behavior.

My impression of IETF policy is "you have to trust the web services
provider (not to share/correlate/abuse user/client information)" and in the
same breath "you can not trust the network service provider (to behave in the
same way)". Would love to get pointed to documents proving this impression to
be wrong. Especially the option that there can be network providers that
users may want to trust more than arbitrary web services providers should IMHO
be acknowledged. And thats definitely an option i think is worthwhile to build
solutions against. 

Cheers
    Toerless

> Tom


From nobody Fri Nov  3 13:35:30 2017
Return-Path: <r_atarius@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAEE213FFB3 for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 13:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.311
X-Spam-Level: 
X-Spam-Status: No, score=0.311 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_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 Wwb04ZHGR7Kh for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 13:35:26 -0700 (PDT)
Received: from sonic310-27.consmr.mail.gq1.yahoo.com (sonic310-27.consmr.mail.gq1.yahoo.com [98.137.69.153]) (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 0203713FFBE for <ietf@ietf.org>; Fri,  3 Nov 2017 13:35:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1509741324; bh=dMln++BCR+R8LmBHfRokX4L5V8BSaOQMF5xEdX8G/QM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=cj+UGfIkyWI4SbA3Tav5vCBygF0vnd5pqKfPL77SPrFU9jcBxyipj5vL0zY5gzZumyAO2YhPj6RoWT1DIHBRaKtxgMkrm2CwL2bUbdYT6v6v7HV2XZMDeAxf5ZvnQm31xnZpjd6Gz1HvriVFp0YMwRckekCLS87wL7JE2ipweOZZzA17cOK4gpOZKGNbqZmu6/9FLX9Py0RU2fDQ+vBZzfUJ25p75lQ3DhdgdFrvnQh8De4Oec0J/pDw9qAdNnuS1jiOLM+GBT6o76EK2RaOwdJjLpTHa5VSr2tfG26d7oZagWDdWK121gsv7lm63YFStCkdTa8LoncguEBo5wChkg==
X-YMail-OSG: _FkTHYwVM1lkxJjScFNISLe2dHj2oG_Z.8ZGwXQImnuai9IRne5A1xdmlyjyzu2 jl6CUCEJ1C1oiNN.V5U8I.YKO38c13csmpNQN6O4tHiaRamliuOO3fHsHEXmFbR4W9S_Th8l1TA5 xZ8FuzXSOMOC8CTbQfbpRg1mTRgWPQv0VcHnUhyiQiHWVIf7U868Yquq3FGjgLGx8lqsvhm8pBo9 XUxhmBIBo0GFO8960y136I9LJi4Qok6wjvdCy9eqUv.sQNs1YtK8z0.HEClQfbV5rMMM6864XeX9 DzA3a4QgsFSC1XzeH.BSJEDgUaXybwskVbmHW5FNQPvpo0CagMpSkAjMVVdtidql4CmgX.ck26HA oLkvyD0jHGAHLJKywdpQ3rYiHqIlWAlc7e4j0XEcT9_QHuqc.lPIXWcYq8EcottiZdEItwKcn0gk HNCwS2mW4lRIaloPeVh16BAcO8oq3WwXJipgQ3srdh7gUWoePnllzV11lATL3_vjAr4hQJf.dMUa tgSyObWclQ0k5bfsBzYPCstvLpwWobqaTw69YCaOiwCyDl5Mf8GyF
Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.gq1.yahoo.com with HTTP; Fri, 3 Nov 2017 20:35:24 +0000
Date: Fri, 3 Nov 2017 20:35:21 +0000 (UTC)
From: R Atarius <r_atarius@yahoo.com>
Reply-To: R Atarius <r_atarius@yahoo.com>
To: Ben Campbell <ben@nostrum.com>,  Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: "draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org" <draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>,  "aallen@blackberry.com" <aallen@blackberry.com>
Message-ID: <14878392.1994847.1509741321099@mail.yahoo.com>
In-Reply-To: <039BDED8-AD0F-4AA2-8408-343D4D828751@nostrum.com>
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com> <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie> <039BDED8-AD0F-4AA2-8408-343D4D828751@nostrum.com>
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_1994846_688546350.1509741321096"
X-Mailer: WebService/1.1.10849 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lhd4d01ydcuBrwvwNJqA9YV9bxA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Nov 2017 20:35:28 -0000

------=_Part_1994846_688546350.1509741321096
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi
Just agreeing with Ben. RFC 5626 highlights that the UA could omit the inst=
ance ID for private or anonymous calls. So this is the problem with instanc=
e ID and not UUID, MEID, IMEI which have been employed to create the instan=
ce ID.
ThanksRoozbeh

      From: Ben Campbell <ben@nostrum.com>
 To: Stephen Farrell <stephen.farrell@cs.tcd.ie>=20
Cc: draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org; ietf@ietf.org; =
aallen@blackberry.com
 Sent: Thursday, November 2, 2017 10:57 PM
 Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.=
txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN=
) as an Instance ID) to Informational RFC
  =20


> On Nov 2, 2017, at 8:17 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> w=
rote:
>=20
>=20
> Hiya,
>=20
> I don't claim to fully understand the usage of this ID,
> but I'm quite sure that I have no clue what this text
> is supposed to mean (as a piece of specification):
>=20
>=C2=A0 "In particular, the "sip.instance" media feature tag
>=C2=A0 containing the 3GPP2 MEID URN MUST NOT be included in requests or
>=C2=A0 responses intended to convey any level of anonymity, as this could
>=C2=A0 violate the users privacy."
>=20
> I guess this is either an existing problem with whatever
> a "'sip.instance' media feature tag" really is or else this
> draft creates a new problem, but the quoted text seems to
> me to be non-deterministic impossible-to-program-for words
> seemingly about (but not actually helping with) privacy.
>=20
> Am I confused?

Possibly, but only because it=E2=80=99s confusing :-)

As S. Moonesamy pointed out separately, this draft borrows quite a bit of l=
anguage from RFC 7255, which was pretty much the same things for IMEIs.

RFC 3261 (SIP) and a few related RFCs (especially 3323) talk about placing =
anonymous calls. The point here is that, when a user is trying to place an =
anonymous call, don=E2=80=99t screw up and stick identifying information so=
mewhere else in the request.=C2=A0 I suspect (but do not know) that the lan=
guage =E2=80=9Cany level of anonymity=E2=80=9D originally came from the dis=
tinction between=C2=A0 =E2=80=9Cuser-provided privacy=E2=80=9D vs =E2=80=9C=
network-provided privacy=E2=80=9D discussed in RFC 3323.

The =E2=80=9Csip.instance=E2=80=9D media feature tag is defined in RFC 5626=
. It carries a URL to persistently identify a specific SIP user agent. That=
 RFC contains guidance to not use the sip.instance tag for anonymous reques=
ts or responses, i.e. when you don=E2=80=99t want to the UA to reveal its i=
dentity.

Would citations help?

(Authors, feel free to jump in).

Thanks!

Ben.


>=20
> Cheers,
> S.
>=20
> On 02/11/17 22:43, The IESG wrote:
>>=20
>> The IESG has received a request from an individual submitter to consider=
 the
>> following document: - 'Using the Mobile Equipment Identity (MEID) Unifor=
m
>> Resource Name (URN)
>>=C2=A0 as an Instance ID'
>>=C2=A0 <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> as Informat=
ional RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits fi=
nal
>> comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2017-12-08. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the beginni=
ng of
>> the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>=C2=A0 This specification specifies how the Uniform Resource Name (URN)
>>=C2=A0 namespace reserved for the Third Generation Partnership Project 2
>>=C2=A0 (3GPP2) identities and its Namespace Specific String (NSS) for the
>>=C2=A0 Mobile Equipment Identity (MEID) can be used as an instance-id.=C2=
=A0 Its
>>=C2=A0 purpose is to fulfill the requirements for defining how a specific
>>=C2=A0 URN needs to be constructed and used in the "+sip.instance" Contac=
t
>>=C2=A0 header field parameter for outbound behavior.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as-inst=
anceid/
>>=20
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as-inst=
anceid/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>>=20
>>=20
>>=20
>=20


  =20
------=_Part_1994846_688546350.1509741321096
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:13px"><div id=3D"yui_3_16_0_ym19_1_1509664152491_32128"><span>Hi</spa=
n></div><div id=3D"yui_3_16_0_ym19_1_1509664152491_32128"><span><br></span>=
</div><div id=3D"yui_3_16_0_ym19_1_1509664152491_32128"><span id=3D"yui_3_1=
6_0_ym19_1_1509664152491_32163">Just agreeing with Ben. RFC 5626 highlights=
 that the UA could omit the instance ID for private or anonymous calls. So =
this is the problem with instance ID and not UUID, MEID, IMEI which have be=
en employed to create the instance ID.</span></div><div id=3D"yui_3_16_0_ym=
19_1_1509664152491_32128"><span><br></span></div><div id=3D"yui_3_16_0_ym19=
_1_1509664152491_32128">Thanks</div><div id=3D"yui_3_16_0_ym19_1_1509664152=
491_32128">Roozbeh</div><div class=3D"qtdSeparateBR" id=3D"yui_3_16_0_ym19_=
1_1509664152491_32129"><br><br></div><div class=3D"yahoo_quoted" id=3D"yui_=
3_16_0_ym19_1_1509664152491_32236" style=3D"display: block;">  <div style=
=3D"font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-seri=
f; font-size: 13px;" id=3D"yui_3_16_0_ym19_1_1509664152491_32235"> <div sty=
le=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida =
Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1509664152491=
_32234"> <div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1509664152491_32233"> <fo=
nt size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_ym19_1_1509664152491_32232"> =
<hr size=3D"1"> <b id=3D"yui_3_16_0_ym19_1_1509664152491_32240"><span style=
=3D"font-weight:bold;" id=3D"yui_3_16_0_ym19_1_1509664152491_32239">From:</=
span></b> Ben Campbell &lt;ben@nostrum.com&gt;<br> <b><span style=3D"font-w=
eight: bold;">To:</span></b> Stephen Farrell &lt;stephen.farrell@cs.tcd.ie&=
gt; <br><b id=3D"yui_3_16_0_ym19_1_1509664152491_32238"><span style=3D"font=
-weight: bold;" id=3D"yui_3_16_0_ym19_1_1509664152491_32237">Cc:</span></b>=
 draft-atarius-dispatch-meid-urn-as-instanceid@ietf.org; ietf@ietf.org; aal=
len@blackberry.com<br> <b id=3D"yui_3_16_0_ym19_1_1509664152491_32231"><spa=
n style=3D"font-weight: bold;" id=3D"yui_3_16_0_ym19_1_1509664152491_32230"=
>Sent:</span></b> Thursday, November 2, 2017 10:57 PM<br> <b><span style=3D=
"font-weight: bold;">Subject:</span></b> Re: Last Call: &lt;draft-atarius-d=
ispatch-meid-urn-as-instanceid-05.txt&gt; (Using the Mobile Equipment Ident=
ity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational =
RFC<br> </font> </div> <div class=3D"y_msg_container"><br><div dir=3D"ltr">=
<br clear=3D"none"><br clear=3D"none">&gt; On Nov 2, 2017, at 8:17 PM, Step=
hen Farrell &lt;<a shape=3D"rect" ymailto=3D"mailto:stephen.farrell@cs.tcd.=
ie" href=3D"mailto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>=
&gt; wrote:<br clear=3D"none">&gt; <br clear=3D"none">&gt; <br clear=3D"non=
e">&gt; Hiya,<br clear=3D"none">&gt; <br clear=3D"none">&gt; I don't claim =
to fully understand the usage of this ID,<br clear=3D"none">&gt; but I'm qu=
ite sure that I have no clue what this text<br clear=3D"none">&gt; is suppo=
sed to mean (as a piece of specification):<br clear=3D"none">&gt; <br clear=
=3D"none">&gt;&nbsp; "In particular, the "sip.instance" media feature tag<b=
r clear=3D"none">&gt;&nbsp;  containing the 3GPP2 MEID URN MUST NOT be incl=
uded in requests or<br clear=3D"none">&gt;&nbsp;  responses intended to con=
vey any level of anonymity, as this could<br clear=3D"none">&gt;&nbsp;  vio=
late the users privacy."<br clear=3D"none">&gt; <br clear=3D"none">&gt; I g=
uess this is either an existing problem with whatever<br clear=3D"none">&gt=
; a "'sip.instance' media feature tag" really is or else this<br clear=3D"n=
one">&gt; draft creates a new problem, but the quoted text seems to<br clea=
r=3D"none">&gt; me to be non-deterministic impossible-to-program-for words<=
br clear=3D"none">&gt; seemingly about (but not actually helping with) priv=
acy.<br clear=3D"none">&gt; <br clear=3D"none">&gt; Am I confused?<br clear=
=3D"none"><br clear=3D"none">Possibly, but only because it=E2=80=99s confus=
ing :-)<br clear=3D"none"><br clear=3D"none">As S. Moonesamy pointed out se=
parately, this draft borrows quite a bit of language from RFC 7255, which w=
as pretty much the same things for IMEIs.<br clear=3D"none"><br clear=3D"no=
ne">RFC 3261 (SIP) and a few related RFCs (especially 3323) talk about plac=
ing anonymous calls. The point here is that, when a user is trying to place=
 an anonymous call, don=E2=80=99t screw up and stick identifying informatio=
n somewhere else in the request.&nbsp; I suspect (but do not know) that the=
 language =E2=80=9Cany level of anonymity=E2=80=9D originally came from the=
 distinction between&nbsp; =E2=80=9Cuser-provided privacy=E2=80=9D vs =E2=
=80=9Cnetwork-provided privacy=E2=80=9D discussed in RFC 3323.<br clear=3D"=
none"><br clear=3D"none">The =E2=80=9Csip.instance=E2=80=9D media feature t=
ag is defined in RFC 5626. It carries a URL to persistently identify a spec=
ific SIP user agent. That RFC contains guidance to not use the sip.instance=
 tag for anonymous requests or responses, i.e. when you don=E2=80=99t want =
to the UA to reveal its identity.<br clear=3D"none"><br clear=3D"none">Woul=
d citations help?<br clear=3D"none"><br clear=3D"none">(Authors, feel free =
to jump in).<br clear=3D"none"><br clear=3D"none">Thanks!<br clear=3D"none"=
><br clear=3D"none">Ben.<div class=3D"yqt8367785295" id=3D"yqtfd51502"><br =
clear=3D"none"><br clear=3D"none"><br clear=3D"none">&gt; <br clear=3D"none=
">&gt; Cheers,<br clear=3D"none">&gt; S.<br clear=3D"none">&gt; <br clear=
=3D"none">&gt; On 02/11/17 22:43, The IESG wrote:<br clear=3D"none">&gt;&gt=
; <br clear=3D"none">&gt;&gt; The IESG has received a request from an indiv=
idual submitter to consider the<br clear=3D"none">&gt;&gt; following docume=
nt: - 'Using the Mobile Equipment Identity (MEID) Uniform<br clear=3D"none"=
>&gt;&gt; Resource Name (URN)<br clear=3D"none">&gt;&gt;&nbsp;  as an Insta=
nce ID'<br clear=3D"none">&gt;&gt;&nbsp; &lt;draft-atarius-dispatch-meid-ur=
n-as-instanceid-05.txt&gt; as Informational RFC<br clear=3D"none">&gt;&gt; =
<br clear=3D"none">&gt;&gt; The IESG plans to make a decision in the next f=
ew weeks, and solicits final<br clear=3D"none">&gt;&gt; comments on this ac=
tion. Please send substantive comments to the<br clear=3D"none">&gt;&gt; <a=
 shape=3D"rect" ymailto=3D"mailto:ietf@ietf.org" href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a> mailing lists by 2017-12-08. Exceptionally, comments =
may be<br clear=3D"none">&gt;&gt; sent to <a shape=3D"rect" ymailto=3D"mail=
to:iesg@ietf.org" href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. =
In either case, please retain the beginning of<br clear=3D"none">&gt;&gt; t=
he Subject line to allow automated sorting.<br clear=3D"none">&gt;&gt; <br =
clear=3D"none">&gt;&gt; Abstract<br clear=3D"none">&gt;&gt; <br clear=3D"no=
ne">&gt;&gt; <br clear=3D"none">&gt;&gt;&nbsp;  This specification specifie=
s how the Uniform Resource Name (URN)<br clear=3D"none">&gt;&gt;&nbsp;  nam=
espace reserved for the Third Generation Partnership Project 2<br clear=3D"=
none">&gt;&gt;&nbsp;  (3GPP2) identities and its Namespace Specific String =
(NSS) for the<br clear=3D"none">&gt;&gt;&nbsp;  Mobile Equipment Identity (=
MEID) can be used as an instance-id.&nbsp; Its<br clear=3D"none">&gt;&gt;&n=
bsp;  purpose is to fulfill the requirements for defining how a specific<br=
 clear=3D"none">&gt;&gt;&nbsp;  URN needs to be constructed and used in the=
 "+sip.instance" Contact<br clear=3D"none">&gt;&gt;&nbsp;  header field par=
ameter for outbound behavior.<br clear=3D"none">&gt;&gt; <br clear=3D"none"=
>&gt;&gt; <br clear=3D"none">&gt;&gt; <br clear=3D"none">&gt;&gt; <br clear=
=3D"none">&gt;&gt; The file can be obtained via<br clear=3D"none">&gt;&gt; =
<a shape=3D"rect" href=3D"https://datatracker.ietf.org/doc/draft-atarius-di=
spatch-meid-urn-as-instanceid/" target=3D"_blank">https://datatracker.ietf.=
org/doc/draft-atarius-dispatch-meid-urn-as-instanceid/</a><br clear=3D"none=
">&gt;&gt; <br clear=3D"none">&gt;&gt; IESG discussion can be tracked via<b=
r clear=3D"none">&gt;&gt; <a shape=3D"rect" href=3D"https://datatracker.iet=
f.org/doc/draft-atarius-dispatch-meid-urn-as-instanceid/ballot/" target=3D"=
_blank">https://datatracker.ietf.org/doc/draft-atarius-dispatch-meid-urn-as=
-instanceid/ballot/</a><br clear=3D"none">&gt;&gt; <br clear=3D"none">&gt;&=
gt; <br clear=3D"none">&gt;&gt; No IPR declarations have been submitted dir=
ectly on this I-D.<br clear=3D"none">&gt;&gt; <br clear=3D"none">&gt;&gt; <=
br clear=3D"none">&gt;&gt; <br clear=3D"none">&gt;&gt; <br clear=3D"none">&=
gt;&gt; <br clear=3D"none">&gt; <br clear=3D"none"></div></div><br><br></di=
v> </div> </div>  </div></div></body></html>
------=_Part_1994846_688546350.1509741321096--


From nobody Fri Nov  3 18:11:43 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29F6313FAD6 for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 18:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=jBOUgulk; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=LSd2Nck9
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udrCCEOOh5K8 for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 18:11:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF6D513FAC9 for <ietf@ietf.org>; Fri,  3 Nov 2017 18:11:40 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.50.182]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA41BLbI022218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Nov 2017 18:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1509757895; x=1509844295; bh=HTbIX1Z5a0VuDJGyYj6lGIFE7ctSYP42izkpNRzm9kY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jBOUgulkjAmqkkr9gV/N5bFuwptPZp8t8zC19CoJfU9ojInO+MPZscsmMSyLrV48c fClx40dKj+WKjns8y1NqAI8wSYwTcuRfWxS4II4dKcxZOYhXsnUB/lu6GoCIEnNGIB nGUzMhFzMUyAE8HwonnnR+IKhzpTgRgLiufyY0Zk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1509757895; x=1509844295; i=@elandsys.com; bh=HTbIX1Z5a0VuDJGyYj6lGIFE7ctSYP42izkpNRzm9kY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LSd2Nck9Luhynj5HOcf/X8TO2m99bDnE9AaDiFme+2X8y0x2AQ1x8xuct/dlJuC6j M2y1aKQDG5eKuCPRE+YGoIGa/d1VNtJxE9NTAGe2v+FyTGIEXhRaF/v/0pWaUrP5e5 e6J5IBWKSKbjTRkRTRKgLw6/6n5cfBMKNvPDYB9I=
Message-Id: <6.2.5.6.2.20171103174950.130619c0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 03 Nov 2017 18:10:17 -0700
To: R Atarius <r_atarius@yahoo.com>, Ben Campbell <ben@nostrum.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
In-Reply-To: <14878392.1994847.1509741321099@mail.yahoo.com>
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com> <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie> <039BDED8-AD0F-4AA2-8408-343D4D828751@nostrum.com> <14878392.1994847.1509741321099@mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8jhP4lyWvQ6zAGrxT5wbIwjJg8Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Nov 2017 01:11:42 -0000

Hi Roozbeh, Ben,
At 01:35 PM 03-11-2017, R Atarius wrote:
>Just agreeing with Ben. RFC 5626 highlights that the UA could omit 
>the instance ID for private or anonymous calls. So this is the 
>problem with instance ID and not UUID, MEID, IMEI which have been 
>employed to create the instance ID.

RFC 5626 was published in 2009.  RFC 7258 was published in 2014.  Are 
the Security Considerations the same as in 2009?

The Document Shepherd write-up mentioned "his affiliation".  There 
isn't any information about affiliation in the write-up or in 
draft-atarius-dispatch-meid-urn-as-instanceid-05.

Regards,
S. Moonesamy 


From nobody Fri Nov  3 21:32:46 2017
Return-Path: <ben@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 C384413FB34 for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 21:32:44 -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, 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 3n0WrPK_snMU for <ietf@ietfa.amsl.com>; Fri,  3 Nov 2017 21:32:42 -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 D0EC713FB04 for <ietf@ietf.org>; Fri,  3 Nov 2017 21:32:42 -0700 (PDT)
Received: from [10.0.1.82] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id vA44WJgA008398 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 3 Nov 2017 23:32:21 -0500 (CDT) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.82]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <AC4D673F-D994-4F1C-AB56-4F31D2D6DC74@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_C16D8D29-1940-4CFA-89CE-1EFA702A2871"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
Date: Fri, 3 Nov 2017 23:32:17 -0500
In-Reply-To: <6.2.5.6.2.20171103174950.130619c0@elandnews.com>
Cc: R Atarius <r_atarius@yahoo.com>, ietf@ietf.org, Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com> <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie> <039BDED8-AD0F-4AA2-8408-343D4D828751@nostrum.com> <14878392.1994847.1509741321099@mail.yahoo.com> <6.2.5.6.2.20171103174950.130619c0@elandnews.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1jTeuFLOxHWGsjCdCUeknIT1CLI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Nov 2017 04:32:45 -0000

--Apple-Mail=_C16D8D29-1940-4CFA-89CE-1EFA702A2871
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On Nov 3, 2017, at 8:10 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>=20
> Hi Roozbeh, Ben,
> At 01:35 PM 03-11-2017, R Atarius wrote:
>> Just agreeing with Ben. RFC 5626 highlights that the UA could omit =
the instance ID for private or anonymous calls. So this is the problem =
with instance ID and not UUID, MEID, IMEI which have been employed to =
create the instance ID.
>=20
> RFC 5626 was published in 2009.  RFC 7258 was published in 2014.  Are =
the Security Considerations the same as in 2009?
>=20

The draft says the UAC MUST NOT include a sip.instance tag with the MEID =
in a request intended to be anonymous, and that the service provider =
MUST NOT forward it towards the UAS.  That seems as relevant today as in =
2009 or 2014. It may well be that the guidance in 5626 is not sufficient =
to guarantee anonymity, but I don=E2=80=99t see how that would change =
the guidance in this draft. Is there something in particular you would =
like to see?

> The Document Shepherd write-up mentioned "his affiliation".  There =
isn't any information about affiliation in the write-up or in =
draft-atarius-dispatch-meid-urn-as-instanceid-05.

I=E2=80=99m guessing that is because the affiliation change since the =
shepherd did the writeup. Is there a specific concern there? The writeup =
does say that the author stated that he was not aware of any IPR, which =
is our usual standard.

Thanks,

Ben.

--Apple-Mail=_C16D8D29-1940-4CFA-89CE-1EFA702A2871
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAln9QtEACgkQgFZKbJXz
1A05Ng//ZtCA6liHs4u61+bBr2K/tetXGCHAro2bJbECrtLS44C5bMII4s69PNPO
8/RSacnDP2HsCIG/n9C3RcqL79S2+NcHP3Bw5yL7zgdwamQzIQP7PRRen6hVM5D3
LJBj3/9AhNcVJ+w/O1DlLfwyVdWPOW9vrbOfe9FbU7ASQ/gDfYtwGQpJ1ebsf/E0
Tm9UTKS66KrHZ4nT6A8oRcYcS6kPh2lAe13t4Y5hFTePJTQQIiON2wgRrhHclzJl
W1ciJ5tM7aYDHWA8QdDHHJp/bAhIMsC4M3eT1TX81Fqq9PopjYUIwg9O/3/dxqIj
bPbU1XGjclmvSkgKK89ZO48Cpfwdu5d75+J3tKO3x5yNe4cpfQinHfup8WNBraw6
NCXT7jKimGZOfKEidXH18k/UurlS/bU1KfbZj5pN5j+mhlwekFNziapwtf+bUzc/
0c7jHq4/HR32RiQUWbJSNWq5kTEteLoz58RsfsY8GRXIlYFa0sP3J1TcEO7W4fEB
fMpXAC/MRLlNF9TmG396WqxaKExsN87CvGLcpIMesY3qa2zz8JlQPWJWSp4sM0v0
S7TlwoqAOGmyc3n7OWYwRavUStEuKVgkbHHkp5o3qH91/BEL00pBXFmooBA2ncJI
XHmz5//fy7LCXW4A1fMU6Bgwb5jjJtXF7JfWgs87/9I5jXK14NY=
=/oj6
-----END PGP SIGNATURE-----

--Apple-Mail=_C16D8D29-1940-4CFA-89CE-1EFA702A2871--


From nobody Sat Nov  4 09:34:13 2017
Return-Path: <tom@herbertland.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0374613FB87 for <ietf@ietfa.amsl.com>; Sat,  4 Nov 2017 09:34:11 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 562hN5SGsvS6 for <ietf@ietfa.amsl.com>; Sat,  4 Nov 2017 09:34:09 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D95BC13FB7D for <ietf@ietf.org>; Sat,  4 Nov 2017 09:34:08 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id q83so6589502qke.6 for <ietf@ietf.org>; Sat, 04 Nov 2017 09:34:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=N2cJJmGPQB3YYPqVgzmP/XInW/7BxdRmLIQi8CY91Pg=; b=SLVMLd1oUhfPI8BfXMj5rbfed6hDXq6K4OR06KM95pN1s8sRFVay6VEUu3Eknxkenb nEcdMNlogGqHmeEGA3lu/Lbru7Csbu0m4jjrERRBAStnd4yWFmhgARpNTFx65+7adnnD Y+iemAysANswGEvnUCNRo8NtcUxwkLkgG2liqPH+fhtUXJ//dQttkxSZBfvH8dLXypvk jN051OnphMpC/0WdXjYUGsFcTo7iSuKSD5lQuYXJhGvPqCPneYdDC/T+MsqzVlgFRwVx KXbNca05EGG46tXUUy3s46pl0wkTcWfHZxe6bQGZK9/OVrLgMGjxsjyU6vgT8gaOj318 2urg==
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=N2cJJmGPQB3YYPqVgzmP/XInW/7BxdRmLIQi8CY91Pg=; b=dIy72PkX/lyflPYtDWK/VHGQhBCYEEZWDqx53zE1GuVxG1ZLYSVIy4x0vfFSKYx20T c3kXprhrNQZyhtJ4PoIMvRSe4/e8ZsGlkho2Ko+bYhpVYrKqaTkQmHnfqHHR1N1ZgERn GjO6HAOOONH49pEHuZJo2y+2CFQcVdcUoynitwFi4+r1NUSCar4A8sC3tllSQPu/Pol2 Pdq+rKcWnHYEikUcezHmYDnuwDT2UKwomnt7XIODeuxyuG0GBx/T9RvnRR1o7OroGfK1 jcc0y+KCNAho3X3wqoFlCrZLZ7YyCQSBglUq1t6MRpkWhZp7cHixnrA2yfSFPvS1vrV8 RCdw==
X-Gm-Message-State: AJaThX4NJ+RIVJ3KrW/YONG0lammE6a8Ydx3lhiozrO+p4RCcpD2s3WU mm1WZmeTfXP0i5LwHzGOaV9cEAAxLrLpLnGN1bvAUQ==
X-Google-Smtp-Source: ABhQp+T6kd5WKzMvnG7nDu0/M2o48uS3IEAY6PhlJ7ZYBWKFNSM1x/PE0uCmDI0e8xl2J4KRyHvmd9jjUPl/5+tz73o=
X-Received: by 10.55.148.70 with SMTP id w67mr15088843qkd.102.1509813247785; Sat, 04 Nov 2017 09:34:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.54.4 with HTTP; Sat, 4 Nov 2017 09:34:07 -0700 (PDT)
In-Reply-To: <20171103175258.GA6808@faui40p.informatik.uni-erlangen.de>
References: <644DA50AFA8C314EA9BDDAC83BD38A2E0EAA7204@sjceml521-mbx.china.huawei.com> <dd2c3bd5-dd37-109b-2e81-0327db4daa09@cs.tcd.ie> <0BA14206-DC82-49EF-A625-B2425FA396F6@gmail.com> <1f254140-1340-6c7d-9c73-e7137562c685@gmail.com> <fa644cc2-161f-8884-3445-2b50d2c2ad23@htt-consult.com> <cf2ca920-f2d2-b65e-05eb-ebe3c30b76d1@huitema.net> <CAG-CQxrdS9L+2+bN=1NcPGuztn4U4OwSWUiNaVcS9Bsm2mtpfA@mail.gmail.com> <b18459d1-7ce1-b83d-787d-9066267d584b@huitema.net> <20171101172146.GA12437@faui40p.informatik.uni-erlangen.de> <CALx6S34Bkv4ipyA5si4KkW7VaYU6A=3=cPpRo_ss00H+vDms-w@mail.gmail.com> <20171103175258.GA6808@faui40p.informatik.uni-erlangen.de>
From: Tom Herbert <tom@herbertland.com>
Date: Sat, 4 Nov 2017 09:34:07 -0700
Message-ID: <CALx6S34g99F=6WZJWUfxRjPbYcBaRZzhSjC0DeNev3GY6mLUBw@mail.gmail.com>
Subject: Re: [Ideas] [lisp] WG Review: IDentity Enabled Networks (ideas)
To: Toerless Eckert <tte@cs.fau.de>
Cc: Christian Huitema <huitema@huitema.net>, Padma Pillay-Esnault <padma.ietf@gmail.com>,  "ietf@ietf.org" <ietf@ietf.org>, "ideas@ietf.org" <ideas@ietf.org>, Dino Farinacci <farinacci@gmail.com>, "lisp@ietf.org list" <lisp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jdkf5HrHApO6NBpp_PcFqSyk5m0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Nov 2017 16:34:11 -0000

On Fri, Nov 3, 2017 at 10:52 AM, Toerless Eckert <tte@cs.fau.de> wrote:
> Thanks, Tom, inline
>
> On Thu, Nov 02, 2017 at 08:30:11AM -0700, Tom Herbert wrote:
>> Toerless,
>>
>> That maybe true, but personal devices, such as smart phones and cars
>> that are associated with individuals, are hardly going away anytime
>> soon. How addresses are assigned to these devices has a material
>> impact on individual privacy. Even right now there are two long
>> threads on v6ops right now that are delving precisely into privacy of
>> IPv6 addresses that may be relevant. This includes discussion about
>> CGNAT and efforts by some governments to illegalize it because the
>> privacy it gives is too strong for law enforcement.
>
> Sure. All i was saying is that we should not dismiss solutions if they
> do not help to improve privacy. It reminds me of the congestion control
> principles and the fact that a lot of money is made with video in
> controlled networks without congestion control. As in: "Sorry, we couldn't
> build a great solution for sensor devices in manufacturing plants because
> those solutions wouldn't pass the privacy bar".
>
> I am not even aware if we have good characterizations of solutions
> vs. privacy like IMHO we have for congestion control, but of course its
> a more complex topic. (IMHO: lot more cases IMHO to distinguish).
>
> That being said, i would of course love to see that we leverage IDEAs to
> also create options that (could) enhance privacy, i just don't think that
> we will make a lot of progress if we can not do this work in a WG but
> if all the complex issues have to be resolved on pre-wg mailing lists before
> even charters are accepted. This is part of whats wrong with the IETF
> if i may say so.
>
> For example, Christian contested that long lived identifiers help to
> improve privacy (for device = individual case) and those arguments about
> privacy had the IESG turn their opinions.
>
> IMHO: The long-lived identifiers are meant to be functionally limited. You do
> increase the bar of identifying an individual when you do this because the
> web applications need to do more work to correlate application layer
> information across multiple functional identifiers.
>
> So, how & where do we even create a common understanding about the qualitative and
> quantitative privacy benefits of technology options if not in a WG. Functional
> identifiers just being one example.
>
> Even more fundamentally: If each individual application layer function requires
> authentication via e.g.: government, google or facebook ID, and all those
> web services are free to correlate their information in the backend, any
> network layer privacy work is just like growing organic tobacco.
>
> Which is why i really would like to know what the state of requirements/BCP etc.
> is re. privacy at app layer in the IETF, because without that knowledge, i can
> only define the privacy benefits of a network layer enhancement under the
> ASSUMPTION of particular application behavior.
>
I don't think that's true. Privacy enhancements at the network layer
are needed to prevent inferences of PII by third party using just
network layer information that might be passively intercepted.
Knowledge of the application is not needed. In the base case scenario,
it should be impossible for a random intermediate node in the Internet
to determine who is communicating to whom (identity), where someone is
communicating from (location), and what they are saying (content).

> My impression of IETF policy is "you have to trust the web services
> provider (not to share/correlate/abuse user/client information)" and in the
> same breath "you can not trust the network service provider (to behave in the
> same way)". Would love to get pointed to documents proving this impression to
> be wrong. Especially the option that there can be network providers that
> users may want to trust more than arbitrary web services providers should IMHO
> be acknowledged. And thats definitely an option i think is worthwhile to build
> solutions against.
>
I doubt there's any IETF RFC or BCP stating whom were required to
trust as a MUST. Personally, I don't inherently trust web service
providers, network service providers, government, vendors, or really
anyone else involved in communications (including myself :-) ). Some
trust is needed out of necessity to do anything useful, but we should
always be searching for ways to further minimize that. A good example
is turning up the TLS on the Internet; this eliminated the need to
trust the network with our plaintext. I believe a similar thing will
happen with addressing, we'll figure out how to eliminate all PII from
addresses so that we don't have to trust the network to not be making
inferences that breaks privacy.

Tom


From nobody Sat Nov  4 14:37:29 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 490D413FB06; Sat,  4 Nov 2017 14:37:28 -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 K6xc3ak-BtB0; Sat,  4 Nov 2017 14:37:27 -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 12AA313FADA; Sat,  4 Nov 2017 14:37:26 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eB67z-0005ws-Fk; Sat, 04 Nov 2017 17:37:19 -0400
Date: Sat, 04 Nov 2017 17:37:12 -0400
From: John C Klensin <john-ietf@jck.com>
To: Tom Herbert <tom@herbertland.com>, Toerless Eckert <tte@cs.fau.de>
cc: ideas@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>, Christian Huitema <huitema@huitema.net>, Dino Farinacci <farinacci@gmail.com>,  ietf@ietf.org
Subject: Re: [Ideas] [lisp] WG Review: IDentity Enabled Networks (ideas)
Message-ID: <B6CAD3DCDB18980FA879E936@PSB>
In-Reply-To: <CALx6S34g99F=6WZJWUfxRjPbYcBaRZzhSjC0DeNev3GY6mLUBw@mail.gmail.com>
References: <644DA50AFA8C314EA9BDDAC83BD38A2E0EAA7204@sjceml521-mbx.china.huawei.com> <dd2c3bd5-dd37-109b-2e81-0327db4daa09@cs.tcd.ie> <0BA14206-DC82-49EF-A625-B2425FA396F6@gmail.com> <1f254140-1340-6c7d-9c73-e7137562c685@gmail.com> <fa644cc2-161f-8884-3445-2b50d2c2ad23@htt-consult.com> <cf2ca920-f2d2-b65e-05eb-ebe3c30b76d1@huitema.net> <CAG-CQxrdS9L+2+bN=1NcPGuztn4U4OwSWUiNaVcS9Bsm2mtpfA@mail.gmail.com> <b18459d1-7ce1-b83d-787d-9066267d584b@huitema.net> <20171101172146.GA12437@faui40p.informatik.uni-erlangen.de> <CALx6S34Bkv4ipyA5si4KkW7VaYU6A=3=cPpRo_ss00H+vDms-w@mail.gmail.com> <20171103175258.GA6808@faui40p.informatik.uni-erlangen.de> <CALx6S34g99F=6WZJWUfxRjPbYcBaRZzhSjC0DeNev3GY6mLUBw@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.10
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/RX7COl2vZGBK0ZBY83hQ_WKrTcQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Nov 2017 21:37:28 -0000

--On Saturday, November 4, 2017 09:34 -0700 Tom Herbert
<tom@herbertland.com> wrote:

>...
> A good example
> is turning up the TLS on the Internet; this eliminated the
> need to trust the network with our plaintext. 

And, for many people, replaces it with the need to trust
firewall and security appliance providers who have concluded
that they need to intercept and decrypt traffic in order to
identify malware and other undesirable traffic.   At least in
principle, one does get to choose which vendor to trust and does
know (by virtue of having to install special certificates) which
vendor or provider is being trusted, but those options may not
be meaningful for typical users.

I worry with that example and several others that the IETF is
not adequately distinguishing between "increasing privacy" or
"preventing mass surveillance" on the one hand and forcing users
into a "who do your trust" or even "who does someone trust on
your behalf" shell game on the other.

best,
   john





From nobody Sat Nov  4 19:18:39 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 9862513FC3B for <ietf@ietfa.amsl.com>; Sat,  4 Nov 2017 19:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 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, 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 VEaSQlROJYAG for <ietf@ietfa.amsl.com>; Sat,  4 Nov 2017 19:18:36 -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 4872813FADE for <ietf@ietf.org>; Sat,  4 Nov 2017 19:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3108; q=dns/txt; s=iport; t=1509848316; x=1511057916; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+yGaF45giQWIz7rlX4oi8fXBTxWKReczhSiEB9d4TNk=; b=HIGifQCceDa91xJnvUTORfCaZvYjkpuXosmRjeNqOsIVyVQz4yQ85aPj aQ0py8SYD2SDm6VKAN7TIdzLFAB7cInJ7fqmkfREBHYSh3W2YYMpXpdFf Qn3fP5nlssnB5wE/usDVoalyco99w8SWO8GUSk+EmhSpoeBneasZucfKb g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CgAQCTc/5Z/5JdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgwYugVInB4N2mTmBfJhXCoIBgzoCGoQ9QhUBAQEBAQEBAQFrKIU?= =?us-ascii?q?eAQEBAQMjEUUMBAIBCA4DAwECAQICJgICAjAVCAgCBAENBYojqQiCJ4sFAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBHYEPgh+CB4M8KYMBiCYwgjIFog4ClHqCFYoHhxi?= =?us-ascii?q?VaQIRGQGBOAE1IoFsehV2AYI2hF93imSBEQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.44,345,1505779200"; d="scan'208";a="98623226"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Nov 2017 02:18:35 +0000
Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id vA52IZ4u020980 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 5 Nov 2017 02:18:35 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 4 Nov 2017 21:18:34 -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.1320.000; Sat, 4 Nov 2017 21:18:37 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Toerless Eckert <tte@cs.fau.de>, Eliot Lear <lear@cisco.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: letting IETF build on top of Open Source technology
Thread-Topic: letting IETF build on top of Open Source technology
Thread-Index: AQHTUSufYIZ3ZhLpqkGwXBFj35JsrqL8DBoAgAAA5wCAAAJsAIAABfsAgAEr/wCAAAJuAIAAB+eAgAF6oACABrDngA==
Date: Sun, 5 Nov 2017 02:18:37 +0000
Message-ID: <D786359E-D919-42D5-89AA-9893BBA63CF5@cisco.com>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <CABkgnnWzJr_n4qLnJsu=mvBLjHwCH2LdbbjNGENaavVX357NpQ@mail.gmail.com> <CAG4d1regBTXfK798D0_hunWbC5beiWFsN_uR2q3vWyhwcmZ6vA@mail.gmail.com> <CABkgnnUoBBdUBiFMzD964eSpDkouaNSfUhvCKnBkSg87me9EFQ@mail.gmail.com> <79eaeafe-a35d-8342-4b6a-7413b4309ed9@gmail.com> <149d4316-a633-c4ba-e287-340afe3b1e0d@cisco.com> <7e02dce3-524b-1d56-362b-ef5bf2faab3c@cs.tcd.ie> <c860c143-6dee-c682-20f8-ba6180ca40a8@cisco.com> <20171031205427.GB5968@faui40p.informatik.uni-erlangen.de>
In-Reply-To: <20171031205427.GB5968@faui40p.informatik.uni-erlangen.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.66.254.240]
Content-Type: text/plain; charset="utf-8"
Content-ID: <02B294399213A34CB9D7AE8E26C4ED99@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ny3wd6Neeb7Ub_NJplJdnzKA7Ng>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Nov 2017 02:18:37 -0000

LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYgPGlldGYtYm91bmNlc0BpZXRm
Lm9yZz4gb24gYmVoYWxmIG9mIFRvZXJsZXNzIEVja2VydCA8dHRlQGNzLmZhdS5kZT4NCkRhdGU6
IFdlZG5lc2RheSwgTm92ZW1iZXIgMSwgMjAxNyBhdCA3OjU1IEFNDQpUbzogImxlYXJAY2lzY28u
Y29tIiA8bGVhckBjaXNjby5jb20+DQpDYzogImlldGZAaWV0Zi5vcmciIDxpZXRmQGlldGYub3Jn
Pg0KU3ViamVjdDogUmU6IGxldHRpbmcgSUVURiBidWlsZCBvbiB0b3Agb2YgT3BlbiBTb3VyY2Ug
dGVjaG5vbG9neQ0KDQogICAgU28sIHdoYXRzIHRoZSByaWdodCB0ZXJtaW5vbG9neSBoZXJlIGZv
ciBhdCBsZWFzdCB0aGUgdHdvIGNsYXNzZXMNCiAgICB0aGF0IGkgdGhpbmsgYXJlIGVhc3kgdG8g
ZGVzdGluZ3Vpc2g6DQogICAgDQogICAgYSkgSW4gb25lIGNhc2UgaSBoYXZlIEZPU1MgdGhhdCBp
bXBsZW1lbnRzIGEgbmV3IHByb3RvY29sIGxpa2UgcnN5bmMgZG9lcywNCiAgICAgICBhbmQgaW50
ZXJvcCBtZWFucyB0aGF0IHlvdSB3YW50IHR3byBpbmRlcGVuZGVudCBpbXBsZW1lbnRhdGlvbnMg
c3VwcG9ydA0KICAgICAgIHRoZSBwcm90b2NvbC4NCiAgICANCiAgICBiKSBJbiBhbm90aGVyIGNh
c2UsIHdoaWNoIGkgdGhpbmsgYXJlIGFsbCB5b3VyIGV4YW1wbGVzLCB5b3UgaGF2ZSBzb21lDQog
ICAgICAgZm9ybSBvZiAic2VydmljZSIgd2hpY2ggaXMgcHJvdmlkaW5nIHNvbWUgZm9ybSBvZiAi
QVBJIiBhbmQgaW50ZXJvcA0KICAgICAgIHJlYWxseSBtZWFucyB0aGF0IG9ubHkgb25lIGltcGxl
bWVudGF0aW9uIGlzIHJlcXVpcmVkIHRvIHNob3cgaG93DQogICAgICAgaXQgd29ya3Mgd2l0aCBt
dWx0aXBsZSBjbGllbnRzIG9mIHRoZSBzZXJ2aWNlLg0KICAgIA0KICAgIEkgYWxzbyB0aGluayB0
aGF0IGIpIGlzIGVhc2llciB0byBhZG9wdCBiZWNhdXNlIA0KICAgIC0gaW50ZXJvcCBkb2VzIG5v
dCByZXF1aXJlIHlvdSB0byBmaW5kIG90aGVyIGltcGxlbWVudGF0aW9ucyBvZiB0aGUNCiAgICAg
IHNhbWUgcHJvdG9jb2wvc2VydmljZQ0KICAgIC0gQW4gQVBJIHRoYXQgTVVTVCBiZSB1c2VkIGJ5
IGEgdGhpcmQgcGFydHkgY2xpZW50IGlzIG1vcmUgbmF0dXJhbGx5DQogICAgICBkb2N1bWVudGVk
IHRoYW4gYSBwcm90b2NvbCB0aGF0IHdhcyBtZWFudCB0byBiZSB1c2VkIGJldHdlZW4gbXVsdGlw
bGUNCiAgICAgIGluc3RhbmNlcyBvZiBhIHNpbmdsZSBGT1NTIHNvZnR3YXJlICh0eXBpY2FsIGEp
IGNhc2UpLg0KDQpbY3VlXSBJIGFncmVlLldoZW4gSSB0aGluayBhYm91dCBvcGVucyBzb3VyY2Ug
c29mdHdhcmUgdGhhdCB3b3VsZCBzdGFuZCB1cCB3ZWxsIGluIHRoZSBmYWNlIG9mIHRoZSA1IHJl
cXVpcmVtZW50cyBpbiBzZWN0aW9uIDIgb2YgdGhlIGRyYWZ0LCB5b3VyIGNsYXNzIGIgd291bGQg
Y2VydGFpbmx5IHN0YW5kIGEgYmV0dGVyIGNoYW5jZS4gV2hlbiBJIHJlYWQgdGhlIGRyYWZ0LCBJ
IHNhdyBpdCBhcyB0YXJnZXRpbmcgdGhhdCBjbGFzcyBvZiBvcGVuIHNvdXJjZSBwcm9qZWN0cy4g
DQoNCkNoZWVycywNCkNoYXJsZXMNCiAgICANCiAgICBDaGVlcnMNCiAgICAgICAgVG9lcmxlc3MN
CiAgICANCiAgICBPbiBNb24sIE9jdCAzMCwgMjAxNyBhdCAxMToxOToxOVBNICswMTAwLCBFbGlv
dCBMZWFyIHdyb3RlOg0KICAgID4gVGhlIG9idmlvdXMgZXhhbXBsZSB3b3VsZCBiZSB0aGUgdmFz
dCBxdWFudGl0aWVzIG9mIFlBTkcgdGhhdCBhcmUNCiAgICA+IGNyb3BwaW5nIHVwIGV2ZXJ5d2hl
cmUuIEFub3RoZXIgb25lIHRoYXQgbWFueSByZWZlcmVuY2Ugb3V0c2lkZSBvZiB0aGUNCiAgICA+
IElFVEYgY29udGV4dCBpcyBBcmNTaWdodCBDRUYsIHdoaWNoIGlzIGFuIG92ZXJsYXkgb24gU1lT
TE9HIHRoYXQgaXMNCiAgICA+IGZyZXF1ZW50bHkgdXNlZC4gIFdoZW4gdGhlcmUncyBhY3RpdmUg
ZGV2ZWxvcG1lbnQgb24gYSBwcm9qZWN0LCB0aGlzDQogICAgPiBpc24ndCBhIGdvb2QgZml0LCBk
dWUgdG8gZmVhdHVyZSB2ZWxvY2l0eS4gIEV2ZW4gdGhlcmUsIHRob3VnaCwgc29tZSBtYXkNCiAg
ICA+IHdpc2ggdG8gZGVjbGFyZSBjZXJ0YWluIGludGVyZmFjZXMgYm90aCBwdWJsaWMgYW5kIHN0
YWJsZS4gIEkgY291bGQNCiAgICA+IGltYWdpbmUgdGhlIGdpdCB0ZWFtIGRvaW5nIHRoYXQsIGZv
ciBpbnN0YW5jZSwgZ2l2ZW4gdGhlIG51bWJlciBvZiBmcm9udA0KICAgID4gZW5kcyB0aGVyZSBh
cmUgd2l0aCBpdC4NCiAgICA+IA0KICAgID4gRWxpb3QNCiAgICANCiAgICANCg0K


From nobody Sat Nov  4 19:18:46 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 E263813FC3B for <ietf@ietfa.amsl.com>; Sat,  4 Nov 2017 19:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 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, 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 BvnFmL7pYRnR for <ietf@ietfa.amsl.com>; Sat,  4 Nov 2017 19:18:37 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B70413FC3A for <ietf@ietf.org>; Sat,  4 Nov 2017 19:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3810; q=dns/txt; s=iport; t=1509848317; x=1511057917; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=2SJ9fomz0Q/PbZP90pClUt/SQtj3Q9m3ljSt1+6VtMU=; b=gUKGxGT9bz78T9jtdtQYVtE3Fg2dIJNjwxEDWZMvyiQb0iePAuvanZ1v pnPHqe/rSJB13ducs8wdzWkOreekbkJd69WatZircOYSt2D/GouIXrmNl U2RI5FkJJLQQBPfUlyfR2FGPFq3TfMPM+1c0uoeEI5aT5cqPKOcfYn6cU M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CnAACTc/5Z/4cNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgwYugVInB4N2ih+PGoFWJohRjXWCEQqCAYM6AhqEPT8YAQEBAQE?= =?us-ascii?q?BAQEBayiFHgEBAQEDIxFFDAQCAQgRAwECAwImAgICHxEVCAgCBAENBYoLAxWpC?= =?us-ascii?q?IInhzINg0YBAQEBAQEBAQEBAQEBAQEBAQEBAQEdgQ+CH4IHg2ULgWmBDYJqgie?= =?us-ascii?q?DFTCCMgWKKpcoPAKPMVCEeYIVHZECii2CbYhPAhEZAYE4AR84gWx6FXYBgjaEX?= =?us-ascii?q?3eKZIERAQEB?=
X-IronPort-AV: E=Sophos;i="5.44,345,1505779200"; d="scan'208";a="316579571"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Nov 2017 02:18:35 +0000
Received: from XCH-ALN-018.cisco.com (xch-aln-018.cisco.com [173.36.7.28]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id vA52IZqP012433 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 5 Nov 2017 02:18:36 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-018.cisco.com (173.36.7.28) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 4 Nov 2017 21:18:38 -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.1320.000; Sat, 4 Nov 2017 21:18:38 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: Keith Moore <moore@network-heretics.com>, Alia Atlas <akatlas@gmail.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: letting IETF build on top of Open Source technology
Thread-Topic: letting IETF build on top of Open Source technology
Thread-Index: AQHTUSufYIZ3ZhLpqkGwXBFj35JsrqL/UM0AgAYp5oA=
Date: Sun, 5 Nov 2017 02:18:37 +0000
Message-ID: <56CEC7A6-2F04-4913-A3CE-15BC1B846BE2@cisco.com>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <E6ED7F15-8855-45B6-A42E-707E32966CFA@network-heretics.com>
In-Reply-To: <E6ED7F15-8855-45B6-A42E-707E32966CFA@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.66.254.240]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D1B023F14E342E429CCAA35C8A5CCCD2@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LMNt-V3wipx6LcdScaut71c1XmE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Nov 2017 02:18:39 -0000

VGhpcyBpcyB0cnVlIGluIHNvbWUgY2FzZXMsIGJ1dCBub3QgaW4gb3RoZXJzLiBUaGVyZSBoYXMg
YmVlbiBhbmQgY29udGludWVzIHRvIGJlIGEgYmlnIHB1c2ggaW4gb3BlbiBzb3VyY2Ugc29mdHdh
cmUgYW5kIGluIHNvZnR3YXJlIGluIGdlbmVyYWwgdG8gY3JlYXRlIGFwcGxpY2F0aW9ucyB0aGF0
IGFyZSBjb21wb3NlIG9mIG1hbnkgc21hbGwgcGllY2VzIHRoYXQgaW50ZXJhY3Qgd2l0aCBlYWNo
IG90aGVyIHRocm91Z2ggd2VsbCBkZWZpbmVkIGludGVyZmFjZXMuIFRoaXMgbGVhZHMgdG8gbW9y
ZSBtb2R1bGFyIHNvZnR3YXJlIGFuZCBiZXR0ZXIgY29kZS9jb21wb25lbnQgcmV1c2UuIFRoaXMg
cHJhY3RpY2UgcmVzdWx0cyBpbiBjb2RlIHRoYXQgaXMgbW9yZSBhcHByb3ByaWF0ZSBhcyBhIG5v
cm1hdGl2ZSByZWZlcmVuY2UuIEkgd291bGQgZXhwZWN0IHRoZSBub3JtYXRpdmUgcmVmZXJlbmNl
IHRvIGJlIHRvIGEgc3BlY2lmaWMgdmVyc2lvbiBvciByZWxlYXNlIG9mIHRoZSBzb2Z0d2FyZSBh
bmQgaXRzIGNvcnJlc3BvbmRpbmcgQVBJKHMpLiBUaG9zZSBBUElzIGNvdWxkIGNoYW5nZSB3aXRo
IGZ1dHVyZSB2ZXJzaW9ucyBvZiB0aGUgc29mdHdhcmUsIGJ1dCBhcyB3aXRoIHN0YW5kYXJkcywg
d2UgdGVuZCB0byB0cnkgcHJldHR5IGhhcmQgdG8gYXZvaWQgbm9uLWJhY2t3YXJkIGNvbXBhdGli
bGUgQVBJcyBjaGFuZ2VzIGFmdGVyIHRoZSBzb2Z0d2FyZSBoYXMgcmVhY2hlZCBhIHN0YXRlIG9m
IG1hdHVyaXR5IHRoYXQgb3RoZXJzIG9uIGJ1aWxkaW5nIG9uIHRvcCBvZiBpdCBhbmQgcmVseWlu
ZyBvbiB0aG9zZSBBUElzLg0KICANCkNoZWVycywNCkNoYXJsZXMNCg0KLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCkZyb206IGlldGYgPGlldGYtYm91bmNlc0BpZXRmLm9yZz4gb24gYmVoYWxm
IG9mIEtlaXRoIE1vb3JlIDxtb29yZUBuZXR3b3JrLWhlcmV0aWNzLmNvbT4NCkRhdGU6IFdlZG5l
c2RheSwgTm92ZW1iZXIgMSwgMjAxNyBhdCA0OjEwIFBNDQpUbzogQWxpYSBBdGxhcyA8YWthdGxh
c0BnbWFpbC5jb20+DQpDYzogImlldGZAaWV0Zi5vcmciIDxpZXRmQGlldGYub3JnPg0KU3ViamVj
dDogUmU6IGxldHRpbmcgSUVURiBidWlsZCBvbiB0b3Agb2YgT3BlbiBTb3VyY2UgdGVjaG5vbG9n
eQ0KDQogICAgSXQgc2VlbXMgdG8gbWUgdGhhdCBhIGZ1bmRhbWVudGFsIHByb2JsZW0gd2l0aCBy
ZWZlcmVuY2luZyBPcGVuIFNvdXJjZSBzb2Z0d2FyZSBpcyB0aGF0IGluIG11Y2ggKG5vdCBhbGwp
IG9mIHRoZSBPcGVuIFNvdXJjZSB3b3JsZCwgcmFwaWQgaW5ub3ZhdGlvbiBhbmQgZXZvbHV0aW9u
IGlzIHZhbHVlZCBtb3JlIHRoYW4gc3RhYmxlIHByb3RvY29sIGludGVyZmFjZXMuICAgVGhlcmUg
aXMgYSB0ZW5kZW5jeSB0byByZWx5IG9uIHVzZXJzIHRvIGZyZXF1ZW50bHkgdXBkYXRlIHRoZWly
IHNvZnR3YXJlLCB3aGljaCBpcyBzZWVuIGFzIGdpdmluZyBkZXZlbG9wZXJzIGZyZWVkb20gdG8g
Y2hhbmdlIGludGVyZmFjZXMgb24gcmVsYXRpdmVseSBzaG9ydCBub3RpY2UuICANCiAgICANCiAg
ICBPZiBjb3Vyc2UgdGhhdCdzIGFuIG92ZXJzaW1wbGlmaWNhdGlvbi4gIEluIHByYWN0aWNlIGdv
b2Qgb3BlbiBzb3VyY2UgZGV2ZWxvcGVycyBhcmUgY2FyZWZ1bCB0byBhdm9pZCBhYnJ1cHQgY2hh
bmdlcyB0byBpbnRlcmZhY2VzOyBpbnN0ZWFkIHRoZXkgY3JlYXRlIG5ldyBpbnRlcmZhY2VzIGFu
ZCBkZXByZWNhdGUgb2xkIG9uZXMuICAgQnV0IHNpbmNlIG9uZSBvZiB0aGUgb2Z0LXRvdXRlZCBi
ZW5lZml0cyBvZiBPcGVuIFNvdXJjZSBpcyB0byBhbGxvdyBzb2Z0d2FyZSBzeXN0ZW1zIHRvIGV2
b2x2ZSByYXBpZGx5LCB0aGlzIHNvbWV0aW1lcyBhbHNvIHJlc3VsdHMgaW4gbmV3IHByb3RvY29s
IGZlYXR1cmVzIGJlaW5nIGRlcGxveWVkIHJhcGlkbHkgdG8gdGhlIHBvaW50IHRoYXQgaXQgaW1w
YWlycyBpbnRlcm9wZXJhYmlsaXR5IGJldHdlZW4gbmV3IGFuZCBvbGQgaW1wbGVtZW50YXRpb25z
LiAgIFRoaXMgY2F1c2VzIGEgZ3JlYXQgbWFueSBwcm9ibGVtcyBvdGhlciB0aGFuIGp1c3QgcHJv
dG9jb2wgaW50ZXJvcGVyYWJpbGl0eSBmYWlsdXJlcywgaW5jbHVkaW5nIGRlcGVuZGVuY3kgaGVs
bC4NCiAgICANCiAgICBTbyBwYXJ0IG9mIHRoZSBlZmZvcnQgdG8gaW1wcm92ZSBjb29wZXJhdGlv
biBiZXR3ZWVuIElFVEYgYW5kIE9wZW4gU291cmNlIGRldmVsb3BlcnMgLSB3aG8gdGVuZCB0byBo
YXZlIHNpbWlsYXIgbW90aXZhdGlvbnMgZXZlbiBpZiB0aGVpciBtZXRob2RzIGRpZmZlciAtIG1p
Z2h0IGJlIGluIGNvbnZpbmNpbmcgdGhlbSB0aGF0IHRoZXkgd291bGQgYmVuZWZpdCBmcm9tIG1v
cmUgc3RhYmxlIGludGVyZmFjZXMgLSBhdCBsZWFzdCBvbiB0aGUgd2lyZSAtIG9yIGF0IGxlYXN0
IGVuY291cmFnaW5nIHRoZW0gdG8gZGVmaW5lIHByb3RvY29scyBzbyB0aGF0IHRoZXkgYXJlIGNs
ZWFubHkgZXh0ZW5zaWJsZSwgYW5kIGRlZmluaW5nIGEgYmFzZWxpbmUgZm9yIGludGVyb3BlcmFi
aWxpdHkgZXZlbiBhcyB0aGV5IGV4dGVuZCBwcm90b2NvbHMgdG8gYWNjb21tb2RhdGUgbmV3IGZl
YXR1cmVzLiAgIEFuZCBhY3R1YWxseSBpdCBtaWdodCBiZSB0aGUgY2FzZSB0aGF0IElFVEYgY291
bGQgbGVhcm4gc29tZXRoaW5nIGFib3V0IHByb3RvY29sIGV4dGVuc2liaWxpdHkgZnJvbSBwZW9w
bGUgd2hvIGhhdmUgc3RydWdnbGVkIHRvIGFjY29tbW9kYXRlIHJhcGlkIGV2b2x1dGlvbiBvZiB0
aGVpciBzb2Z0d2FyZS4NCiAgICANCiAgICBLZWl0aA0KICAgIA0KICAgIA0KDQo=


From nobody Sun Nov  5 03:00:06 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 8C16613FC5B; Sun,  5 Nov 2017 02:59:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 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, MISSING_MIMEOLE=1.899, SPF_PASS=-0.001, URIBL_BLOCKED=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 3bFTx2iaRRim; Sun,  5 Nov 2017 02:59:51 -0800 (PST)
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 2043613FC5C; Sun,  5 Nov 2017 02:59:51 -0800 (PST)
Received: from seraph (69-172-65-098.static.imsbiz.com [69.172.65.98]) by gondrom.org (Postfix) with ESMTPSA id 5B5356536D; Sun,  5 Nov 2017 11:59:44 +0100 (CET)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=SJlhOi32Hqzt59DDVyuZSRALh/K8Qn47f+cN0Zq9JcFuoa53K3y7Aen6LPGI3Yx2HirwdkwQ8+6QqZzodiSQCJn8obApiP9BQFIdydgTDZqSfD9zfOjALEfk0Xld4+wssYtIfssgXLH6j1uJVjvIgRCVz0/Qd0gpfdIQYLZR09w=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:X-Mailer:Thread-Index:Content-Language:Importance;
From: "Tobias Gondrom" <tobias.gondrom@gondrom.org>
To: "'IETF Chair'" <chair@ietf.org>, "'IETF Discussion'" <ietf@ietf.org>, "'IETF Announcement List'" <ietf-announce@ietf.org>
References: <C027BEF6-DC85-492B-B1EB-064653F6954F@ietf.org>
In-Reply-To: <C027BEF6-DC85-492B-B1EB-064653F6954F@ietf.org>
Subject: RE: Call for nominations for the IAOC appointment by the IESG
Date: Sun, 5 Nov 2017 18:59:43 +0800
Message-ID: <09de01d35625$304abf20$90e03d60$@gondrom.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_09DF_01D35668.3E718190"
X-Priority: 5 (Lowest)
X-MSMail-Priority: Low
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJZxoIbxnGO08uYqOTJEMtL5xalnqH4uAKA
Content-Language: en-us
Importance: Low
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vvoGPaVYU9zYFxq6w6ioyjffn9A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Nov 2017 10:59:54 -0000

This is a multipart message in MIME format.

------=_NextPart_000_09DF_01D35668.3E718190
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Dear all,=20

=20

Following a good practice that candidates should not run for more than 2 =
terms, I do not intend to volunteer again for the IAOC.=20

=20

To all interested, I think the work on the IAOC is a very interesting =
and rewarding activity for our community.=20

And I like to highly encourage interested volunteers to come and help =
with your time and advise.=20

Over the last few years we went through interesting times with =
challenges from the IANA transition work, funding and new considerations =
for meeting location selections, to name just a few. Many things that =
matter to our community. It takes time, but it is important to help =
fulfill a smooth operation for our meetings and other administrative =
aspects of our community and the IETF Trust.=20

=20

On a personal note: I found the IAOC is a bit short of diversity when it =
comes to members from non-Western regions and especially as Asia is a =
region of more and more relevance, I like to encourage candidates from =
Asia to consider volunteering.=20

=20

With best wishes and see you all soon in Singapore,=20

=20

Tobias

=20

=20

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of IETF Chair
Sent: Tuesday, October 24, 2017 2:24 AM
To: IETF Discussion <ietf@ietf.org>; IETF Announcement List =
<ietf-announce@ietf.org>
Subject: Call for nominations for the IAOC appointment by the IESG

=20

Tobias Gondrom is the IAOC member who was last appointed by the IESG. =
His two-year term is up in March. The IESG is starting the process to =
fill this seat in March 2018, with the term ending in March 2020.

=20

The IESG is responsible for filling one seat every other year. BCP 101 =
says:

=20

The IAOC shall consist of eight voting members who shall be selected as =
follows:

=20

o Two members appointed by the IETF Nominations Committee (NomCom);

=20

o One member appointed by the IESG;

=20

o One member appointed by the IAB;

=20

o One member appointed by the ISOC Board of Trustees;

=20

o The IETF Chair (ex officio);

=20

o The IAB Chair (ex officio);

=20

o The ISOC President/CEO (ex officio).

=20

Current IAOC members can be found at =
=E2=80=8Bhttp://iaoc.ietf.org/members.html

=20

=20

DESIRABLE QUALIFICATIONS AND SELECTION CRITERIA

=20

Candidates for the IAOC position should have a demonstrable involvement =
in the IETF, knowledge of contracts and financial procedures, and some =
awareness of the administrative support needs of the IETF. Candidates =
are also expected to understand the respective roles and =
responsibilities of the IETF and ISOC in IASA, and be able to articulate =
these roles within the IETF community.

=20

Candidates must be able to exercise all the duties of an IAOC member, =
including fiduciary responsibilities, setting of policies, oversight of =
the administrative operations of the IETF, representing the interests of =
the IETF, and participating in IAOC meetings and activities. More =
information about expertise and duties for a member of the IAOC =
(including time commitments) can be found at =
=E2=80=8Bhttps://datatracker.ietf.org/nomcom/2017/expertise/ under the =
"IAOC member" tab

=20

Candidates must be able to serve as a Trustee for the IETF Trust.

=20

Although the IESG selects this member of the IAOC, the selected member =
does not directly represent the IESG. The IESG-selected member is =
accountable directly to the IETF community.

=20

=20

NOMINATIONS AND ELIGIBILITY

=20

The IESG is making a public call for nominations. Self-nominations are =
permitted. All IETF participants, including working group chairs, IETF =
NomCom members, IAB members, and IESG members are eligible for =
nomination. Of course, IESG members who accept nomination will recuse =
themselves from selection discussions. Persons who are under =
consideration by the Nomcom in the 2017-2018 cycle for the open IAOC =
position are also permitted to apply. Please send nominations to iesg at =
ietf.org <http://ietf.org> . Please include the following with each =
nomination:

=20

o Name

=20

o Contact information

=20

o Candidate background and qualifications

=20

=20

SELECTION

=20

The IESG will publish the list of nominated persons prior to making a =
decision, allowing time for the community to provide any relevant =
comments to the IESG.

=20

The IESG will review the nomination material, any comments provided by =
the community, and make a selection.

=20

=20

CARE OF PERSONAL INFORMATION

=20

The following procedures will be used in managing candidates' personal =
information:

=20

o The list of candidate names will be published at the close of the =
nominations period. A candidate that refuses the nomination will not be =
included on the list.

=20

o Except as noted above, all information provided to the IESG during =
this process will be kept as confidential to the IESG.

=20

=20

TIMEFRAME

=20

The nominations period will open on October 23, 2017 and close on =
November 17, 2017.

=20

The list of candidates will be posted shortly after the nominations =
close, and the community will have two weeks to provide comments on the =
candidates to the IESG.

=20

The IESG will make a selection on the IESG telechat following the =
comment period.

=20

=20

On behalf of the IESG,

=20

Alissa Cooper

IESG Chair

=20

=20


------=_NextPart_000_09DF_01D35668.3E718190
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size: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=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>Dear all, =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Following a good practice that candidates should not =
run for more than 2 terms, I do not intend to volunteer again for the =
IAOC. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>To all interested, I think the work on the IAOC is a =
very interesting and rewarding activity for our community. =
<o:p></o:p></p><p class=3DMsoNormal>And I like to highly encourage =
interested volunteers to come and help with your time and advise. =
<o:p></o:p></p><p class=3DMsoNormal>Over the last few years we went =
through interesting times with challenges from the IANA transition work, =
funding and new considerations for meeting location selections, to name =
just a few. Many things that matter to our community. It takes time, but =
it is important to help fulfill a smooth operation for our meetings and =
other administrative aspects of our community and the IETF Trust. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>On a personal note: I found the IAOC is a bit short of =
diversity when it comes to members from non-Western regions and =
especially as Asia is a region of more and more relevance, I like to =
encourage candidates from Asia to consider volunteering. =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>With best wishes and see you all soon in Singapore, =
<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Tobias<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><a =
name=3D"_MailEndCompose"><o:p>&nbsp;</o:p></a></p><span =
style=3D'mso-bookmark:_MailEndCompose'></span><div><div =
style=3D'border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b>From:</b> ietf =
[mailto:ietf-bounces@ietf.org] <b>On Behalf Of </b>IETF =
Chair<br><b>Sent:</b> Tuesday, October 24, 2017 2:24 AM<br><b>To:</b> =
IETF Discussion &lt;ietf@ietf.org&gt;; IETF Announcement List =
&lt;ietf-announce@ietf.org&gt;<br><b>Subject:</b> Call for nominations =
for the IAOC appointment by the IESG<o:p></o:p></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Tobias =
Gondrom is the IAOC member who was last appointed by the IESG. His =
two-year term is up in March. The IESG is starting the process to fill =
this seat in March 2018, with the term ending in March =
2020.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The IESG is responsible for filling one seat every =
other year. BCP 101 says:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The IAOC shall consist of eight voting members who =
shall be selected as follows:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
Two members appointed by the IETF Nominations Committee =
(NomCom);<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
One member appointed by the IESG;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
One member appointed by the IAB;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
One member appointed by the ISOC Board of =
Trustees;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
The IETF Chair (ex officio);<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
The IAB Chair (ex officio);<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
The ISOC President/CEO (ex officio).<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Current IAOC members can be found at =E2=80=8B<a =
href=3D"http://iaoc.ietf.org/members.html">http://iaoc.ietf.org/members.h=
tml</a><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>DESIRABLE QUALIFICATIONS AND SELECTION =
CRITERIA<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Candidates for the IAOC position should have a =
demonstrable involvement in the IETF, knowledge of contracts and =
financial procedures, and some awareness of the administrative support =
needs of the IETF. Candidates are also expected to understand the =
respective roles and responsibilities of the IETF and ISOC in IASA, and =
be able to articulate these roles within the IETF =
community.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Candidates must be able to exercise all the duties of =
an IAOC member, including fiduciary responsibilities, setting of =
policies, oversight of the administrative operations of the IETF, =
representing the interests of the IETF, and participating in IAOC =
meetings and activities. More information about expertise and duties for =
a member of the IAOC (including time commitments) can be found at =
=E2=80=8B<a =
href=3D"https://datatracker.ietf.org/nomcom/2017/expertise/">https://data=
tracker.ietf.org/nomcom/2017/expertise/</a> under the &quot;IAOC =
member&quot; tab<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Candidates must be able to serve as a Trustee for the =
IETF Trust.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Although the IESG selects this member of the IAOC, the =
selected member does not directly represent the IESG. The IESG-selected =
member is accountable directly to the IETF =
community.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>NOMINATIONS AND =
ELIGIBILITY<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The IESG is making a public call for nominations. =
Self-nominations are permitted. All IETF participants, including working =
group chairs, IETF NomCom members, IAB members, and IESG members are =
eligible for nomination. Of course, IESG members who accept nomination =
will recuse themselves from selection discussions. Persons who are under =
consideration by the Nomcom in the 2017-2018 cycle for the open IAOC =
position are also permitted to apply. Please send nominations to iesg at =
<a href=3D"http://ietf.org">ietf.org</a>. Please include the following =
with each nomination:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
Name<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
Contact information<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
Candidate background and qualifications<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>SELECTION<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The IESG will publish the list of nominated persons =
prior to making a decision, allowing time for the community to provide =
any relevant comments to the IESG.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The IESG will review the nomination material, any =
comments provided by the community, and make a =
selection.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>CARE OF PERSONAL =
INFORMATION<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The following procedures will be used in managing =
candidates' personal information:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
The list of candidate names will be published at the close of the =
nominations period. A candidate that refuses the nomination will not be =
included on the list.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>o =
Except as noted above, all information provided to the IESG during this =
process will be kept as confidential to the =
IESG.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>TIMEFRAME<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The nominations period will open on October 23, 2017 =
and close on November 17, 2017.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The list of candidates will be posted shortly after =
the nominations close, and the community will have two weeks to provide =
comments on the candidates to the IESG.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>The IESG will make a selection on the IESG telechat =
following the comment period.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>On behalf of the IESG,<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Alissa Cooper<o:p></o:p></p></div><div><p =
class=3DMsoNormal>IESG Chair<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------=_NextPart_000_09DF_01D35668.3E718190--


From nobody Sun Nov  5 15:17:48 2017
Return-Path: <ramkri123@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 0E0BA13FD0D for <ietf@ietfa.amsl.com>; Sun,  5 Nov 2017 15:17:47 -0800 (PST)
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 Tq6slXX6SPt5 for <ietf@ietfa.amsl.com>; Sun,  5 Nov 2017 15:17:45 -0800 (PST)
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 277A513FBC5 for <ietf@ietf.org>; Sun,  5 Nov 2017 15:17:45 -0800 (PST)
Received: by mail-it0-x232.google.com with SMTP id 72so3137931itk.3 for <ietf@ietf.org>; Sun, 05 Nov 2017 15:17:45 -0800 (PST)
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=jywBW6FmssOV2lLsQQ1On1071nrknVqHXvTyWOF3AzQ=; b=H+SHX83qQ2/VCucUv6X0K9kCwmMc1sZ10639+vbw1Y3pa/O3WLUkV/KxjUYohln6B/ ivgoBjcbEN48frS63OQY6XrsbbHezi4/xSeuJIAZM2QJOPbeOIfjLAUXd8fVKpsMQExp PpzFnq2IItoNoI/oE9zkKrxwl1fO6P+Zwx/UxsQFRa923MRL++pMydKTFHY/t0tOBTIJ 0uP+uLoPrKW8uhO/qSLlWxkdkbrt3JTzHu0BJUg55sq9XkpXBtXAa7kKVGt6kwba2UJc f2VSQQtxUrjtiBwbHgzbM5M9YdIwX21VMEl1FfhP3+e4AyzU4ZzYFThmXG3aTwjjobYp 6U6Q==
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=jywBW6FmssOV2lLsQQ1On1071nrknVqHXvTyWOF3AzQ=; b=uOBkeYWo9CXhnrz7nhf214HfUQ1/v/QOFs/5UoC20W4NLuda2xQf4EIvRrdNZ2FwTM 1twqq/ugOgty/nlSD3ZVkn1Q8kL7lSifRFOxxpPEvv1iwNLGRrfTQjckNHBa9gtK5pWh HeHZxlzNJyvpvDHx2CcX27fXZskckxEcdjgI1F9PasSZBIq2Al0QQE3GWVQ9t5KfvH2K fhtEuMdB6k9i/SH1cMID756lgWq7yk9t2zaxnSvfdnlZWEwBUw+quJKZnz3o0A9T1jbz 3BVwKMI/EXMmNUBTeXYk9Celx2f9RcN+LJJOhH+DJYVgW3Nhr5BJ+8W3alvXF87Nmfih eEag==
X-Gm-Message-State: AJaThX5uVf7X7DF2wMMGN6z+pD0lQhIvFOap1FzPqZg+mKWtpxo/Gi6T 3D8yECvMPzKae6HLF+kBCJPwx58Fr2JjqdnKKn8=
X-Google-Smtp-Source: ABhQp+RYGzMrL+rW/QAITQ6Hl9Vv9koXACYfkyJc/0ZRM/EbNtUH0s1W4FG/0uC69LSdO4dMT2fF35pKk9EhK/9/XQg=
X-Received: by 10.36.17.193 with SMTP id 184mr7281390itf.68.1509923864396; Sun, 05 Nov 2017 15:17:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.141.85 with HTTP; Sun, 5 Nov 2017 15:17:43 -0800 (PST)
In-Reply-To: <56CEC7A6-2F04-4913-A3CE-15BC1B846BE2@cisco.com>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <E6ED7F15-8855-45B6-A42E-707E32966CFA@network-heretics.com> <56CEC7A6-2F04-4913-A3CE-15BC1B846BE2@cisco.com>
From: Ramki Krishnan <ramkri123@gmail.com>
Date: Sun, 5 Nov 2017 15:17:43 -0800
Message-ID: <CAKOuegDhoi4dPgpU96srO4DVgjA9yro478fJhjZ95OYeXwbHsA@mail.gmail.com>
Subject: Re: letting IETF build on top of Open Source technology
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
Cc: Keith Moore <moore@network-heretics.com>, Alia Atlas <akatlas@gmail.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143ea36934656055d448b2f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ws3aOe3KhQOu0zgtzay8vSTmLwc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Nov 2017 23:17:47 -0000

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

I would agree with Charles, this is what we have in mind for a large open
source project such as ONAP.

Thanks,
Ramki

On Sat, Nov 4, 2017 at 7:18 PM, Charles Eckel (eckelcu) <eckelcu@cisco.com>
wrote:

> This is true in some cases, but not in others. There has been and
> continues to be a big push in open source software and in software in
> general to create applications that are compose of many small pieces that
> interact with each other through well defined interfaces. This leads to
> more modular software and better code/component reuse. This practice
> results in code that is more appropriate as a normative reference. I would
> expect the normative reference to be to a specific version or release of
> the software and its corresponding API(s). Those APIs could change with
> future versions of the software, but as with standards, we tend to try
> pretty hard to avoid non-backward compatible APIs changes after the
> software has reached a state of maturity that others on building on top of
> it and relying on those APIs.
>
> Cheers,
> Charles
>
> -----Original Message-----
> From: ietf <ietf-bounces@ietf.org> on behalf of Keith Moore <
> moore@network-heretics.com>
> Date: Wednesday, November 1, 2017 at 4:10 PM
> To: Alia Atlas <akatlas@gmail.com>
> Cc: "ietf@ietf.org" <ietf@ietf.org>
> Subject: Re: letting IETF build on top of Open Source technology
>
>     It seems to me that a fundamental problem with referencing Open Source
> software is that in much (not all) of the Open Source world, rapid
> innovation and evolution is valued more than stable protocol interfaces.
>  There is a tendency to rely on users to frequently update their software,
> which is seen as giving developers freedom to change interfaces on
> relatively short notice.
>
>     Of course that's an oversimplification.  In practice good open source
> developers are careful to avoid abrupt changes to interfaces; instead they
> create new interfaces and deprecate old ones.   But since one of the
> oft-touted benefits of Open Source is to allow software systems to evolve
> rapidly, this sometimes also results in new protocol features being
> deployed rapidly to the point that it impairs interoperability between new
> and old implementations.   This causes a great many problems other than
> just protocol interoperability failures, including dependency hell.
>
>     So part of the effort to improve cooperation between IETF and Open
> Source developers - who tend to have similar motivations even if their
> methods differ - might be in convincing them that they would benefit from
> more stable interfaces - at least on the wire - or at least encouraging
> them to define protocols so that they are cleanly extensible, and defining
> a baseline for interoperability even as they extend protocols to
> accommodate new features.   And actually it might be the case that IETF
> could learn something about protocol extensibility from people who have
> struggled to accommodate rapid evolution of their software.
>
>     Keith
>
>
>
>


-- 
Thanks,
Ramki

--001a1143ea36934656055d448b2f
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:courier =
new,monospace">I would agree with Charles, this is what we have in mind for=
 a large open source project such as ONAP.</div><div class=3D"gmail_default=
" style=3D"font-family:courier new,monospace"><br></div><div class=3D"gmail=
_default" style=3D"font-family:courier new,monospace">Thanks,</div><div cla=
ss=3D"gmail_default" style=3D"font-family:courier new,monospace">Ramki</div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sat, Nov 4, 2=
017 at 7:18 PM, Charles Eckel (eckelcu) <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:eckelcu@cisco.com" target=3D"_blank">eckelcu@cisco.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">This is true in some cases, but no=
t in others. There has been and continues to be a big push in open source s=
oftware and in software in general to create applications that are compose =
of many small pieces that interact with each other through well defined int=
erfaces. This leads to more modular software and better code/component reus=
e. This practice results in code that is more appropriate as a normative re=
ference. I would expect the normative reference to be to a specific version=
 or release of the software and its corresponding API(s). Those APIs could =
change with future versions of the software, but as with standards, we tend=
 to try pretty hard to avoid non-backward compatible APIs changes after the=
 software has reached a state of maturity that others on building on top of=
 it and relying on those APIs.<br>
<br>
Cheers,<br>
Charles<br>
<br>
-----Original Message-----<br>
From: ietf &lt;<a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">i=
etf-bounces@ietf.org</a>&gt; on behalf of Keith Moore &lt;<a href=3D"mailto=
:moore@network-heretics.com" target=3D"_blank">moore@network-heretics.com</=
a>&gt;<br>
Date: Wednesday, November 1, 2017 at 4:10 PM<br>
To: Alia Atlas &lt;<a href=3D"mailto:akatlas@gmail.com" target=3D"_blank">a=
katlas@gmail.com</a>&gt;<br>
Cc: &quot;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org<=
/a>&quot; &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.=
org</a>&gt;<br>
Subject: Re: letting IETF build on top of Open Source technology<br>
<br>
=C2=A0 =C2=A0 It seems to me that a fundamental problem with referencing Op=
en Source software is that in much (not all) of the Open Source world, rapi=
d innovation and evolution is valued more than stable protocol interfaces.=
=C2=A0 =C2=A0There is a tendency to rely on users to frequently update thei=
r software, which is seen as giving developers freedom to change interfaces=
 on relatively short notice.<br>
<br>
=C2=A0 =C2=A0 Of course that&#39;s an oversimplification.=C2=A0 In practice=
 good open source developers are careful to avoid abrupt changes to interfa=
ces; instead they create new interfaces and deprecate old ones.=C2=A0 =C2=
=A0But since one of the oft-touted benefits of Open Source is to allow soft=
ware systems to evolve rapidly, this sometimes also results in new protocol=
 features being deployed rapidly to the point that it impairs interoperabil=
ity between new and old implementations.=C2=A0 =C2=A0This causes a great ma=
ny problems other than just protocol interoperability failures, including d=
ependency hell.<br>
<br>
=C2=A0 =C2=A0 So part of the effort to improve cooperation between IETF and=
 Open Source developers - who tend to have similar motivations even if thei=
r methods differ - might be in convincing them that they would benefit from=
 more stable interfaces - at least on the wire - or at least encouraging th=
em to define protocols so that they are cleanly extensible, and defining a =
baseline for interoperability even as they extend protocols to accommodate =
new features.=C2=A0 =C2=A0And actually it might be the case that IETF could=
 learn something about protocol extensibility from people who have struggle=
d to accommodate rapid evolution of their software.<br>
<br>
=C2=A0 =C2=A0 Keith<br>
<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"m_-2172997933281261214gmail_signature" data-smartmail=3D"gmail_signatur=
e"><div dir=3D"ltr">Thanks,=C2=A0<div>Ramki<br></div></div></div>
</div></div>

--001a1143ea36934656055d448b2f--


From nobody Sun Nov  5 17:43:54 2017
Return-Path: <mfidelman@meetinghouse.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 7A41C13FD2A for <ietf@ietfa.amsl.com>; Sun,  5 Nov 2017 17:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M6-RgbvyzArb for <ietf@ietfa.amsl.com>; Sun,  5 Nov 2017 17:43:52 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 021EA13FC02 for <ietf@ietf.org>; Sun,  5 Nov 2017 17:43:51 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 25830CC495; Sun,  5 Nov 2017 20:43:51 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id xTLKTRsY7ISY; Sun,  5 Nov 2017 20:43:50 -0500 (EST)
Received: from Miless-MacBook-Pro.local (71-223-225-69.phnx.qwest.net [71.223.225.69]) by server1.neighborhoods.net (Postfix) with ESMTPSA id B31C3CC494; Sun,  5 Nov 2017 20:43:49 -0500 (EST)
Subject: Re: letting IETF build on top of Open Source technology
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <CAG4d1rev-e2_CbPqjNjwD_wgNL=rS_BJ6KL=0f5VZJe=t=k9yg@mail.gmail.com> <6.2.5.6.2.20171101132245.10d04f48@elandnews.com> <CAG4d1rc2k4A53DXJW0NSZbrjSBQoK6uc-u1G2PwEJfoM2w5i-A@mail.gmail.com> <CAMm+LwjLySeeNigm-nTbBjFkQ+7=UqjXAB4qk4Kwau_C9Q_3Tw@mail.gmail.com> <a72fab79-1c5b-07a2-b21d-efe4491d9339@meetinghouse.net> <CAMm+Lwi-_sECr0Ls6fUk6VJTGovS4_zk-BO8_2gHWHS8P8+xbQ@mail.gmail.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <df50fa83-0fd6-3605-723e-2c76c4a1ec09@meetinghouse.net>
Date: Sun, 5 Nov 2017 18:43:48 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAMm+Lwi-_sECr0Ls6fUk6VJTGovS4_zk-BO8_2gHWHS8P8+xbQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/chJ97MPJZIqJkxjiPxnAPj_UDBY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 01:43:53 -0000

Meant to reply earlier - on a trip...

On 11/3/17 5:07 AM, Phillip Hallam-Baker wrote:

> On Thu, Nov 2, 2017 at 1:01 PM, Miles Fidelman
> <mfidelman@meetinghouse.net> wrote:
>> On 11/1/17 10:35 PM, Phillip Hallam-Baker wrote:
>>
>>> My specifications are my code.
>>>
>>> If you look at any of the protocol specifications for the Mesh, you
>>> will find a reference section in the back that is generated directly
>>> from the schema and examples taken from running code generated from
>>> the same schema. And the running code used to generate the examples is
>>> the same as the reference code.
>>>
>> That's a little bit disingenuous, isn't it - particularly since you've
>> written quite a bit of documentation beyond your code.
> I did not say my code is my specification. Which is what a lot of
> people have done in the past.
>
> I develop the documentation and the code at the same time. Of course
> there are parts of the documentation that are not code, the user
> guide, requirements, etc. But every specification has normative and
> non-normative sections.

More precisely, can you elaborate just a tad on HOW your "specifications 
are your code?"

I've taken a look at some of the documentation you've pointed at, but 
have yet to find any that have "a reference section in the back that is 
generated directly from the schema and examples taken from running code 
generated from the same schema" - can you perhaps give a specific reference?

And can you say just a tad more about the representation of the schema, 
your tool chain, and process?  (Without taking a really deep dive, what 
I surmise is that the Goedel tools can ingest ASN and generate code - am 
I reading that correctly?)


>
>> Beyond that, the point of a specification is to DRIVE implementation &
>> testing of multiple, interoperable implementations.  A reference
>> implementation is one thing, but as soon as one specific piece of code
>> (warts & all) becomes the "spec" - it's not really a specification anymore.
> Reference code is not necessarily the same as production. Production
> code should be conservative in what it sends and liberal in what it
> accepts. Reference code should be the other way round. It should
> complain when the sender fails to abide by the strict specification.

Now that is a very good point - well worth remembering.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Sun Nov  5 22:03:56 2017
Return-Path: <cbowers@juniper.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 308B713FBBC; Sun,  5 Nov 2017 22:03:53 -0800 (PST)
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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZEcKf1dtazP2; Sun,  5 Nov 2017 22:03:51 -0800 (PST)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0091.outbound.protection.outlook.com [104.47.40.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 EDADF13FB24; Sun,  5 Nov 2017 22:03:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=wQ5UkK14pt06dhYDFkkguJkRssuDkg8rk7WUY58lyv0=; b=ajV6kYyWRT84z133NJpwlEtCUmAG2a2Ke/X5tAprFoTRlYqqNQqmEH2KivRtl9LHU2dxEJjQwSruckgF18eDAfJtvf0AuFDIF6OymCBjxMwdzgZYnciGewb+m+4Cphp7pGc/tFQzdLfpyDxV1hwX8UlDaTImeoRH/xqgbxDMAnM=
Received: from CY4PR05MB2823.namprd05.prod.outlook.com (10.169.182.145) by CY4PR05MB2821.namprd05.prod.outlook.com (10.169.182.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.218.6; Mon, 6 Nov 2017 06:03:45 +0000
Received: from CY4PR05MB2823.namprd05.prod.outlook.com ([10.169.182.145]) by CY4PR05MB2823.namprd05.prod.outlook.com ([10.169.182.145]) with mapi id 15.20.0218.005; Mon, 6 Nov 2017 06:03:45 +0000
From: Chris Bowers <cbowers@juniper.net>
To: Peter Yee <peter@akayla.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-mpls-ldp-mrt.all@ietf.org" <draft-ietf-mpls-ldp-mrt.all@ietf.org>
Subject: RE: Genart last call review of draft-ietf-mpls-ldp-mrt-06
Thread-Topic: Genart last call review of draft-ietf-mpls-ldp-mrt-06
Thread-Index: AQHTI4jhh6E6s3q4rkO4/c4xKksDIaMHKUag
Date: Mon, 6 Nov 2017 06:03:44 +0000
Message-ID: <CY4PR05MB28238637E28ACC68855DBF98A9500@CY4PR05MB2823.namprd05.prod.outlook.com>
References: <150431489114.6649.9807443646105756121@ietfa.amsl.com>
In-Reply-To: <150431489114.6649.9807443646105756121@ietfa.amsl.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=cbowers@juniper.net; 
x-originating-ip: [66.129.239.12]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR05MB2821; 6:F1V2Z3BqDIkbxuxUlWh/eLxwQys+XrCWRQMACGMgjtB4MdYwbtaRJkkFeJLtNc9llolCl3Rdt1ntY4ptOyABB1WSOE/wCeIM0cOx3tTJ+B2CBQ1VofcZea5/8s2uyo4pkzBe4qSarARyZ2uGi/AbLJduc6JAKXWsjpE/IBCRzfSWQOP+kJv4McKQzVPnPOiwj3Ztc+ZRC8wH/zwL9VChAka7ZCePJlCSqiCqQxt7lxqy0j959uUAEd5TWNUyiExo2rnFIem7LjQGaG7Laa52rQv5hTpAnoNYAYmKuI5rh7zYzhsjRW9qdADqDNyow0gCg3MRvDq/xecX3Pp93XS81hrPMo4QIH5C6HwSlibBzs8=; 5:p8lg/XhijgPuAI93FtyQn3y0HMsbBRzOMUIX8WavQ9sClubmkdkZoT5ScU4sRPTJq4KNywGf9v2wKHcYhy6prfLDzJNuT5B2YcdFh/JU2FVQUe577YH4uNr0WMdlB6YsU0+qZVyQG6ctaHqvcW4yx/9d+DBKcI59+fDfurD5HJE=; 24:0jFB1NOVVSiDQOS4KdNDkcPA3moCa9QxMX79GdJOVdaO0StSFdU36WE3fj14RMuVmao3DcXCgoz1ZP5dViUYi6LdlK94AnaAFOGP7GByUfo=; 7:dHU7fBjHueC6ZcYs29F2LPljDj7eZPO9zboeh/oDq7uI++hFmiZxQf9rlBhzfzFyVSE69mz8CMp05RAJkROwPXCkkyvbUHLAk8seu7DeysrXds1audVnXsCsY1InUMUtl/wqwc7agom5ppThQty8dPGYTGaJlznYuSk/K1cx1TwhKyjb9ldsLtOslKokehPIXmjQpvm6kxZ82uBQWF8akUnK1x59C7B8lU5Bq4Ttnp9MwGKEwo3DYxXkZooEo1CG
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 8cbe261b-b0c6-4a93-887c-08d524dc2386
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:CY4PR05MB2821; 
x-ms-traffictypediagnostic: CY4PR05MB2821:
x-exchange-antispam-report-test: UriScan:(166708455590820);
x-microsoft-antispam-prvs: <CY4PR05MB28219C82073DC70106B17CD2A9500@CY4PR05MB2821.namprd05.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231021)(100000703101)(100105400095)(3002001)(6055026)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR05MB2821; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR05MB2821; 
x-forefront-prvs: 048396AFA0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(376002)(39860400002)(346002)(13464003)(199003)(189002)(377424004)(3280700002)(3660700001)(6436002)(101416001)(2501003)(5660300001)(229853002)(50986999)(7696004)(106356001)(33656002)(6506006)(54356999)(77096006)(76176999)(2906002)(105586002)(86362001)(189998001)(6246003)(53546010)(110136005)(54906003)(66066001)(230783001)(575784001)(316002)(68736007)(478600001)(8676002)(81156014)(7736002)(6116002)(97736004)(305945005)(102836003)(3846002)(966005)(25786009)(2900100001)(14454004)(81166006)(8936002)(53936002)(2950100002)(4326008)(9686003)(99286004)(55016002)(6306002)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR05MB2821; H:CY4PR05MB2823.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: 8cbe261b-b0c6-4a93-887c-08d524dc2386
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Nov 2017 06:03:44.9280 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR05MB2821
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aH16yI83aY7lprcwKZHkDGHcYh0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 06:03:53 -0000

VGhhbmtzLiBUaGlzIGZlZWRiYWNrIGlzIGFkZHJlc3NlZCBpbiB0aGUgZm9sbG93aW5nIGNvbW1p
dCAodW5sZXNzIHRoZXkgd2VyZSBmaXhlZCBiYXNlZCBvbiBvdGhlciBjb21tZW50cy4pICANCg0K
aHR0cHM6Ly9naXRodWIuY29tL2Nib3dlcnMvZHJhZnQtaWV0Zi1tcGxzLWxkcC1tcnQvY29tbWl0
LzExZWI3ZWUyYzBjNzg1M2Q1NzZhM2I0NjE2NzRiNWEwMGRmY2QxY2MNCg0KU2VlIHJlc3BvbnNl
cyB0byBmZWVkYmFjayBiZWxvdyB3aXRoIFtDQl0uDQoNCkNocmlzDQoNCi0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQpGcm9tOiBQZXRlciBZZWUgW21haWx0bzpwZXRlckBha2F5bGEuY29tXSAN
ClNlbnQ6IEZyaWRheSwgU2VwdGVtYmVyIDEsIDIwMTcgODoxNSBQTQ0KVG86IGdlbi1hcnRAaWV0
Zi5vcmcNCkNjOiBtcGxzQGlldGYub3JnOyBpZXRmQGlldGYub3JnOyBkcmFmdC1pZXRmLW1wbHMt
bGRwLW1ydC5hbGxAaWV0Zi5vcmcNClN1YmplY3Q6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9m
IGRyYWZ0LWlldGYtbXBscy1sZHAtbXJ0LTA2DQoNClJldmlld2VyOiBQZXRlciBZZWUNClJldmll
dyByZXN1bHQ6IFJlYWR5IHdpdGggSXNzdWVzDQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQg
cmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0gKEdl
bi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieSB0aGUg
SUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVz
dCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQoNCkZvciBtb3JlIGluZm9ybWF0
aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCg0KPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFj
L2dlbi93aWtpL0dlbkFydGZhcT4uDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLW1wbHMtbGRwLW1y
dC0wNg0KUmV2aWV3ZXI6IFBldGVyIFllZQ0KUmV2aWV3IERhdGU6IDIwMTctMDktMDENCklFVEYg
TEMgRW5kIERhdGU6IDIwMTctMDktMDENCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wOS0xNA0K
DQpTdW1tYXJ5OiAgVGhlIGRyYWZ0IGlzIHJlYWR5IGZvciBwdWJsaWNhdGlvbiBhZnRlciBjb3Jy
ZWN0aW5nIHNvbWUgbWlub3IgaXNzdWVzLg0KDQpNYWpvciBpc3N1ZXM6ICBOb25lDQoNCk1pbm9y
IGlzc3VlczoNCg0KUGFnZSAzLCBzZWN0aW9uIDMsIElCUiBkZWZpbml0aW9uOiB0aGUgZGVmaW5p
dGlvbiBnaXZlIGhlcmUgYXBwZWFycyB0byBiZSBhIGR1cGxpY2F0ZSBvZiB0aGUgb25lIGdpdmVu
IGZvciBJTi4gIENvcHkgdGhlIGNvcnJlY3QgZGVmaW5pdGlvbiBmcm9tIFJGQyA3ODEyIGluc3Rl
YWQuDQpbQ0JdIGNvcnJlY3RlZCBpbiBwcmV2aW91cyBjb21taXQNCg0KTml0cy9lZGl0b3JpYWwg
Y29tbWVudHM6DQoNClBhZ2UgMywgc2VjdGlvbiAxLCAybmQgcGFyYWdyYXBoLCAxc3Qgc2VudGVu
Y2U6IGFwcGVuZCBhIGNvbW1hIGFmdGVyICJlLmcuIi4NCg0KW0NCXSBjb3JyZWN0ZWQNCg0KUGFn
ZSA4LCBzZWN0aW9uIDQuNC4sIDFzdCBwYXJhZ3JhcGgsIDJuZCBzZW50ZW5jZTogZGVsZXRlIGR1
cGxpY2F0ZSAib24iLg0KDQpbQ0JdIGNvcnJlY3RlZC4NCg0KUGFnZSA4LCBzZWN0aW9uIDQuNCwg
Mm5kIHBhcmFncmFwaCwgNHRoIHNlbnRlbmNlOiBjaGFuZ2UgY29tbWEgYWZ0ZXIgImNvbXB1dGF0
aW9ucyIgdG8gYSBwZXJpb2QuDQpbQ0JdIGNvcnJlY3RlZC4NCg0KUGFnZSA5LCBzZWN0aW9uIDUu
MS4xLCA0dGggcGFyYWdyYXBoLCAybmQgc2VudGVuY2U6IHRoZSBjb25zdHJ1Y3Rpb24gInJlZChi
bHVlKSIgaXMgdXNlZCB3aXRob3V0IGRlZmluaW5nIHdoYXQgaXQgbWVhbnMgZXhhY3RseS4gIEZy
b20gdGhlIGNvbnRleHQsIGl0IGlzbid0IHF1aXRlICJyZWQgb3IgYmx1ZSIuICBBbiBleHBsYW5h
dGlvbiBvZiB0aGUgbWVhbmluZyBvZiB0aGlzIGNvbnN0cnVjdGlvbiBzaG91bGQgYmUgZ2l2ZW4u
ICBJJ20gYXNzdW1pbmcgaXQgbWVhbnMgc29tZXRoaW5nIGxpa2UgdXNlICJyZWQiDQppbiB0aGUg
c2VudGVuY2UgaW4gYWxsIGNhc2VzIG9yIHVzZSB1c2UgImJsdWUiLCBidXQgZG9uJ3QgbWl4IHRo
ZW0uICBUaGVyZSdzIGFsc28gcmVkL2JsdWUgdXNlZCBsYXRlciBpbiB0aGUgZG9jdW1lbnQgd2hp
Y2ggbXVkZGllcyB0aGUgcG9pbnQuDQo9PT09PT0NCltDQl0gSSBhZGRlZCB0aGUgdGV4dCBiZWxv
dyBhdCB0aGUgZW5kIG9mIHRoZSB0ZXJtaW5vbG9neSBzZWN0aW9uLCBhbmQgSSBjb252ZXJ0ZWQg
dGhlIHVzYWdlIG9mIHJlZC9ibHVlIHRvIHJlZChibHVlKS4NCg0KPHQ+IFRoZXJlIGFyZSBzZXZl
cmFsIHBsYWNlcyBpbiB0aGlzIGRvY3VtZW50IHdoZXJlIHRoZSBjb25zdHJ1Y3Rpb24gDQoicmVk
KGJsdWUpIEZFQyIgaXMgdXNlZCB0byBjb3ZlciB0aGUgY2FzZSBvZiB0aGUgcmVkIEZFQyBhbmQg
dGhlIGNhc2Ugb2YgdGhlIA0KYmx1ZSBGRUMsIGluZGVwZW5kZW50bHkuIEFzIGFuIGV4YW1wbGUs
IGNvbnNpZGVyIHRoZSBzZW50ZW5jZSAiV2hlbiB0aGUgDQpBQlIgcmVxdWlyZXMgYmVzdC1hcmVh
IGJlaGF2aW9yIGZvciBhIHJlZChibHVlKSBGRUMsIGl0IE1VU1Qgd2l0aGRyYXcgDQphbnkgZXhp
c3RpbmcgbGFiZWwgbWFwcGluZ3MgYWR2ZXJ0aXNlbWVudHMgZm9yIHRoZSBjb3JyZXNwb25kaW5n
IHJhaW5ib3cgDQpGRUMgYW5kIGFkdmVydGlzZSBsYWJlbCBtYXBwaW5ncyBmb3IgdGhlIHJlZChi
bHVlKSBGRUMuIiBUaGlzIHNlbnRlbmNlIA0Kc2hvdWxkIGJlIHJlYWQgYXMgYXBwbHlpbmcgdG8g
cmVkIEZFQ3MuIFRoZW4gaXQgc2hvdWxkIGJlIHJlYWQgYXMgDQphcHBseWluZyB0byBibHVlIEZF
Q3MuIDwvdD4NCiA9PT09PT0NClBhZ2UgMTAsIDFzdCBmdWxsIHBhcmFncmFwaCwgMm5kIHNlbnRl
bmNlOiBjaGFuZ2UgImZvbGwiIHRvICJmb2xsb3dzOiIuDQpbQ0JdIGNvcnJlY3RlZCBpbiBwcmV2
aW91cyBjb21taXQNCg0KUGFnZSAxMSwgc2VjdGlvbiA1LjIuMiwgMm5kIHBhcmFncmFwaCwgMXN0
IHNlbnRlbmNlOiBkZWxldGUgdGhlIHBlcmlvZCBhZnRlciAiQS4xLjciLg0KW0NCXSBjb3JyZWN0
ZWQNCg0KUGFnZSAxMiwgMXN0IHBhcmFncmFwaCwgMXN0IHNlbnRlbmNlOiBjb25zaWRlciBkZWxl
dGluZyAiaG93Ii4NCltDQl0gY29ycmVjdGVkDQoNClBhZ2UgMTMsIDJuZCBwYXJhZ3JhcGggYWZ0
ZXIgbnVtYmVyZWQgbGlzdCwgMXN0IHNlbnRlbmNlOiBhcHBlbmQgInRvIiBhZnRlciAicmVzcGVj
dCIuDQpbQ0JdIGNvcnJlY3RlZA0KDQpTZWN0aW9uIHRpdGxlcyBmb3IgNS4yLCA1LjMsIGFuZCA3
OiBhcHBlbmQgYSBzcGFjZSBhZnRlciAiUkZDIiB0byBzZXBhcmF0ZSBpdCBmcm9tIHRoZSBudW1i
ZXIuICBUaGUgc3BhY2VsZXNzIGZvcm0gc2hvdWxkIG9ubHkgYmUgdXNlZCBmb3IgcmVmZXJlbmNl
cyBlbmNsb3NlZCBpbiBicmFja2V0cy4NCltDQl0gY29ycmVjdGVkDQo=


From nobody Mon Nov  6 00:14:26 2017
Return-Path: <gonzalo.camarillo@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 0A98113FB48 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 00:14:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 qKBR2oQLxcaF for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 00:14:23 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 B16A713FB34 for <ietf@ietf.org>; Mon,  6 Nov 2017 00:14:22 -0800 (PST)
X-AuditID: c1b4fb3a-dffff70000006897-42-5a0019dc4b87
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 6C.D8.26775.CD9100A5; Mon,  6 Nov 2017 09:14:20 +0100 (CET)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.39) with Microsoft SMTP Server (TLS) id 14.3.352.0; Mon, 6 Nov 2017 09:14:20 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=BYxGlK9XGDYPYFh6W6bLgzNHl8eX0aaOXT4uDRfZ7QI=; b=NM5PzaxTCYlwx3VYkzA2SCDHg75+3/JILMZt2OjT8fJW6q5LDec7Dh3C4GkPMIWOFI9qkq9QT++ThnImIvF2qLxACYD0ueIxv3WEIGFgl29cp0w6qy8EDs2vUcB1HhjYhqkVUnbIk64WMP5nfiRdlBuJINY1pGK9d5OUi5MfH/s=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
Received: from [192.168.1.7] (37.136.86.88) by DB3PR07MB0634.eurprd07.prod.outlook.com (2a01:111:e400:943c::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Mon, 6 Nov 2017 08:14:17 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Marc Petit-Huguenin <petithug@acm.org>, Alia Atlas <akatlas@gmail.com>
CC: Doug Royer <douglasroyer@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <8a8634e2-de7f-0a56-bca8-41914b9473d5@gmail.com> <CAG4d1rde91LcVi56DZ-Vchit5jiwPHNP5Mwgn+cOi=wQFmaz_g@mail.gmail.com> <a3c0a285-8cf9-28c4-41c7-cc776029c4d9@ericsson.com> <26185.1509118832@obiwan.sandelman.ca> <a09cad34-e7f7-d510-93ab-9114a8f19b1e@acm.org> <CAG4d1rfCKS+HWVWayk4ZjnuJcWQJwzGgxx2pwSBFLpXcGok=hw@mail.gmail.com> <17268669-48d6-4f70-d67a-5e642ae50b8e@acm.org> <CBF4104B-2DEF-4F88-AD9F-59996CB58735@cisco.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <d337f209-aa56-32dc-51b3-a8c19f2c29fe@ericsson.com>
Date: Mon, 6 Nov 2017 10:14:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CBF4104B-2DEF-4F88-AD9F-59996CB58735@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR0102CA0014.eurprd01.prod.exchangelabs.com (2603:10a6:7:14::27) To DB3PR07MB0634.eurprd07.prod.outlook.com (2a01:111:e400:943c::24)
X-MS-Office365-Filtering-Correlation-Id: 06ef8d78-6b63-4099-9071-08d524ee6094
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:DB3PR07MB0634; 
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0634; 3:FzytEo1E38AhYRZKDOaJIv6IFSftixnv1pkdpNpaeecP0abnzBZGilvQnOHSv3QQlLIXXfQ1Gog4q3hu+r0kz9+oTiVp5VdM+Dcgbdb4MqP4b2WfKPLntzLkfWSCyfgw8xOe1s2n4bILcTrGC8xtGoixAZqN0aBwVMvKfEhW0/fWbyxwMwnOgfzfllyr6M1qsz2XbipRLm9aP1MLqwS42KKAkRMgQixz5kYjv40qa6Ykx4oAQsfDwKWVvPK8gCvb; 25:jekHNLmi2wpp8O9RPSUjO3FFzcGVByIMpoj1xMEWWeQRCnowsb6zTrXrGr9WK++ppRIvsfNwUtVXI+Fz9dXqezKAhPpjnz+/b118xnnPZEe4fsUi9Ab5sj6RGaq7F6yf8l1Fn6meHnKS8Sm45KFxlhV5AZ/GBaGBnseWK8+iKpxTN5lsdODJj2sQbwdMu1VXkbD+hBYEzrA4kdy5ye2B4i4RYBy21IR06iOR6mKlVb2ScHFGTjSx/AQoYc0lCbgSOGRnsQjf1GJLI5k29vGm0pTpLJQeNyoE4OKISdrlwfHt1DYlE3iD2JUjvLUkS2rCMySWiwwdCrytE9b4f8MIUw==; 31:AwMTo8kTT8NVxl77y1I3hP6I/9YnHtBAyTLUt9Nfs1t4ljVYaKpj9iIjfIGaw+NNaFAwanUoDY/rD5aOJNL8sFgvNIm603zRq3aSDraulniOZnbtxay4fm57zfMYRxtniG5UpNp9QlxkpgIJwd8YbWB9A5+TnmOWPVWWEcTbQGgclRPf8jCvxAyNRHSyVFShJZchZQXgqoCZGIcd7OFl+TSgwh3woMDWzslU2DThHfM=
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DB3PR07MB0634:
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0634; 20:wb1HFZ9Ms8mQz33FSNOEEgwg7Bn3ouQ/L0bQoLavkjGme8cieo+oSvbVF+QHawoEdC3g9BZIS96fS91OyD2+/gqfySElzLvIshlznrvwcTIr/04J2GopdfB8TQiJMAcBlHF/roi6Lhp36blRVNHO8PEUHk4vMLFPfLRtcDatk59tiLRFpyn/qo5lna2flh3bMvey3mHQXPIytc37NZjY5PCdUc0+89JFFYO6+gnpgpHcoyhYaHWHREH1GJjwOm9OWQ+BABJ2HAa/1UK3kCZFu7LBNRpguQ9iv2S+VAufveic0vplwjSmuReUF2SZdWmsFOyjKD5FB8K5zfZi94KqMMgUP2XdBD/86X7+NUhec1q0K8vvm+jvCwNhP3411K/8qAVxy6o66ow7SHLH67iWD/xF7b1ivY0Wxe3d7oJe4nFN0baJ9fs3jjWR1maFVZlAskWYWHSNWdRzjagRs27fIlMgIXKiWid+jdnDPSCOu5Vo4eRl0tHow+n4UKAtINKt; 4:bYUuTWG5ZPRmwHIRGbctLI2Tf2N+Gsr01zSzoMSbXLAvfVuC1LkSPw7/qq47+60NugI/6OogE1KxD9wlZvTe/SbSZCkwqdZHj/JUNnPuXmuT0B7WjOyrAEgGyU1LqsX51azIEZxZDSpRttmF7yU/AGKSUDqV34+ScguQNoUa/XJXmTuVZ/+WYxnjwAENwNdCVMkgzwEGhYrLsuIMRXCzDc4Vsi75BKJ9+0lBkCe88NCsvdLPynuZQCVRxllMU2fV38MuXrsgveb48x3XShpYKw==
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <DB3PR07MB0634B895BBF443A72F11C05B83500@DB3PR07MB0634.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(100000703101)(100105400095)(3231021)(6041248)(20161123562025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123564025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB3PR07MB0634; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB3PR07MB0634; 
X-Forefront-PRVS: 048396AFA0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(979002)(6049001)(6009001)(39860400002)(376002)(346002)(199003)(189002)(117156002)(6116002)(33646002)(97736004)(189998001)(3846002)(6486002)(478600001)(50466002)(77096006)(305945005)(47776003)(65956001)(66066001)(65806001)(7736002)(64126003)(83506002)(86362001)(8676002)(81166006)(8936002)(16526018)(68736007)(25786009)(31696002)(23676003)(81156014)(229853002)(6246003)(101416001)(5660300001)(54906003)(50986999)(4326008)(65826007)(53936002)(6666003)(54356999)(39060400002)(316002)(58126008)(106356001)(105586002)(31686004)(76176999)(110136005)(93886005)(2950100002)(16576012)(2906002)(36756003)(230700001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR07MB0634; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjNQUjA3TUIwNjM0OzIzOkxkWndWOWdMbXJoUDQwZlVFOEFocDRNU1B2?= =?utf-8?B?L1l1Ky9VcGR3Znd4Q2M2UXlJMFZzSHpkNVBwMFlzak5EMG9ocG9lTGY0ZmY0?= =?utf-8?B?eVF3RjRCQWZCRVY0em81UTFsS0FrcTJkSVpDMEd2aUY1Vm1TbS80OGJ1YVNF?= =?utf-8?B?R3lCSGx2NTg2cGxLeUxCckQvNzJjc0FiTitKS25VSERVZlR0ajBhc3ZjaHJ3?= =?utf-8?B?aTI0a3dyNXhPZUpIcmNQZE5ENm1LOUYzOXBnUmYzK1hiTkhlWithM1FVQmNV?= =?utf-8?B?ci9sRUNsbU1aRGtwS3ZPTHJzVFJxVEVsdGpKNEUzZmtkVGZ3T3Z2aS9PeG9s?= =?utf-8?B?T1dUbmJFWFRCa1ZMd2dPbDM3bFVwM1NNU0htN0VOZFJEZjZ3d3VXY3RLWngx?= =?utf-8?B?b09aT0lhL28wdXFtMGFnb1lqOE5sZHU2NWUxNEZBR05DZ3VveDM2cDhxbHc4?= =?utf-8?B?c3BXY01iL043NWlEZUMrT3djeUlMVHZ6emJwSlFqa3dHaWZvdUtDbVZJbkVH?= =?utf-8?B?UnlhaWFxOHFEaVR2ajB4MHVQUE5VSkZlMWYxMGlUNWlYY2JnU0FncWhhdEFK?= =?utf-8?B?TXd0WU1RMFcvcWxUTXVIK3g3OCtSemtXbUliUGFyL0Z2S01TNllia2RtbERX?= =?utf-8?B?WUpxOWtpSEVEZ0xoVEp1ZU1mVS9hRitNUmlpdW9VTjYrVWtkQmlyODZpV3pG?= =?utf-8?B?dEsweHQwZ1BkT1M0TDJOV3pJZ29lS0c0MGxXR044cGo4NW55RFoyKzhvNGR2?= =?utf-8?B?d080ZXRjTi9UYWdKZENNdVRYK1pqWGJQYkUzSXd0Q2lVaXB1bUovdUcxNWVR?= =?utf-8?B?cTR1cUQ3SXRSaktsWGVxZG1STFVpSm8zV3hSRlA2Q0txSTBVOU5WZHljWFN2?= =?utf-8?B?cVVaRzQvQWp2NjRKT0FXbHdoVnc1bURIQWdUbXBWOEJTdDF1VEJRNGVaUzY5?= =?utf-8?B?aG5LV2N5YXFVcTZmYWZDaXNLbHo1U280WUJhQ2hHYTJLOEpPd1hDUmJXbGlt?= =?utf-8?B?U1NqRjZNNW42QkJaUFlBWjhTUmtvU1dvT3ZLYUxEbjdyWW4wYnV6UCsvQTly?= =?utf-8?B?bEg5VnZpTGVXc3JuSjU5ZlM3UjlScEdyaG4xQ0t4VXRHMEpYZk9LU3UxZU1T?= =?utf-8?B?VnljSnpJaDcxcnZPWjJaNzE0dTBQdnVnSWs4OUpyaW5mTFZTT2Rmd2JKbmFN?= =?utf-8?B?MTVVdWlJTUtzUkdSb2NCMWtUWlhEUWVySi9GaFVPYzZoRDZ6Q2tKZjYvT1l2?= =?utf-8?B?T2lsTEhoOTgxY3dpU1BKWks4WEFtbUlTVEt6SEpKcGpQVEU3amxROEd4TU9O?= =?utf-8?B?OWJnZDZtUmgwc2tOTGE5VlpjV3BMRDlBZTV1VE04ckVZNE9RR1dTM0NrczdD?= =?utf-8?B?NG1iT3NZZHp0VVNoZ3hFam5JOHZOTzlkUGU5TjJQSit1NXBLWG51eWkyYTIr?= =?utf-8?B?c2RaR3d4alZDaWtqQ2M3c24zSW5SVGVFZXVidG9VNGFiTW9YbFc1ZU94d0Ev?= =?utf-8?B?NmNZQU5VVU1LeWY2NmNlQ3dwWkFRdlBEVURJc0pwVVYvaDFONFJWYTRTWWVY?= =?utf-8?B?K3UrZjBudjVTYmdMOHNlbnhQT0NjTG10WVZyc2JDSldqL2hwNW9uTjZTbHQr?= =?utf-8?B?UWwrQUlHTkdDSzN3OExlY3JzL21TYjZoS1FKSXozcElkREkzTTFWSXFTdWto?= =?utf-8?B?TjZ0MGhvSWc3SFdWUkovakVsUC92RUFKTi8xMWFnZllndTk4NTl2cXlsZy9O?= =?utf-8?B?bXJtOC8rYkIwQ3RxRUVLbXBVQVpHOTJ6YlE2TUYrV3FtbXBFMVVkdzgvdWtp?= =?utf-8?B?dlZEN1NVck9XWTJoOTNzdWhGeXJXNHU1OHpjY0RZbzFuUXlmRzgzeEFIdmxO?= =?utf-8?B?dll1VTRzV204cTEvV1JiK3BXMkd4U2l4cGRrNVBBNXFNeTdaVVNmaDRYUzNP?= =?utf-8?B?YlczdTRKbm5LOU14ZWtZSVM0VFBST01LQ2FxUy8wcHFMcUttL1FjSmYrZzQy?= =?utf-8?B?Y21sUUkrYUtUejI5NEluNldhYjVxQ2FSYWxqQT09?=
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0634; 6:bIRljhlVOEtRHE8AzA6zYNMlnGfQbR5vJQjZXuqf8R3+q6iL11Naq6qjTmKdwv3Br7pNppJYj/6PEgLIxY8wSPx8ngFbi7GtmZ3JGBZ1fby0bJysD5O4pU75/jNBRqPNgVcuj5elLmtqXkG78levQeoGAWTEZrDiCrMN1g3ToUUpyFqDLRlzmrRlgo2dftbl8A88LoVXSrN5+tbGk5Q+ZxUndChLIvZF0Gr1XyUdkz2wQLEqy4+GVx6uu8GJ7vCl6M9puQIlBdRambMBxLykjnFH40aC9DO38+Pj4f/Wyc6s+ipW42fXehluJqH1+2nJGJkvR212GZcHfNzkiDFbuqfl2/6XwajNNC6eWbmZ3Uk=; 5:Dndu2BqlmkdFblw57qp9AiPQVMQcj1wzGvSXGJhYwbNkBAtM6AL2b7SnWJPI6P1tOBxdnIWRR0febS3bCo6uX0xcVbk/O9g3EpsnWPOsCzgzXo+h/HL5PKNQ2M/1B7c69anbJjJsezzSXW+mUYEtznEtc1Qk2stC9SzMPVI+T3Q=; 24:C7eU6c/cz5SC7fXOQAEtm5weIX6In2uyqxAdQjjkEUKn6G+4//Z6f9ZwZDgtlTybxcz36e1bxwbpHKnJ2X5/SMaoRXS8dtLwj8NgciQPhac=; 7:SQ4o9zERm/tmylazgCSWjnaS2EDs0m/Q/YdxmpsXlTeSEQPYO2WWmKEt2M8Agw5dK9vL4xeh0hmWZMEtpEPYWmOl10IyJUNfuLv9E6KE3ekSjx+GODGThVMbnkDfarlvO2LlsEMUlTmQo3va3snUDF4LimsFTCwsRSBCy/Ar1/8lxKjejWq32WEB7x40p/OWr5hNs6hwfK2JUVLhAdXgiqCo0kPjG7GznMG6HPmBhAV/SH/Ar61XsssZUzUScigD
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Nov 2017 08:14:17.7396 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 06ef8d78-6b63-4099-9071-08d524ee6094
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR07MB0634
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrBKsWRmVeSWpSXmKPExsUyM2K7uu4dSYYog+azmhafHl5itrg84Reb xaZZX9gsnm2cz2LRc6if3eLCmrtMDmwel694e0z5vZHVY+esu+weS5b8ZPJombOHOYA1issm JTUnsyy1SN8ugStjU9ck1oINbBULz69haWCcxtrFyMkhIWAicfj3PpYuRi4OIYHDjBKrP+1j hnCOM0qsW3WOGaSKRaCXWWLX/gwQm1EgUeLvvbdsEEWtTBIdT3+xgySEBSwkHlz4BzZWRKBa 4uS7dYwgRcwCzYwS/zdNZ4Lo+MIs8WTla7AONqCOLbfus4DYvAL2ElO+vWGBWKcicWrNQbAa UYEYiYkPLjJC1AhKnJz5BKyGU8BWYuvxV0DncQBt0JRYv0sfJMwsIC5x68l8JghbXmL72znM EH8qSOz/sRLsagmBeYwSP1rmgl0qJKAtsfxZCwtEka9E05Gz7BBFMxkltvz/AOU0sEvMnLcD qkpW4ujZOVC2lsT8q7egii6wSfzvm8oOk1h39SPYeRIC2RIPzspA1Fxhlfj+aCvUTTISPVfP Mk9g1JmF5LtZCB/NQvLRLCQfLWBkWcUoWpxaXJybbmSkl1qUmVxcnJ+nl5dasokRmH4Obvlt tYPx4HPHQ4wCHIxKPLw7eBiihFgTy4orcw8xSnAwK4nwOrMAhXhTEiurUovy44tKc1KLDzFK c7AoifM67LsQISSQnliSmp2aWpBaBJNl4uCUamCc2t701TryzblzLBcaimfwvHyzQz/zvmPg uUpJ4ZZZy06zhtxNN/fb9Gd3bsUyxfR/u7vbk5efPJvW1Vdt0KjsoPnz1LfAJXfzTIzbfSp3 +rE/keo2WG3xueDAhraNltvu8Sva/urYfEhT8Im+s/pvOSP/+xbsD/t3e0zVnNsavildY+U6 dWMlluKMREMt5qLiRACJFpnYOwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ygcpf5ZGEZmSDDrDEEq_fG0Ptf8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 08:14:24 -0000

Hi Charles,

> Overall I think the new mission statement is quite good.

Thanks!

> Rather than add more specific examples to the existing set of
> highlighted activities, how about adding something in the mission
> statement about implementation and application in addition to the
> development of open standards. This would leave it to the IETF
> community to decide on methods to achieve this, e.g. more emphasis
> on running code, reference implementations, protocol validation,
> workshops on enabling new standards and functionality, etc.

Good point! In fact, ISOC is *already* supporting the implementation
and deployment of some technologies. I agree we should not be only
talking about development. I will discuss with the board how to
address this comment. Thanks!

Cheers,

Gonzalo


From nobody Mon Nov  6 00:16:51 2017
Return-Path: <gonzalo.camarillo@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 C0BB713FB42 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 00:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 bWsDi4OAgiCa for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 00:16:48 -0800 (PST)
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 706D513FA6E for <ietf@ietf.org>; Mon,  6 Nov 2017 00:16:48 -0800 (PST)
X-AuditID: c1b4fb2d-fc3a89c00000268d-b3-5a001a6eab3e
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 3B.2D.09869.E6A100A5; Mon,  6 Nov 2017 09:16:46 +0100 (CET)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.75) with Microsoft SMTP Server (TLS) id 14.3.352.0; Mon, 6 Nov 2017 09:16:44 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Tk0HXXZKfHnd3XZWa+zXrz7o+XFJVvu4YlxqO/oGE2I=; b=YskBi1QoBa5+fI7FV11rXgbFP4GfdpSbeXWIa9J5xPC2Q6YRnKzNDIUMekBJN9FH5nWYSyUe13vTXgVnfXzEq8nyfEvPFRwF+oL8FZuXLUkvr6kTf/wuuRETje+jOfmtoURHgCzWnhmkG2z5sJyFxBX/EUhrEwrDC12jBweXwLk=
Received: from [192.168.1.7] (37.136.86.88) by DB3PR07MB0635.eurprd07.prod.outlook.com (2a01:111:e400:943c::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Mon, 6 Nov 2017 08:16:42 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: Marc Petit-Huguenin <petithug@acm.org>, Alia Atlas <akatlas@gmail.com>
CC: Michael Richardson <mcr+ietf@sandelman.ca>, IETF Discussion Mailing List <ietf@ietf.org>, Doug Royer <douglasroyer@gmail.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <8a8634e2-de7f-0a56-bca8-41914b9473d5@gmail.com> <CAG4d1rde91LcVi56DZ-Vchit5jiwPHNP5Mwgn+cOi=wQFmaz_g@mail.gmail.com> <a3c0a285-8cf9-28c4-41c7-cc776029c4d9@ericsson.com> <26185.1509118832@obiwan.sandelman.ca> <a09cad34-e7f7-d510-93ab-9114a8f19b1e@acm.org> <CAG4d1rfCKS+HWVWayk4ZjnuJcWQJwzGgxx2pwSBFLpXcGok=hw@mail.gmail.com> <17268669-48d6-4f70-d67a-5e642ae50b8e@acm.org>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <f0beec95-7ce1-a2b7-3ad9-736c4b5a1fcc@ericsson.com>
Date: Mon, 6 Nov 2017 10:16:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <17268669-48d6-4f70-d67a-5e642ae50b8e@acm.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR0501CA0010.eurprd05.prod.outlook.com (2603:10a6:3:1a::20) To DB3PR07MB0635.eurprd07.prod.outlook.com (2a01:111:e400:943c::25)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 1a6d8774-6854-4b69-295d-08d524eeb746
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603249); SRVR:DB3PR07MB0635; 
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0635; 3:/Yip8q4iQf3d3PXQlhaVwRim9OPP7U52zj4h2m6MMS65jMuwZVAuWeJ6yRTnQbsnwNfhWxON9cqOVHdwtEBX+gezFhgYn3gQWsrKN+iBTh1Iq7a2xYxk4/Z/9cxs/UKFfZGNxfROsby4S9n90vHUYPb4QS3adX7jP5GQfbCM0+Pg35mPT9IcRBFrMMz4gkpykxpoi1xc53JM6WbhM2m05cr0/n3vE481pkL3z5718eM2Uaf3QsiS2llmIekLb3d5; 25:n95m4F9UyG+EIRCj9hXqE4pWibu+KoXMHp2XGQDv+fmzZmTTW2Ipezjaj0VpJJUsrCUam8c7m4lF/9p6/DY663Lc8x3/Gl7I9EmoEpau4f23LDCDg0mBCL98wOmTpXGoJLkHMAlde6cjkaA+xqy/xadpbBfeXTDrWcZoCmWWKVw8ttdygQe1MUGasrbjr1ecA0Dcfx6Yz9SLOT1/k168do73WMd/NgnqPwziV324uiJ/vodsYahZRVqvdrQCCVozUBhq6t/MpAPENv5Vx9fT7/cI0kKLJJpwckTY7chbVnXvpHO+pbTsqGjx9MqZUlmgpk8f1fjmgqfqGiahGEMYLA==; 31:Yr9FUSX71a9Wj3P0U+smXZxvxzGuX+xEfgu0TFzMmNEjheo9uKCOV+raiX0L9qt3tYua0P78MXpDzPK4S42lnwJPOLkRqvGXU+eiSQGYdyJn1dTnE9GATro/JBI2mwX9oS08Q/nFY+6v6OPtshpISS5mB23uCkUvS5q22GgF1DycQH8FrRrf7e78FuCXiq7jCqIQxdZq2cde9BaVf3HNqiOoGsOeCy5f8F5FtXzQfko=
X-MS-TrafficTypeDiagnostic: DB3PR07MB0635:
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0635; 20:3kVRu/KX1qFQ4hO+he2o6dt/+Df8RGT+RvyE8PXGdeLtNrZpAOwCCyg3GQfO+kzcE+VtGdzd093nT5fbLpYMrPJ8sQQ77XOnoSkVmipv8u5YSmE5T/NZ1W0Pym8A7RaZqtF+x7yU5+mUKS+lEGc1PvpHhjPHzJ3Te7MOiYFDGNGPrcU8AJ/cxvK0pv9vvNuDvhY8L6CQCCg6tjcwso+t9tbLBcsLFOqcSXPSAaSRREQeNkOsAsAHJy3xaj1LpKrjLzs+H+ioJptLp8qXeUcDIgC/IbshdFWDt9d5HJxJrhLsSV6EaueqPLontVoyNfuB2awIR5Y5Q6W5rD0jsPspIYXL5pNXjpvZy82hc0s4ZB3vj/hTKnn7jxsn2ozhhfi+RmMeA6sYBRmGLjKrC9dj9NaM+cefa05+/rp+51j8Hr/axr7ZvFqTeP7ilW/S7QdOyep26EKji50PBbDyBsNkvHVcEhDpU4hafqBCAuxUa4KLfqhgcnZLDZFKMhFDPjzp; 4:X1OZqth1ekhspqn/rt920NK2GTigu2C1KRhOqb0JsltZNHKawaHHNwDde8P2kgYVPq3Di35A2CfwIoU9e36/JalsEgTZNZtDfmJsHEKjjY+SWvuK2ypvmSWh8zjwHycLTwJvGW5nu4e/s15us5KnSIvtJkwaIhUhXXUGqZ4BcG4U29m/cCcsBm0tH6ZsMK8SL8QW3g+yzvhOlzLFmE36eW5H4SmmDZKaYEcZWkytqzentyxJUq7arQvFq7Muu+sDfMhD6KFRWH70ISHZDQeFpA==
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <DB3PR07MB063586347E0B7ECFC594341783500@DB3PR07MB0635.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(3002001)(10201501046)(3231021)(100000703101)(100105400095)(93006095)(93001095)(6041248)(20161123564025)(20161123558100)(20161123560025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB3PR07MB0635; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB3PR07MB0635; 
X-Forefront-PRVS: 048396AFA0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(376002)(346002)(39860400002)(199003)(189002)(110136005)(229853002)(8676002)(33646002)(3846002)(58126008)(66066001)(23676003)(54356999)(76176999)(50986999)(7736002)(478600001)(8936002)(6486002)(77096006)(2906002)(6246003)(54906003)(25786009)(305945005)(81156014)(6116002)(105586002)(81166006)(106356001)(65806001)(65956001)(47776003)(36756003)(68736007)(31696002)(16576012)(117156002)(93886005)(39060400002)(189998001)(86362001)(50466002)(4326008)(16526018)(316002)(5660300001)(230700001)(2950100002)(6666003)(83506002)(101416001)(97736004)(31686004)(53936002)(64126003)(65826007); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR07MB0635; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjNQUjA3TUIwNjM1OzIzOm50NEErc0ltZTlGMHQwV05wTUdDNXBaQmFx?= =?utf-8?B?NnNpdTg2VzdGT3RTcXRmbDcxUVQ3bjdoRkhoY1NCbVpKb1d0Mk9kVUp6UXBE?= =?utf-8?B?bElxbSt3cW5mVFlSWENlZ2R0UHl3V3JaRTlPVnF3aHQ5S2IzWDZmQTFvRVpn?= =?utf-8?B?ZVB0ZWVHN09lR2xJQk80UmVNMkRYTnoraEJHYWxZSXQvR3I2SVFGcllJTk9i?= =?utf-8?B?aURxT2RzRnVKVENhSFY1Ym03QVlta1NnY3paREhhS093b2hDUjh2VndCRmFK?= =?utf-8?B?bThXYi9kVFVENWVxVE1YcHp2dFNJWnlrRzZYQU4zaWlXV3J5SzIwYVR0c3cx?= =?utf-8?B?VFRWUmZiVUkxSWNDQUZ1K2pCRFBGWHZJbWxJMENHUTc5cit6YmxlbVRCNFJw?= =?utf-8?B?M0g0RWZpaHBnSTFaM2xVL1pRcTQ3NTRBRzVEd2Z6RVlsanNidm9SZjNBWlN0?= =?utf-8?B?cTFWdGtEanVYWjhMVU9ISjFmQ05qa3dKV21FTDNvVzhhOXQ0UERaTHQ0WWdp?= =?utf-8?B?MjRwOURnZHAvc0lmWnVwbFFMenNnTGFRbEN5a3YrOHNlaUR4RmRtVXAvVmZU?= =?utf-8?B?MU5KTHl6OEpSbmJ1UlIxQ3VHbVFVOTZIUWJQSzg5U0lNa2xNTUxQV0tydjZV?= =?utf-8?B?d0FrSG12bGNtWFgweGZBV3hndXpFaFRUbE9tWUlmVHU4bSt0YVZRZi9aOC9R?= =?utf-8?B?dS9pOVdJMVpxR3BpYkNpWSsvZ2NpWTFMTWlZbmN6QlR3aDZmMk1iY2hlRy9j?= =?utf-8?B?SmRJcDBHRFRBVkJjZDl0dWh1Wm45cmtqdlpHeUdReTFXYWNlYXVIUFAySVJq?= =?utf-8?B?eGZucDBuRFJpalUxb2JSTVJLZmlySEdzN0pyWGlYQi9QSmdHUmxHb255VTFy?= =?utf-8?B?elZDQkdKZWlKUDRxVFZYbTVuQVRUWTYwOU1kR1cxWXp1eGdXWmFZaWVHOEQv?= =?utf-8?B?UU1haHZZSFhITnBzOVBzWDN3aVUyaHpQVmJWb0liOVVSS3RuZGJTNGcwZFlr?= =?utf-8?B?NS8rbnVqRlRhKzFNY2ZsemZsMmpGcjJWdkNkY0VjMkJFTDJGdVRHdUZncnBu?= =?utf-8?B?Ky9nMVE1QXRybUVwTGFrVmlpTllRQ2dmZW1kTDJrT0tsTUcyL29YUE5LNHNR?= =?utf-8?B?MjMzb0xTait6ZXFpL21jOGRqZXhQYTlMcEo1NGZoT0RMRnhSWm4zNjN0Mnps?= =?utf-8?B?dnlYZjJzdzl6eU1zN0krcEJlMW9pL1dDczhQbEtmaDZmQnpYRXFZUFFRZGlW?= =?utf-8?B?NEhlL1hCNUlUUHd0QUZCbHZQVlc5QUdoQjFEWkhMb1ZaTXkxS29jNVBoM0o2?= =?utf-8?B?SmNEelp3WGh4UHREZ2pkOHFGTFFsc1E5S1ZTRnlJQ2lNcW1PRFpyZmprcmMx?= =?utf-8?B?VnI5Z1BTRXBZOWZuM0gzTERidmRHeWdmZ3BXOWhJUnV3R2xuOUhwSVp4VWZv?= =?utf-8?B?cXJUcEpmRThKanJJZGY3UktFSlduL3o4MDBEdzVwNjBVQm9meG9FTXpWSUdj?= =?utf-8?B?UDl0UFMwRzA3RFNSMFR5UXlVM3dwa2NDV1JWN3hMQjZTQTZjdXV5UmJRUmQ0?= =?utf-8?B?aW5nZ1pIeGV4dWZEVFFXZi8vV1E5SzRrTHpTMWx2WjJDMVZBOHF6NmMwb3dK?= =?utf-8?B?eHVvdEphM2pDcnpLbjdEeCtKb0JwNVlJbFFUeWg3RmdGTFVMSnR6dCtJYWZF?= =?utf-8?B?c0JWSzh0dlZjUm5qK1AydTdkclRKQjBmSk9DMnk2UEsxWmptM09hUlFDcXNU?= =?utf-8?B?MCtrMUo4d3VkS3ZCbXpnRzJPVFZNY2l6cEp5ZjNlcUdNMmZmZDliVzN5THVp?= =?utf-8?B?dmlSdklyTE5EZ1pWaW41d1BuVERxRkZIWUNoclVpUWo2K2FnV1dpTFBmMEFN?= =?utf-8?Q?/eD94o19QNc=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0635; 6:DygFoEw4u4AP/ZPkTJ6r9Iaq4gQ9jEfjvDtoYU0BgbWJJn+rqmk825TUt1Qtxi1FIhIBWFM4HOSIuWcR64xjYFwgAdUPyuOzRZt3so3pM2Fy24JCYo01vzMwR1KNLmEL/2i2gGxvyxQRxVy8WwArSZh0JvOih1nvRNZNJz7JPRFM5kfnQhETiq+myPociKE/z4rXT2ixeYlrXcZ7Jn4H9RKdRfJWBd2+liGovbazzIfRwBTTllMXs8IrG5cJ/NOjxNLK6C2GLUXPJbnwapIZc0rUQ3qU/SRxFSk/mbcpW8aJ5WhqRe47NXi7sxD16tA47CRfD9qtqjgtel+e9RsvF2hs2tErb+PbOByfWCec5ZE=; 5:oYXWDM7g+3zxgRt7aWenH/HjvoZGJlbHW+qe6q4ZedQ4v8ZCriUoXImMAjS5A3yYmAb6GQZm9ZWg2t020Se1hMIpENRuteBcDhRyMyIydYHQ+WNf3LRTwXKAvvADjpDgakJTetZswiWMjNdJocVgxNR8CicdIz+oQ1D05clwsJI=; 24:XerOpx4Hyhfp8YPqGXGQ6zeLJIK2EBgLLxQVPV6MgaSANduDUxfAqXJs1WoyC6lNM6DHX5h/yD5cnWGVsoLCghyjRXUah6qjNJb/KGDZ3j0=; 7:NtZznuiagwLRgSiZ4bztCIaRyCDaXQMG5CAnuGpAwa1qgrxzbcZhkHG94gQmhIPPOKCW2wynrRNHA0j/bKI7MY1nhFXKoKnpmO4jH4LWWv1snvXmUxFbv9SLcEG2ZB/eCSIxAxpBe5/ByDRZClzx3tMhR+2dMfmI03vLr+SXcjsG73I9EVVlj0OaRnqiiDGFP8nEtjztGeNqKlpxd2Op1qwkONWX0IMOqaUvdM5eWkOzfdyc3rm1GER7r+FzDkYb
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Nov 2017 08:16:42.5469 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 1a6d8774-6854-4b69-295d-08d524eeb746
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR07MB0635
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFKsWRmVeSWpSXmKPExsUyM2K7t26eFEOUwYa5+hafHl5itrg84Reb xbON81kseg71s1tcWHOXyYHV4/IVb4+ds+6yeyxZ8pPJo2XOHuYAligum5TUnMyy1CJ9uwSu jL7nhgVzmCu+bZ3N1sB4gqmLkZNDQsBEonvyVTBbSOAwo0Rru3cXIxeQfZxR4s/E7WAJFoFe Zom9l1QgEq1MEktbVrGBJIQFLCQeXPjHCmKLCHhJfDk8BSzOLNDMKPH0DB9Ew0FmiSPH+lhA EmxADVtu3QezeQXsJRbcOcsOsUFFovnJJrC4qECMxMQHFxkhagQlTs58AhbnFLCWOP70L9BF HEALNCXW79KH2CUucevJfCYIW15i+9s5zBCfKUjs/7GSDeQGCYGZjBJ3XmxkgXhTW2L5sxYW iCJZiaNn57CAzJQQ8JWY+C4Erv5V80ZmCKeBXeLGshZoeGlJnOj6CXY0o0CixN97b6E2XGCT uHZmJhtM0bqrH6HOyJa4//oPVPMVVok/J8UhbBmJnqtnmScw6sxC8ugshOdmIXluFpLnFjCy rGIULU4tLs5NNzLWSy3KTC4uzs/Ty0st2cQITDEHt/zW3cG4+rXjIUYBDkYlHl5XPoYoIdbE suLK3EOMEhzMSiK8zixAId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rwO+y5ECAmkJ5akZqemFqQW wWSZODilGhhddt6/bctlbPHp8L1H+csrtxXtNL5+OHPW9S06Xv4JuQ83XAnbKmC99H1aTb9u etVGFgOnlZ23dj3sk9as/jvdr2JtznFb7tpS51imRc80pkypVwp/7ufwS/pX8+0PrF6Nh55v tXBKEul8vF7jEtOmHzmm9VtZXr1JCslZ7dxtXZJnInX3XYwSS3FGoqEWc1FxIgDHS9LZLQMA AA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bdrwoltra8ta0s-hthMsk1IrW_I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 08:16:50 -0000

Hi Marc,

> Sure, but it would be a good start to have something in the ISOC
> mission statement about promoting protocol checking (hackathon,
> testing) and formal verifications of the IETF standards.

Per my response to Charles's message a minute ago, capturing at a high
level the fact that ISOC supports some technologies beyond their
development seems like a good idea to me.

Cheers,

Gonzalo


From nobody Mon Nov  6 00:43:31 2017
Return-Path: <gonzalo.camarillo@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 E7ED413FB4F for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 00:43:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 IhnJXNTbv8dd for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 00:43:28 -0800 (PST)
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 6D25213F963 for <ietf@ietf.org>; Mon,  6 Nov 2017 00:43:28 -0800 (PST)
X-AuditID: c1b4fb30-771ff70000007d10-26-5a0020ae1375
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id E0.5E.32016.EA0200A5; Mon,  6 Nov 2017 09:43:26 +0100 (CET)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.78) with Microsoft SMTP Server (TLS) id 14.3.352.0; Mon, 6 Nov 2017 09:43:25 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=YDYCYGSdFKM8WUG+mqhBa5gi29KMD8Bxhult6TfLm0g=; b=PiGCpR6vt3n05lTAaTYooB/J6DSeynXP+xfJgqxEP4B3xmAMJgul9pLzM2KAQU7nVsLWxOD/vFue8t/MLKOZgcSPddmUBDp000epgDgmWNdt1DJDf0sj16xz5IPx4wgMAYznq4q82BSO7RXq51KLZm/GxVU8SZwdpwLhBbOIisU=
Received: from [192.168.1.7] (37.136.86.88) by DB3PR07MB0633.eurprd07.prod.outlook.com (2a01:111:e400:943c::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Mon, 6 Nov 2017 08:43:24 +0000
Subject: Re: conformance testing [wasRe: Proposal to revise ISOC's mission statement]
To: Richard Shockey <richard@shockey.us>, Russ Housley <housley@vigilsec.com>,  Sam Hartman <hartmans-ietf@mit.edu>
CC: IETF <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <8a8634e2-de7f-0a56-bca8-41914b9473d5@gmail.com> <CAG4d1rde91LcVi56DZ-Vchit5jiwPHNP5Mwgn+cOi=wQFmaz_g@mail.gmail.com> <a3c0a285-8cf9-28c4-41c7-cc776029c4d9@ericsson.com> <26185.1509118832@obiwan.sandelman.ca> <a09cad34-e7f7-d510-93ab-9114a8f19b1e@acm.org> <6623260d-17ba-63b7-a942-4fe09ea2efca@gmail.com> <49FB8EC3-2308-4B35-8638-260F341A69AE@vigilsec.com> <tsl60azwfbl.fsf@suchdamage.org> <9A30C139-C14C-46C5-B93D-608BB7FD2E39@vigilsec.com> <1D55A328-A5B5-46DA-A39A-BFB8B37CE15A@shockey.us>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <109fcbf7-3cee-0b48-9c16-52f4e9115434@ericsson.com>
Date: Mon, 6 Nov 2017 10:43:15 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <1D55A328-A5B5-46DA-A39A-BFB8B37CE15A@shockey.us>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR1001CA0006.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:3:f7::16) To DB3PR07MB0633.eurprd07.prod.outlook.com (2a01:111:e400:943c::23)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 74067b82-d943-44f5-c645-08d524f27187
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603249); SRVR:DB3PR07MB0633; 
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0633; 3:SlDyzfCw2hkp0h5RnbVF1N7XUt67oqCWsgV+SssEvAw9FhioXLPqz3PLB+M247rH6tCIax86/ahbRcZDYyvWvmB8XqbC5cdO8a1RiW8TOmrw+mBNmcwvcb9OIX/NKxlYCMxLu26qTpVXSmBgQBHoYA8qJSBT7tO7eNJ3AqZHIvRZYfSnWUSKey7+MR9+33ANaMXX5rLTDWwklq5UH4TWxn121KfJP7S1WoE5Bw0smJby/AuMQgbsWQDvEPj6wY4H; 25:YqDRxWhw/UvCCYGVWw9mSpnyir2GSJzniOSnwhjT/hbgrZ4Sxz6Lj08e9GiAdj7G52BxzxrSf44+UuBPpPYFrAqLd60hb5qIlAWGkxJGb68yMsTQACPLfaevUGcf8BF32lcauvuZF9Xf0G2r+rJvlhNIUONHzl/rF8nWm9L/2Z+679PsSuGT7QTz7qECFr13ruQMjz2srOw4iLZR4KNA/4kqKWu8mTEap3PlcHtwkXWJzsmaR1FwKcHAUG7p8Qp0ewQGT+oixdFAC+mQwsI7qkFcvxgqKxrr652MsboPqwlcIJHCaiZqMEQlBWcmKGVI+XwZhdUHymytsrUNxGRwWA==; 31:x0ObwlLW48qNcv/VHw1U8rnGTOWYhK1oDvOQvBf/ZuVkHW4VHC0XLBLt9ayear/C8kEaWENXv3KlckPOAtlzQ9hKuQf4zf6kP7QDzFvu62oX/onCWrZ1nNBuPrsn2SMuLCdZTvhrVvlcibdWV3ucV3EsfhOg05uJV6U6KmJPe1yeUCniDCpLp/KBN6mP5S1PzppqPM4PgPooeOHSyXJ17catoIthXQ7SqqZ8+9Q2zng=
X-MS-TrafficTypeDiagnostic: DB3PR07MB0633:
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0633; 20:+WYwlKlHSblQdcAyZDiwOcZ/0JX07F4whZHCch32fq7av8TDEH1LALKj68Ep2wkdyPg9/ZuyWAmmb3hyaLbaAD6aQi+djOnv9jn0XEvA+QVib9SZC6KgmefN6Qd5ab4mlGb1oXD6dBOpXhPiivCr/RpF/HGDhC4BhKCdITIt/qt2Oahx8TofvNKEKpsUR+uMj3uY4xvtfMULfepEpniprBNcfo7CTjBVIGUYw7PjaDAivBYCyvng3jHRbgZjY2S25a5gIXNbyPFIM95NAMM0UybK0nGXNF6NaCxdzO9XeZeMXYK93C3/naiAy+SgWeGSdXv1llc6Xciotegotkc7vi7EPn+fna/NAAvNgEN4N/6SKcD1c+crL7q4vqdSHU//COKxHXbhivot1pLO9LY/TLsN7LO9PF84p8pjo1x8v+5tff/GL/mgE7lVDGFglPkHphjy3AwIjRKguEf9ooIVH6WIyh6TF9sV4i5xPqd0AKzQDV8GhXslSv2xEe+IucE5; 4:Zh6K1Sno9sgt0FU18N2QgVQCa0zbka9LMAoXUCclHkCm/c5AfFO8eRgDu8BZ/jZQQM/MIbD1Ls69LYkrBPsBzEt7tbH6lxNPhTAdIvhx+wjHXbV0Fhm9ibg1OHjFlPOT3w0XtGioQAlwnLfXXKh7LybOUOMbubTUC2YPuTKhvo4rslHG3jE5WqQK97PBLZB5QBq9Hp+l2COBqrizlW1gB+C25wRQQy0+LAeGcwOutoqCskLNLe+ybTxvraBopo+tx37j4kE1C2w1ZzYL+P7S6k/6tqfO/liQY1EjDU8A5cY0Zkt5BIemKmE/xc2nbb1s
X-Exchange-Antispam-Report-Test: UriScan:(100405760836317);
X-Microsoft-Antispam-PRVS: <DB3PR07MB063395A7942B34341757F96283500@DB3PR07MB0633.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(3231021)(100000703101)(100105400095)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123562025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123558100)(20161123555025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB3PR07MB0633; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB3PR07MB0633; 
X-Forefront-PRVS: 048396AFA0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(376002)(346002)(39860400002)(189002)(199003)(110136005)(76176999)(6666003)(33646002)(4326008)(36756003)(68736007)(478600001)(189998001)(2950100002)(117156002)(2906002)(6486002)(77096006)(2870700001)(229853002)(54356999)(25786009)(106356001)(105586002)(50986999)(101416001)(5660300001)(58126008)(93886005)(16576012)(316002)(65826007)(3846002)(65956001)(65806001)(83506002)(64126003)(8676002)(47776003)(31686004)(6116002)(66066001)(50466002)(31696002)(81156014)(86362001)(81166006)(2171002)(53936002)(23676003)(8936002)(305945005)(7736002)(6246003)(16526018)(97736004); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR07MB0633; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjNQUjA3TUIwNjMzOzIzOnpNdXNlbHhuejM3ZnFwMUtyL1lwcXFqREdF?= =?utf-8?B?MlF0cWQ2Z1Fhc3RXbG54UXpPNmxhVjQ2dW5hcG5hbGlIM25JU04yV3hjdGt3?= =?utf-8?B?Kyt6VGk1SDBkNVlxVnlOY0t6M0FqUWxYY1RHMGZKa3NCdGw2aU9jUFB3S29K?= =?utf-8?B?WnI5V0w0Z2EzTE9tTXYwWVp4MzR4S1psemZENkUrZkJ4ejNRMTNkRGJ4Vk9z?= =?utf-8?B?TmhCSUFPNko2d2tBbUV5YVp6My9hWFZjakR1Zk5QcXFKRmdqRTVMVStEV0cw?= =?utf-8?B?MEVDVFVSWEU3ZWhFSDViV1VBRlppdFNxMCtkRTh5SGpuS09mYWhaV2RFMmRt?= =?utf-8?B?YzlpdWFTRFR4SUNwQnkzZWFkTW5OZWwxdnEvUGFmRGl6UG91R2dtL3BKQjdT?= =?utf-8?B?LzdqR3VycFU0YkxVV2tjR0RDU05ZZWZaclRvOTU2djlsZUVxYWUxaTQ3cHFu?= =?utf-8?B?YTA0ZFl5dXh5bWRTazFYU1BqaHFhOFFML1h5RnFTOUlFbkp4TDhtUzkwV1Nq?= =?utf-8?B?Wi9UZE5GNHVwRVhncWl2Y2cxRHp3dGlocjVDWi9xY0xvQWUxa3V5cTJIWEZY?= =?utf-8?B?T25GQ05ueXF2ZW1saDR2UTAzNjJPMFM0QnB4NktiRkl3aFhVSEhJWllDYitC?= =?utf-8?B?ajhBa0gwM1BFM3pEMkZERFZMa3JHS0tKV2toUFJhcUpOWnVaK2YzTFJiTEZl?= =?utf-8?B?Qzk4QVRPMkJrRnZ3NzRjMXdOQ20vMDJmY1RrNWZ5VjZ6Y1dROWFjeWsvWWk3?= =?utf-8?B?T2hBSklEVWZxbWZBblltbjVqZ2N0MWtaUWZlQlhvSXRkbGsvZjE2a0J2dVpU?= =?utf-8?B?Sy9LNjF0RVBqRU5JUXp1Y1V0VXVBZkVJb3JxdytkWmlBTVJZeWZsTU1SYVBy?= =?utf-8?B?dFU3WUJaNFBJNkNaeGtZaTVUOUtEa1FlaUw2NGtGcDNOd1NyTFpRVTNsbFJr?= =?utf-8?B?MzdkNTByOHorM2x1T0xrdFhRU3pneDMyNUpGTW1vRk1SUUhPdHliMnpuZ05s?= =?utf-8?B?THlXTXBoNXhJdGQ5MUcvRm1wQkkrR3RtK0NnbmkwcDFKcnR1Q25XSFBmK3g4?= =?utf-8?B?UUpTVTRoTnh0RUJOSms0Rlo1NGxEQjVLblNlb0d5V2trSkp6Z0FkSENDRDl5?= =?utf-8?B?VytvQ1NiU0VpVjhNbURUN3FnMlNKeDNTYnNWdDU1aHdoWGVCeGNIbkxoT2Ry?= =?utf-8?B?MUNaRHFXRGVHdHc5ZnhRcUlrRkR0NkwydlRIRGxEaUNMSjBQbWgzbk9UNDM0?= =?utf-8?B?SUx5UnltMGl1VmtGWFV4dm1nbnpHU203c1EwV3lZRS9FRExmdGN3MFJ3RXVS?= =?utf-8?B?Vzd5a0pSRzZUOEFEblp6YlRNMmNnSnN6dGVlZEJHeURDMnZLU0tkbGxjK2xY?= =?utf-8?B?Nk8zc2NscHVCV09Db0ZCOUt1ZmFlRHYzTFNwZjlubU9sTFVjRmZzQU9lTzYv?= =?utf-8?B?YmI3am1xQis1TUpWQzdWZDl4QWtnR3g1elhiUVBSRWowa2RNbTMzblROWVdF?= =?utf-8?B?eXpHMitSbVovakFuQXFhOFNqQ2l3MzJwMjRyTzVZam1VVjNlRkxVU3pRcng1?= =?utf-8?B?UGVrMURlWDZhQTdsck10RnVvK0Rrb0lsZmtLMnJ4QXA1RFhudHFDK0Vvck1W?= =?utf-8?B?aGMycnh5ckFOdlo3VE1TNXhwTTRoeHQxTG5LdXFyNy96V3F6MUw2VmpONURp?= =?utf-8?B?bDUyZGM4N1lhcEJhUjJZdXdEQ0xpS1poaGNVRG8ya2ZDdVp6VjJWY2ltZWNs?= =?utf-8?B?d05mRHVjWmVuRUlGVHhTdDZDY3lqejErU3djT1ptWTZNOGswTm8rZ1hVeVJF?= =?utf-8?B?QmZQK1BSMGY2d2E3bEpMekVtSEdib0JDeFNlVVpPUDE3dlE9PQ==?=
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0633; 6:MBZp+ZQ9ZILl6Z3hKoDMHGb6mMtz0MLS6qE1I/pCVV/ezfTt7kbtZWElsgtx9/GP7AlDKTGBCZEHSQlxRoLKdCb5S3OTK6dyaTue98FHwYtpRMzmf/x2+xVkuvUTycYD6xaU6XSSLEnWa0dvNeb4LyTWO0lu3drkGtWpd0yRB5hU0vdfcMQyEpU9EeB7XdgMUlwCPoCTLUZfE85UqHuz6NGTzkkv6lJ1Ub4SCll1LMStDE/+7UMzCywGq9BmwR8llAC366ZAmXC89sXcaTYgG5wuKQgsb3jyTxxtzNcH4oMv6Qi/uJUMZuXF6iXvbQrT3TtVCydCYqLs5oPm31wGqwUCgmnoMzZPUhz+UlFGelg=; 5:3Q1kyZ4XMy/eeH+gMpxpJyhsB0oVEhbTF5PmLLJSiHhneqMJLHGCWejmDgeEIQ8MJpS27cp1cQzc262q01iuYqIC7Tae/Z5N65WScaNREb4o9l+n9lMUZ11urRvN+jS+xhmXH1qEitvPMV3OdSJadoJ+UAUxx4pq6A4rlhpzYj0=; 24:gMDSmAzSMDC/Em8H/FOliSYkl9XTpwdTM3Hqoj3L5Vwa5IwZMTYoD3mZPDVksMLys4tWZhxyspeJ/3Fc3OeLP9i2ZdgmDTHxMoyQvgnwLAo=; 7:oORQCLAQIoGdG1H8q+tkAneqtQZg+0l3AkNdYd+dTdlajHv3EePRYt2kKuoaxzph5DwKY96wLgL9aAZBRiYC2N6o7kqTwFy5SH8XVcQJwhYSjNBIahpSncHbt6pklokKUSNEXzfepyh8+b5wGKYX+/Uq4SGu4PIOEHC69JiEFMOOrnL2zMM69okQm78N1jGe6OwE23AGwl7dxMvBmxlQbgXdP0XYTaS6MzYKAVkzZEQZqEL2WyAzIqJkgZqgrPBi
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Nov 2017 08:43:24.1483 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 74067b82-d943-44f5-c645-08d524f27187
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR07MB0633
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCKsWRmVeSWpSXmKPExsUyM2K7n+46BYYog5NvDSzmfF3NZvHqxU12 i2cb57NYzPhh4MDisWTJTyaPpjNHmT0mfjzD7LHqzhfWAJYoLpuU1JzMstQifbsEroynLTsZ C85zVeyfP5+lgfEIRxcjJ4eEgInE3gtd7F2MXBxCAocZJVrX3WEGSQgJHGeUWH7FGyTBItDL LPHtzERGiKpWJonVm5vYuhg5OIQFwiUeLNAFaRARKJF4t2kLE4jNLCAhcX3COyaI+v0sEnta F4NNZROwkNhy6z4LiM0rYC/R1LCJEcRmEVCRWLF2JZgtKhAjMfHBRUaIGkGJkzOfsIDs4hSw k/h3uQLEZBbQlFi/Sx9ilbjErSfzodbKSzRvnc0M8ZiCxP4fK9kg7JmMEhvO+UH8pS2x/FkL C0RcVuLo2Tlg0yUEfCXWfvYBuRisfEfLfKg5DewSq27GQNhaEkcaJrOD2IwCiRJ/771lg2j4 wSbR/+Mi1FBriVXrj0HZ2RLHpq9ghii6wiqxY/ohJoiEjETP1bPMExh1ZiF5cxbCb7OQ/DYL yW8LGFlWMYoWpxYn5aYbGemlFmUmFxfn5+nlpZZsYgSmlYNbfhvsYHz53PEQowAHoxIPbzsf Q5QQa2JZcWXuIUYJDmYlEV5nFqAQb0piZVVqUX58UWlOavEhRmkOFiVxXsd9FyKEBNITS1Kz U1MLUotgskwcnFINjBvnrfbwidjx/9CW1WfsQiduODBBWlAg2z2q7M6b6HR2a69Jii+UO0pe aHus2hv69eP5DWWXV8fPjuVvknOoNFPMvpC4IzDyj+b7kJoOPv472vOVsnb61864a3RJ6j67 m6oLM/efWcdXLhL0XNe575lQ18rI5ScWZ1zRmTg578xXqfyfIkl2R5RYijMSDbWYi4oTAXL7 qbQnAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/As-GXo-dZlcibzEYoDAtzzfocBU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 08:43:30 -0000

Hi Richard,

thanks for your comments. I am very much aware of the activities of
the SIP Forum ;-) Thanks for your work during all these years.

A couple of comments inline:

> Stephen Farrell is spot on in having some skepticism about mission
> statements.

FWIW, I myself am not a big fan of mission statements
either. Nevertheless, getting staff, the board, and the different
communities to think of what ISOC should stand for has been useful,
IMHO. As I mentioned elsewhere, in addition to the work on the mission
statement, we are also working on defining the scope of ISOC's
activities at a more detailed level. In fact, we are working on the
three pillars (communities, technology, and policy) and discussing
what should be the scope of engagement in each of those areas.

>  I’m not saying ISOC shouldn’t be involved in implementation and
> compliance issues. It could be very useful in kickstarting efforts
> by specific protocol communities in self organizing if there is
> sufficient consensus to do so, but acting as an overall umbrella for
> such efforts IMHO is not the best use of ISOC resources.

I personally agree with you that ISOC can be most useful when involved
in kickstarting efforts. Currently, we always look into the
sustainability of any effort we choose to initially support.

Cheers,

Gonzalo


From nobody Mon Nov  6 01:17:59 2017
Return-Path: <gonzalo.camarillo@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 5A60913FB57 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 01:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 ltw_P3p1gQPz for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 01:17:56 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 D7C2B13F963 for <ietf@ietf.org>; Mon,  6 Nov 2017 01:17:55 -0800 (PST)
X-AuditID: c1b4fb25-debff70000000c94-57-5a0028c197c9
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id C5.88.03220.1C8200A5; Mon,  6 Nov 2017 10:17:54 +0100 (CET)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.45) with Microsoft SMTP Server (TLS) id 14.3.352.0; Mon, 6 Nov 2017 10:17:53 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ZXiCE7I5kuI5XlU8tdZ4Jwv0SGFtj0baYk4wlSpYTBY=; b=UW2mbPoPmiP8hou66vFJtpoze0bP3AKlgF+ntQv6luOB02vjS1qmQhpdNrJWj5y8SKePXiW+6dGVG1LJVKfwQCA+NDgohoeg+4mOQvieT6gexeWMLOyEIlOQpMwj+wZnwu9V7/hHcc3r+J3MXznVsiBfSlDrybgksFKrRjUuU9c=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
Received: from [192.168.1.7] (37.136.86.88) by AM2PR07MB0628.eurprd07.prod.outlook.com (2a01:111:e400:840d::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Mon, 6 Nov 2017 09:17:51 +0000
Subject: Re: ISOC money, was Proposal to revise ISOC's mission statement
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, <ietf@ietf.org>
References: <6.2.5.6.2.20171027150629.11739938@elandnews.com> <20171028104008.14206.qmail@ary.lan> <6.2.5.6.2.20171029091040.10c4b4a0@elandnews.com> <20171029213436.htd2r2rrtz34fvpp@mx4.yitter.info> <d2e6abfc-218e-26f7-63a6-3995b8c37bfe@gmail.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <5819f6e8-2d5d-0202-7ab2-ca1d5a405d09@ericsson.com>
Date: Mon, 6 Nov 2017 11:17:45 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <d2e6abfc-218e-26f7-63a6-3995b8c37bfe@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1P192CA0012.EURP192.PROD.OUTLOOK.COM (2603:10a6:3:fe::22) To AM2PR07MB0628.eurprd07.prod.outlook.com (2a01:111:e400:840d::27)
X-MS-Office365-Filtering-Correlation-Id: c3a12ec2-1049-48fe-56cf-08d524f741eb
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:AM2PR07MB0628; 
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0628; 3:nU96bR/LxrQe2fHCaQNmt3irwBPr7HjqtokBjClR52FO92Hd9IofYcgISj1A9VbDZJ87t2EKB+45do8fln8FeIq30b3HZQtI+mRd3/+yO6AGnKi8Zo6XOM7qUfA53fFhtFKXpLL/YIEXoTJwagWWhBI3xjO4+4dGD0DEi66owf4ZnrMKw0P+YVIdN5TOKGWlnUg3QdriY6JR/YkYPkbp3YCvBxk191Kqjv0vEGTU3C83hJwoyLSFK9G+VNXSU0My; 25:i06uJ37tFqBbxXUcJQe+RMzkDiL7CF45hXSbkdPIZFaLDcbxRPEZWSS523QxtYgqsjR+LUE/IP+N5Tv7UUtSH2TVsdntUTdPx0dinUC7qHPBqIzmXF8FikrbFOD6tdKXu78F+NtFu/gY/WFjgkPXworBSnqi79TjmGQGkIWXt2N3JCBiHZVoxEH/b5xXt3zGHjGm6y2QoCO+OPyXCTLs+Q9mQYCymunE79HQbeG1mbzZGpTan6+tKegCMCrlTeqrwo8N55AFmpzEFk4ktHkKEA3lrQDzpsXNwcIndHeYbuue7CX8dYsTjr4/mFs+TIqowxRHkuGdDPVUVaL7PFhw/w==; 31:EfQn3S9QFS9HTL3pAJXeGyFhAZpjm/mMTmih15a5dQCx1ftUYBoRjPShpV70/5nZyNQo0DtqYSbVCtHi1oLR8ssSRdEx2rB2rQiikseXO+Igl8HodlLa/jNm5pX+RQ+sTgYJOdv1XUpS4+h3K24cFqNcHxpOw+gEL2tCcBjmyiwJzrp40OPtqiWGOPzGMcHZ/B5zUVCn40fNBs9W2rtbxoXsMoYXlu67Wc52YkwlfxE=
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: AM2PR07MB0628:
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0628; 20:u087ZeOEIlGJ9tynzUAprzXA5E6+aKjPjAYnE6IOIlhlzQqoJOHDnmk8ArqnO5o4pnH09TgHE7JybEXGxWtpu3Y51ydFzxJjUuMuc1L6QWvXJoTPLyTa/cfoAVdJKa3X+f4TjcWnB9BfQKfnq6zSaRdO9kVSOPitg9A5eR1RXjqT2fo8CgZzIh16y9wuwURhvse9ujFU8xSvQjbnEMgIxS5XKqBXXHCmkqjYqdjcVkywgGAD36k8Zg7p1GU1sPJHWa8YhJRJ6c8FvQj4ESWj7IE05SiM3BfGTVElfq7DkGf3ez4boaZjaR5+1nxBQ38ewdWo+Fw3rHo1WrFIRObpw8HZH1RfPyYRDZzX67Mye9bTPlhARVlD9lPRFfm/cAikXedBOVQrLEtK3qwzYpeIT9IOJJejyLZklpoqHxpLPQ/99mZVKFFGOkbZfawo3vSqxf42ZyC68C69TqLKdstXt5v03D5mSVi0FqxFpiBhLJF4rFSOvk6wwEE9mLFPDMaH; 4:mJscCn73i07a3R4ZEBwopqzM3Ghjm7os4aLLCPuJUQzTKQs6+s3bkzy+mHdZRJw8Gp33HIArauE0v7TGa5iECWrXaZuWwmWD4hEs/t9axhWgP/gu9Y5RfpozULHf11Byj9ma4wRknzlhxGhDBkZYRWpX5kRH42u9A/BuVvP5zUgotpCsknMS2izsPEBLwEM05kkz2SD17D0U2VYku5Rh5wyZc4vVpUlMtbBlCk72NM7iqrQ5XhSViCtTPn6IObKBE832Wvg4OmBOxA0LOO61GWkj6YRyXjqrU353RhbGGnm6W3gCRAMJegQid7Pd8AuCYzBewgN5BIQH+q0gz4X5oLDl5uTrtCATp6Lh0OuPpHM=
X-Exchange-Antispam-Report-Test: UriScan:(81227570615382)(275809806118684);
X-Microsoft-Antispam-PRVS: <AM2PR07MB0628A189013B2AFC55C2691F83500@AM2PR07MB0628.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3231021)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123558100)(20161123560025)(20161123562025)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM2PR07MB0628; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM2PR07MB0628; 
X-Forefront-PRVS: 048396AFA0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(346002)(39860400002)(376002)(199003)(189002)(47776003)(77096006)(316002)(16576012)(93886005)(230700001)(66066001)(110136005)(6486002)(58126008)(86362001)(65956001)(65806001)(23676003)(65826007)(97736004)(83506002)(966005)(36756003)(229853002)(5660300001)(478600001)(31696002)(54356999)(76176999)(50466002)(6246003)(8936002)(117156002)(8676002)(101416001)(31686004)(6116002)(50986999)(53936002)(25786009)(68736007)(64126003)(16526018)(6666003)(7736002)(105586002)(305945005)(2950100002)(189998001)(33646002)(3846002)(106356001)(6306002)(2906002)(39060400002)(81156014)(81166006); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0628; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTJQUjA3TUIwNjI4OzIzOmpDYitwV3VjZmRHVFIrd0dGT1U0V0UyNkxT?= =?utf-8?B?Y1I0Qi92RE5OMktEQW9xaWZucllHeFhuZDFXMi9TYW1TMWZWc2RsS2hqOFVE?= =?utf-8?B?dG1vZmNPbjNQQ3BVb2dCL1k3VnMzVmZNN3A3YURJMkFaOXhtY05KSHZFd0JI?= =?utf-8?B?dVBVelFpZVowS1JTNXRCaUhvQkVtVDFjZGxQZEIzYXkwaFJlNEV4dElJeG9p?= =?utf-8?B?MUVGKzZwRTR5M0JqSUpDU0Voa1Fhb1NFQ1d6OHhmRm5TTDN5b2krWnZhbFM5?= =?utf-8?B?OTdBU3hBZVpLY05RVDVTeURicWhnd0VFc3A1Rk5STTdPSjduK0Z1NGRON2FN?= =?utf-8?B?WEphZW9uaGU3eU9hVXFGM2N2S1I1OG5lZ0pDOVR3djJFRDgvVFk0N3piZlRw?= =?utf-8?B?cVVwNGZ5MHBQUlFpRklhZW9YZ29kazNDbWEyTFBZZmNGMDlFanFLcTNnbFoy?= =?utf-8?B?TVIzTUdVZTlTbVJqbW91d0VGKytVM0F6MTR3QXRIRU41VHJOSjgzY3FsN0Nv?= =?utf-8?B?UUR5R1hGbXFEVGhhWC9PNjk1TEFPajc4OHh0SENSMnB3L2g4VWxxbHpqUEgw?= =?utf-8?B?TkRUQThCMk1BTVJDVmt1VlhSOGxYVTBmM1I1VTV4MDhPNWxuWXduL0R1R1k2?= =?utf-8?B?MmNxdXI3bklmSmZTUEFhTDR6RUErL29oNDFKQ2NzeWtZZG9LMEdtSlNlMTVu?= =?utf-8?B?b0pyRVVmaForT29rdjBxem5WRllXUU41R3lTQ3E3ZUdvd1Jjc2Q5SC9mZm93?= =?utf-8?B?M3pZQTZUN2tNQXRuc3hCZTQ4YVkyd0Y3VUlIbXZQS1Y1UWZmUTB6OU5YcktY?= =?utf-8?B?WE9oWEZ0RkFRMXVvaDZUeDBUOW5rWUpUaldqQ05JeDBPSFAvaW92b1pNM1Jq?= =?utf-8?B?V2NwQ0xJTTF4TEp3NjF2akNuR3ZLVFV2QWtZRk1vMThQWnZ5STBtYjRSTHJM?= =?utf-8?B?czlvcjB0UERzaXJVbEVMUHJDS3hab2FHTWRlbkRXeFhraXozVE1RaFdEQjVF?= =?utf-8?B?NlV5SjJiQ2V3b2JhZ0tnMXVid0M4QzcwSUtTWnY5Ykt0anpBenc3M2ZneUY5?= =?utf-8?B?cklEVHJoZzg5by9qR0dmU0h3TlArSXhRMHVWbUd2OUlmVUVYaklWNEY4T1da?= =?utf-8?B?TWVaLzM4K2JxcGJiUytVWndLeVdRaWxpQ29FRDQ4cHF0K29Qdm5qdTA0cE5S?= =?utf-8?B?WU1YR0VZUkhIRUQ1dFdLUEtoa3BHVnYvZGZyWXpITUlVdWRBSHI3azlKbmZn?= =?utf-8?B?a0hCREY3cHl1YUhzT3lsME05ZTdTeC9jeFVmM3FRMjllSkgxSTI3OVUyVHJq?= =?utf-8?B?QmxHZis1Z2JkaW9scDRHYmJZV2JHbHoreW5lczJWMWU0UUVwaUdSSmhpVlYv?= =?utf-8?B?ZHhTa0hsNjN3R0gzeXpnUFFNcmVyUmdjZmI4UkJJSUh6NjhQa01wMnMzaDUy?= =?utf-8?B?a1BSTWFMWVBVVDNZblAyQUY1NldWa0FmTlJtR2VtUTFuUGFYUVh6L1V1Mno1?= =?utf-8?B?ejk1Tkd6UVJETWVGU2hNWElaNXk0T0NMdkdoOEpVUndoYkttMW96eUdVUFVT?= =?utf-8?B?MVEwMWE0OWJBZ0lWclYyZXJxVFI3SW03QmZKQldrRjJlenpHT2l1OUYyZlQ1?= =?utf-8?B?Qm1YOEUvUk96TTNjZWNhSzBHeFZIa0sxQ2hlQUFhNlZRY2dXWW1FSHIxTG1V?= =?utf-8?B?TmJ3V0pmOE4xd0QxR3E2NWl0SXdUcHFCd0x6STI1RlUzOXM1VnRxeFlYallO?= =?utf-8?B?VExYcTVFREttTFJOV255eWlUMTM1Zk5BUzU1VnNNTVR6b1dZZi9OSGhVK3hE?= =?utf-8?B?bE1rWlREVlNEckRoaEQ4SmQ0T2dVLzY2a1dRZmdqVE5aNEMrS2g4VEdBSnJp?= =?utf-8?Q?KPtCMorPkzU=3D?=
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0628; 6:qsMIrtgCh3uT+eT7AAwwOIvENLzLsYOuLN2MVB4WzCotBvzasTcuQ9BkOuFK/8w36ykoiEdwBtpGxfF7ILmJZldxt8wVzTg8Wyt25j8bH0BfJYkhFKYzCu09zY4S7i5HrthpNklXOvHVQNIp0wLDbLgg2GwqwL6rVCufSj4EXE2T3T4Z1aBeme9oJq41eEYe56ga3gVk58a1a4L/W5vkj1tCymwHrm2+5qGPRce6c56Z/KF/nS1g16Fgzt37fVA5Y2BvcIIJ3Gt0bhcfSgtoM9wRlHIlo1Nx0daZvQxd+ioG98hJFr9Ntbxv2Dkx6XhvFmg0Up+lmBpXEgPQ+gZrcXvbDGJnLZjUalI+qwIev5A=; 5:jJUVGL2KRO4FN38jDyBJ6CRG5C27gtPAKMk/6YkaD6bUeHsg4tBdjvxgjTpk4OtcSfa4MnJw4eG/t3AvCuOZtGTaLuwWKH4m/vAsR/JIkNtgoP2O1MHfiEXG2ou+OaAJNGthoYY6UF2CndL6JlXbHfGKPvwXnIR1qJvaxpdgbm4=; 24:oubrzd7f5VIBu0PEoEVrcy7+7j1psiJgt2Zsfo6JTEMdQFFCYLGto4gd2OB3mTg5d22WOQQuyK3db/Mw+k1DS2DR+LPPOA+7Ivznxf9ljXk=; 7://TG2z3I1hnkdz6aqoll7h6u6obClph+d8edm0q6iuoYTgLpRAHyZsaL3h937j5OZmmTknUiBbIQX7+bewgH3NnIlfc/+TbZ92vrh+bA49MHYx+IvmNuOstQbxmCiJkLt+A+SKvtnbzxO7hH1lg3fmFR1vGGFjNKWwLyMbt2tbCqP2X2qa/gpb+tyFHZxZzHFWUt7C9Qea79DEz+jPYzRZXv12nEbxHVUi0pkf49+Y0uMZ/7jWDiSl8mEl3Kek8T
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Nov 2017 09:17:51.9882 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: c3a12ec2-1049-48fe-56cf-08d524f741eb
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0628
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42KZGbFdV/eQBkOUwb8NTBYHPl9jsmi7uI/J 4tnG+SwOzB7PTr5i99g56y67x5IlP5kCmKO4bFJSczLLUov07RK4Mu7+0C24zV5x685y1gbG uWxdjJwcEgImEs+OtgDZXBxCAocZJY4e/McO4RxnlHi6+BgjiMMi0MsscfbTQrAWRoFEib/3 3kK1tDJJHP+7nxUkISzgIdF6ZxZQgoNDRKBAYtm+Uoia/4wSLYcbmUFq2AQsJLbcus8CUsMr YC+xYK4OSJhFQEVi3olnTCC2qECMxMQHFxlBbF4BQYmTM5+wgNicArYStxYsZgJpZRbQlFi/ Sx8kzCwgLnHryXwmCFteYvvbOcwQnylI7P+xEuxMCYEpjBI37n5kB0kICWhLLH/WwgJR5Csx f8YZRoiimYwSy1ZPhUo0sEusfWIDYctKHD07ByquJXGjYQELRMMSdolZBzawQiS8JaZ1X4Uq ypb49OYfE0TRFVaJ5yf+QiVkJHqunmWGSHxhlei7d5B5AqP2LCSvzkJ4bxaS92YheW8BI8sq RtHi1OKk3HQjY73Uoszk4uL8PL281JJNjMBUcnDLb9UdjJffOB5iFOBgVOLh9edjiBJiTSwr rsw9xCjBwawkwrtdHSjEm5JYWZValB9fVJqTWnyIUZqDRUmc13HfhQghgfTEktTs1NSC1CKY LBMHp1QDo3JB8HW/lC/Re14p6fHW2/FNTFe23fAvS0j1WL5SxWmJdVIdzanRYZxGM1hDXqz8 FXIy686rk6tyDuvVVblJNHxPM7p9+8/sRSu3cfYtn2vjVjk9SUMj4pKKbkLyyU7LK8x/82cy /w1xzsjaffLmjD7xj5tZ19dPP3hgZ6/isfTtRUrh5l8dlFiKMxINtZiLihMB12d67SEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VcrvmZ8tx6A19oVX19V3-AeQ7ko>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 09:17:57 -0000

Hi Brian,

> isoc-members-discuss@elists.isoc.org seems to have gone silent a long time ago.
> Maybe they use this new "Facebook" thing I keep hearing about.

Just to close the loop on this topic and to point people in the right
direction (to discuss ISOC-related topics that are not related to the
IETF).

ISOC staff is looking into how to involve ISOC individual members in a
better way in general. For example, as you know, we have organized
several open board sessions where the community could talk with the ISOC
board. While the situation is improved, we distributed my original email
(about the proposed mission statement) on the list below as well:

  INTERNETSOCIETY-openforum@ConnectedCommunity.org

ISOC members can manage their subscription to this list from the
following portal:

  https://portal.isoc.org/

People from an ISOC org member or from a chapter can obviously also use
their channels for those types of discussions.

Cheers,

Gonzalo


From nobody Mon Nov  6 01:37:25 2017
Return-Path: <samitac.ietf@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 094FA13FB7C; Mon,  6 Nov 2017 01:37:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Samita Chakrabarti <samitac.ietf@gmail.com>
To: <Iot-dir@ietf.org>
Cc: lwip@ietf.org, ietf@ietf.org, draft-ietf-lwig-crypto-sensors.all@ietf.org
Subject: Iotdir early review of draft-ietf-lwig-crypto-sensors-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.64.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150996104393.8207.2811572203550087788@ietfa.amsl.com>
Date: Mon, 06 Nov 2017 01:37:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aEwV7enVpJ2c8bDQSC3o0DciDoY>
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, 06 Nov 2017 09:37:24 -0000

Reviewer: Samita Chakrabarti
Review result: Ready with Nits

I have reviewed draft-ietf-lwig-crypto-sensors-04 document for  IOT-Directorate
review. The following are my comments:

General : The document is easy reading and informative about current and
previous work. It is ready to publish with minor changes based on review
comments.

Other comments:
Introduction:
 It might be useful to discuss/clarify that multi-level security may be
 important for IOT devices  all the way from 'bootstrapping and management' to
 application security. That perhaps can include obtaining IP-addresses
 securely, mutual authentication between server and devices , etc. ( see
 https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-03) in those cases where each
 device has an IP address.

Section 2:
Regarding problems of provisioning and management of networks for the IOT
devices there may be additional issues – 1) different types of IOT devices and
the lack of standards way to provision them as they might be talking different
RF technologies and running L2 protocols only. 2) The iot nodes may be moving
individually or collectively and change networks; identifying the movement of
the iot nodes or identifying a particular node at any point of time uniquely
requires an intrinsic identification which might be useful to set during
bootstrapping of the node

Regarding related work – does it consider IETF IOT security work only? There
have been some work and thought process going on regarding blockchain IOT
security in the industry. Perhaps that is out-of-scope of this document, but I
wanted to mention for authors’ considerations.

Section 5:
Authors of the document may also want to browse a SRAM PUF based technology
which provides unique ID based authentication mechanism.
https://www.intrinsic-id.com/intrinsic-id-joins-wi-sun-alliance/

Section 9:
Does the example simulate any particular deployment model or research
experiments ? It might be good to clarify that. Section 10 and 11: Looks like
section 11 is closely related to section 10. Should they be combined together ?
Else some more text is needed in section 10 on design trade-offs.

Section 13:
Does this document recommend one layer of security to IOT devices ? There are
different types of IOT devices – some of them are very tiny and some are more
capable. Some definitely benefit for multi-level security  than single layer of
security.  L2 security is generally recommended for for all IOT networks. Does
data object protection only protect the  application data (payload)  or more ?

Thanks for the initiative in documenting the valuable work in IOT security
implementation and crypto comparison. -Samita



From nobody Mon Nov  6 01:39:29 2017
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B21213F963; Mon,  6 Nov 2017 01:39:17 -0800 (PST)
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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.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 8dSfZUkvDpet; Mon,  6 Nov 2017 01:39:15 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0087.outbound.protection.outlook.com [104.47.0.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 94F3513FB7E; Mon,  6 Nov 2017 01:39:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=+2KCbmxqlLiids561RvgYcArmDVgqcRLqNGi7HeVWmg=; b=Hv71ItEWcjDnDAQwYloXgcSozNuT6W89OymQkeIZmZYzEppkBar7OdRXG5f+YlNlmhE2biwdIjRLQx31WuGquebnqp3ITuTes3hESwDBV/UwDmBjUsq2Y4Ucge8E+G5etpPceLsKgimvnXLMhieGfm71PGBQq9eh8XA7E8wKbjs=
Received: from AM4PR0801MB2706.eurprd08.prod.outlook.com (10.167.90.148) by AM4PR0801MB2706.eurprd08.prod.outlook.com (10.167.90.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.197.13; Mon, 6 Nov 2017 09:39:08 +0000
Received: from AM4PR0801MB2706.eurprd08.prod.outlook.com ([fe80::403b:850e:c32c:fad6]) by AM4PR0801MB2706.eurprd08.prod.outlook.com ([fe80::403b:850e:c32c:fad6%13]) with mapi id 15.20.0197.017; Mon, 6 Nov 2017 09:39:08 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Samita Chakrabarti <samitac.ietf@gmail.com>, "Iot-dir@ietf.org" <Iot-dir@ietf.org>
CC: "lwip@ietf.org" <lwip@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-lwig-crypto-sensors.all@ietf.org" <draft-ietf-lwig-crypto-sensors.all@ietf.org>
Subject: RE: [IoT-DIR] Iotdir early review of draft-ietf-lwig-crypto-sensors-04
Thread-Topic: [IoT-DIR] Iotdir early review of draft-ietf-lwig-crypto-sensors-04
Thread-Index: AQHTVuLgMbcCfn77r0W39rAq/y/2u6MHGB4A
Date: Mon, 6 Nov 2017 09:39:08 +0000
Message-ID: <AM4PR0801MB270650AF0ED72FABD13EA028FA500@AM4PR0801MB2706.eurprd08.prod.outlook.com>
References: <150996104393.8207.2811572203550087788@ietfa.amsl.com>
In-Reply-To: <150996104393.8207.2811572203550087788@ietfa.amsl.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=Hannes.Tschofenig@arm.com; 
x-originating-ip: [80.92.116.199]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM4PR0801MB2706; 6:+R6oRnp7NEap43BUFjKHcdJRVbLFfxazmrW3D03JXhP7b3At2JjezJ2EACVPlVwxuP7Knoi9k+2rq0m1OMD0ZRnhLQujhLF+suV3BlIUphQ7w59AJTr0JQNW3G3wYjn5qiv2wX9SiiFxUZu04NgZRowXjxQbldHbJSy/mk/WVk5sQyLY5r3mskC6Bb6NQWqLap3gaecj5oRj57DUPDmyDhc3zcQqwQW8TY9apznbO/6Oo7VDdNxBsSWMNVvouKI6OFRkw4YHg7uohGz+btT3KjO/WnNwAjiqEp3hIBk1pxqZlcfXFJEYQM2CfeV2fLT62WZSN04N8Q2kWJ/zMOqykrHU478rs+x+meu8C2D7ODA=; 5:xjgwdOnZLagLbpX7KTGa7pYMZN7x78fGb3a1mTIIyElJ/D0oqan1SvsSFKWDab3M6EDi+PGEOqXxaAIOCP1cSII/MOksqkTubtOBaS8wX+1GOha95F063AG4D3AB942dzQ8d1Cn9tkn5+xrcjC9r0Lu495tkAFNMCXwCeVLeSZY=; 24:w/jCI4gfZYoOcJO7+LXBcI9GPVaNJ3pL8gVCWpT5P2P3T6B/wTwItPLhFkq2Hho86r+M017psoTAYP0f1npFzdkL9x129xG26TqXV+jWBiE=; 7:vgJLh/GOaFQPmPY8V8ZrMsXpvtYh2NXwSl2wNNm3fl1gevUalWe9HkOZUuNO3SYbk/oD3NjkU5p4/qsCTjoFdPUJEqekrRrF2c+2HGDlIH5cJo+R0FI753EicIC9mgpbIz18DYa2H1OHhe8NvoF1nHgz4mMEAdQjMtFBlNJ5zzG+WtpRS5EycT4XmGov/pXpIE0oCRG3cZTTUIB+Y3DjNWMPsHCJLbCD/IMhsT2jjW+P+lAEIrpok2kgqgsHuW2r
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 1c061b76-a89a-4153-45be-08d524fa3a5e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603249); SRVR:AM4PR0801MB2706; 
x-ms-traffictypediagnostic: AM4PR0801MB2706:
x-exchange-antispam-report-test: UriScan:(158342451672863)(192374486261705);
x-microsoft-antispam-prvs: <AM4PR0801MB2706B5C154753FCEFEC49795FA500@AM4PR0801MB2706.eurprd08.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(100000703101)(100105400095)(3231021)(10201501046)(3002001)(6055026)(6041248)(20161123555025)(20161123560025)(20161123564025)(20161123562025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM4PR0801MB2706; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM4PR0801MB2706; 
x-forefront-prvs: 048396AFA0
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39860400002)(346002)(376002)(13464003)(189002)(199003)(51914003)(40434004)(229853002)(230783001)(54356999)(966005)(6436002)(2950100002)(72206003)(3280700002)(101416001)(25786009)(6506006)(106356001)(105586002)(4326008)(478600001)(3660700001)(33656002)(14454004)(6246003)(189998001)(53936002)(53546010)(76176999)(68736007)(2501003)(54906003)(110136005)(5890100001)(99286004)(66066001)(2900100001)(81156014)(5250100002)(6306002)(55016002)(74316002)(97736004)(305945005)(7696004)(8936002)(81166006)(316002)(8676002)(3846002)(102836003)(6116002)(86362001)(5660300001)(7736002)(50986999)(39060400002)(2906002)(9686003); DIR:OUT; SFP:1101; SCL:1; SRVR:AM4PR0801MB2706; H:AM4PR0801MB2706.eurprd08.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1c061b76-a89a-4153-45be-08d524fa3a5e
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Nov 2017 09:39:08.1380 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR0801MB2706
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p6VWZKLd6m6tl964ONzyGe_nD9g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 09:39:17 -0000

SGkgU2FtaXRhLA0KDQpEbyB5b3UgdGhpbmsgUFVGcyBhcmUgdXNlZnVsIGF1dGhlbnRpY2F0aW9u
IHRlY2hub2xvZ2llcyBmb3IgSW9UIGRldmljZXM/DQoNCkNpYW8NCkhhbm5lcw0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSW9ULURJUiBbbWFpbHRvOmlvdC1kaXItYm91bmNl
c0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFNhbWl0YSBDaGFrcmFiYXJ0aQ0KU2VudDogMDYgTm92
ZW1iZXIgMjAxNyAxMDozNw0KVG86IElvdC1kaXJAaWV0Zi5vcmcNCkNjOiBsd2lwQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnOyBkcmFmdC1pZXRmLWx3aWctY3J5cHRvLXNlbnNvcnMuYWxsQGlldGYu
b3JnDQpTdWJqZWN0OiBbSW9ULURJUl0gSW90ZGlyIGVhcmx5IHJldmlldyBvZiBkcmFmdC1pZXRm
LWx3aWctY3J5cHRvLXNlbnNvcnMtMDQNCg0KUmV2aWV3ZXI6IFNhbWl0YSBDaGFrcmFiYXJ0aQ0K
UmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBOaXRzDQoNCkkgaGF2ZSByZXZpZXdlZCBkcmFmdC1p
ZXRmLWx3aWctY3J5cHRvLXNlbnNvcnMtMDQgZG9jdW1lbnQgZm9yICBJT1QtRGlyZWN0b3JhdGUg
cmV2aWV3LiBUaGUgZm9sbG93aW5nIGFyZSBteSBjb21tZW50czoNCg0KR2VuZXJhbCA6IFRoZSBk
b2N1bWVudCBpcyBlYXN5IHJlYWRpbmcgYW5kIGluZm9ybWF0aXZlIGFib3V0IGN1cnJlbnQgYW5k
IHByZXZpb3VzIHdvcmsuIEl0IGlzIHJlYWR5IHRvIHB1Ymxpc2ggd2l0aCBtaW5vciBjaGFuZ2Vz
IGJhc2VkIG9uIHJldmlldyBjb21tZW50cy4NCg0KT3RoZXIgY29tbWVudHM6DQpJbnRyb2R1Y3Rp
b246DQogSXQgbWlnaHQgYmUgdXNlZnVsIHRvIGRpc2N1c3MvY2xhcmlmeSB0aGF0IG11bHRpLWxl
dmVsIHNlY3VyaXR5IG1heSBiZSAgaW1wb3J0YW50IGZvciBJT1QgZGV2aWNlcyAgYWxsIHRoZSB3
YXkgZnJvbSAnYm9vdHN0cmFwcGluZyBhbmQgbWFuYWdlbWVudCcgdG8gIGFwcGxpY2F0aW9uIHNl
Y3VyaXR5LiBUaGF0IHBlcmhhcHMgY2FuIGluY2x1ZGUgb2J0YWluaW5nIElQLWFkZHJlc3NlcyAg
c2VjdXJlbHksIG11dHVhbCBhdXRoZW50aWNhdGlvbiBiZXR3ZWVuIHNlcnZlciBhbmQgZGV2aWNl
cyAsIGV0Yy4gKCBzZWUNCiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi02
bG8tYXAtbmQtMDMpIGluIHRob3NlIGNhc2VzIHdoZXJlIGVhY2ggIGRldmljZSBoYXMgYW4gSVAg
YWRkcmVzcy4NCg0KU2VjdGlvbiAyOg0KUmVnYXJkaW5nIHByb2JsZW1zIG9mIHByb3Zpc2lvbmlu
ZyBhbmQgbWFuYWdlbWVudCBvZiBuZXR3b3JrcyBmb3IgdGhlIElPVCBkZXZpY2VzIHRoZXJlIG1h
eSBiZSBhZGRpdGlvbmFsIGlzc3VlcyDigJMgMSkgZGlmZmVyZW50IHR5cGVzIG9mIElPVCBkZXZp
Y2VzIGFuZCB0aGUgbGFjayBvZiBzdGFuZGFyZHMgd2F5IHRvIHByb3Zpc2lvbiB0aGVtIGFzIHRo
ZXkgbWlnaHQgYmUgdGFsa2luZyBkaWZmZXJlbnQgUkYgdGVjaG5vbG9naWVzIGFuZCBydW5uaW5n
IEwyIHByb3RvY29scyBvbmx5LiAyKSBUaGUgaW90IG5vZGVzIG1heSBiZSBtb3ZpbmcgaW5kaXZp
ZHVhbGx5IG9yIGNvbGxlY3RpdmVseSBhbmQgY2hhbmdlIG5ldHdvcmtzOyBpZGVudGlmeWluZyB0
aGUgbW92ZW1lbnQgb2YgdGhlIGlvdCBub2RlcyBvciBpZGVudGlmeWluZyBhIHBhcnRpY3VsYXIg
bm9kZSBhdCBhbnkgcG9pbnQgb2YgdGltZSB1bmlxdWVseSByZXF1aXJlcyBhbiBpbnRyaW5zaWMg
aWRlbnRpZmljYXRpb24gd2hpY2ggbWlnaHQgYmUgdXNlZnVsIHRvIHNldCBkdXJpbmcgYm9vdHN0
cmFwcGluZyBvZiB0aGUgbm9kZQ0KDQpSZWdhcmRpbmcgcmVsYXRlZCB3b3JrIOKAkyBkb2VzIGl0
IGNvbnNpZGVyIElFVEYgSU9UIHNlY3VyaXR5IHdvcmsgb25seT8gVGhlcmUgaGF2ZSBiZWVuIHNv
bWUgd29yayBhbmQgdGhvdWdodCBwcm9jZXNzIGdvaW5nIG9uIHJlZ2FyZGluZyBibG9ja2NoYWlu
IElPVCBzZWN1cml0eSBpbiB0aGUgaW5kdXN0cnkuIFBlcmhhcHMgdGhhdCBpcyBvdXQtb2Ytc2Nv
cGUgb2YgdGhpcyBkb2N1bWVudCwgYnV0IEkgd2FudGVkIHRvIG1lbnRpb24gZm9yIGF1dGhvcnPi
gJkgY29uc2lkZXJhdGlvbnMuDQoNClNlY3Rpb24gNToNCkF1dGhvcnMgb2YgdGhlIGRvY3VtZW50
IG1heSBhbHNvIHdhbnQgdG8gYnJvd3NlIGEgU1JBTSBQVUYgYmFzZWQgdGVjaG5vbG9neSB3aGlj
aCBwcm92aWRlcyB1bmlxdWUgSUQgYmFzZWQgYXV0aGVudGljYXRpb24gbWVjaGFuaXNtLg0KaHR0
cHM6Ly93d3cuaW50cmluc2ljLWlkLmNvbS9pbnRyaW5zaWMtaWQtam9pbnMtd2ktc3VuLWFsbGlh
bmNlLw0KDQpTZWN0aW9uIDk6DQpEb2VzIHRoZSBleGFtcGxlIHNpbXVsYXRlIGFueSBwYXJ0aWN1
bGFyIGRlcGxveW1lbnQgbW9kZWwgb3IgcmVzZWFyY2ggZXhwZXJpbWVudHMgPyBJdCBtaWdodCBi
ZSBnb29kIHRvIGNsYXJpZnkgdGhhdC4gU2VjdGlvbiAxMCBhbmQgMTE6IExvb2tzIGxpa2Ugc2Vj
dGlvbiAxMSBpcyBjbG9zZWx5IHJlbGF0ZWQgdG8gc2VjdGlvbiAxMC4gU2hvdWxkIHRoZXkgYmUg
Y29tYmluZWQgdG9nZXRoZXIgPw0KRWxzZSBzb21lIG1vcmUgdGV4dCBpcyBuZWVkZWQgaW4gc2Vj
dGlvbiAxMCBvbiBkZXNpZ24gdHJhZGUtb2Zmcy4NCg0KU2VjdGlvbiAxMzoNCkRvZXMgdGhpcyBk
b2N1bWVudCByZWNvbW1lbmQgb25lIGxheWVyIG9mIHNlY3VyaXR5IHRvIElPVCBkZXZpY2VzID8g
VGhlcmUgYXJlIGRpZmZlcmVudCB0eXBlcyBvZiBJT1QgZGV2aWNlcyDigJMgc29tZSBvZiB0aGVt
IGFyZSB2ZXJ5IHRpbnkgYW5kIHNvbWUgYXJlIG1vcmUgY2FwYWJsZS4gU29tZSBkZWZpbml0ZWx5
IGJlbmVmaXQgZm9yIG11bHRpLWxldmVsIHNlY3VyaXR5ICB0aGFuIHNpbmdsZSBsYXllciBvZiBz
ZWN1cml0eS4gIEwyIHNlY3VyaXR5IGlzIGdlbmVyYWxseSByZWNvbW1lbmRlZCBmb3IgZm9yIGFs
bCBJT1QgbmV0d29ya3MuIERvZXMgZGF0YSBvYmplY3QgcHJvdGVjdGlvbiBvbmx5IHByb3RlY3Qg
dGhlICBhcHBsaWNhdGlvbiBkYXRhIChwYXlsb2FkKSAgb3IgbW9yZSA/DQoNClRoYW5rcyBmb3Ig
dGhlIGluaXRpYXRpdmUgaW4gZG9jdW1lbnRpbmcgdGhlIHZhbHVhYmxlIHdvcmsgaW4gSU9UIHNl
Y3VyaXR5IGltcGxlbWVudGF0aW9uIGFuZCBjcnlwdG8gY29tcGFyaXNvbi4gLVNhbWl0YQ0KDQoN
Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpJb1QtRElS
IG1haWxpbmcgbGlzdA0KSW9ULURJUkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9pb3QtZGlyDQpJTVBPUlRBTlQgTk9USUNFOiBUaGUgY29udGVudHMgb2Yg
dGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgYW5kIG1heSBh
bHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQs
IHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgZG8gbm90IGRpc2Nsb3Nl
IHRoZSBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLCB1c2UgaXQgZm9yIGFueSBwdXJwb3Nl
LCBvciBzdG9yZSBvciBjb3B5IHRoZSBpbmZvcm1hdGlvbiBpbiBhbnkgbWVkaXVtLiBUaGFuayB5
b3UuDQo=


From nobody Mon Nov  6 02:34:47 2017
Return-Path: <gonzalo.camarillo@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 EABA613FB52 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 02:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 x4Wds_jxs1zK for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 02:34:44 -0800 (PST)
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 5A14D13FA82 for <ietf@ietf.org>; Mon,  6 Nov 2017 02:34:44 -0800 (PST)
X-AuditID: c1b4fb2d-fc3a89c00000268d-31-5a003ac20cd8
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 1F.D5.09869.2CA300A5; Mon,  6 Nov 2017 11:34:42 +0100 (CET)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.45) with Microsoft SMTP Server (TLS) id 14.3.352.0; Mon, 6 Nov 2017 11:34:41 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ov+GE3CgW987bjUCRnbur0xYA6z3cFwxQk+U+RULkpQ=; b=azyH8cCEBoG+xIGNjYKlvB8t61ocgZEKgRBNZnMGGQ2srbORPTNqFz8eo5PDj+m/7INDeb1qVZg2NRDlOHMrX6WjEgBmpZONWcq9g9s6dbxAff0ZkYda8JIQVlxYYLMc/KM3ps60di38S3oaIP1m5qTgcbpoyUwynH3Bha5Ns/M=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
Received: from [192.168.1.7] (37.136.86.88) by AM2PR07MB0628.eurprd07.prod.outlook.com (2a01:111:e400:840d::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Mon, 6 Nov 2017 10:34:39 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: Keith Moore <moore@network-heretics.com>, <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
Date: Mon, 6 Nov 2017 12:34:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR0202CA0030.eurprd02.prod.outlook.com (2603:10a6:3:e4::16) To AM2PR07MB0628.eurprd07.prod.outlook.com (2a01:111:e400:840d::27)
X-MS-Office365-Filtering-Correlation-Id: 49ca49b5-0d7f-4dec-a6ac-08d52501fc4c
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:AM2PR07MB0628; 
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0628; 3:Yij1d6Q1I+hCEy3frbjEZIqhtyB2qcWq1hCOHXgV1hipBy53UGd8X3AT5r7T3zKtdQOOZ314jw8b3yO4ioNb+1g5SHvaQCfynXFUU1VmdGk26TiKU8Kd0684x8KOwyQpkFZlkFUR72rFytYJxoQHN2iScB7ddaC9MnkGYdBM2xaJ3+EjzlHC0hWy386fOljuLXbsDccHbRk6Zii1Nzug55G06fZrn7QPLmL9Wg9GfxLRc5detSh6Cb6KtR2PFiRs; 25:BWOGNjwRBqMqBupBAlBr7MSQtM6uS2iNtkgkMq7OLC11UzpQVTKJboDyzp+wa6Lkf9niyy4h6dSWqcik9Rmei15JPFL+5biSCa3EhOIDjMnWXtqTrnQ6wzQtTlLAhjiTYQVeyk47hR2StsKqIixtyZ+XLhyys4FBuTUD9pMZIRMPAvyxn+w1uv9ILE6f+IW4hrj7IbaB9ITLDyRYr3S061IPItbCD1Wprc+U2DOYwdGm20+Dyn5Avy2woS+K0ciBc5Yu3U2iUYnkGWUB2yTOawToH6UZsKhG1Cs4IOdzxrulh1ny8EeO38x6iaNNRq6tCyeIagMX9PI0cKaIT+uI54OEiJL1zzfVzn/kIkD8g5I=; 31:ciTVSGVlj56P22/uGxRWXEePG6XxwlT9uubERX9bwp3W3xOvG4aCiNKhyS0lVpMdCEE6xMhArmpw0gyLwNtdHIiTZvFxNfj5cMJi8LzZ3EW9HrMiZtE86K1lxuKlNoWgTgijaLPfpG4ROquZFB/Oar/d8wCDiaa0TIBzMEqEmKfshSAO8xzv4kVBmI69kXoQEyRXALGZyi+ZNrnGf+HT80K0o4pGMTFcNbxVniUMQ5c=
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: AM2PR07MB0628:
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0628; 20:JVm59I07aCMsmGV2nZxvoY8ffNAaN4N7NbrJdLRpb+sxfTikbw3u5qVHoKePiiWI4NfOUytH32p2GziuuFQY4bH0rNIL0wW0F9PGr8zUHN+waG0Ba9dmwffPJu/O1WizC0zZpfBOcpG1vpRDKc/baSy/Wtb/Fgv2ysA+ykyuFdXx4FeRXB9rYuSrimu1Avi2dw9Yv8UPnHBJVOKGIhfyDNaWOv1kpa/UbLAfg82ZZiWAigSqcAfnhzIYDdcGk0Nzs+3RVDSCiBo8uWTE4ueguViFM/v1CkP6DOJGfpFgQWyb3Se3ZCRI0sUezt+R4HLZtQTDb0v0pgkWBH63ZNgSimAZlMH/5kUSCL/r3JM2MNH6XMnanwsx+Wt7wVtGrcw+Qrh+1CQyUQ3jhUMw3OzNzfoNXr9UN2ohRA1rV8GXf654rGxEOfFUUuBmtoNFgSYv5cd79U87tFbyAsEWsgEBUNWLsMc49Eu/Npeue7bELRV09uMqxXpQ7A3rstGZmVoG; 4:yofJ9G4QGiSzln4yictckR/OMwODWY8X/phmI8NrT3N83fB01s02yGbzSyWtMjQagXXaOTM1iunvcyWoTWx5pRpOnDkimiURKfhfA0L+s294B/1aqk1XfTv1wUlhK4SgtoRm6Ot6ITP7UJb3j3j5HjnPRflLiAqTCdjHUJdotFxVS8OY9LeY57CDyL/qN9ek5niOE8ST6+Bo4Qv2no/QNNupcQaSsnERT2gUNVARLlKOlaLHGetfeLYxrv1W2gzVR58MLAKYe7aSRhURoWQj5A==
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <AM2PR07MB06280893364AAE67F18F6DBB83500@AM2PR07MB0628.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3231021)(10201501046)(93006095)(93001095)(3002001)(6041248)(20161123558100)(20161123560025)(20161123562025)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM2PR07MB0628; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM2PR07MB0628; 
X-Forefront-PRVS: 048396AFA0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(376002)(39860400002)(346002)(189002)(199003)(8676002)(101416001)(8936002)(117156002)(50986999)(31686004)(6116002)(50466002)(76176999)(54356999)(6246003)(2950100002)(3846002)(189998001)(33646002)(81166006)(81156014)(106356001)(2906002)(305945005)(68736007)(64126003)(6666003)(16526018)(53936002)(25786009)(7736002)(105586002)(2870700001)(66066001)(65806001)(65956001)(6486002)(58126008)(86362001)(16576012)(77096006)(316002)(47776003)(93886005)(478600001)(5660300001)(229853002)(31696002)(23676003)(65826007)(97736004)(36756003)(83506002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0628; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTJQUjA3TUIwNjI4OzIzOmFnY1NqUm96ZG13K200UFQ3amkzdGVkamc4?= =?utf-8?B?Y1F1RThaVkVhRWhXU2d2NDBrV3JBZlhvenBwdkg5eWpqQUEweTNDUTNkdTlT?= =?utf-8?B?VzNXR0M4RzlzcXIrV25UVXh4MkoxeFByOStlVWc1eTdMWFhNeWJES2c3TmlV?= =?utf-8?B?RHdtMU9uTWNieFpXdEdGRWNvMHNCaXBid0dRMWdoYXZqS0txT2p0SDBpZm5t?= =?utf-8?B?ZkFIRVlDNStJOEVaWXFNSTg5YkNCNmhNZ1ZiQ1dPRjlKbEs3VDR4YllUSDRt?= =?utf-8?B?bno5TGtRQ3N2WURudEV3aHkxVy9KMnRqQUgxdFUzZHc1Q0xnMCtNcnlqM2xT?= =?utf-8?B?M3lxNWs3VkZ4cVhlR28rWG4zQVFvQXBNbDdua3JEZDVVemZud01sVTcrSEdx?= =?utf-8?B?UmhsK3Izb0ZCU1l1REM5YmVnZU5CRzlOMzM3YTh5TTJ5UDVLdEFVS1RwRTlw?= =?utf-8?B?RFZoMmVQOGFBN2IrcXpFVG9hdlpneEZBdEJKYXFyVWNKQktvNWFGVDlpVjhx?= =?utf-8?B?eWdvekd0Rm5uWDdrQkV5VXg3bkNiTStHSVNSdk03S3c2TU5ZRVRsWGhKRmJh?= =?utf-8?B?T3FaZHVwc25oTUptbkNISmJKS0NpY0U3MXJTV1NmanFEL3ZmY3Y1VXhRSlNH?= =?utf-8?B?OFpGeGl3VThGRk4rSDRuVlJBWW9CTnNqRVpSdmswTDdYUGhzUnlMMTlXMGZY?= =?utf-8?B?WlcxdkZtQzV2VkNHWVdSWUZHdWVVNzZDaW94anRzSlNvT2xZREpTZHdMSmhU?= =?utf-8?B?akZXSGNaQXpCWWVIdVRQSTN1Ukl1dlArS0thOWU3d3psMHhzN21iRmRnR0Z6?= =?utf-8?B?eWdkTGIwNkJjZ1BtVXIyTzhOKzMyQ0h4TEJHWjNiV0NabXhKb2wybDVsa2dJ?= =?utf-8?B?VHB6NDFuRFIrM0VlMjYwRGVnVjlHL0xpdllBdkYzWjdkTXhXWnplNk5wZHBC?= =?utf-8?B?OHZUVlg3RkZTTmVraWY2NVFtSExEdmRsOWIyUCtSTExRdGVpWktKSHFtdUNt?= =?utf-8?B?UUJrWGNrTHhxTmVtd1RrTUk2b0dtWlYrcFlaNFA5bVhNMDJqdTB4K2h0QVJl?= =?utf-8?B?UVRsSVBjUXBYMEczSHViNWt0VSsvU1FjNHBvQjVMcktZYzlTR2ZmK3gxaDgx?= =?utf-8?B?eW9zdGxzVmJzUkY4SGNMdkliVFlYempLRzRzVkl1WkhDRnJqQ1VGZVZsOWNU?= =?utf-8?B?RGdYa1Rsc1Fjb3VhOFZjVWk1NURWU2lLd1RxQllKVEIycU5Nakx3bkZqb2xC?= =?utf-8?B?dGpRREM4TzFkWkxsSWJRREExd1ZyYkhuVlJvWmRmbkN3VGo3RFdGaEVMRWVj?= =?utf-8?B?ZlROSkZzREFxV0FqWEpFZUZBV2FXeFduM1hqSGFYTk9hNWdFSmdIV2xPVVVT?= =?utf-8?B?WEFhMDdiRXI4c1BZVDZWbXp6aUNNQ1VUVHZpQzdzR2hKc1RzU1B4Q2o4a0Vk?= =?utf-8?B?RFI5QlNWc2t6MFduYk50cXhSbDk1ZzJFOHEwOGFMWVNjeld6MzU5b2FHYXFm?= =?utf-8?B?V215WWFMUG1jQ2h6cGJTRGRkdTJnRDRrUjlPR0NQZ1VYU1RNZkpNbXZzK0Q5?= =?utf-8?B?NnVQZHMyK3diOEk1TE9iTHRsRzhuVm04VC9nZUhqMUVXTVN5SEcyUXpBUE1n?= =?utf-8?B?K1dHRm8rd1hIZVE1ZmtpQW5tWVFGaFFpd1hKRmhzT0Z5L0JYY3I1MnpRbC9R?= =?utf-8?B?b1NMbm41ejdqNncxd1VqU29xQ3J6QlozaVNNa3R5TWFXUWFhWjJXQWVQZ0t2?= =?utf-8?B?ekFkeUxVMVpqbGFkd0JIQT09?=
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0628; 6:gcVerPmqaf3T1JEJPCbkwYS6tLEeuP3v5Pgrnyp/jpRWvnLgxTn5HR+5qVDZVdhL8oNp/jeACPov6vx3o64jHdjfAXOvpPUJOM7Vb6dMq5BPgTG3gVH9ylq/pvHGQWqIxUMcfvQTs+9eYZokmtz9L9CVIg599N4Cs047zoGKKgoWu7HXnENU52s9Nv+gkvQeQuK7ySgcFU6qDeNMpIIySU1JNs52qynE/tgiAF/qswI+flsYiZGgZW1Fn2GaORmsKI6YYmiMuH8aFg6Mfhq1JzMX1Xh/o/ll19/jVtHKW0UL6XrJavv9m31mHRWJHpVaHuFKu9l+qIevKw4hCl5uRyoKtcq2m3BrGQnwxrpT7v0=; 5:f9/yfcS681hTmsjf64akLsTgugYZXn8BjRp2FBD+tNlQnMlfBhfZ/znzUEdaJ7aiNPTsq/ALi5/FUUTRch5makmNJ3SSbQWyeKJ6t3hA5aECm/pQW2Z3OoCJVje6IHMrsLpvxL+QjojyL8D3C3x3Ol+ds0b3N+85OnUgNWE+A6I=; 24:a7ckfy9T6/y/tnZmerwgpxlCFYMv4v7z4GukY/4ePiXKdWQ/gqvjN8GKaXTDM5dC8Ut2a7AdZv8UFS76pwyPQ61zhDvowo0mXw9xdrmHOa0=; 7:M/3yBMOhsza6efbwVM/vpwM9nsmkQV90rmAuQzC10RnGbv/2NcIvvLOR2UOo+JKRoy/G3ZE/H/JfS4PUX3PKxP9TPAEdgjTldMJIEVtyCo0DOxLhfTRgdHkBUS97jte58HjALMuG7EiOwfYYlHFRfCNuyiHOCbQvhUk5DwwjP92Jblqm9VgBrcYFC971nsWqiCVWVlyc8o7AGdlsWyK1tm089xcKtyUH8WzcbdpsUEwRE0CURVVkjZYx7XCv3OnB
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Nov 2017 10:34:39.6494 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 49ca49b5-0d7f-4dec-a6ac-08d52501fc4c
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0628
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpnleLIzCtJLcpLzFFi42KZGbFdV/eQFUOUweQDchbPNs5nsZj09Ryb A5PHkiU/mTwmnQgLYIrisklJzcksSy3St0vgyjh8+SJjwRW+im3bLzI1MD7i7mLk5JAQMJG4 2HuOqYuRi0NI4DCjxISTp1ggnOOMEkv2fGYGcVgEepkltj7+zw7SwiiQKPH33ls2iKpWJok/ y16xgCSEBSwkHlz4xwpiiwjYSiyZvJAVoughk8SUSUuYQBJsQEVbbt0Ha+AVsJe4t/AqM4jN IqAiceRwF1hcVCBGYuKDi4wQNYISJ2c+AYtzCnhIfP3YDWRzcDALaEqs36UPEmYWEJe49WQ+ E4QtL9G8dTYzxG8KEvt/rAQ7VEJgJqPEwgObwRJCAtoSy5+1sEAU+UpcfdbDAle0bPVUKGcK u0Tnv29QVbISR8/OgbK1JG40LIAqusAm8XxtExNMYt3Vj1C7syXuN85nhii6wirxae0NNoiE jETP1bNQiTOsEo+Wt7JPYNSeheTXWQj/zULy3ywk/y1gZFnFKFqcWlycm25krJdalJlcXJyf p5eXWrKJEZg8Dm75rbuDcfVrx0OMAhyMSjy8J3UYooRYE8uKK3MPMUpwMCuJ8G5XBwrxpiRW VqUW5ccXleakFh9ilOZgURLnddh3IUJIID2xJDU7NbUgtQgmy8TBKdXAuHajgt/RvTvWhM7W eRWX3zW7cCf7k9oEIbstBUnP1XeYx99cV1/CqOAnKbPWaWL2++7MntSZWoVaUgKXdNc3TJ57 6ze/4GHxuhWMr2Qkfri5RL39mrF8Md/CeUVxDwvsTp2ZnTXD6sTPlvWfZtyfEJdVEXW7wO+H qsjFG3csTc/Nn9Jrtmq2hRJLcUaioRZzUXEiAH+b3HQaAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MskUScUMQO6WqgUmU62-eLS7Amk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 10:34:46 -0000

Hi Keith,

thanks for your comments.

> In the context of ISOC it's important to understand that the Internet
> can be used for good or ill, but it's in danger of becoming more of the
> latter.   Promoting the Internet as if it were a universal good, while
> ignoring the various ways it can be used to exploit or harm its users,
> does not seem either responsible or consistent with ISOC's history.  
> There are of course limits to what ISOC can do about it, but I don't
> think ISOC should be silent and/or pretend that it's not a problem.

I agree with you. In fact, this is a topic I also brought up in my
closing talk at ISOC's 25th anniversary event a few weeks ago. In the
past, it was assumed that more connectivity was always good. Nowadays,
as you point out, ubiquitous and constant connectivity has clear
downsides as well. In addition to the examples you discussed, Internet
addiction and the social problems it is already causing in some parts of
the world (e.g., increases in car accidents, social isolation, etc.) is
an important concern as well.

I also agree with you that there are clear limits to what ISOC can or
should do about it. As I mentioned in previous emails, in addition to
the work on the mission statement we are working on defining ISOC's
scope in more detail in different areas, "policy" being one of them. We
are currently working on identifying particular areas where, based on
ISOC's capabilities, we should engage. We are also identifying areas
where ISOC should not get involved.

With respect to capturing this in the mission statement, the proposed
text reads as follows: The Internet as "a force for good in society".
That sentence tries to capture the social benefits we are after (as
opposed to just wanting connectivity for the sake of it, without any
"higher" purpose).

Cheers,

Gonzalo


From nobody Mon Nov  6 02:48:38 2017
Return-Path: <gonzalo.camarillo@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 3B42013FB61 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 02:48:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 CXa71AJNg243 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 02:48:35 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 89D9E13FB4C for <ietf@ietf.org>; Mon,  6 Nov 2017 02:48:35 -0800 (PST)
X-AuditID: c1b4fb3a-de7ff70000006897-3d-5a003e01af8e
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.183.21]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id DF.B7.26775.10E300A5; Mon,  6 Nov 2017 11:48:33 +0100 (CET)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.21) with Microsoft SMTP Server (TLS) id 14.3.352.0; Mon, 6 Nov 2017 11:48:33 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=TNtxpcB/+Tdl+s3WK+gnDBQdOLE57b2cJ+2hqXypsiM=; b=YWaruXYMMuYBSXEyuK9fViGaU8xwSygP+d1m0b8pU4Kc91I8Q6V4xctNP1vodXGvelE8oIzV4HA4Fw4/KsytlsO8CQuPQ2qx2fV5tc9bjj5vMOvXNpjXoyfJJ7YpAm9aO8KeFvwe1tLNKr4xKR9avWrzPWF+5/veiNWCUUsleNY=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
Received: from [192.168.1.7] (37.136.86.88) by DB4PR07MB0638.eurprd07.prod.outlook.com (2a01:111:e400:984a::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Mon, 6 Nov 2017 10:48:30 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: Toerless Eckert <tte@cs.fau.de>, S Moonesamy <sm+ietf@elandsys.com>
CC: Keith Moore <moore@network-heretics.com>, <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <20171030153844.GA19771@faui40p.informatik.uni-erlangen.de>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <af6e66c0-3504-59a3-1890-e4cf1538d08a@ericsson.com>
Date: Mon, 6 Nov 2017 12:48:17 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171030153844.GA19771@faui40p.informatik.uni-erlangen.de>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR0102CA0022.eurprd01.prod.exchangelabs.com (2603:10a6:7:14::35) To DB4PR07MB0638.eurprd07.prod.outlook.com (2a01:111:e400:984a::25)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: bbc2c13d-c09b-4098-7272-08d52503ebc8
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:DB4PR07MB0638; 
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0638; 3:UukjUdzoyzhlO08mtEPO8UjKDBYzgI+t3orDYY6PnPc5I6oG0MOusdoxEdY3vdXEKYNC6g0p+Dgx2jS92Ag5Z6mxBZud93SysocS4sxYerCLxcjOMGwK40J5oFxMIFJZgnI68YrzwkLIJDCdhO5VS6BonsexpVId8CV6bVOw+JFfcw9eeL+e1A40zZrazL0AvGULVqmmwzwmkLgJaOBy79YnyGbK2GbxTdO7sAESsfHvF1USqxYTnQKJ3lvDdp9t; 25:rrG/oK5HSCpslRmbxGuyiVL2L3Bo84BQtU2necvsB9pg2HWsVb0hyySa4pIevOec85H1W9JYRmoeT2t2I9LUpONgCORuNKZz1SlQCjEsxQBK4tHD19Pm7oC+LnEm1ALjoX5vTHYNwIKPYoR0z1nPHRWHPFLs7GlnXpjRFckyOeufOBwfs8SG0AFmVF07GfWD19T3PyRV0486KQoZJV7/53dFIEPXp0pC55SUVtdUo/9u8wTcy/4RKtYHgPNjxPfKyGZk/vF4skAp4miOxH7l6CO6nmbOGJQsWln8rgPZwaNTLTMoU/SgEfhMda13HmT9CA6k2rQI52KIj7qdXMH1OVJPXXAF+PBTaip/ZpS8i+k=; 31:09JhBs/WZUE+dhb8Td0rPkDsYfuYxli2fTmyKALGFITtvcF7pnRy5cA4FZh6L4DI7rcbxYuCk0hADM0Elt0w/jZ/lMugc9cv3IwGmwsc9q39dZJbIie/u7Tny0NkUZ6/4Hqv6RPbZWN3iLxvcolIHnf8kCYvgXlPb739EyuUwPagqahIAoMyD+pJx4sfktkaiveZ/kYH3WCjmDGRTHaonx+3iTcXHZXOO7OAX0VtHeY=
X-MS-TrafficTypeDiagnostic: DB4PR07MB0638:
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0638; 20:JTTKmQjReFNCOqt0BZAfpEHrVSwInh/D6QX78+LhYBwhj/4R8/q08U0YkC2P1rvmHwPRUHylQsuy+9166NZ/sgaAXek3LqZVlqYdUhrEnqFYh6NgJF5Qfz/4S9m2bAkMqqyQiqqljeJGuNqToEI7GdaJx18kA2sx8pR3x+40lc3KIWz7WwRtCfso/d11Gabcs2xRJlpFZzjQJhGiTHstUt2qv4oVJtb/ytpBZ11qUs/kuACSYINzgsmnJ08eniYkYTp2dlGLU2Qv94XBuGhsaDP8Yna7A7f7xwl1hoim0LTlu9fWdxAlLT253Eaox9BBMyhNK+lP08PZ8V8fi0l5wAf2Jyc7OlaHL1g+oZEkSY+wLB7KBTPWoaEmNW7cWolwlkPuXxg0VSm6UijAKyK7BvUdghvX90QbU629yOnHInJObtLlEr0KTxZZ/deJmxvZ0whdVM8z4cAZC10r0bdfA6Yn7GXiw3BaS3O3HwsFXX7qTtW68XdBHGjcr7Ziol2C; 4:wa5VqJFSNfdGtyJ5fr61vje/tIXq2xm5L5r/m2uGUEppcWmKYmiReHNzLnuVU1uZgnLJ6k6eGgrxu9fIX7TdzXDcSpb0yY0MI0RKOfyCSON/x9UMwaO0B3fSmqaYYwMbLFBqbDlgv3gJbcIJKYE2d0bSK1/pOskF5xxhGjTJbC12JjeeE1TF69Mk754m1G3fMpzjjGyPnvtXzGnPfnZGUxD0XlP/TZiHm/Bs3pl7mlwSUMiJquYMWSm9aNYoTWJXBQhnLV/+BechVo/wbMN5Ng==
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <DB4PR07MB063874E8C5A0F5E478AFEAA583500@DB4PR07MB0638.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(3002001)(10201501046)(3231021)(93006095)(93001095)(100000703101)(100105400095)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB4PR07MB0638; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB4PR07MB0638; 
X-Forefront-PRVS: 048396AFA0
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(39860400002)(376002)(346002)(199003)(189002)(47776003)(189998001)(101416001)(31686004)(81166006)(50986999)(106356001)(33646002)(117156002)(5660300001)(65826007)(478600001)(2906002)(16526018)(8676002)(54356999)(76176999)(105586002)(316002)(81156014)(8936002)(68736007)(4326008)(53936002)(16576012)(50466002)(305945005)(110136005)(6486002)(77096006)(65806001)(64126003)(65956001)(3846002)(66066001)(230700001)(7736002)(31696002)(2950100002)(25786009)(6666003)(86362001)(83506002)(23676003)(36756003)(6116002)(6246003)(93886005)(58126008)(97736004)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR07MB0638; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjRQUjA3TUIwNjM4OzIzOkg4clhrSWczNDZ1bjEwTE9WY1hZMzBaRENF?= =?utf-8?B?MEZxUTZiaXZwbjNWVnBQVFNZbGJnL084Z0pjc3UyZnlxZzZMcE10NW42aWpl?= =?utf-8?B?WE9xeDhtWmdTZjJpWnhyK1gyb2lJa2V5aXJINVZkb2hGQkZqMkFLazFVU1Rv?= =?utf-8?B?aUQrckJvVXdaMnFEaWIrUjZmQlMzQ1FjN1Y1aG85SHRzWjdoWWwxVnR3N1Ev?= =?utf-8?B?WkZoWkRaMkNRQ1VIZXZqRmRaWnYxamVQU3cwdWhQN1BPN21kTE9TZlZscDc0?= =?utf-8?B?Mld6UExXY3ROWXFnZ0dMMXZIbmwyZ2s2RDNLSlFoKzB4SVBQQWYzdVJVejZX?= =?utf-8?B?aGtsQjRvRWpBNFFNa3dXdDA5UVdlZGdlcFJkUkNEVnN6Vi81MVJFUEYxMktF?= =?utf-8?B?SC84Vm5wblY4bWV2NzFpb1h2UEI2bHhoS3NPWkdTelFRcGtxSWUyRFprblZN?= =?utf-8?B?ZWs0dm91dFFQMkxQOW5mWDVWWVBFMjJvb293UHJ1OFNpWlBPcjQveDhNUXND?= =?utf-8?B?b0p6NXNvQ2tpNFBpZ0tTT3FKcEYrcFpTNkZUY09URWs2elhqRHhqSHVEV1A2?= =?utf-8?B?S1ByaEo5VVZTQnpZNjhpbGVhMVpqb0dxbXJHbFluY2FWaE8rQ0liV0RkdTlF?= =?utf-8?B?NEh6UU1IWWh2eS9ZdU9TaXNPcTZKd1NjUEp2YURXWG95ZUZ2dUVkcUNYUmRs?= =?utf-8?B?aytpUEQyYTVaSk5KRy9KbitHOE1sTTMyZ0xyQlZ4YnN0bmZ4bjV3ajJrZnNr?= =?utf-8?B?V1cvV3FOTXVibTAxWHRWWDd6amtmMXVQWjBlb0VCd29abzlSREt0QmdYWHhx?= =?utf-8?B?VC9iRHNNU1NhSjBBalNBclVkRHNGeDl3U1FGYTVmWWlLWWxiM09mcm00S3E2?= =?utf-8?B?cURKdWxGQ01VcGlkeFpLTjJXZXh5bGRGNUcrYTdsdnl0ajJBN2ZndStwUW13?= =?utf-8?B?dUpmMnZHcUpseEg3SzNTTXNGWjlHYmpBRkdHSHdkS1cxTWp2YU5QZjNhc2J4?= =?utf-8?B?VUpSaFJndkNEY2xqVmpiV1FZcjZUNmpOUjJuaUdSeTRUN2NNdU1aNnRwZ3Fr?= =?utf-8?B?WGdCR1FDR1dKbmRSVy95dnljK1kzVDJpUS9Cd0NHRG84OTlhdjFrZ1kwOFRH?= =?utf-8?B?TzJzUitXcE1pZ1YwWlhqQ3hhdGhueVRwWWhQKzFkWENCdGdrUzFsZVRteWxJ?= =?utf-8?B?RWJsN1hleE5jKzljYUVEWnZNeHdIM2tDRW9jbTNBK0pRdHdFWENuVGpvNTB6?= =?utf-8?B?YVNpU0R2a1NvMXFWYXpacDhXdWZrWnR4MFFVaExLL3VteHdiVFlJS3hNRjRF?= =?utf-8?B?cG9MTTAyVWhiWXpQSko1VEEwejdiT0tWM2VJcys1QjFHVU9sNmUycVBGMFls?= =?utf-8?B?cHlPN0F2WWdrUlZIdzBwbjJWMC9DVThkeUswOTZtVERkOWxDcmI2WjlFcENs?= =?utf-8?B?RE13am83b2c1MkNQWTU5bzFlQ25MSnNwNUxHdXZwRGxwU0xCTXA4K0hLbUVN?= =?utf-8?B?MG9GU1U3UytoSldDRUFKTlFRZU9wQlJZekp6NWNqcVRyckpHZ2NvYTB3b1J2?= =?utf-8?B?QTAxTDFieHRxTnRPbkdISmpqUU9HdXZPS2p1SEpNSk51NnN1Z0p4UFliQmJa?= =?utf-8?B?TmhEWE9raVhkeHpOY2RkWEVHWTBBdUg5UWlKdHFSaFQxVS96R2pCSDhxd1Yw?= =?utf-8?B?ZGtSMHRjeWNCV0hHQlozUDBlZ2FIR04wWERoeU1UNnM0bC8xMy9EMkRKcWoz?= =?utf-8?B?MndJN3ppNjAwY2ZXN04rUXJJeis4ZlhZNXF4ejVvMnVIUjJWUDd4TzNBT052?= =?utf-8?Q?Oy+s0frhOuHUh?=
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0638; 6:7diuYBKtNjM1ck7W8SsiyINmytH+Db3Gq8n4reXNVKUyKFDtrcHrsUAsNny1V9sqOo95hUxVi1RUrd88wq7VF0SRwWyFrwlzYUeUb5PX3WLRdFdmSwdpr+M0kulgPK3ci4TtLr/qFZUqu2SQouypCMkit0EHpPRhNUNaVKUqGtOlbh+5MgEQwMfh/sVBtl8F+TrZwt/CH8GWgz/D9BWJOg1RQ2D5uZNFbrM71udKGZ+OrLmNchbXDc7k8tjywJbbvyoFy/sBPpLIOOubxDHcHbeoSe3VCnCgszcph4t9Y+4H0xlySpk+56JBckMGiL6F49fWP7rmgJUNwskZ26ZoW+Ugt13dpTvrBVs0rAU2JuM=; 5:Kl+6+Dr07xaceCggpxOB3Jk3/hbTVgslgLbhI2swUxHXTgPa1WxLYdwpGGNXFZFm+vA1o6/de4XPuwYej8dPZ53FVQmb9k6pTjp2CLYWZYCTOjlVqbQcouIOc7vpiwJpeJEX0GmYdhoItHkrP1e5TT2j/hLPPrUUoMVuqX2XvDE=; 24:FHBrg+AtmkMs2qK2qxF49vX+e+/dsTclhML+xyxvfj7ouhNQugP8a+CrbN4tBM9xvB/KYumiAOc8kFq3hTabJIi5O/j4gRSVCgHFJrXh0nE=; 7:yjtcmiI0HiFQsqRz2UBm5A+8eCNZ4eDqK0UJcevx6D7S64a5MV1rxMx+b2fKHaiqlrs3L8mb1dCMhYYpdkOZMmyi8vaHxpo2WiNNFQtR1QoG9/WPPzF6fQotKB9GGJ6xaN0eaZp9nxcpxT1cPBQXYt51/j9lnLXPwCK2+H9u9p2tNqIMV8FA9N9gwPzHP1VgVxjb5kKZAqT6mJiVajsD9dnLrFb7NfPh8vg1A7Vfp7ZkDlh47dG4IJ7vCKXVJzTg
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Nov 2017 10:48:30.7455 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: bbc2c13d-c09b-4098-7272-08d52503ebc8
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR07MB0638
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJKsWRmVeSWpSXmKPExsUyM2K7qC6jHUOUQd8bNYtnG+ezWEz6eo7N 4lX/TVaLc9d/MzuweMzc+JbR496bj0weS5b8ZPKYdCIsgCWKyyYlNSezLLVI3y6BK2P/yoss Bft5Kp40HmRuYGzh6mLk5JAQMJG4sn0KWxcjF4eQwGFGiekf+hkhnOOMEncbd7KDOCwCvcwS T3puMYK0MAokSvy99xaqpZVJovX5cVaQhLCAhcSDC//AbBEBd4mps4+ygdjMArYSO0/OYoFo eMgk8efJB2aQBBtQw5Zb91lAbF4Be4nbTc1gDSwCKhI/F0PERQViJCY+uMgIUSMocXLmE7A4 p4CHROvF80BzOIAWaEqs36UPsUtc4taT+UwQtrzE9rdzmCH+VJDY/2MlG4Q9j1Hi7yc1EFtI QFti+bMWFoi4rMTRs3OgbF+J31M2gn0vITCTUeLGmzNsEM4UdonGjlYmiCotiatHnzNBJC6w SbRfWMAMk1h39SOUnS3RePcaVPcVVommy4fYIRIyEj1XzzJPYNSZheS7WQgfzULy0SwkHy1g ZFnFKFqcWlycm25kpJdalJlcXJyfp5eXWrKJEZhgDm75bbWD8eBzx0OMAhyMSjy8TtoMUUKs iWXFlbmHGCU4mJVEeLerA4V4UxIrq1KL8uOLSnNSiw8xSnOwKInzOuy7ECEkkJ5YkpqdmlqQ WgSTZeLglGpgrLDpDVzmnRo0Y27quTOVCszGOtYb5F8f1WmddeNdSM76VSkT5QU39k6UObfk VbjggrvuMtNm7nDzP1T5Z+P8i6mMxy/+Vrnku8NyTYqF85meJS9lpLueCkYxrXs2eULF271u E9hWsps8Wdmxi3Enf8CpfherxWyPm1T1O5luqc37uf+UQ0X4NSWW4oxEQy3mouJEAL4HzGcs AwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bevDvOpmfC9OnPqn7yBhVUy5cUs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 10:48:37 -0000

Hi Toerless,

> I suggest ISOC sits down, takes those 8 bullet points and converts
> them into 8 sections for the ISOC wikipedia entry, where each section
> could be lets say 1/2 ... 1 page long, highlighting the core historic
> achievements, current challenges and ongoing activies for each of
> these bullet points.

As I have discussed elsewhere, based on the preliminary feedback
we received, we have decided to keep the list you are referring to
*unmodified* for the time being. We may want to revise it at some point
in the future, but the plan is not to do that now. When we (eventually)
get to revise it, I fully agree with you such a highlights of activities
list should contain the most relevant *current* activities. I also agree
that having explicit explanations about ISOC's activities is useful.
ISOC's new web page will hopefully address that.

> ISOC is not only the Internet (surprise). I am totally missing a
> statement about supporting proliferation of open technologies, 
> development, operations and management practices of the Internet to
> infinity and beyond. Is that not what IoT will be all about ? That is
> not going to be the Internet. That is going to be many internets
> totalling much more than the Internet will ever be.

So, you do not think the *Internet* Society is about the "Internet" ;-)
And you do not think the *Internet* of Things is part of the Internet? :-)

Seriously though, the term Internet in this context is used in general
and includes IoT deployments that are connected to the public Internet.

Cheers,

Gonzalo


From nobody Mon Nov  6 06:28:32 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAFF913FC2A for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 06:28:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=rRj6Y82n; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=UAzScA3v
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrLwx7LRsM46 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 06:28:29 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C7C4013FC27 for <ietf@ietf.org>; Mon,  6 Nov 2017 06:28:29 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.224.148.217]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA6ES484014286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Nov 2017 06:28:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1509978498; x=1510064898; bh=NMf+0E4/1O8RAhLKG/nldUFsZds86jrFFn9aL6oG67g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rRj6Y82nXuESugJJCvuMXeNICxtD+asZNO509/JtFIEG0JIlX3y0EQ9GycXoj0Slq g1VafHK4m4sSCCN3ofjx6kP8J0+5ze0h32nyWR8fLyTtO6VNwckNsXLoEpHF2pdo9p XMPuW/Pp9Fvi23rw5HxpZ08pKDDhPwXMqSGVBGDQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1509978498; x=1510064898; i=@elandsys.com; bh=NMf+0E4/1O8RAhLKG/nldUFsZds86jrFFn9aL6oG67g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UAzScA3vlfsntHjire48Jx5QG4r6RwArKsTSuF300D21DtMNAV5tKk20tJ4S6MnP6 LZ+vcoq4aEKLdZuGjSnDMVU0NcwG2xEGjzBnC1q8eb+Mj/BaC25VdgQ3rpLxM0aoqX gDx1JQXt46LVvQB7zeDADD0UHAVCwVeGPspZZaw4=
Message-Id: <6.2.5.6.2.20171106052105.10044308@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 06 Nov 2017 05:51:30 -0800
To: Ben Campbell <ben@nostrum.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
Cc: R Atarius <r_atarius@yahoo.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
In-Reply-To: <AC4D673F-D994-4F1C-AB56-4F31D2D6DC74@nostrum.com>
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com> <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie> <039BDED8-AD0F-4AA2-8408-343D4D828751@nostrum.com> <14878392.1994847.1509741321099@mail.yahoo.com> <6.2.5.6.2.20171103174950.130619c0@elandnews.com> <AC4D673F-D994-4F1C-AB56-4F31D2D6DC74@nostrum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j0B4wbJlFsuPByDrTQztrjNWKtI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 14:28:31 -0000

Hi Ben,
At 08:32 PM 03-11-2017, Ben Campbell wrote:
>The draft says the UAC MUST NOT include a sip.instance tag with the 
>MEID in a request intended to be anonymous, and that the service 
>provider MUST NOT forward it towards the UAS.  That seems as 
>relevant today as in 2009 or 2014. It may well be that the guidance 
>in 5626 is not sufficient to guarantee anonymity, but I don't see 
>how that would change the guidance in this draft. Is there something 
>in particular you would like to see?

 From the draft:

  "MEID a globally unique identifier that identifies mobile devices
   used in the 3GPP2 networks."

The BCP states that "It is therefore timely to revisit the security 
and privacy properties of our standards".  This draft is about using 
the MEID in the in the "+sip.instance".  Shouldn't the properties be 
revisited instead of relying on what was written in 2009?

>I'm guessing that is because the affiliation change since the 
>shepherd did the writeup. Is there a specific concern there? The 
>writeup does say that the author stated that he was not aware of any 
>IPR, which is our usual standard.

I found it unusual that the write-up included a comment about 
"affiliation".  It seems better to provide clear information about 
that instead of leaving the reader guessing or, as in this case, to 
ask whether there is a specific concern about IPR.

Regards,
S. Moonesamy 


From nobody Mon Nov  6 09:36:34 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 BD7CF13FAF7; Mon,  6 Nov 2017 09:36:26 -0800 (PST)
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 axq_7LnoHNXn; Mon,  6 Nov 2017 09:36:24 -0800 (PST)
Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::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 566AC13FAEF; Mon,  6 Nov 2017 09:36:24 -0800 (PST)
Received: by mail-qk0-x241.google.com with SMTP id f199so11915343qke.2; Mon, 06 Nov 2017 09:36:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version; bh=d/iJCAPLKb+ngrYkBwRR2i5q2iiNszcp0V/6kD8CsQk=; b=tv2rtEJAYRm5a/Mx2kky6vqBSz4ZxdwB7KGWUC1IMdBlddsZ9szrSD0iabvv4Dfh70 2H5ZwcywPTqEf3RaEnYHtsH3PgRbILdOxYRLHPZnP78MeyjstwYW5MSvxPzOMloFvHRB mSQi7uCMwYEuhyXWWbVfDblT23+48gEIKbwJw/FrYOkoMZsjokmteoQ5o1dx2zYNSVXV o8tOumo50r9L+8U+VA99zIHw3YJsUV7jiJHYxle+YFj87Uc0zsdjoHtW4OxX8tL76DTe ipAhRQvCLQnr0x3hCFwGV389Zfy+JexFg31181zdUGBw4fbNrchgBvJQryyuxB3RTtOQ KXNg==
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; bh=d/iJCAPLKb+ngrYkBwRR2i5q2iiNszcp0V/6kD8CsQk=; b=Sd3i/0JALholtAn99x9BrmU4mg3QEJrFj5LI7w3Q77ymZzGT570TYJ4HVqDb9FVFKM NRVZ8t17cLrb26idRB4QUmTZ1FPDOMXr7lvKZYtzIszuKvQAgUv2YoPu14bQ/Y4DxLDg getz+ZbbM7/BmpWMytCcua5UW/EW0iBPoAtcq3hD5coYXTxadriVQqHRLC1KaTZoXhsq VF/rYjL7XnIA0pxjAD2RG+5mMvHgKnmKJ/deToZt781zC8I3tJg+Nq9wPOSwjSt9tFRG ecoISwm69fwJ9jBPv3+Pe2HgbphsZ0/iRFukyWLhFVO6pbjYjQQgj5mvWtZ4nMmRtvHv x9AQ==
X-Gm-Message-State: AJaThX4QKIgzfHOPDUvFIDbP0nWJAWbzsOi1wJx1kq6FwwB5wcTtQY3p 5nHibaRxofY5lxzDdpGXdIfUFkM1
X-Google-Smtp-Source: ABhQp+RlW+Jalvs+lYx+/c6BKhEuqhXS60Vz92u2wKA5Wn3Y6FWTaVK84218AZQ15JcJRGyt9+aolQ==
X-Received: by 10.55.5.149 with SMTP id 143mr3702520qkf.298.1509989783057; Mon, 06 Nov 2017 09:36:23 -0800 (PST)
Received: from [172.19.45.178] ([2601:184:4980:a321:2592:b69c:fca:b70a]) by smtp.gmail.com with ESMTPSA id o70sm8698170qki.35.2017.11.06.09.36.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Nov 2017 09:36:21 -0800 (PST)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "100attendees@ietf.org" <100attendees@ietf.org>
Subject: CFP: PechaKucha at IETF-100
Date: Mon, 06 Nov 2017 12:36:18 -0500
Message-ID: <9B50505D-A7E7-40E0-B789-419DA14C6021@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_7D0F8324-554C-4EB5-89D6-6EBD3A9036FD_="
X-Mailer: MailMate (1.9.7r5425)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qINYbyVD6cCUYdoKXReM8FmbX0k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 17:36:27 -0000

--=_MailMate_7D0F8324-554C-4EB5-89D6-6EBD3A9036FD_=
Content-Type: text/plain; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

Thinking about doing a PechaKucha in the past and never had time.  **NOW =

IS THE TIME!**

Come share your favorite stories, rants, or calls to action with your =

colleagues at IETF-100.  If you have a topic about which you are =

passionate, you can give a PechaKucha. (Here are two of my personal =

favorites by =

[Pete](http://snaggletooth.akam.ai/Prague-videos/07-pete-resnick-8.mp4) =

and [Brian](http://snaggletooth.akam.ai/Berlin-videos/2_trammel-8.mp4), =

although there are many other excellent examples.)

What is a PechaKucha, you ask? A PechaKucha is a lightning-talk =

presentation format, originating in Japan, where a speaker presents 20 =

image-only slides that are each on the screen for 20 seconds and advance =

automatically.  With each talk lasting for 6:40, it has the feature of =

forcing presentations -- good or bad -- to be focused and brief.

This is an unofficial event. Topics are encouraged to be a IETF-related =

and satirical or controversial in some way, although not mean-spirited.  =

Anyone can participate in this social event.

Video from the Berlin, Seoul, Chicago, and Prague PKs can be found =

[here](http://snaggletooth.akam.ai).

Format Details:

* Presentation slots are open to all, assigned first come, first served.
* To reserve a presentation slot, send a name and title to =

aaron.falk@gmail.com and receive confirmation.
* Presenters must agree to adhere to the Pecha Kucha format (20 slides, =

primarily image-only, automatically advancing every 20 seconds).
* There are lots of online tutorials and suggestions for how to make a =

good PechaKucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

[[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pecha=
=2Ehtml)], =

[[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].
--=_MailMate_7D0F8324-554C-4EB5-89D6-6EBD3A9036FD_=
Content-Type: text/html
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">Thinking about doing a PechaKucha in the past and never h=
ad time.  <strong>NOW IS THE TIME!</strong></p>

<p dir=3D"auto">Come share your favorite stories, rants, or calls to acti=
on with your colleagues at IETF-100.  If you have a topic about which you=
 are passionate, you can give a PechaKucha. (Here are two of my personal =
favorites by <a href=3D"http://snaggletooth.akam.ai/Prague-videos/07-pete=
-resnick-8.mp4" style=3D"color:#3983C4">Pete</a> and <a href=3D"http://sn=
aggletooth.akam.ai/Berlin-videos/2_trammel-8.mp4" style=3D"color:#3983C4"=
>Brian</a>, although there are many other excellent examples.)</p>

<p dir=3D"auto">What is a PechaKucha, you ask? A PechaKucha is a lightnin=
g-talk presentation format, originating in Japan, where a speaker present=
s 20 image-only slides that are each on the screen for 20 seconds and adv=
ance automatically.  With each talk lasting for 6:40, it has the feature =
of forcing presentations -- good or bad -- to be focused and brief.</p>

<p dir=3D"auto">This is an unofficial event. Topics are encouraged to be =
a IETF-related and satirical or controversial in some way, although not m=
ean-spirited.  Anyone can participate in this social event.</p>

<p dir=3D"auto">Video from the Berlin, Seoul, Chicago, and Prague PKs can=
 be found <a href=3D"http://snaggletooth.akam.ai" style=3D"color:#3983C4"=
>here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#3983C4">aaron.falk@gmail.com<=
/a> and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good PechaKucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/"=
 style=3D"color:#3983C4">1</a>], [<a href=3D"http://blog.indezine.com/201=
2/05/10-tips-to-create-and-present-pecha.html" style=3D"color:#3983C4">2<=
/a>], [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-=
kucha/" style=3D"color:#3983C4">3</a>].</li>
</ul>
</div>
</div>
</body>
</html>

--=_MailMate_7D0F8324-554C-4EB5-89D6-6EBD3A9036FD_=--


From nobody Mon Nov  6 12:02:19 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 54D6913FB3E; Mon,  6 Nov 2017 12:01:54 -0800 (PST)
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] 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 R41QdZQirOvw; Mon,  6 Nov 2017 12:01:51 -0800 (PST)
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 0450713AF75; Mon,  6 Nov 2017 12:01:50 -0800 (PST)
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 4950D58C4FA; Mon,  6 Nov 2017 21:01:45 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 320C6B0D0C7; Mon,  6 Nov 2017 21:01:45 +0100 (CET)
Date: Mon, 6 Nov 2017 21:01:45 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Tom Herbert <tom@herbertland.com>
Cc: "ideas@ietf.org" <ideas@ietf.org>, "lisp@ietf.org list" <lisp@ietf.org>, Christian Huitema <huitema@huitema.net>, Dino Farinacci <farinacci@gmail.com>, Padma Pillay-Esnault <padma.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Ideas] [lisp] WG Review: IDentity Enabled Networks (ideas)
Message-ID: <20171106200144.GA21604@faui40p.informatik.uni-erlangen.de>
References: <0BA14206-DC82-49EF-A625-B2425FA396F6@gmail.com> <1f254140-1340-6c7d-9c73-e7137562c685@gmail.com> <fa644cc2-161f-8884-3445-2b50d2c2ad23@htt-consult.com> <cf2ca920-f2d2-b65e-05eb-ebe3c30b76d1@huitema.net> <CAG-CQxrdS9L+2+bN=1NcPGuztn4U4OwSWUiNaVcS9Bsm2mtpfA@mail.gmail.com> <b18459d1-7ce1-b83d-787d-9066267d584b@huitema.net> <20171101172146.GA12437@faui40p.informatik.uni-erlangen.de> <CALx6S34Bkv4ipyA5si4KkW7VaYU6A=3=cPpRo_ss00H+vDms-w@mail.gmail.com> <20171103175258.GA6808@faui40p.informatik.uni-erlangen.de> <CALx6S34g99F=6WZJWUfxRjPbYcBaRZzhSjC0DeNev3GY6mLUBw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALx6S34g99F=6WZJWUfxRjPbYcBaRZzhSjC0DeNev3GY6mLUBw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cfVE-ToiuJeJ2DbAeThJnkbX27k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Nov 2017 20:01:54 -0000

On Sat, Nov 04, 2017 at 09:34:07AM -0700, Tom Herbert wrote:
> On Fri, Nov 3, 2017 at 10:52 AM, Toerless Eckert <tte@cs.fau.de> wrote:
> > Thanks, Tom, inline
> >
> > On Thu, Nov 02, 2017 at 08:30:11AM -0700, Tom Herbert wrote:
> >> Toerless,
> >>
> >> That maybe true, but personal devices, such as smart phones and cars
> >> that are associated with individuals, are hardly going away anytime
> >> soon. How addresses are assigned to these devices has a material
> >> impact on individual privacy. Even right now there are two long
> >> threads on v6ops right now that are delving precisely into privacy of
> >> IPv6 addresses that may be relevant. This includes discussion about
> >> CGNAT and efforts by some governments to illegalize it because the
> >> privacy it gives is too strong for law enforcement.
> >
> > Sure. All i was saying is that we should not dismiss solutions if they
> > do not help to improve privacy. It reminds me of the congestion control
> > principles and the fact that a lot of money is made with video in
> > controlled networks without congestion control. As in: "Sorry, we couldn't
> > build a great solution for sensor devices in manufacturing plants because
> > those solutions wouldn't pass the privacy bar".
> >
> > I am not even aware if we have good characterizations of solutions
> > vs. privacy like IMHO we have for congestion control, but of course its
> > a more complex topic. (IMHO: lot more cases IMHO to distinguish).
> >
> > That being said, i would of course love to see that we leverage IDEAs to
> > also create options that (could) enhance privacy, i just don't think that
> > we will make a lot of progress if we can not do this work in a WG but
> > if all the complex issues have to be resolved on pre-wg mailing lists before
> > even charters are accepted. This is part of whats wrong with the IETF
> > if i may say so.
> >
> > For example, Christian contested that long lived identifiers help to
> > improve privacy (for device = individual case) and those arguments about
> > privacy had the IESG turn their opinions.
> >
> > IMHO: The long-lived identifiers are meant to be functionally limited. You do
> > increase the bar of identifying an individual when you do this because the
> > web applications need to do more work to correlate application layer
> > information across multiple functional identifiers.
> >
> > So, how & where do we even create a common understanding about the qualitative and
> > quantitative privacy benefits of technology options if not in a WG. Functional
> > identifiers just being one example.
> >
> > Even more fundamentally: If each individual application layer function requires
> > authentication via e.g.: government, google or facebook ID, and all those
> > web services are free to correlate their information in the backend, any
> > network layer privacy work is just like growing organic tobacco.
> >

> In the base case scenario,
> it should be impossible for a random intermediate node in the Internet
> to determine who is communicating to whom (identity), where someone is
> communicating from (location), and what they are saying (content).

As an individual i agree. An individual who needs to VPN
across his home gateway routers in different countries to get access to
entertainment options when being abroad. But then there are so many paychecks
people want to live off: 

There is a lot of "Internet" business riding on geo-location of locators
(for better or worse). So, when it comes to IESG review of proposed work,
how would a scheme be vetted wrt.  those business models ? 

If we would take this geo-location awareness away from the network layer,
i can already see how any web browser would become even more DRM encumbered,
reaching down into the system to also protect reading of GPS location, and
i have to run from my hotel room outside to the street to catch a GPS signal
to let me watch my movie. Like those pico-cells from ATT.

Likewise, service-provider want to have subscriber-IDs to be able to treat
traffic from multiple subscribers fairly because there is really no good way
to do this without an explicit subscriber-ID if you want real address
anonymity (whether its identifier or locators). And that requirement i actually
agree to as an individual even a lot more than the geoloc one.

IMHO we must as the IETF be a lot more flexibility with allowing different
requirements and business models, else we will just see ore and more
of the counter reaction nicely summarized in http://queue.acm.org/detail.cfm?id=1242499>

I like a well standardized and documented IETF solution that exposes
end-user data a lot more than the secret dealings at application level
that happen today. Especially when we could start thinking of how to
guarantee that we provide means for the end-user/app to device what to
present to whom and why.

> > Which is why i really would like to know what the state of requirements/BCP etc.
> > is re. privacy at app layer in the IETF, because without that knowledge, i can
> > only define the privacy benefits of a network layer enhancement under the
> > ASSUMPTION of particular application behavior.
>
> I don't think that's true. Privacy enhancements at the network layer
> are needed to prevent inferences of PII by third party using just
> network layer information that might be passively intercepted.
> Knowledge of the application is not needed.

Right. I can make life for those third parties harder by introducing what
i called functional identifiers, where ultimately every type of interaction
you do uses a different identifier and can therefore at network layer
by passive observers not be correlated into a single identity. But introducing
that type of work into network layer makes only sense if we want to assume
that there is no correlation across multiple functions at the application
layer anyhow. That was the example.

> > My impression of IETF policy is "you have to trust the web services
> > provider (not to share/correlate/abuse user/client information)" and in the
> > same breath "you can not trust the network service provider (to behave in the
> > same way)". Would love to get pointed to documents proving this impression to
> > be wrong. Especially the option that there can be network providers that
> > users may want to trust more than arbitrary web services providers should IMHO
> > be acknowledged. And thats definitely an option i think is worthwhile to build
> > solutions against.
> >
> I doubt there's any IETF RFC or BCP stating whom were required to
> trust as a MUST. Personally, I don't inherently trust web service
> providers, network service providers, government, vendors, or really
> anyone else involved in communications (including myself :-) ).

+1

> Some trust is needed out of necessity to do anything useful, but we should
> always be searching for ways to further minimize that.

The more you want to do across the Internet, the more you need to trust
those web services providers with your data. The real challenge is create more transparency
in those web service providers to allow for more verification of what they do. 

And why the heck should i not be able to get better services from network service
providers ? What they would need to know for interesting services is so much
less than what app providers are collecting about me. Why would i oppose a
subscriber ID so a network service provider can provide fairness better ?

> A good example
> is turning up the TLS on the Internet; this eliminated the need to
> trust the network with our plaintext.

The problem with TLS is that it is evolving in a way that will again lead to
a weapons race. For example the fact that 1.3 removed totally the option for
no-encryption. Therefore eliminating the option of apps who need observable,
authenticated traffic to rely on just TLS. Or the fact that it mandates
encryption of certs so you can not even authenticate the identify of a web
service (not the client). There are good reasons why you want to have this
profile, but there are also good reason why you want othre profiles, and those
get consistently shot down in the IETF. And thats bad politics.

> I believe a similar thing will
> happen with addressing, we'll figure out how to eliminate all PII from
> addresses so that we don't have to trust the network to not be making
> inferences that breaks privacy.

The VPN service providers to access netflix abroad are an interesting
data point in this battle. Obviously i need to trust them to keep my
identify "private". Netflix did recently block a lot of them. What would
happen if ever more subscriber would use SPs offering that type of
locators. Would the OOT provider like hulu/netflix wake up and relax
geo-locking  Or do we get the GPS geoloc as i fear ?

In any case: a) if we want to get more addressing privacy, it would be good
to discuss the expectable outcomes of that, and b) i can not see how
to create that privacy without putting more trust into some entities
(such as the access==VPN SP).

Cheers
    Toerless

> Tom
> 
> _______________________________________________
> Ideas mailing list
> Ideas@ietf.org
> https://www.ietf.org/mailman/listinfo/ideas

-- 
---
tte@cs.fau.de


From nobody Mon Nov  6 16:01:20 2017
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B53A13F698 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 16:01:02 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: 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_AskRadUqZW for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 16:01:00 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA9B313FCA1 for <ietf@ietf.org>; Mon,  6 Nov 2017 16:01:00 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 1DD82206AC; Mon,  6 Nov 2017 19:00:59 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Mon, 06 Nov 2017 19:00:59 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=L55zTd gEA/K9CAtKAToHZVptj5GiP5V3AuMZbDtKuNQ=; b=SwkN51SfFvFEVfSiFOMNbW iN7NzDW11RcItBMrbzWt3D9lS6WkOZZGe5PRdeW4ikGCK4ZSWCUbUmSP1rz/RDWc X1TMFjoZJ2Lu02Q/Ii+DiYD1QQQAcG+p9pkZRMFLc9i4li0Wv7cQqcl0sXI31s+x zxMhIo+MHn1U0I5dR4JzDHrZOzDQ6iF2hKF2Z2YdurwbZrznl2bUz1l4qDAIbQLN 6M9ropua6LyDnFCXpwSB6kvxqQ8YgFrssWIKcbKyRrLaLSc8alRSmBRBMleUJlxa aP/DCSu6mHTi7+ZXowibaMLp/4tQzDINJ+qtSmJ3O/kx1OyY4bwCXtn0P1WS2R0w ==
X-ME-Sender: <xms:u_cAWlrcyIZsKc7zjd5CzdthQP20V9G_xcjex4eJdd6r-_HLwsH57g>
Received: from [192.168.1.66] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 821AD2484D; Mon,  6 Nov 2017 19:00:58 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com>
Date: Mon, 6 Nov 2017 19:00:57 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/40IereQTlPn1s6Xg1cOgWGsnUzM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 00:01:02 -0000

Hi Gonzalo,

Thanks your your reply.  I understand that it's necessary to word things 
carefully, but I hope ISOC can find a way to specifically call out both 
mining of personal data (whether or not traceable to individual 
identities) and mass surveillance (whether or not by state-supported 
actors) as significant threats to the public welfare.

Keith

On 11/06/2017 05:34 AM, Gonzalo Camarillo wrote:
> Hi Keith,
>
> thanks for your comments.
>
>> In the context of ISOC it's important to understand that the Internet
>> can be used for good or ill, but it's in danger of becoming more of the
>> latter.   Promoting the Internet as if it were a universal good, while
>> ignoring the various ways it can be used to exploit or harm its users,
>> does not seem either responsible or consistent with ISOC's history.
>> There are of course limits to what ISOC can do about it, but I don't
>> think ISOC should be silent and/or pretend that it's not a problem.
> I agree with you. In fact, this is a topic I also brought up in my
> closing talk at ISOC's 25th anniversary event a few weeks ago. In the
> past, it was assumed that more connectivity was always good. Nowadays,
> as you point out, ubiquitous and constant connectivity has clear
> downsides as well. In addition to the examples you discussed, Internet
> addiction and the social problems it is already causing in some parts of
> the world (e.g., increases in car accidents, social isolation, etc.) is
> an important concern as well.
>
> I also agree with you that there are clear limits to what ISOC can or
> should do about it. As I mentioned in previous emails, in addition to
> the work on the mission statement we are working on defining ISOC's
> scope in more detail in different areas, "policy" being one of them. We
> are currently working on identifying particular areas where, based on
> ISOC's capabilities, we should engage. We are also identifying areas
> where ISOC should not get involved.
>
> With respect to capturing this in the mission statement, the proposed
> text reads as follows: The Internet as "a force for good in society".
> That sentence tries to capture the social benefits we are after (as
> opposed to just wanting connectivity for the sake of it, without any
> "higher" purpose).
>
> Cheers,
>
> Gonzalo


From nobody Mon Nov  6 20:21:59 2017
Return-Path: <samitac.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 BC66413FAEA; Mon,  6 Nov 2017 20:21:51 -0800 (PST)
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 MXuOkSTF3drV; Mon,  6 Nov 2017 20:21:49 -0800 (PST)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6455C13FAD8; Mon,  6 Nov 2017 20:21:49 -0800 (PST)
Received: by mail-vk0-x229.google.com with SMTP id x65so7193713vkx.1; Mon, 06 Nov 2017 20:21:49 -0800 (PST)
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=Cq6Ep2/a0iKgYm1K8AbG5goUz3+TJ3KBOs/qSOPTQW8=; b=XvVBi0BMQKfsxqqQ8l7S7zKW30pXhWPkO7QCt6BRWyXeSP/yMD3oKQH81zZEwcUFhy W10cbGu4H7bvphNWBXVaK4c49x/vuYa5lb+7cNDptBL8Mb5AZWr+/VBGx7RE/yyAsdcV 2TxkodntWOdSEQcFJ93SiNCAzunzeYNSby/gdut4GZcNyiccp+nCLPcSvuW650lTYMqi wd4/lBKe3LOCU1d/XGBc9m8xQwvQKG3lwZO6myll6V95GZ5oYLBYqTBc5PFxsutKgGyD yYeVTywuZz3431HR+V/r4CYMjUE7DsIoG4cMFIMYl2W/rSs/ts5Yo8R1UYI5bo67+1Kn ycVQ==
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=Cq6Ep2/a0iKgYm1K8AbG5goUz3+TJ3KBOs/qSOPTQW8=; b=fQ4da4iRLPAQVW+AIWgQUxkA0F/Xe8YnTWX5bBozSgz19+ZOVctpN9FDTGzyIUoN/w 8tw7U5o/p9Yd9LD2jnBzLJoOBT+p9nxuq+vEHe0vqeGujgqVslm0DL/mS0qR1vtnq4zD +mMRN3IWkxjHR23ZZr5gC+FpZItrAzULUiL0jjdIg9/hocEDdJVkDClyIrSwvVmqdWAo 9m7DJ0zjyutvmGpTpCcErWs1DWvV7zeQMCSNsrj+sZeE5GyVcCJu40VVmRB9a3VJ9UqA mMNen3d2dsn27BCESJCNlnDIguxVoAh8EfQjUZCS4w6m9L38TPhpK+mRDjKAB5cxwjR1 tQxg==
X-Gm-Message-State: AMCzsaUdPpDsdG0jIqXNiVrMSvn7QNSmo9wJuFR/pvwFr7rJZ/llbPmT /oFCNzPMQtzH0zaHrdTZTxWv9W3fBl4efkqkOFo=
X-Google-Smtp-Source: ABhQp+Q4mW2e3wZcL4htUEe4jJ/Ym3fOqdMEmEhjTjhWh/uaPTHNVzyinoXir1Ba1JEoHHYIcrmZe7RgEgKRUy5qlQo=
X-Received: by 10.31.80.195 with SMTP id e186mr13247339vkb.175.1510028508125;  Mon, 06 Nov 2017 20:21:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.133.73 with HTTP; Mon, 6 Nov 2017 20:21:47 -0800 (PST)
In-Reply-To: <AM4PR0801MB270650AF0ED72FABD13EA028FA500@AM4PR0801MB2706.eurprd08.prod.outlook.com>
References: <150996104393.8207.2811572203550087788@ietfa.amsl.com> <AM4PR0801MB270650AF0ED72FABD13EA028FA500@AM4PR0801MB2706.eurprd08.prod.outlook.com>
From: Samita Chakrabarti <samitac.ietf@gmail.com>
Date: Mon, 6 Nov 2017 20:21:47 -0800
Message-ID: <CAKmdBpeP9A8VNGB9tCE=wYyBvAMzvZs4vBJq3uS6QoTbVsa4zg@mail.gmail.com>
Subject: Re: [IoT-DIR] Iotdir early review of draft-ietf-lwig-crypto-sensors-04
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: "Iot-dir@ietf.org" <Iot-dir@ietf.org>, "lwip@ietf.org" <lwip@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "draft-ietf-lwig-crypto-sensors.all@ietf.org" <draft-ietf-lwig-crypto-sensors.all@ietf.org>
Content-Type: multipart/alternative; boundary="001a114e34b4d3e178055d5ce819"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MKgjIpTMP9kfLtyCqOHFK0vwpb8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 04:21:52 -0000

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

Hi Hannes,
I have not done comparison with other technologies. But as I mentioned that
it exists. I like the fact it can generate unique 'intrinsic-id' based on
the physical properties of the chip-set. If IOT-DIR folks like to know
more, perhaps I can find out if there is a remote presentation and Q&A
session possible from the Intrinsic-id folks sometime in the near future. (
Disclaimer: I have no particular interest other than knowing more about the
feasibility  of application of that technology) I was thinking that this ID
can be used in any mutual authentication protocols ( especially generating
the private key). Do you have more information on them or think otherwise ?

Regards,
-Samita

On Mon, Nov 6, 2017 at 1:39 AM, Hannes Tschofenig <Hannes.Tschofenig@arm.co=
m
> wrote:

> Hi Samita,
>
> Do you think PUFs are useful authentication technologies for IoT devices?
>
> Ciao
> Hannes
>
> -----Original Message-----
> From: IoT-DIR [mailto:iot-dir-bounces@ietf.org] On Behalf Of Samita
> Chakrabarti
> Sent: 06 November 2017 10:37
> To: Iot-dir@ietf.org
> Cc: lwip@ietf.org; ietf@ietf.org; draft-ietf-lwig-crypto-
> sensors.all@ietf.org
> Subject: [IoT-DIR] Iotdir early review of draft-ietf-lwig-crypto-
> sensors-04
>
> Reviewer: Samita Chakrabarti
> Review result: Ready with Nits
>
> I have reviewed draft-ietf-lwig-crypto-sensors-04 document for
> IOT-Directorate review. The following are my comments:
>
> General : The document is easy reading and informative about current and
> previous work. It is ready to publish with minor changes based on review
> comments.
>
> Other comments:
> Introduction:
>  It might be useful to discuss/clarify that multi-level security may be
> important for IOT devices  all the way from 'bootstrapping and management=
'
> to  application security. That perhaps can include obtaining IP-addresses
> securely, mutual authentication between server and devices , etc. ( see
>  https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-03) in those cases
> where each  device has an IP address.
>
> Section 2:
> Regarding problems of provisioning and management of networks for the IOT
> devices there may be additional issues =E2=80=93 1) different types of IO=
T devices
> and the lack of standards way to provision them as they might be talking
> different RF technologies and running L2 protocols only. 2) The iot nodes
> may be moving individually or collectively and change networks; identifyi=
ng
> the movement of the iot nodes or identifying a particular node at any poi=
nt
> of time uniquely requires an intrinsic identification which might be usef=
ul
> to set during bootstrapping of the node
>
> Regarding related work =E2=80=93 does it consider IETF IOT security work =
only?
> There have been some work and thought process going on regarding blockcha=
in
> IOT security in the industry. Perhaps that is out-of-scope of this
> document, but I wanted to mention for authors=E2=80=99 considerations.
>
> Section 5:
> Authors of the document may also want to browse a SRAM PUF based
> technology which provides unique ID based authentication mechanism.
> https://www.intrinsic-id.com/intrinsic-id-joins-wi-sun-alliance/
>
> Section 9:
> Does the example simulate any particular deployment model or research
> experiments ? It might be good to clarify that. Section 10 and 11: Looks
> like section 11 is closely related to section 10. Should they be combined
> together ?
> Else some more text is needed in section 10 on design trade-offs.
>
> Section 13:
> Does this document recommend one layer of security to IOT devices ? There
> are different types of IOT devices =E2=80=93 some of them are very tiny a=
nd some
> are more capable. Some definitely benefit for multi-level security  than
> single layer of security.  L2 security is generally recommended for for a=
ll
> IOT networks. Does data object protection only protect the  application
> data (payload)  or more ?
>
> Thanks for the initiative in documenting the valuable work in IOT securit=
y
> implementation and crypto comparison. -Samita
>
>
> _______________________________________________
> IoT-DIR mailing list
> IoT-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/iot-dir
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy th=
e
> information in any medium. Thank you.
>

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

<div dir=3D"ltr">Hi Hannes,<div>I have not done comparison with other techn=
ologies. But as I mentioned that it exists. I like the fact it can generate=
 unique &#39;intrinsic-id&#39; based on the physical properties of the chip=
-set. If IOT-DIR folks like to know more, perhaps I can find out if there i=
s a remote presentation and Q&amp;A session possible from the Intrinsic-id =
folks sometime in the near future. ( Disclaimer: I have no particular inter=
est other than knowing more about the feasibility=C2=A0 of application of t=
hat technology) I was thinking that this ID can be used in any mutual authe=
ntication protocols ( especially generating the private key). Do you have m=
ore information on them or think otherwise ?</div><div><br></div><div>Regar=
ds,</div><div>-Samita</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, Nov 6, 2017 at 1:39 AM, Hannes Tschofenig <span di=
r=3D"ltr">&lt;<a href=3D"mailto:Hannes.Tschofenig@arm.com" target=3D"_blank=
">Hannes.Tschofenig@arm.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">Hi Samita,<br>
<br>
Do you think PUFs are useful authentication technologies for IoT devices?<b=
r>
<br>
Ciao<br>
Hannes<br>
<div><div class=3D"h5"><br>
-----Original Message-----<br>
From: IoT-DIR [mailto:<a href=3D"mailto:iot-dir-bounces@ietf.org">iot-dir-b=
ounces@ietf.<wbr>org</a>] On Behalf Of Samita Chakrabarti<br>
Sent: 06 November 2017 10:37<br>
To: <a href=3D"mailto:Iot-dir@ietf.org">Iot-dir@ietf.org</a><br>
Cc: <a href=3D"mailto:lwip@ietf.org">lwip@ietf.org</a>; <a href=3D"mailto:i=
etf@ietf.org">ietf@ietf.org</a>; <a href=3D"mailto:draft-ietf-lwig-crypto-s=
ensors.all@ietf.org">draft-ietf-lwig-crypto-<wbr>sensors.all@ietf.org</a><b=
r>
Subject: [IoT-DIR] Iotdir early review of draft-ietf-lwig-crypto-<wbr>senso=
rs-04<br>
<br>
Reviewer: Samita Chakrabarti<br>
Review result: Ready with Nits<br>
<br>
I have reviewed draft-ietf-lwig-crypto-<wbr>sensors-04 document for=C2=A0 I=
OT-Directorate review. The following are my comments:<br>
<br>
General : The document is easy reading and informative about current and pr=
evious work. It is ready to publish with minor changes based on review comm=
ents.<br>
<br>
Other comments:<br>
Introduction:<br>
=C2=A0It might be useful to discuss/clarify that multi-level security may b=
e=C2=A0 important for IOT devices=C2=A0 all the way from &#39;bootstrapping=
 and management&#39; to=C2=A0 application security. That perhaps can includ=
e obtaining IP-addresses=C2=A0 securely, mutual authentication between serv=
er and devices , etc. ( see<br>
=C2=A0<a href=3D"https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-03" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-ie=
tf-6lo-ap-nd-03</a>) in those cases where each=C2=A0 device has an IP addre=
ss.<br>
<br>
Section 2:<br>
Regarding problems of provisioning and management of networks for the IOT d=
evices there may be additional issues =E2=80=93 1) different types of IOT d=
evices and the lack of standards way to provision them as they might be tal=
king different RF technologies and running L2 protocols only. 2) The iot no=
des may be moving individually or collectively and change networks; identif=
ying the movement of the iot nodes or identifying a particular node at any =
point of time uniquely requires an intrinsic identification which might be =
useful to set during bootstrapping of the node<br>
<br>
Regarding related work =E2=80=93 does it consider IETF IOT security work on=
ly? There have been some work and thought process going on regarding blockc=
hain IOT security in the industry. Perhaps that is out-of-scope of this doc=
ument, but I wanted to mention for authors=E2=80=99 considerations.<br>
<br>
Section 5:<br>
Authors of the document may also want to browse a SRAM PUF based technology=
 which provides unique ID based authentication mechanism.<br>
<a href=3D"https://www.intrinsic-id.com/intrinsic-id-joins-wi-sun-alliance/=
" rel=3D"noreferrer" target=3D"_blank">https://www.intrinsic-id.com/<wbr>in=
trinsic-id-joins-wi-sun-<wbr>alliance/</a><br>
<br>
Section 9:<br>
Does the example simulate any particular deployment model or research exper=
iments ? It might be good to clarify that. Section 10 and 11: Looks like se=
ction 11 is closely related to section 10. Should they be combined together=
 ?<br>
Else some more text is needed in section 10 on design trade-offs.<br>
<br>
Section 13:<br>
Does this document recommend one layer of security to IOT devices ? There a=
re different types of IOT devices =E2=80=93 some of them are very tiny and =
some are more capable. Some definitely benefit for multi-level security=C2=
=A0 than single layer of security.=C2=A0 L2 security is generally recommend=
ed for for all IOT networks. Does data object protection only protect the=
=C2=A0 application data (payload)=C2=A0 or more ?<br>
<br>
Thanks for the initiative in documenting the valuable work in IOT security =
implementation and crypto comparison. -Samita<br>
<br>
<br>
______________________________<wbr>_________________<br>
IoT-DIR mailing list<br>
<a href=3D"mailto:IoT-DIR@ietf.org">IoT-DIR@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/iot-dir" rel=3D"noreferrer=
" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/iot-dir</a><=
br>
</div></div>IMPORTANT NOTICE: The contents of this email and any attachment=
s are confidential and may also be privileged. If you are not the intended =
recipient, please notify the sender immediately and do not disclose the con=
tents to any other person, use it for any purpose, or store or copy the inf=
ormation in any medium. Thank you.<br>
</blockquote></div><br></div>

--001a114e34b4d3e178055d5ce819--


From nobody Mon Nov  6 23:31:01 2017
Return-Path: <gonzalo.camarillo@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 47AEB13FB32 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 23:30:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 0bilfBmQcgng for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 23:30:57 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 2CF3E13FAC5 for <ietf@ietf.org>; Mon,  6 Nov 2017 23:30:57 -0800 (PST)
X-AuditID: c1b4fb3a-dffff70000006897-06-5a01612ffbab
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 42.6C.26775.F21610A5; Tue,  7 Nov 2017 08:30:55 +0100 (CET)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.33) with Microsoft SMTP Server (TLS) id 14.3.352.0; Tue, 7 Nov 2017 08:30:55 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=RoVhHIY2cvEJ4LmVN/as8jPPnqGeT68Ml/7niDLhJw0=; b=VVoBzj86+4AHMdpKX7yWuIvLy/nQy7JwGsXj29N31/92aNhpjeEDYhpv2Jl7WvB1dvKpMSU+8f9VlLiTawykWjq6nyKCjOvxILW1XTfLTvW4roG3CjIGhRggyA67r2mXZT090QhaY9KS9ruxWHob7rtglluSTIDeOJ5Nt6r7Uik=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
Received: from [192.168.1.7] (37.136.86.88) by AM2PR07MB0627.eurprd07.prod.outlook.com (2a01:111:e400:840d::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Tue, 7 Nov 2017 07:30:53 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: Keith Moore <moore@network-heretics.com>, <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com>
Date: Tue, 7 Nov 2017 09:30:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR09CA0090.eurprd09.prod.outlook.com (2603:10a6:7:3d::34) To AM2PR07MB0627.eurprd07.prod.outlook.com (2a01:111:e400:840d::26)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: c4143293-6d8b-4ff5-f03a-08d525b17a7f
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:AM2PR07MB0627; 
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0627; 3:46ZljP2XMmO1xZaNanVr9oi7PmqvbOSJnZ6HENLAbdiVz2mIeuVACSkDIj27FXkOvtqBznhhfWETGU0beZsBs2pELp2JTUG/6fmL2+dQ19DaCDHkT558/4giaBLfNB1Njn1DQe80IcVfzeKuKZAzKXFAdhSyCLUZmmm9PPZ/dA4iLjshTaoj2WPAjLBtJzDQ554UBHxgSMOYMPK6G8L6f9QL+L+e7QKiVAeik40k/6W26wtsPLQhrlvxQQpfUoR0; 25:Al3PJRNYuourib3VbXyl1Q4IC/nHQmm0OMCDMAd8GT9ZKyn3GCdbWqTxaJhorR248AmlyIaxHLzIZrLnRYHYFRHHHZehWLB91Rr1Ud5PYTtWKSN1uV7sgu6XUb+iiv66522RzI7L1gfN8FmkKZcM+JpJg8CXxQxKlmIvy0v6vs0clarp1uCTYeHE5MIma3WpiEbZs3t44ZHu6eguwZpHWOCp2/ARxfxm0GX12ovavjy7ZWCzL5qImxqd1MggknmO1+LE7woiL304uW/omqf8UMxz3SJ8/x9FfmbPg980GYyx9bw0JllVnbAKv6kxUSKPvCLpxyYO3mqVb3D+F2QNdg==; 31:w2uRpen33f6NoXCL8Bvh9UVaxSwZyqQejisEnrojIq2Iu5IC6RoU9knRZPEgfQ6xLRrIdq+RxVJq8zsRgYOnLu6ndgoTBpI65nz3jymwxfeStUbpYDeAWvqXtg/TWaAVecdFPh/o0Bl7omZZJmQ3HWoWTVqDfqNELfFR8RZJ6hNk18NKS85QIdG+g76WrMEkN8IQ+oO4lRq5LwEB7zMvNeo23t0YfGq5e/pgtK2OB40=
X-MS-TrafficTypeDiagnostic: AM2PR07MB0627:
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0627; 20:I+MhfnO+KzQNn9uzlFLdFZvjIEH11pvPl52FAcKwyCoHn7PXH73ZiBuZuUDeYITva0t+9uqb+xXpeCqJBdX7MuMMi5ii5mT0Lbr848GbxpdxrotCws+ozrL/J140GlkC8ftQr2hrYYmi/H54/qi6SbQtaC4wDRE3aVekCSolq3Lqqb/R6VYDJfEBV4GWVPtwq3plXQXZHi3obHAQMpI/5CqiILSc8OK2pWWFysO2FlDfAUjaxCrH32WBGqvJwwojaxjyjUJF21NJF/14UG3MrEC5uzUGRmpUx/X0OmUGElnmW+tBXoGCL6PNQlZiiIR6XQUG2qO/q0gCVNJVAtMTTzsFxB+N73BSxwiZQjGNhyAbhsPd4SF9L/MsTCrufjSlKS0Yx8dA7hUT0ldhQEoueH6lPIBh9nTJc6Zxp+zaOcKbEYW6oXzXmtb+o6s9hsLleI34HS1RwsCPCrCn5lofq/tYnd8QGgyzpw6liYF4rHJCPeOJ2+s+4CiEiH1oOkIw; 4:IyweRkI+RX8Q+ytkuBZ/3/u6WnkF4P145ZmDb7erTn0mSfaWSWOxTdl+3ljBBpoyaYPaiHNIjfBG7Uueajmf9jk5tGcqIyPzWk3sPZlP4yaEfj/81qFxSvFQSlqm8JFtzzOgQimFtnUXAXTlB5EH1P3hrcwkx974eorJ/lNcqIy3K1Mn4mHLfxKhbzKYLUS6MMfZbAlfkqG6YEiHxHzCk5S7jxkc2gxjv9FyT4WunOVQ5agLphpPr1mTjD6QrunnhkMJdNsRhyjFpUhhEy+v2/37TfdTcNnXu4Ukm9jmDepMyry04ZBCN5PHEI+BkTDg
X-Exchange-Antispam-Report-Test: UriScan:(173461626932800);
X-Microsoft-Antispam-PRVS: <AM2PR07MB06273E5F75610DCDFBA3E69583510@AM2PR07MB0627.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(3002001)(3231021)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM2PR07MB0627; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM2PR07MB0627; 
X-Forefront-PRVS: 0484063412
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(376002)(39860400002)(346002)(199003)(189002)(24454002)(81156014)(50986999)(86362001)(8936002)(966005)(53936002)(31686004)(47776003)(478600001)(31696002)(8676002)(7736002)(305945005)(76176999)(23676003)(54356999)(53546010)(16526018)(64126003)(6246003)(189998001)(33646002)(83506002)(65806001)(66066001)(65956001)(81166006)(36756003)(68736007)(2950100002)(2870700001)(6306002)(229853002)(316002)(58126008)(117156002)(105586002)(6486002)(50466002)(6666003)(25786009)(16576012)(97736004)(77096006)(93886005)(6116002)(2906002)(106356001)(3846002)(101416001)(65826007)(5660300001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0627; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTJQUjA3TUIwNjI3OzIzOjRXTUMrV3pHcEhTYnFHZHRHb1VMK1A4NkdM?= =?utf-8?B?UkJMck0veG5GYXJnOUZ1MHpNV1hXc0RGRFFvVUYxMGoyT3lHNXlMTWZ6UGFx?= =?utf-8?B?RUQxemFiSU4rUytzc0k3VytjdHJwVGkxMkNIUndsMzJGQ3JjMnZTQit2TTQx?= =?utf-8?B?ZENLdGsxbzNNMkhUd2NNQllEb2tYaWNHMnAvZVBxOFFwWExGd2M3RXg3WWFP?= =?utf-8?B?U3ZkbmpaSlNWZzJFVUxIMFM4Sk1JY3FEYjVOUko5SlE1V21SQWxpR2ZGZHgv?= =?utf-8?B?em9yeWRCWXZ6M1M5RElOL3MxY1A5VjNVSnpTQnBJR20ybjNYaUt5NUY0OVJ3?= =?utf-8?B?bmlkWGhVQXBlZmExYUZIbExWWm1zSGdVbUxwZE43V2VPa2ZodTcxMHZtMEht?= =?utf-8?B?aXVHTXNPME5HVldYSW5uQ05MV3hFcEhvRGpaanZmbVp6bHFkaUY0aGJoZUFF?= =?utf-8?B?LzE4TlZRYkdQMlZsQ1JNU252RzVDM3IxVjZJZ3laSkZTYjZEWEJvS2gwTGhM?= =?utf-8?B?RUJ4R1ZZM1p1VVpMWFMxSzc4NmJzZWJMSlg2YkdHeCtsOUc1bW82U1FOMENY?= =?utf-8?B?ZVRyYWNzdzQ4Yy9UemRuNU1oQXd4WHNrZ0l0RW42dXZkdy83N3JDQ0E0bnQy?= =?utf-8?B?ZEZQandVU2ZzeXdDSy92MGdLWFgrSlYrQlBkVElpYWFzOU9iUHdlRGRPa0I5?= =?utf-8?B?TmliV1oxV0xqSFN4bncvd3VBNWIrSFhNcytMdGhHVmovNGU4WE96elJtbVZ1?= =?utf-8?B?amlycG1GRXF4YzgxNWFtK0xEam9ySnhjK2Q2MWF2Zmw1UWtHcmJORVprbmNz?= =?utf-8?B?cTlreGxJMnRlODRybVBTUUk5dUJjcVV3RDBjc0Z1NWh2Wk80UU1TK095T1BD?= =?utf-8?B?MzlqdkhHdmJMeGZjdGhZU29ueWl3OEg4bjZoS0ZEemVXUDlQZy85R21TQ3Er?= =?utf-8?B?d3lnaDVFRHFvc3hxV1pTYzBTQmkzU2gwVVdUUWtsa25jM3hWNHdKRTFSU3Zh?= =?utf-8?B?dmo3TWNKaTFRbkpQZ2xjTWMyc2syN2cyV2dUdlhxUHh5UjlaalVaQkgzTHcr?= =?utf-8?B?TDMzUEZUMjY0TTI0SUN4bzVZb1VSUkkyWGZUQkNhOVRIUHZZdVNhc1Qyb1BM?= =?utf-8?B?OWdVQUpzaXR4Ump1SGkyOEtIbllQanN0eC9xRVBvYVF1RkZrV0doNU5qRGE3?= =?utf-8?B?dmpEcDJFL3MreE4vL1pZOG15bk1MamMvQjFHeHhqZXJEdi9vbFdzeEl5Sy90?= =?utf-8?B?SjJoNmNlY2xyR0R2Q1p2UnZiQVNGckh4WVZ3WnA2WUNlSmp6ckEvMlNpOVFW?= =?utf-8?B?K2kwNGU0Zm9SZ1l3MVhLKzQxWEFreGsxckVnTzJaRnZHcEJQa2FTa3BRZkI4?= =?utf-8?B?Zk1GaXlpdmw2SFpaRTYwZjF6YjQ4a0swV1BlaGh1VVREQTcyWTVXdk9DK0hy?= =?utf-8?B?RGRmUWZYQTR2cFY5dWJkV2Y1dlUyS0wvMFdiTkgxS2tsdGlrQ1NLZURqTC9T?= =?utf-8?B?UHAraFJUMmRNSDZoNWNMcTlnaUZiS1p0SVJ5NzBNWC8zd09LR05MZXhqNXpx?= =?utf-8?B?TFNURnQ2TGNoaW5ObjJxTnY4eml6bWhnNXJVTXZ4dHhmQ01acE9nV2pJTGVk?= =?utf-8?B?bUhwdkV1ZVpTbkVjTkJ5WUlyVHByakNwb21jZCtaYTlDbG1EdERndTZiU0tu?= =?utf-8?B?VC94bVNPSEFQWkpZdmpmMXJZeUVJc1dqSVJLb1NwSDhyZjczN0grYVpmYnN4?= =?utf-8?B?NHNFcDVzNC9PZzVENEM2TU82cm1KNjhIc2JlSXVGNjhRa1pkNlo4WDR2UmJs?= =?utf-8?B?ZXBDcy9UVk12ZUpOamNVeVZCLytsMStybmNMdHFScVFUY0VZbm9GemtwbUtM?= =?utf-8?Q?1aZ0DO3NOGc=3D?=
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0627; 6:zHGRNd+2HJuO9caUTLHl4VZ2NvWjIFPV35VjbgSoWTAn/GmzppmgJoW687SpxoVDxZgoadIvZ/j2Wh0uaaaKDQk9W51e1N2IvXscW8qFutrautTICsjTRu70nO/3As5HmkGJXf/kRjr9tp/xwDZDJ6JHZXpWIEbuT793f3SauS/bO39QLDQwotzvwOIrVR98qcOgT2lIfJFrYPBZ6IdyIJBj/w5gj48ppMIsUdDnFApLBdxKGWUeayOFyQWtWQ8AIVFzuZrlimlPTHZeT1Lsi1RfB6vqEDABk1VHRAphxSaPeQZJTpocLykBaOs2yCAt0Gu+bvOlpJRCmLBbMnQCHfiHhzHMxVJI8U763nI+2ZA=; 5:jSAfM+GeUSJUCsOkL0C3VFhNXiGU2UZS4me2MUuFb9MYIOeVtxfksO6KN/zg6b9BfTPv1Aus9xK3ztRAdzr7nzvK1kFsxdJEpXZduvZpr4Log0fVRGyyHp7aHeVFpOAvv0m9HyV4uxJZAtjImmJPbRFNo0iboBJqltVihcZRVLU=; 24:+gA4ZeGqpweLCW9wcfQH6keeKPrPlv8+dUwMhcTsWsINa4kCEdr95K/W3EHdCTHuFbJLb7Wa1Ur+5RoT4OwPHZBSenDOisq81kjT2OnBqDo=; 7:7sLhcWmt+8cnF9uWvVKV3QfTuZi1AIz6YwaH1cejtFT2YMtrxiAIuTV3ZD10hfdH7t762steeq9qS4H3ODx1TcqpVXzr2fnwUB1val7Y1cDFYVqt6qqN9bj9bo0HfVEl45kqy/3DQ62D+iUg84L7y3WqtY5tkCJu7DxrfNzRuyKg0M4D+Um2ldMcwdwFAe1O+OlBzcp4WeMHprqlyrC8YqgH7+jDWnt3ydkNxPRMjqG5mBIlapFIKFTP9fsakIbY
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Nov 2017 07:30:53.3062 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: c4143293-6d8b-4ff5-f03a-08d525b17a7f
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0627
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplleLIzCtJLcpLzFFi42KZGbFdUVc/kTHK4OhzaYtnG+ezWEz6eo7N gcljyZKfTB6TToQFMEVx2aSk5mSWpRbp2yVwZbS1LmUsWChacWnHSZYGxjbBLkYODgkBE4ne xXJdjFwcQgKHGSVu373OCOEcZ5TYdbiTHcRhEehlllj35h6Qw8nBKJAo8ffeWzaIqlYmid3P 3zGCJIQFLCQeXPjHCmKLCNhKLJm8EMwWErjKLLH/Tj6IzQZUs+XWfRYQm1fAXuLApENgNSwC KhLb1lxhArFFBWIkJj64yAhRIyhxcuYTsHpOAQ+J5gVNLCBnMwtoSqzfpQ8SZhYQl7j1ZD4T hC0v0bx1NjOILSGgILH/x0qwOyUEpjNKtD09AXWPtsTyZy0sEEWyEkfPzoGyfSWWnT4J1TCT UaKr8S0rhNPALjHt7jJ2iCotia6/R5khEj/YJFb+msIGkbCWeLStH8rOlng9cwMjRNEVVome H/+gumUkuro3QXV/ZJXo69/BOoFRexaSX2ch/DcLyX+zkPy3gJFlFaNocWpxcW66kZFealFm cnFxfp5eXmrJJkZg4ji45bfVDsaDzx0PMQpwMCrx8Oa7M0YJsSaWFVfmHmKU4GBWEuHdrs4Q JcSbklhZlVqUH19UmpNafIhRmoNFSZzXYd+FCCGB9MSS1OzU1ILUIpgsEwenVAPj2h5ha1WV jB7uM4bmoh7+u+YxMOSU1oltF5x79eA0qSdP4txdzxXaTjMN+ZXoUd+5ac2dSYvaxLNvFG1h bb66V7av6m/j6fJ2D44Du419GWI1+LKjQsxuC/w3cdBK3HhlukeihPfsU5cn3xN/v/D5izcO p+0mLZq3+7H/+kkxew/52VUf3BakxFKckWioxVxUnAgApO/TnRgDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zJw_OrkMSyouK2wyksoWF34CPzw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 07:30:59 -0000

Hi Keith,

yes, ISOC has activities on that front. For instance, a couple of weeks
ago ISOC organized the following Chatham House Roundtable on Encryption
and Lawful Access:

https://www.chathamhouse.org/event/encryption-and-lawful-access

Cheers,

Gonzalo

On 07/11/2017 2:00 AM, Keith Moore wrote:
> Hi Gonzalo,
> 
> Thanks your your reply.  I understand that it's necessary to word things
> carefully, but I hope ISOC can find a way to specifically call out both
> mining of personal data (whether or not traceable to individual
> identities) and mass surveillance (whether or not by state-supported
> actors) as significant threats to the public welfare.
> 
> Keith
> 
> On 11/06/2017 05:34 AM, Gonzalo Camarillo wrote:
>> Hi Keith,
>>
>> thanks for your comments.
>>
>>> In the context of ISOC it's important to understand that the Internet
>>> can be used for good or ill, but it's in danger of becoming more of the
>>> latter.   Promoting the Internet as if it were a universal good, while
>>> ignoring the various ways it can be used to exploit or harm its users,
>>> does not seem either responsible or consistent with ISOC's history.
>>> There are of course limits to what ISOC can do about it, but I don't
>>> think ISOC should be silent and/or pretend that it's not a problem.
>> I agree with you. In fact, this is a topic I also brought up in my
>> closing talk at ISOC's 25th anniversary event a few weeks ago. In the
>> past, it was assumed that more connectivity was always good. Nowadays,
>> as you point out, ubiquitous and constant connectivity has clear
>> downsides as well. In addition to the examples you discussed, Internet
>> addiction and the social problems it is already causing in some parts of
>> the world (e.g., increases in car accidents, social isolation, etc.) is
>> an important concern as well.
>>
>> I also agree with you that there are clear limits to what ISOC can or
>> should do about it. As I mentioned in previous emails, in addition to
>> the work on the mission statement we are working on defining ISOC's
>> scope in more detail in different areas, "policy" being one of them. We
>> are currently working on identifying particular areas where, based on
>> ISOC's capabilities, we should engage. We are also identifying areas
>> where ISOC should not get involved.
>>
>> With respect to capturing this in the mission statement, the proposed
>> text reads as follows: The Internet as "a force for good in society".
>> That sentence tries to capture the social benefits we are after (as
>> opposed to just wanting connectivity for the sake of it, without any
>> "higher" purpose).
>>
>> Cheers,
>>
>> Gonzalo
> 


From nobody Mon Nov  6 23:38:10 2017
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79D1313FB8A for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 23:38:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8N_fZ9izSpXa for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 23:38:06 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68D6613FB25 for <ietf@ietf.org>; Mon,  6 Nov 2017 23:38:06 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B86F420D6C; Tue,  7 Nov 2017 02:38:05 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 07 Nov 2017 02:38:05 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=FR11CK SYQoAQImjSXKqTVs5l1lefHRADtMQ0cHnvAo8=; b=LYdXOrCu9nnOIjQ2hmPWxF mYLFNFrKzhUTj59sq9gQC0HgQST7YomVF002ZsAbjniW1vmu4rwxrruJMWuf7FFn U9RAsulE7ZkkM0tsMk9NBmppT7i3Ioi4WiWJ3AMG3yBEfW0D+E5pO9gNl3xgfZjk bO8Gp2eMvtLirfm7tvaR4+HD3CsKOZMyg7+j/L/hoki/APJDGse7WcLIqehBFCP3 pq0CvbRtQLCx4Ha5wTybm1oM2JLOSb5rXwCmCI6hgIP/S4l0hC+vZvijZXch728q VmBcssdpwmrQxNApNMKMF72X7vOa6CeGQEi0COakZz8d/Cmr1ACZQsiSJ16BRe7w ==
X-ME-Sender: <xms:3WIBWsdDARM1ifFLiRvCSCxwiWSef8h1w54tBV7KQiEfdaqiDmS8JQ>
Received: from [192.168.1.65] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id 1CCA77FA6B; Tue,  7 Nov 2017 02:38:05 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com>
Date: Tue, 7 Nov 2017 02:38:03 -0500
Cc: <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7_SJnI8HYWgNui_P4ckuZoyUktg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 07:38:08 -0000

Having "activities", and prominently taking a stand for what's right, =
are very different things.


On Nov 7, 2017, at 2:30 AM, Gonzalo Camarillo wrote:

> Hi Keith,
>=20
> yes, ISOC has activities on that front. For instance, a couple of =
weeks
> ago ISOC organized the following Chatham House Roundtable on =
Encryption
> and Lawful Access:
>=20
> https://www.chathamhouse.org/event/encryption-and-lawful-access
>=20
> Cheers,
>=20
> Gonzalo
>=20
> On 07/11/2017 2:00 AM, Keith Moore wrote:
>> Hi Gonzalo,
>>=20
>> Thanks your your reply.  I understand that it's necessary to word =
things
>> carefully, but I hope ISOC can find a way to specifically call out =
both
>> mining of personal data (whether or not traceable to individual
>> identities) and mass surveillance (whether or not by state-supported
>> actors) as significant threats to the public welfare.
>>=20
>> Keith
>>=20
>> On 11/06/2017 05:34 AM, Gonzalo Camarillo wrote:
>>> Hi Keith,
>>>=20
>>> thanks for your comments.
>>>=20
>>>> In the context of ISOC it's important to understand that the =
Internet
>>>> can be used for good or ill, but it's in danger of becoming more of =
the
>>>> latter.   Promoting the Internet as if it were a universal good, =
while
>>>> ignoring the various ways it can be used to exploit or harm its =
users,
>>>> does not seem either responsible or consistent with ISOC's history.
>>>> There are of course limits to what ISOC can do about it, but I =
don't
>>>> think ISOC should be silent and/or pretend that it's not a problem.
>>> I agree with you. In fact, this is a topic I also brought up in my
>>> closing talk at ISOC's 25th anniversary event a few weeks ago. In =
the
>>> past, it was assumed that more connectivity was always good. =
Nowadays,
>>> as you point out, ubiquitous and constant connectivity has clear
>>> downsides as well. In addition to the examples you discussed, =
Internet
>>> addiction and the social problems it is already causing in some =
parts of
>>> the world (e.g., increases in car accidents, social isolation, etc.) =
is
>>> an important concern as well.
>>>=20
>>> I also agree with you that there are clear limits to what ISOC can =
or
>>> should do about it. As I mentioned in previous emails, in addition =
to
>>> the work on the mission statement we are working on defining ISOC's
>>> scope in more detail in different areas, "policy" being one of them. =
We
>>> are currently working on identifying particular areas where, based =
on
>>> ISOC's capabilities, we should engage. We are also identifying areas
>>> where ISOC should not get involved.
>>>=20
>>> With respect to capturing this in the mission statement, the =
proposed
>>> text reads as follows: The Internet as "a force for good in =
society".
>>> That sentence tries to capture the social benefits we are after (as
>>> opposed to just wanting connectivity for the sake of it, without any
>>> "higher" purpose).
>>>=20
>>> Cheers,
>>>=20
>>> Gonzalo
>>=20


From nobody Mon Nov  6 23:49:52 2017
Return-Path: <gonzalo.camarillo@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 A7EB813FB32 for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 23:49:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 SUL-PoQZXuCP for <ietf@ietfa.amsl.com>; Mon,  6 Nov 2017 23:49:48 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 3FC2D13FB2D for <ietf@ietf.org>; Mon,  6 Nov 2017 23:49:47 -0800 (PST)
X-AuditID: c1b4fb3a-1c7889c000006897-91-5a01659a1ee8
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.183.66]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 81.03.26775.A95610A5; Tue,  7 Nov 2017 08:49:46 +0100 (CET)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.66) with Microsoft SMTP Server (TLS) id 14.3.352.0; Tue, 7 Nov 2017 08:49:45 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=P/tK2pIJmjjUMwiu3dUwyrbIP6v0VzOMYblJmdbXX6E=; b=SXWUYr29tmOmXEskPTvUPsUv/3QBGyL/6CsiYNYXaX+DdaNWuYPgfLbRewK1L2hVecJnivqYxotVx9yiz92NJnudiAUmBCATk1/Nl41DCYto9ZltdHD30MwkdHSBa0HV2QuznAMMHV4J+mF2gBRfcKoWrzG+h1MfKgmReQUT6dw=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
Received: from [192.168.1.7] (37.136.86.88) by DB4PR07MB0640.eurprd07.prod.outlook.com (2a01:111:e400:984a::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Tue, 7 Nov 2017 07:49:43 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: Keith Moore <moore@network-heretics.com>
CC: <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>
Date: Tue, 7 Nov 2017 09:49:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR07CA0042.eurprd07.prod.outlook.com (2603:10a6:7:66::28) To DB4PR07MB0640.eurprd07.prod.outlook.com (2a01:111:e400:984a::27)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: a658c25a-3849-4f37-9d08-08d525b41c5f
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:DB4PR07MB0640; 
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0640; 3:Z8HjpKwnpdS/WlYJfqcpOAB5aKIfpx0tkEyIkOSu5UlH7Vo+CYUhgCUwjhYCeR6Jh+uGI1aWvnE7LIhkHSiSpcfylaI9ACobTZQZP7qkPoD1CIJaui5wcfr/YWSWbq3kum4GkJNj46YxP7NFpCzjqCsxhuTw5ITy9L6i/cpeyJCp/aa9l7iVuUVDQlNoEkjXe4wwpxebxmwcftQuOrdWShMnq7/nSawHL/O787X81y/8if5NH8/0mCL/NdbT4zQI; 25:75DS9ZgKfINI5YjFRDIX97esZ2783I1S6n/lQQ0h83f51Dxb2unLlCdPjTpUYwJbsbNHjn6bmp8l4bNUXrMlndNizxAz5zbQjXF5bueofm8i306YUm5toMnYHgaN7U8iT/U5IAMCIinnlt2KZkRmfcYuT7wAX6XKtak5TWfp3PjOGqhMvsR4fbYjUqAm4TwV3JB3L/FWsqw2rlrjTMEUAVzLze+cDg0F3AF380Dj+wHFllSqkDvrVtQwlW7jw1vqjpukYro2oDRQNUT8DFTftaHpaJK39YrxBPQ1XUNxdlRFtlykRPpBJf1pb1PVbpIomt+ibKF+sEaYKzDoe/gjnA==; 31:aaP+l2e73YpaDWELTJw8KTj0k7sTKPxJ3f81b/8+2xiyfXt17L2IAqdhWHwqHWfsrfEzntjq+gHj7/88D12xu8EhrJmItmyJEdzGBERvfKzowFcnbZDuaoWVARBroNgwqiVgf6eiKsQ9P1GWcE9m0WZqIsO6Kil4RBg9PqwXQO8d6KinwIKtwoAZbS3dNsxvpLUygzaisa+SCqs9wVdiLuZIVVEEiUUktq1Lhqmf3NU=
X-MS-TrafficTypeDiagnostic: DB4PR07MB0640:
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0640; 20:ZHxzwIYZ0VQMlWAMoZ7DuVI1eoBHh22VELriSAuLI5Vo2a5lvBz4S6Z0E3A6/gv16U7tD6lEY0ZeONywhHJduKJrit1Bgg0j09dF6AMfiqSvG9S3bBNz7LAE1hXIDIa7+5d/r8yab9mJn+KLhPCuj+6WcV4u6YM31sJFji1ga3gCC4r8dPMVgyJIFOPhrnUyjrHSX1Kph1Hv3VY5p8yLpv1Uj7dqdxh4pjKsrChDv8FHJhp0zQE+9AE9WOzJuS2RX8MS1buznLgq9mv6uzg9MOzrCqmanlF8IzPLnLrSFNn8Gkv43Uof3IVSKgeZ1Ul8ScGPL62mrZdFRAoHITt1s13Ko9MP0ALLkZHAKZb8tGSuzMZ8BrCI1R2fZ6UAiMamiobAgt7MPPTThKPK987jzlgGVP0JzMY+nhpGdKyqI3F92xd1AVLh7bp9dgf5wHJStojFxkXBotZouqj1foB3sZnxYVFiZiXgfYp7iRmKnGdM3v23J1U3WDrSRB/JZ9FS; 4:LJVwV+hmGYylIsVCS9QH+49gq9za6AZertf2+E0z3hcTyjWMS5gbIX+chz0i3Tu3U37VNWcrmOeRqk436x8aaqg7NaKcdbK10yYFNw2wMIdjf3+jrGXpK/fgBiHfu8JG4FpPi27iYS17sHtGac5n86jRqcT5APSrnF9xPugN2PHYiG4cpQzdyYIYGWrY1CMJTonPUHpIPh4Ss9zJE0jciXxT37iJycgId5Ck/rq3bOj5DWuo+tcspRPa2VnWVUWzv2pGuj1nM1nhMhglOhEvCJo6nZFP8UcZANudWt7eFe6/my/zWOJdmbVnz+NmhbIi
X-Exchange-Antispam-Report-Test: UriScan:(173461626932800);
X-Microsoft-Antispam-PRVS: <DB4PR07MB0640076371BD3DCD2164C54E83510@DB4PR07MB0640.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(10201501046)(3231021)(93006095)(93001095)(6041248)(20161123564025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123560025)(20161123558100)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB4PR07MB0640; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB4PR07MB0640; 
X-Forefront-PRVS: 0484063412
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(39860400002)(346002)(376002)(24454002)(189002)(199003)(229853002)(7736002)(101416001)(53936002)(6246003)(6916009)(105586002)(230700001)(50986999)(5660300001)(8936002)(316002)(33646002)(76176999)(2950100002)(53546010)(6666003)(6116002)(68736007)(106356001)(16526018)(36756003)(81166006)(8676002)(25786009)(16576012)(64126003)(3846002)(50466002)(81156014)(58126008)(2906002)(77096006)(117156002)(6486002)(478600001)(97736004)(23676003)(54356999)(65956001)(65806001)(65826007)(31696002)(66066001)(93886005)(31686004)(4326008)(47776003)(966005)(189998001)(305945005)(6306002)(83506002)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR07MB0640; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjRQUjA3TUIwNjQwOzIzOmM0U3JQSUhBbmZjY1FocHhrTENuak8wZ1RN?= =?utf-8?B?OE82Z3RvRjdGcVhZcm9qT0JrTGtPZUs2OWhpSzRka1RiUDc2RHJHWWFOSVFj?= =?utf-8?B?NUNkMm94WTVUT1BzSitsVFBwQkVUb1hLSGtOdkYxQk5PUFFRNGxXblNVdUlW?= =?utf-8?B?MUlEOXFyL1liSHE3ODI5WTU3WTMrT3ovU3VBSGpFNlA5R21lQVgrcU0rYlNm?= =?utf-8?B?dmQybFExOGZaVlN6dkNiNlNhYjdXWUpua0hYdzJUazY1MzRIWEx1VmV0b3BU?= =?utf-8?B?VkdRZ0t5QW1jWDllMWJFQ0VLWG9pRFRFMC9xMS9QY2d6d1puVjVXSEZ2NWVh?= =?utf-8?B?SHp3cFRHaDhmb2JFWkFrLy9DYXM4MDZCcnNTWHhhdFBTdi9lVlF6MWd0NUhB?= =?utf-8?B?YWFHeDYzQXQwVVVkSHNKTkxXZ3E5eUQ5TlVrVVkzdWNGUVYyVmJwMmF4TnQr?= =?utf-8?B?YURaZXVGVUZXTXBzaE5jN1AzdjNIOXZhRTNZaTQzMHkzMHc3MWlaMHE5U0Fn?= =?utf-8?B?YVYwQ214dTJvQ3g1L0RVbXRNazhOVFg2dEFjSkR1Q2l0c2FST3pVWGxzeWli?= =?utf-8?B?NFMzYWNHbVlOZnpPb2MybWJ2ajFPUjJPR3NrU3lEYlhIMC95UzJGOFNFaSt2?= =?utf-8?B?dmtNVVFKY2YwWGJ4YWRjZ1hJVkxsLytkcGNWc2lHZ1E3azIwMEl6eDY1cVlL?= =?utf-8?B?QW04SFZUeTlHMkRxcEphS29JWURGQ3JaVXVxZHpEZ3Z0ek1UQXI4ZWdtOFV2?= =?utf-8?B?MHVIUDN3bUR1RVpUY0VrbXhXNk1qRXFGd0d5SUVzWUZVUlNBSFp1dGZocGRZ?= =?utf-8?B?ZHloVmpkaFpBMlNtNHdIR0FtVUg2anRQTHRhR1d1ZVBNTDRHcmFxUGZUbzJ6?= =?utf-8?B?SFdSRWdzVFIxUHdvVnBhcGlrL0pBVjF1a2MydmhXQUI2U2V5YnlpeC91R3dE?= =?utf-8?B?dWdsTjVrdzIvNHl6U1hBUzJjQURSREp4dG94THdDUDJhSUZJeHVaVlZqQlUy?= =?utf-8?B?ZEttNDc2cW52alNBNUttOE03UGFuclNEMXMxUG1HR1FXcGtqNTVBNkp2a1V3?= =?utf-8?B?YWdodlkzNUdiODhrbWFFejlhTU5hcit0WDRQTEt1Vk9wSXBLTHRTUTVWb3NP?= =?utf-8?B?VTl3VEF0cHlhUTQ3QjRNV1VEeTJhZWw1QkdOUi9GUWZ2VHdmTXlXZElMSnFv?= =?utf-8?B?VkIyZ01VWm9zZ3lhREZ6KzIrR0o4Rll4UG1WbDdrRzFtd1F2WEljMHR6R0FF?= =?utf-8?B?b28wWlV3Z0hnbkthajJidTQ4RG94KzNYTktHOVhEWG1ZY1dyWjhaWHF6dDhE?= =?utf-8?B?RVNzbHpTekdUN2djZ2RpSTlFSnR6WnhGNDI4VVhLbGdmNkVzUW5jYkVEbURS?= =?utf-8?B?a29CMk9rNU04elNNMHY3U1oyWXpkdW5CNEZkemEwMGFlRzNTMzBUQW1yZkRL?= =?utf-8?B?SlJZTk5GMUI2b1pVODFPMytrTmhMVmRscUlVd3dSaUhXQlZOWlVLbDZwR1Rq?= =?utf-8?B?dGZzT3RkdThyc20xbWlNQlZRVm10RkpIWlhXUUlCNU0wd1B4YnkzaG5uNXZP?= =?utf-8?B?a2NYQmYrS29ib1hyYy9USWhJMTVCWXRXeXFkYjlwQXBQbmxzQmU1YW54NFg3?= =?utf-8?B?TUMvT1pPQ0MvcUR5OWpPS0owNHNpem9saEdRSE5Va1FYc1FsdndpbEI5VG9X?= =?utf-8?B?akVUWTJNbENiWTRsanVaVU02ZGEvdVpUWWtQT05zR2g5Sm1xYnd6KzV1b2pR?= =?utf-8?B?QWh0enc4M3BjWHdpUk9VcTQzb3FzclY2QTlyWFJEVUZ0cFBWcUhaWUdMZ2J0?= =?utf-8?B?R3lJRitlUU1vTHQvRVJJZTdUdFN3VmhYTXZiSGpZVllKMjVJVVpKSTUxUXVv?= =?utf-8?B?M3ZJTzFZYWxFb1V3ZnBRYmU2YVdnRWhnblJKdTI1a1FKQzJMMkpnVlRtUlFu?= =?utf-8?B?ZDlGYjJJaUp3PT0=?=
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0640; 6:Tw9S7QgnJn4XNejMdjcvjvn/ggugXIgf+brgLCSq7rbwgAXV1NT7xeYF1UEXEQ4EvoqW/9Kzojj5SSRf7JQq+UZt9lRLoyCpCasfzeWvpog1puv+U1X2cc1CVAaR16ihPXehRUerXG68Xg+YCv55ibnje/4Ck1pnlZcFAmeXieSTR+SVyQzaccnR3LTIopaOz26zfQ2HUo68rAkY4Djy5xw26OF3z7bzDEW/nSwnTg2YGsn0Vat6WteHVGHFikZZdt9loVAM0Vs0x/LL8RuSXWGIndYuto6RXNTLdqupp3iGQ8PvYslSWeXPmBE1HqeeuspvMyFlKaupLqpbSmAqjwUzVGshNRXK1BwJ+K+U/QE=; 5:g33iPDNUnVgjuGeZlAaMlCe3Wi7kual6zDAD52t3mzYxd4vKWXY5XDAcza9c7UBDFSXOz0xYNcpoybqcP6pLzwkK8pAqieIkzVS6GMgmB2b1wO5E12x8GxnN1Xbr6bSqiPNGYN/dVgESWihNkmDDMn5gwY7x15tFs5NvQxzUHMA=; 24:Q5f/q3tjfU1tJPWns5QnR93oUua29pwB5d6ljWdIyjT25czdZv6epeufLm8K/8tKaT/PxtIw/DdVUnucscoOsLVFiTmOLySW1tkUdZSUAUw=; 7:05ljaRAjWPxLsBsImk5DP/mDQSgq8j5f/exez2gCxIuzrUbhfmZSOHU9c/zW/UFlRPLdcRx0J90y+t9fKS3BNVxPK6ZCEQj19paJXOs6UKuRREaa9cZGCBwPj+BRYCIXFQX10/3ayu+cim3cZLYLJneDfXTwaPrUfZKzq6NthVMONuOgNBsEy5WmXidA4sLHOin3nheeizoxl84AJpmDc39282FRFKs2ga3nowyBP32NFKWiJ+AMLl/zw/6McerC
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 07 Nov 2017 07:49:43.7381 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: a658c25a-3849-4f37-9d08-08d525b41c5f
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR07MB0640
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplleLIzCtJLcpLzFFi42KZGbHdSXdWKmOUwcw+IYtnG+ezWEz6eo7N gcljyZKfTB6TToQFMEVx2aSk5mSWpRbp2yVwZWx6952toF26YuLKFrYGxvuiXYycHBICJhK9 l14xdTFycQgJHGaU2LeuhxnCOc4ocWI2hMMi0MssMeXPbhaQFkaBRIm/996yQVS1MkmsuLoQ LCEsYCHx4MI/VhBbREBHYvb2w2wgNrOAsMS7dbNZIBpOskjMfgExiQ2oYcut+0A2BwevgL3E +tZ0kDCLgIrEr54tjCC2qECMxMQHF8FsXgFBiZMzn4C1cgp4SHw7848ZpJVZQFNi/S59iFXi EreezGeCsOUltr+dwwzxpoLE/h8rwW6WEJjOKNG6FmKOkIC2xPJnLSwQRbISR8/OgbJ9Jd58 e80M0TCTUeLu234op4Fd4s6Vn0wQVVoSz3Y2skIkfrBJLN/zjREiYS3xaFs/G4SdLXF/53wm iKIrrBITZz9mhUjISHR1b2KewKgzC8l7sxBemoXkpVlIXlrAyLKKUbQ4tbg4N93ISC+1KDO5 uDg/Ty8vtWQTIzBxHNzy22oH48HnjocYBTgYlXh4ZyczRgmxJpYVV+YeYpTgYFYS4d2uzhAl xJuSWFmVWpQfX1Sak1p8iFGag0VJnNdh34UIIYH0xJLU7NTUgtQimCwTB6dUA2OPo/rZf/u2 9ZsHPnYpuNISv0J/6utFXc9CZdyPd31f/dI4cOqUNfM7e0ranmZcONW965L4MlOjVd8qppsX vK7MfmO170rI76ubuRpytoct3LxBt3Dp4Yvp0z6J9P73OjGDbXp0SpK0+2Lt7us/Zm927frh POPcNomfEQJJTl2/fb6cVC5I+MmvxFKckWioxVxUnAgAUdpsaBgDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aodckAanP0D0VtTBsVOIyOupF6g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 07:49:51 -0000

Hi Keith,

ah, now I see where you are coming from. Yes, we are also discussing
whether ISOC should be closer to a neutral "convener" or, instead,
"advocate" more strongly in certain areas... and the ideal role may
depend on the particular area, actually.

In summary, yes, we are thinking about it... and, FWIW, based on my
discussions many IETFers share your view.

Cheers,

Gonzalo


On 07/11/2017 9:38 AM, Keith Moore wrote:
> Having "activities", and prominently taking a stand for what's right, are very different things.
> 
> 
> On Nov 7, 2017, at 2:30 AM, Gonzalo Camarillo wrote:
> 
>> Hi Keith,
>>
>> yes, ISOC has activities on that front. For instance, a couple of weeks
>> ago ISOC organized the following Chatham House Roundtable on Encryption
>> and Lawful Access:
>>
>> https://www.chathamhouse.org/event/encryption-and-lawful-access
>>
>> Cheers,
>>
>> Gonzalo
>>
>> On 07/11/2017 2:00 AM, Keith Moore wrote:
>>> Hi Gonzalo,
>>>
>>> Thanks your your reply.  I understand that it's necessary to word things
>>> carefully, but I hope ISOC can find a way to specifically call out both
>>> mining of personal data (whether or not traceable to individual
>>> identities) and mass surveillance (whether or not by state-supported
>>> actors) as significant threats to the public welfare.
>>>
>>> Keith
>>>
>>> On 11/06/2017 05:34 AM, Gonzalo Camarillo wrote:
>>>> Hi Keith,
>>>>
>>>> thanks for your comments.
>>>>
>>>>> In the context of ISOC it's important to understand that the Internet
>>>>> can be used for good or ill, but it's in danger of becoming more of the
>>>>> latter.   Promoting the Internet as if it were a universal good, while
>>>>> ignoring the various ways it can be used to exploit or harm its users,
>>>>> does not seem either responsible or consistent with ISOC's history.
>>>>> There are of course limits to what ISOC can do about it, but I don't
>>>>> think ISOC should be silent and/or pretend that it's not a problem.
>>>> I agree with you. In fact, this is a topic I also brought up in my
>>>> closing talk at ISOC's 25th anniversary event a few weeks ago. In the
>>>> past, it was assumed that more connectivity was always good. Nowadays,
>>>> as you point out, ubiquitous and constant connectivity has clear
>>>> downsides as well. In addition to the examples you discussed, Internet
>>>> addiction and the social problems it is already causing in some parts of
>>>> the world (e.g., increases in car accidents, social isolation, etc.) is
>>>> an important concern as well.
>>>>
>>>> I also agree with you that there are clear limits to what ISOC can or
>>>> should do about it. As I mentioned in previous emails, in addition to
>>>> the work on the mission statement we are working on defining ISOC's
>>>> scope in more detail in different areas, "policy" being one of them. We
>>>> are currently working on identifying particular areas where, based on
>>>> ISOC's capabilities, we should engage. We are also identifying areas
>>>> where ISOC should not get involved.
>>>>
>>>> With respect to capturing this in the mission statement, the proposed
>>>> text reads as follows: The Internet as "a force for good in society".
>>>> That sentence tries to capture the social benefits we are after (as
>>>> opposed to just wanting connectivity for the sake of it, without any
>>>> "higher" purpose).
>>>>
>>>> Cheers,
>>>>
>>>> Gonzalo
>>>
> 


From nobody Tue Nov  7 00:59:51 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 59DD613FCB2 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 00:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=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 7u6WBN6CCAAd for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 00:59:47 -0800 (PST)
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 4B46413FA6E for <ietf@ietf.org>; Tue,  7 Nov 2017 00:59:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 815D2BE2E; Tue,  7 Nov 2017 08:59:39 +0000 (GMT)
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 y5O-fleHQJSA; Tue,  7 Nov 2017 08:59:37 +0000 (GMT)
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 8CAA1BDF9; Tue,  7 Nov 2017 08:59:37 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1510045177; bh=HJaWEmW7Q1IW7hoI7pav2U4OH+K19DE1E3LQY4mUfVc=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=xiPBKahjEGa9/Jlpubpx52HUZF9zgV5LVE7b49Aba9lePQrdCJ3RKpS9Eg2wbQSpx ApM5pwLGEsx+qndbxEMv3QEeoRR9QLroGSmv024i7AXliLupjof/34ZPeATDTv/Oqu aXwQx4x1Dv5Epy3ZI6bZHpBeWKLqDgqSXZIdlK4g=
Subject: Re: Proposal to revise ISOC's mission statement
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Keith Moore <moore@network-heretics.com>
Cc: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
Date: Tue, 7 Nov 2017 08:59:36 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wXqGWsPdSJWU8cd5NLNJV7rjOBJ9wVKcR"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5KONHgWm6v7jdpJLgSo6MS5fFss>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 08:59:50 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--wXqGWsPdSJWU8cd5NLNJV7rjOBJ9wVKcR
Content-Type: multipart/mixed; boundary="i9N9na0FBHvEmoInrvtKfk5O7J6jJGEsN";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>,
 Keith Moore <moore@network-heretics.com>
Cc: ietf@ietf.org
Message-ID: <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
Subject: Re: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com>
 <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com>
 <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com>
 <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com>
 <6.2.5.6.2.20171029130937.113d0e80@elandnews.com>
 <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com>
 <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
 <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com>
 <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com>
 <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com>
 <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>
In-Reply-To: <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>

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


Hiya,

On 07/11/17 07:49, Gonzalo Camarillo wrote:
> Hi Keith,
>=20
> ah, now I see where you are coming from. Yes, we are also discussing
> whether ISOC should be closer to a neutral "convener" or, instead,
> "advocate" more strongly in certain areas... and the ideal role may
> depend on the particular area, actually.
>=20
> In summary, yes, we are thinking about it... and, FWIW, based on my
> discussions many IETFers share your view.

As an input there, (not that you'll be short of them:-),,, I
hope that ISOC don't differentiate too much between government
surveillance and corporate surveillance. While the latter
may have some fig-leaf of so-called "consent" or clicked-EULA,
it's the same information being gathered/centralised etc. (And
of course the latter form of surveillance can nicely feed the
former when companies are compelled.)

I realise that commenting on corporate surveillance might be
harder for ISOC and IETFers as we end up criticising basically
ourselves/our-employers, but ISTM that logic and consistency
call for doing just that.

Cheers,
S.


>=20
> Cheers,
>=20
> Gonzalo
>=20
>=20
> On 07/11/2017 9:38 AM, Keith Moore wrote:
>> Having "activities", and prominently taking a stand for what's right, =
are very different things.
>>
>>
>> On Nov 7, 2017, at 2:30 AM, Gonzalo Camarillo wrote:
>>
>>> Hi Keith,
>>>
>>> yes, ISOC has activities on that front. For instance, a couple of wee=
ks
>>> ago ISOC organized the following Chatham House Roundtable on Encrypti=
on
>>> and Lawful Access:
>>>
>>> https://www.chathamhouse.org/event/encryption-and-lawful-access
>>>
>>> Cheers,
>>>
>>> Gonzalo
>>>
>>> On 07/11/2017 2:00 AM, Keith Moore wrote:
>>>> Hi Gonzalo,
>>>>
>>>> Thanks your your reply.  I understand that it's necessary to word th=
ings
>>>> carefully, but I hope ISOC can find a way to specifically call out b=
oth
>>>> mining of personal data (whether or not traceable to individual
>>>> identities) and mass surveillance (whether or not by state-supported=

>>>> actors) as significant threats to the public welfare.
>>>>
>>>> Keith
>>>>
>>>> On 11/06/2017 05:34 AM, Gonzalo Camarillo wrote:
>>>>> Hi Keith,
>>>>>
>>>>> thanks for your comments.
>>>>>
>>>>>> In the context of ISOC it's important to understand that the Inter=
net
>>>>>> can be used for good or ill, but it's in danger of becoming more o=
f the
>>>>>> latter.   Promoting the Internet as if it were a universal good, w=
hile
>>>>>> ignoring the various ways it can be used to exploit or harm its us=
ers,
>>>>>> does not seem either responsible or consistent with ISOC's history=
=2E
>>>>>> There are of course limits to what ISOC can do about it, but I don=
't
>>>>>> think ISOC should be silent and/or pretend that it's not a problem=
=2E
>>>>> I agree with you. In fact, this is a topic I also brought up in my
>>>>> closing talk at ISOC's 25th anniversary event a few weeks ago. In t=
he
>>>>> past, it was assumed that more connectivity was always good. Nowada=
ys,
>>>>> as you point out, ubiquitous and constant connectivity has clear
>>>>> downsides as well. In addition to the examples you discussed, Inter=
net
>>>>> addiction and the social problems it is already causing in some par=
ts of
>>>>> the world (e.g., increases in car accidents, social isolation, etc.=
) is
>>>>> an important concern as well.
>>>>>
>>>>> I also agree with you that there are clear limits to what ISOC can =
or
>>>>> should do about it. As I mentioned in previous emails, in addition =
to
>>>>> the work on the mission statement we are working on defining ISOC's=

>>>>> scope in more detail in different areas, "policy" being one of them=
=2E We
>>>>> are currently working on identifying particular areas where, based =
on
>>>>> ISOC's capabilities, we should engage. We are also identifying area=
s
>>>>> where ISOC should not get involved.
>>>>>
>>>>> With respect to capturing this in the mission statement, the propos=
ed
>>>>> text reads as follows: The Internet as "a force for good in society=
".
>>>>> That sentence tries to capture the social benefits we are after (as=

>>>>> opposed to just wanting connectivity for the sake of it, without an=
y
>>>>> "higher" purpose).
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Gonzalo
>>>>
>>
>=20
>=20


--i9N9na0FBHvEmoInrvtKfk5O7J6jJGEsN--

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

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

iQEcBAEBCAAGBQJaAXX4AAoJEC88hzaAX42iteEH/20bX/kGFnDxv0kvxrYpbINb
5plNfVk4XhUUUQf3NGf+KlzsEZYusHVcUcto75zkRm3nULTmmLPDekkE9VSPnvKa
12GRTpsLTrf5TJvbLUcN+6tcu/kCW+CkODxg4lQM78T+zlQiPicjYNrPt1I8/MBJ
5Li+DOAXgoxtemMy5aAclh/VJT0qKQ5zbax/6Y99+wD+dB1litS0yiLendwX+qFp
EKkjmD/FKadAxryyobzZrAoxrOGhTk3stE7kZuBDIbAOQt/+Zr2GFwXTpl0EjaP3
l8CdJdFV8ACEyDU9dPn5vLs59d5SUpMDW4Ob2BhZY6n1+A2B2C6ypdB/PvTr3dI=
=t0OW
-----END PGP SIGNATURE-----

--wXqGWsPdSJWU8cd5NLNJV7rjOBJ9wVKcR--


From nobody Tue Nov  7 01:19:32 2017
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8F913FDF3 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 01:19:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLNKYcZEEHEg for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 01:19:30 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B38D13FD7B for <ietf@ietf.org>; Tue,  7 Nov 2017 01:14:32 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 7915A20BA9; Tue,  7 Nov 2017 04:14:31 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Tue, 07 Nov 2017 04:14:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=jewxLOQytV3QEJK8rQX0Mw8TZcxu+ 7h6oAtTmT7UNyk=; b=nH1qjrSnO6eBf6puPpYgSvjL2uOhJ9ANM7uzq61wcBxGG OlBtUgMaG5o64g8RI1S1i6SIr11gWE1+OM0WEyOdDdmLU8cF3uUQOaxhP/n/1uHY n9knBEg7buDnPb8r/5ObAV4cv02P90UEXjhX4W0DnmfBb+yJSWyMkAgrFIchHRdE HAMoJIfvuEqBg1Qc2Iskqe+NxZB0/SQ5pwMUk0KlynJ9T2N6Mji/4ZbTVYs9itgI zi/DIL61SdLKjKnI4s4SrbKgXNhdyRCK4ECifFOEDFfCT3Ux+Lbq6TIgN8Z2nHZB OQ+ilNdzK7Rqizx1MW7YGp8O0W3Px6trnzF286SNw==
X-ME-Sender: <xms:d3kBWg8D9dhajBGkKh2XIEznHrthDu3_CeM7RwF5gYZw8DEt4C-MSg>
Received: from [192.168.1.65] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id C3B1E7E6B8; Tue,  7 Nov 2017 04:14:30 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_4CCB5D36-BF89-40B7-980B-FBC4340F5D01"
From: Keith Moore <moore@network-heretics.com>
In-Reply-To: <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
Date: Tue, 7 Nov 2017 04:14:27 -0500
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, ietf@ietf.org
Message-Id: <48E50FD2-452F-4212-88C8-409D796C03A8@network-heretics.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1283)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/697Tc5fmp89Oy8XMjXoVbsRIvHE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 09:19:31 -0000

--Apple-Mail=_4CCB5D36-BF89-40B7-980B-FBC4340F5D01
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


On Nov 7, 2017, at 3:59 AM, Stephen Farrell wrote:

> As an input there, (not that you'll be short of them:-),,, I
> hope that ISOC don't differentiate too much between government
> surveillance and corporate surveillance. While the latter
> may have some fig-leaf of so-called "consent" or clicked-EULA,
> it's the same information being gathered/centralised etc. (And
> of course the latter form of surveillance can nicely feed the
> former when companies are compelled.)
> 
> I realise that commenting on corporate surveillance might be
> harder for ISOC and IETFers as we end up criticising basically
> ourselves/our-employers, but ISTM that logic and consistency
> call for doing just that.

+1


--Apple-Mail=_4CCB5D36-BF89-40B7-980B-FBC4340F5D01
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Nov 7, 2017, at 3:59 AM, Stephen Farrell =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"font-family: monospace; ">As an =
input there, (not that you'll be short of them:-),,, I<br>hope that ISOC =
don't differentiate too much between government<br>surveillance and =
corporate surveillance. While the latter<br>may have some fig-leaf of =
so-called "consent" or clicked-EULA,<br>it's the same information being =
gathered/centralised etc. (And<br>of course the latter form of =
surveillance can nicely feed the<br>former when companies are =
compelled.)<br><br>I realise that commenting on corporate surveillance =
might be<br>harder for ISOC and IETFers as we end up criticising =
basically<br>ourselves/our-employers, but ISTM that logic and =
consistency<br>call for doing just =
that.</span></span></blockquote></div><br><div>+1</div><div><br></div></bo=
dy></html>=

--Apple-Mail=_4CCB5D36-BF89-40B7-980B-FBC4340F5D01--


From nobody Tue Nov  7 06:05:45 2017
Return-Path: <nomcom-chair-2017@ietf.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 C39EF13FE91; Tue,  7 Nov 2017 06:05:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2017 <nomcom-chair-2017@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: NomCom Second Call for Feedback and Office Hours: IETF 100
X-Test-IDTracker: no
X-IETF-IDTracker: 6.65.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <151006354277.18561.585049119013667650.idtracker@ietfa.amsl.com>
Date: Tue, 07 Nov 2017 06:05:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HDH9Apb_E_thz3a_HzrCKXt5uCw>
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, 07 Nov 2017 14:05:43 -0000

All -

Please consider entering your feedback for the 2017-2018 NomCom early this
week. We'll be doing on-site interviews in Singapore and would appreciate your
inputs as we sort through our options. We have nominees to consider for the
the IESG, IAB, and IAOC this cycle:

https://datatracker.ietf.org/nomcom/2017/feedback/

If you have general feedback areas or positions please send email to:

nomcom-2017 at ietf dot org

On-site in Singapore you can also give your feedback directly to the NomCom 
either by talking with any NomCom Member (identified with an orange dot on 
their badge). The full list of members can be found here:

https://datatracker.ietf.org/nomcom/2017/

or drop by during our open office hours:

MONDAY	11/13/17

	1515-1540      Partial overlap with the beverage and snack break
        NomCom Office Hour: Fullerton Room

TUESDAY	11/14/167

	1515-1540	Partial overlap with the beverage and snack break
	NomCom Office Hour: Fullerton Room

WEDNESDAY   11/15/17

	1200-1335	Lunch break
	1515-1540	Partial overlap with the beverage and snack break
	NomCom Office Hours: Fullerton Room

THURSDAY  11/16/17
	1250-1335	Lunch break
	1515-1540	Partial overlap with the beverage and snack break
	NomCom Office Hours: Fullerton Room

Thanks -

Peter Yee
NomCom Chair 2017-2018
peter at akayla dot com (preferred if you have SPF problems with my MTA)
nomcom-chair-2017 at ietf dot org


From nobody Tue Nov  7 06:38:38 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 6044D13FE7A; Tue,  7 Nov 2017 06:38:36 -0800 (PST)
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 wLzM5T2CppNE; Tue,  7 Nov 2017 06:38:29 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::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 91E2013FD98; Tue,  7 Nov 2017 06:38:29 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id h4so15417168qtk.8; Tue, 07 Nov 2017 06:38:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=hx68YFGdHuj2zX6MvaJkatNdn3oXfGo+B2eQPN54Jmo=; b=txKuZGcuAtbhEmsdBHzZbFmVY62HnwiCGJGKaExvcta9aPNyzlQoxS5GxQdibu9xit Rfl1wS49DI+al/Dtvh3NooOLgQrIAdsy07r4KHhKOc8bFAI+m+ATB/UtJV7DbQ+wRqvH FB9/1NSGjicX9XDEvtvZineXo9UK2ZzRIG3jmiGp4K8jBTBseMwKNPXxW1Uoxb0nrwQd J+d4RplVSYiV8RyZGDmFN7W7K78BOlUBUU1gN2M6HxNAUjNX7l+1UmBMtC4YiJsAr17Y OdaFnPo5uyyl6It0h2+6LKrsysexq8rmzy35D8YGxY2jgS93gKcF3C84QJ/Ylphm2v++ Yb0g==
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:in-reply-to :references:mime-version; bh=hx68YFGdHuj2zX6MvaJkatNdn3oXfGo+B2eQPN54Jmo=; b=oJK0Fgr/d/eqy+N/UM+Ar87qjXjPepxYuPvLkibaBcZvkL5DydVAagAKqmNcrazl6T sIddH+VlgN/yDPzuDvGggR8G/fzBcd/x/lSHhSPB2pWQTl4MOHyKswv2zY0Ze6UIN+Ea nnO0avvi+PqmFxsoiAMnMQG1533ahxO4OIpBSLxs3KJyWm0VjQppl1EkIrJaocDAmQyn qVIIDb0DdFzrJ0YGIX7ApjATDMPgcD6QVv/VM5IShzOvlWsN7AXvvXzvISoA7MJRWSfZ 0FVjl+s+y7GznPBIfVVPJte0DVs+vg8ivgWCB/Aauhg7THI0n5z+5uXnzj/B8YAGsmBD h+LA==
X-Gm-Message-State: AMCzsaVZwseAYevATIfZVHmM4JRpiDbZIgrxhfY3+7TFKJrwZ2OunkMb NmYohthWP5io7YdAv1SO8plrmut3s30=
X-Google-Smtp-Source: ABhQp+R4AbiZoAXmdrbLlnk2uwit81QyHfxgY6frrCkGFtHaUO/ZnbDDJnP16hMTwg0YgMZve/iWeA==
X-Received: by 10.200.42.118 with SMTP id l51mr29566124qtl.37.1510065508278; Tue, 07 Nov 2017 06:38:28 -0800 (PST)
Received: from [172.19.36.243] ([2001:4878:a000:3000:d40b:f5ef:9d59:c34d]) by smtp.gmail.com with ESMTPSA id f62sm996278qkh.51.2017.11.07.06.38.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 06:38:27 -0800 (PST)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "100attendees@ietf.org" <100attendees@ietf.org>
Subject: Re: CFP: PechaKucha at IETF-100
Date: Tue, 07 Nov 2017 09:38:28 -0500
Message-ID: <399B1F51-1C36-4F6D-B1ED-2F293707A6BF@gmail.com>
In-Reply-To: <9B50505D-A7E7-40E0-B789-419DA14C6021@gmail.com>
References: <9B50505D-A7E7-40E0-B789-419DA14C6021@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_BCA60B84-89D1-49F9-BB6D-91E66953EEBE_="
X-Mailer: MailMate (1.9.7r5425)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P6rO97EQ7pzOa3XAr_CqLEsaJ28>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 14:38:36 -0000

--=_MailMate_BCA60B84-89D1-49F9-BB6D-91E66953EEBE_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

Should have mentioned this yesterday: we=E2=80=99re a bit under critical =
mass =

to hold a pechakucha in Singapore.  If you are on the fence, be brave =

and step up.  It=E2=80=99s fun and you=E2=80=99ll get as friendly a recep=
tion as =

possible at an IETF (although this is not an IETF event).

=E2=80=94aaron

On 6 Nov 2017, at 12:36, Aaron Falk wrote:

> Thinking about doing a PechaKucha in the past and never had time.  =

> **NOW IS THE TIME!**
>
> Come share your favorite stories, rants, or calls to action with your =

> colleagues at IETF-100.  If you have a topic about which you are =

> passionate, you can give a PechaKucha. (Here are two of my personal =

> favorites by =

> [Pete](http://snaggletooth.akam.ai/Prague-videos/07-pete-resnick-8.mp4)=
 =

> and =

> [Brian](http://snaggletooth.akam.ai/Berlin-videos/2_trammel-8.mp4), =

> although there are many other excellent examples.)
>
> What is a PechaKucha, you ask? A PechaKucha is a lightning-talk =

> presentation format, originating in Japan, where a speaker presents 20 =

> image-only slides that are each on the screen for 20 seconds and =

> advance automatically.  With each talk lasting for 6:40, it has the =

> feature of forcing presentations -- good or bad -- to be focused and =

> brief.
>
> This is an unofficial event. Topics are encouraged to be a =

> IETF-related and satirical or controversial in some way, although not =

> mean-spirited.  Anyone can participate in this social event.
>
> Video from the Berlin, Seoul, Chicago, and Prague PKs can be found =

> [here](http://snaggletooth.akam.ai).
>
> Format Details:
>
> * Presentation slots are open to all, assigned first come, first =

> served.
> * To reserve a presentation slot, send a name and title to =

> aaron.falk@gmail.com and receive confirmation.
> * Presenters must agree to adhere to the Pecha Kucha format (20 =

> slides, primarily image-only, automatically advancing every 20 =

> seconds).
> * There are lots of online tutorials and suggestions for how to make a =

> good PechaKucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

> [[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pec=
ha.html)], =

> [[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].

--=_MailMate_BCA60B84-89D1-49F9-BB6D-91E66953EEBE_=
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">Should have mentioned this yesterday: we=E2=80=99re a bit=
 under critical mass to hold a pechakucha in Singapore.  If you are on th=
e fence, be brave and step up.  It=E2=80=99s fun and you=E2=80=99ll get a=
s friendly a reception as possible at an IETF (although this is not an IE=
TF event).</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<p dir=3D"auto">On 6 Nov 2017, at 12:36, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">Thinking about doing a PechaKucha in the past and never h=
ad time.  <strong>NOW IS THE TIME!</strong></p>

<p dir=3D"auto">Come share your favorite stories, rants, or calls to acti=
on with your colleagues at IETF-100.  If you have a topic about which you=
 are passionate, you can give a PechaKucha. (Here are two of my personal =
favorites by <a href=3D"http://snaggletooth.akam.ai/Prague-videos/07-pete=
-resnick-8.mp4" style=3D"color:#777">Pete</a> and <a href=3D"http://snagg=
letooth.akam.ai/Berlin-videos/2_trammel-8.mp4" style=3D"color:#777">Brian=
</a>, although there are many other excellent examples.)</p>

<p dir=3D"auto">What is a PechaKucha, you ask? A PechaKucha is a lightnin=
g-talk presentation format, originating in Japan, where a speaker present=
s 20 image-only slides that are each on the screen for 20 seconds and adv=
ance automatically.  With each talk lasting for 6:40, it has the feature =
of forcing presentations -- good or bad -- to be focused and brief.</p>

<p dir=3D"auto">This is an unofficial event. Topics are encouraged to be =
a IETF-related and satirical or controversial in some way, although not m=
ean-spirited.  Anyone can participate in this social event.</p>

<p dir=3D"auto">Video from the Berlin, Seoul, Chicago, and Prague PKs can=
 be found <a href=3D"http://snaggletooth.akam.ai" style=3D"color:#777">he=
re</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#777">aaron.falk@gmail.com</a>=
 and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good PechaKucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/"=
 style=3D"color:#777">1</a>], [<a href=3D"http://blog.indezine.com/2012/0=
5/10-tips-to-create-and-present-pecha.html" style=3D"color:#777">2</a>], =
[<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/=
" style=3D"color:#777">3</a>].</li>
</ul>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_BCA60B84-89D1-49F9-BB6D-91E66953EEBE_=--


From nobody Tue Nov  7 06:59:51 2017
Return-Path: <rstruik.ext@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 4E07A13FED0; Tue,  7 Nov 2017 06:59:44 -0800 (PST)
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 zfaeXzuLaAXd; Tue,  7 Nov 2017 06:59:42 -0800 (PST)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::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 B225513FEB5; Tue,  7 Nov 2017 06:52:39 -0800 (PST)
Received: by mail-it0-x230.google.com with SMTP id y15so2705878ita.4; Tue, 07 Nov 2017 06:52:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=2AfF2Md+Hxn3JLIUSIPE0v+nGy1DoU17XRfoknnia80=; b=DmTDICcR10vxVuiuHod5MPTbMbcqKjVdlmWllU7fkBAZBxqFrqnVNVbnmBWJU/9cjU JZ4UTR4gwciSEdAZ3xher/XKXoO4iMqdECjmFbXFF3BJoJooBIuUCyvA+zsFYbmzWLdD vbBYw22PWWJeIcrYn3p2JlqjWxcF5rGOLZTV/yxxojSXij2gAJ1JLKWox0gPg4EDpNSD UcZdJILD2xfmwi/3c8o9V9WpMkAMGW2onnrOh/oNgMvghSoQG/ByIuwXf0cUn9RTwnwZ XavqehI+Iv/oglKsRiVsKaMe5OJ+9bZ/x6ESzW77/Lcs1k5zVlxkZq3pBXQRq1c3EFVa Ktfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=2AfF2Md+Hxn3JLIUSIPE0v+nGy1DoU17XRfoknnia80=; b=MGx4KXKdKk92FOGxIEybORCrcWltwkvQEuvOM7U3J28Xz3cufybIJojLXs8C12Bqyr /tjFXfz7D5BiUJr79eQMpPqa9wEAeXHqEV6+0INDlR9f5YfZ3kYe/+gJnHxjup8zFweI iGd0rIzTClZsHU4ruO6tDNLbftxeWJWF9EQR01Qw5+93+hYDlC+6eoAPAFoP44j77/1A 6Q0STxMm2WjXpR/tdY4zamvbLnXjNErZsiji3nbKcLOelF3glBvlcsy5dG6HmzDpbTcy 6KqL6h1VqzOfCd8FsgMLFZxCnfSzXnmII1VGN0AU2LKGXZQMQAJPT6s8mYQFf00ULHB+ +6RA==
X-Gm-Message-State: AJaThX4RwvNq5XyohR17kLr38ktNhIulCJOzZj2GcLqiMZ6oDAkmX/cY MeTCN00l3+mjFDHO9z9kN97+ZA==
X-Google-Smtp-Source: ABhQp+TD0waSm/M36VvbnMBNjsbF6ukeiE2ELqnGC402lMXHjZTLxYjzVVIWjceuM45MoD8m+ZOVcg==
X-Received: by 10.36.112.143 with SMTP id f137mr2315902itc.84.1510066358713; Tue, 07 Nov 2017 06:52:38 -0800 (PST)
Received: from [192.168.0.14] (CPE7cb21b2cb904-CM7cb21b2cb901.cpe.net.cable.rogers.com. [99.230.209.238]) by smtp.gmail.com with ESMTPSA id q1sm906713itc.9.2017.11.07.06.52.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 06:52:37 -0800 (PST)
Subject: (on PUFs) Re: [Lwip] [IoT-DIR] Iotdir early review of draft-ietf-lwig-crypto-sensors-04
To: Samita Chakrabarti <samitac.ietf@gmail.com>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: "lwip@ietf.org" <lwip@ietf.org>, "draft-ietf-lwig-crypto-sensors.all@ietf.org" <draft-ietf-lwig-crypto-sensors.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Iot-dir@ietf.org" <Iot-dir@ietf.org>
References: <150996104393.8207.2811572203550087788@ietfa.amsl.com> <AM4PR0801MB270650AF0ED72FABD13EA028FA500@AM4PR0801MB2706.eurprd08.prod.outlook.com> <CAKmdBpeP9A8VNGB9tCE=wYyBvAMzvZs4vBJq3uS6QoTbVsa4zg@mail.gmail.com>
From: Rene Struik <rstruik.ext@gmail.com>
Message-ID: <a3ca29f7-e2ef-175e-0348-babd97d71ae1@gmail.com>
Date: Tue, 7 Nov 2017 09:52:33 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAKmdBpeP9A8VNGB9tCE=wYyBvAMzvZs4vBJq3uS6QoTbVsa4zg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------0071639AD541C804D543813E"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/khc-uHoVj8P2TehS-daiZHgbfNs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 14:59:44 -0000

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

Hi Samita, Hannes, et al:

I gave a presentation on physically unclonable functions at NIST key 
management workshop 5 years ago (see [1]), which explains the main 
concepts. Please note that the "unique device property" is lost as soon 
as the PUF f or a deterministically-derived key K=H(f) is exposed (see 
Slide 6 -- hence, the color coding in "red", not to be exposed 
material). One needs to do extra tricks, i.e., design a 
challenge-response protocol that witnesses possession of f without 
revealing this, to use this for ongoing authentication. There are ways 
to do this, though.

Best regards, Rene

[1] R. Struik, “Secure Key Storage and True Random Number Generation,” 
presented at/NIST-KMW: NIST Cryptographic Key Management Workshop/, 
Gaithersburg, MD, September 10-11, 2012

Available from 
https://csrc.nist.gov/csrc/media/events/cryptographic-key-management-workshop-2012/documents/struik_nist_kmw_2012.pdf


On 11/6/2017 11:21 PM, Samita Chakrabarti wrote:
> Hi Hannes,
> I have not done comparison with other technologies. But as I mentioned 
> that it exists. I like the fact it can generate unique 'intrinsic-id' 
> based on the physical properties of the chip-set. If IOT-DIR folks 
> like to know more, perhaps I can find out if there is a remote 
> presentation and Q&A session possible from the Intrinsic-id folks 
> sometime in the near future. ( Disclaimer: I have no particular 
> interest other than knowing more about the feasibility  of application 
> of that technology) I was thinking that this ID can be used in any 
> mutual authentication protocols ( especially generating the private 
> key). Do you have more information on them or think otherwise ?
>
> Regards,
> -Samita
>
> On Mon, Nov 6, 2017 at 1:39 AM, Hannes Tschofenig 
> <Hannes.Tschofenig@arm.com <mailto:Hannes.Tschofenig@arm.com>> wrote:
>
>     Hi Samita,
>
>     Do you think PUFs are useful authentication technologies for IoT
>     devices?
>
>     Ciao
>     Hannes
>
>     -----Original Message-----
>     From: IoT-DIR [mailto:iot-dir-bounces@ietf.org
>     <mailto:iot-dir-bounces@ietf.org>] On Behalf Of Samita Chakrabarti
>     Sent: 06 November 2017 10:37
>     To: Iot-dir@ietf.org <mailto:Iot-dir@ietf.org>
>     Cc: lwip@ietf.org <mailto:lwip@ietf.org>; ietf@ietf.org
>     <mailto:ietf@ietf.org>;
>     draft-ietf-lwig-crypto-sensors.all@ietf.org
>     <mailto:draft-ietf-lwig-crypto-sensors.all@ietf.org>
>     Subject: [IoT-DIR] Iotdir early review of
>     draft-ietf-lwig-crypto-sensors-04
>
>     Reviewer: Samita Chakrabarti
>     Review result: Ready with Nits
>
>     I have reviewed draft-ietf-lwig-crypto-sensors-04 document for 
>     IOT-Directorate review. The following are my comments:
>
>     General : The document is easy reading and informative about
>     current and previous work. It is ready to publish with minor
>     changes based on review comments.
>
>     Other comments:
>     Introduction:
>      It might be useful to discuss/clarify that multi-level security
>     may be  important for IOT devices  all the way from 'bootstrapping
>     and management' to  application security. That perhaps can include
>     obtaining IP-addresses  securely, mutual authentication between
>     server and devices , etc. ( see
>     https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-03
>     <https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-03>) in those
>     cases where each  device has an IP address.
>
>     Section 2:
>     Regarding problems of provisioning and management of networks for
>     the IOT devices there may be additional issues – 1) different
>     types of IOT devices and the lack of standards way to provision
>     them as they might be talking different RF technologies and
>     running L2 protocols only. 2) The iot nodes may be moving
>     individually or collectively and change networks; identifying the
>     movement of the iot nodes or identifying a particular node at any
>     point of time uniquely requires an intrinsic identification which
>     might be useful to set during bootstrapping of the node
>
>     Regarding related work – does it consider IETF IOT security work
>     only? There have been some work and thought process going on
>     regarding blockchain IOT security in the industry. Perhaps that is
>     out-of-scope of this document, but I wanted to mention for
>     authors’ considerations.
>
>     Section 5:
>     Authors of the document may also want to browse a SRAM PUF based
>     technology which provides unique ID based authentication mechanism.
>     https://www.intrinsic-id.com/intrinsic-id-joins-wi-sun-alliance/
>     <https://www.intrinsic-id.com/intrinsic-id-joins-wi-sun-alliance/>
>
>     Section 9:
>     Does the example simulate any particular deployment model or
>     research experiments ? It might be good to clarify that. Section
>     10 and 11: Looks like section 11 is closely related to section 10.
>     Should they be combined together ?
>     Else some more text is needed in section 10 on design trade-offs.
>
>     Section 13:
>     Does this document recommend one layer of security to IOT devices
>     ? There are different types of IOT devices – some of them are very
>     tiny and some are more capable. Some definitely benefit for
>     multi-level security  than single layer of security.  L2 security
>     is generally recommended for for all IOT networks. Does data
>     object protection only protect the  application data (payload) or
>     more ?
>
>     Thanks for the initiative in documenting the valuable work in IOT
>     security implementation and crypto comparison. -Samita
>
>
>     _______________________________________________
>     IoT-DIR mailing list
>     IoT-DIR@ietf.org <mailto:IoT-DIR@ietf.org>
>     https://www.ietf.org/mailman/listinfo/iot-dir
>     <https://www.ietf.org/mailman/listinfo/iot-dir>
>     IMPORTANT NOTICE: The contents of this email and any attachments
>     are confidential and may also be privileged. If you are not the
>     intended recipient, please notify the sender immediately and do
>     not disclose the contents to any other person, use it for any
>     purpose, or store or copy the information in any medium. Thank you.
>
>
>
>
> _______________________________________________
> Lwip mailing list
> Lwip@ietf.org
> https://www.ietf.org/mailman/listinfo/lwip


-- 
email: rstruik.ext@gmail.com | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Samita, Hannes, et al:<br>
      <br>
      I gave a presentation on physically unclonable functions at NIST
      key management workshop 5 years ago (see [1]), which explains the
      main concepts. Please note that the "unique device property" is
      lost as soon as the PUF f or a deterministically-derived key
      K=H(f) is exposed (see Slide 6 -- hence, the color coding in
      "red", not to be exposed material). One needs to do extra tricks,
      i.e., design a challenge-response protocol that witnesses
      possession of f without revealing this, to use this for ongoing
      authentication. There are ways to do this, though.<br>
      <br>
      Best regards, Rene<br>
      <p class="MsoNoSpacing"
        style="margin-left:.25in;text-indent:-.25in;mso-list:
        l0 level1 lfo1"><span style="font-size:10.0pt;font-family:
Wingdings;mso-fareast-font-family:Wingdings;mso-bidi-font-family:Wingdings;
          mso-bidi-font-style:italic"><span style="mso-list:Ignore"><span
              style="font:7.0pt &quot;Times New Roman&quot;"></span></span></span><span
style="font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-ascii-theme-font:
minor-latin;mso-hansi-theme-font:minor-latin;mso-bidi-font-family:&quot;Times
          New Roman&quot;;
          mso-bidi-font-style:italic">[1] R. Struik, “Secure Key Storage
          and True Random
          Number Generation,” presented at<i> NIST-KMW: NIST
            Cryptographic Key Management
            Workshop</i>, Gaithersburg, MD, September 10-11, 2012</span></p>
      <p class="MsoNoSpacing"
        style="margin-left:.25in;text-indent:-.25in;mso-list:
        l0 level1 lfo1"><span
style="font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-ascii-theme-font:minor-latin;mso-hansi-theme-font:minor-latin;mso-bidi-font-family:&quot;Times
          New Roman&quot;;
          mso-bidi-font-style:italic">Available from </span><a class="moz-txt-link-freetext" href="https://csrc.nist.gov/csrc/media/events/cryptographic-key-management-workshop-2012/documents/struik_nist_kmw_2012.pdf">https://csrc.nist.gov/csrc/media/events/cryptographic-key-management-workshop-2012/documents/struik_nist_kmw_2012.pdf</a><br>
      </p>
      <br>
      On 11/6/2017 11:21 PM, Samita Chakrabarti wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKmdBpeP9A8VNGB9tCE=wYyBvAMzvZs4vBJq3uS6QoTbVsa4zg@mail.gmail.com">
      <div dir="ltr">Hi Hannes,
        <div>I have not done comparison with other technologies. But as
          I mentioned that it exists. I like the fact it can generate
          unique 'intrinsic-id' based on the physical properties of the
          chip-set. If IOT-DIR folks like to know more, perhaps I can
          find out if there is a remote presentation and Q&amp;A session
          possible from the Intrinsic-id folks sometime in the near
          future. ( Disclaimer: I have no particular interest other than
          knowing more about the feasibility  of application of that
          technology) I was thinking that this ID can be used in any
          mutual authentication protocols ( especially generating the
          private key). Do you have more information on them or think
          otherwise ?</div>
        <div><br>
        </div>
        <div>Regards,</div>
        <div>-Samita</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Nov 6, 2017 at 1:39 AM, Hannes
          Tschofenig <span dir="ltr">&lt;<a
              href="mailto:Hannes.Tschofenig@arm.com" target="_blank"
              moz-do-not-send="true">Hannes.Tschofenig@arm.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Samita,<br>
            <br>
            Do you think PUFs are useful authentication technologies for
            IoT devices?<br>
            <br>
            Ciao<br>
            Hannes<br>
            <div>
              <div class="h5"><br>
                -----Original Message-----<br>
                From: IoT-DIR [mailto:<a
                  href="mailto:iot-dir-bounces@ietf.org"
                  moz-do-not-send="true">iot-dir-bounces@ietf.<wbr>org</a>]
                On Behalf Of Samita Chakrabarti<br>
                Sent: 06 November 2017 10:37<br>
                To: <a href="mailto:Iot-dir@ietf.org"
                  moz-do-not-send="true">Iot-dir@ietf.org</a><br>
                Cc: <a href="mailto:lwip@ietf.org"
                  moz-do-not-send="true">lwip@ietf.org</a>; <a
                  href="mailto:ietf@ietf.org" moz-do-not-send="true">ietf@ietf.org</a>;
                <a
                  href="mailto:draft-ietf-lwig-crypto-sensors.all@ietf.org"
                  moz-do-not-send="true">draft-ietf-lwig-crypto-<wbr>sensors.all@ietf.org</a><br>
                Subject: [IoT-DIR] Iotdir early review of
                draft-ietf-lwig-crypto-<wbr>sensors-04<br>
                <br>
                Reviewer: Samita Chakrabarti<br>
                Review result: Ready with Nits<br>
                <br>
                I have reviewed draft-ietf-lwig-crypto-<wbr>sensors-04
                document for  IOT-Directorate review. The following are
                my comments:<br>
                <br>
                General : The document is easy reading and informative
                about current and previous work. It is ready to publish
                with minor changes based on review comments.<br>
                <br>
                Other comments:<br>
                Introduction:<br>
                 It might be useful to discuss/clarify that multi-level
                security may be  important for IOT devices  all the way
                from 'bootstrapping and management' to  application
                security. That perhaps can include obtaining
                IP-addresses  securely, mutual authentication between
                server and devices , etc. ( see<br>
                 <a
                  href="https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-03"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://tools.ietf.org/html/<wbr>draft-ietf-6lo-ap-nd-03</a>)
                in those cases where each  device has an IP address.<br>
                <br>
                Section 2:<br>
                Regarding problems of provisioning and management of
                networks for the IOT devices there may be additional
                issues – 1) different types of IOT devices and the lack
                of standards way to provision them as they might be
                talking different RF technologies and running L2
                protocols only. 2) The iot nodes may be moving
                individually or collectively and change networks;
                identifying the movement of the iot nodes or identifying
                a particular node at any point of time uniquely requires
                an intrinsic identification which might be useful to set
                during bootstrapping of the node<br>
                <br>
                Regarding related work – does it consider IETF IOT
                security work only? There have been some work and
                thought process going on regarding blockchain IOT
                security in the industry. Perhaps that is out-of-scope
                of this document, but I wanted to mention for authors’
                considerations.<br>
                <br>
                Section 5:<br>
                Authors of the document may also want to browse a SRAM
                PUF based technology which provides unique ID based
                authentication mechanism.<br>
                <a
                  href="https://www.intrinsic-id.com/intrinsic-id-joins-wi-sun-alliance/"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://www.intrinsic-id.com/<wbr>intrinsic-id-joins-wi-sun-<wbr>alliance/</a><br>
                <br>
                Section 9:<br>
                Does the example simulate any particular deployment
                model or research experiments ? It might be good to
                clarify that. Section 10 and 11: Looks like section 11
                is closely related to section 10. Should they be
                combined together ?<br>
                Else some more text is needed in section 10 on design
                trade-offs.<br>
                <br>
                Section 13:<br>
                Does this document recommend one layer of security to
                IOT devices ? There are different types of IOT devices –
                some of them are very tiny and some are more capable.
                Some definitely benefit for multi-level security  than
                single layer of security.  L2 security is generally
                recommended for for all IOT networks. Does data object
                protection only protect the  application data (payload) 
                or more ?<br>
                <br>
                Thanks for the initiative in documenting the valuable
                work in IOT security implementation and crypto
                comparison. -Samita<br>
                <br>
                <br>
                ______________________________<wbr>_________________<br>
                IoT-DIR mailing list<br>
                <a href="mailto:IoT-DIR@ietf.org" moz-do-not-send="true">IoT-DIR@ietf.org</a><br>
                <a href="https://www.ietf.org/mailman/listinfo/iot-dir"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://www.ietf.org/mailman/<wbr>listinfo/iot-dir</a><br>
              </div>
            </div>
            IMPORTANT NOTICE: The contents of this email and any
            attachments are confidential and may also be privileged. If
            you are not the intended recipient, please notify the sender
            immediately and do not disclose the contents to any other
            person, use it for any purpose, or store or copy the
            information in any medium. Thank you.<br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Lwip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lwip@ietf.org">Lwip@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/lwip">https://www.ietf.org/mailman/listinfo/lwip</a>
</pre>
    </blockquote>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
email: <a class="moz-txt-link-abbreviated" href="mailto:rstruik.ext@gmail.com">rstruik.ext@gmail.com</a> | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363</pre>
  </body>
</html>

--------------0071639AD541C804D543813E--


From nobody Tue Nov  7 08:10:09 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 13A3D133437 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 08:10:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 XvYASixs-GWm for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 08:10:06 -0800 (PST)
Received: from atl4mhob04.registeredsite.com (atl4mhob04.registeredsite.com [209.17.115.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED87E1334E6 for <ietf@ietf.org>; Tue,  7 Nov 2017 08:00:05 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob04.registeredsite.com (8.14.4/8.14.4) with ESMTP id vA7G02Y1022163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 7 Nov 2017 11:00:02 -0500
Received: (qmail 17905 invoked by uid 0); 7 Nov 2017 16:00:02 -0000
X-TCPREMOTEIP: 174.204.13.217
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?172.20.10.2?) (lee@asgard.org@174.204.13.217) by 0 with ESMTPA; 7 Nov 2017 16:00:01 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Tue, 07 Nov 2017 10:59:57 -0400
Subject: Re: Proposal to revise ISOC's mission statement
From: Lee Howard <lee@asgard.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Keith Moore <moore@network-heretics.com>
CC: <ietf@ietf.org>
Message-ID: <D6274256.8B776%lee@asgard.org>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
In-Reply-To: <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DiOsNoSouqftQVNr5B5_9M0kVWw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 16:10:08 -0000

On 11/7/17, 4:59 AM, "ietf on behalf of Stephen Farrell"
<ietf-bounces@ietf.org on behalf of stephen.farrell@cs.tcd.ie> wrote:

>
>Hiya,
>
>On 07/11/17 07:49, Gonzalo Camarillo wrote:
>> Hi Keith,
>>=20
>> ah, now I see where you are coming from. Yes, we are also discussing
>> whether ISOC should be closer to a neutral "convener" or, instead,
>> "advocate" more strongly in certain areas... and the ideal role may
>> depend on the particular area, actually.
>>=20
>> In summary, yes, we are thinking about it... and, FWIW, based on my
>> discussions many IETFers share your view.
>
>As an input there, (not that you'll be short of them:-),,, I
>hope that ISOC don't differentiate too much between government
>surveillance and corporate surveillance. While the latter
>may have some fig-leaf of so-called "consent" or clicked-EULA,
>it's the same information being gathered/centralised etc. (And
>of course the latter form of surveillance can nicely feed the
>former when companies are compelled.)

Another form of corporate surveillance is monitoring your employees=E2=80=99 use
of your corporate resources. I hope we don=E2=80=99t collectively object to that.
Similarly, parents may surveill their childrens=E2=80=99 use of family resources.

Lee



From nobody Tue Nov  7 08:19:16 2017
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCED1333F7 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 08:19:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTf8Lf-RZyxy for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 08:19:09 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A99A1335CD for <ietf@ietf.org>; Tue,  7 Nov 2017 08:11:03 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 7944520AAF; Tue,  7 Nov 2017 11:11:02 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 07 Nov 2017 11:11:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=LcXFc7 HIxtSELn3RG9NkRDr7+Hip6skTYtyIMmXpc0g=; b=G/mrqNYvY8LOiUXw6o4kh9 CuEP9QTi2wsZ3NdxzPO007FJXlf5baCDubKNvfpZThj2D/9g/U/snnWwAeRFOQCm AA4kWA8tFO4VttabClYCLmaNwMGvECtKbxEEo6+CzMcvql4iAfNhZQp9Gqd4gEf0 ofhR8XIys2i5iC1QMwRHdfENQeAyOWq2PyJnRmYAJW26eCyl1Uqoub4RIsBZ3coh W9x4t5et9LwCcKzF0oD1tWuwtgo6kxnKQxbW5YUOV5YS4r8WmOC5A+e8l6OTM8KQ V+s8dBy16gmn0P3w3FPSIARJy+7fzoKKbqWjPHzVPWFs3QdpOGWi+YyikTz2yaDA ==
X-ME-Sender: <xms:FtsBWtKI7Qf2eskUoQPWtIP5UNi8ex2Zpxtgq887yb7rfipPZgoqiw>
Received: from [21.25.221.60] (99-203-15-209.pools.spcsdns.net [99.203.15.209]) by mail.messagingengine.com (Postfix) with ESMTPA id 189C024A8B; Tue,  7 Nov 2017 11:11:02 -0500 (EST)
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org>
In-Reply-To: <D6274256.8B776%lee@asgard.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-Mailer: iPhone Mail (12F70)
From: Keith Moore <moore@network-heretics.com>
Subject: Re: Proposal to revise ISOC's mission statement
Date: Tue, 7 Nov 2017 11:10:58 -0500
To: Lee Howard <lee@asgard.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bqRva08x0wN8nb6Vzl0zUti-ywo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 16:19:15 -0000

Sent from my iPhone

> On Nov 7, 2017, at 9:59 AM, Lee Howard <lee@asgard.org> wrote:
>=20
> Another form of corporate surveillance is monitoring your employees=E2=80=99=
 use
> of your corporate resources. I hope we don=E2=80=99t collectively object t=
o that.

That's also a heinous practice, along with drug testing, demanding employees=
' social media credentials, etc.  =20=


From nobody Tue Nov  7 09:04:28 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 E49BE133038 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 09:04:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level: 
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-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 EbxJAkUK5Mur for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 09:04:24 -0800 (PST)
Received: from atl4mhob16.registeredsite.com (atl4mhob16.registeredsite.com [209.17.115.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F2EA132025 for <ietf@ietf.org>; Tue,  7 Nov 2017 09:04:24 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob16.registeredsite.com (8.14.4/8.14.4) with ESMTP id vA7H4MTi008820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 7 Nov 2017 12:04:22 -0500
Received: (qmail 30090 invoked by uid 0); 7 Nov 2017 17:04:22 -0000
X-TCPREMOTEIP: 174.204.13.217
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?172.20.10.2?) (lee@asgard.org@174.204.13.217) by 0 with ESMTPA; 7 Nov 2017 17:04:21 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Tue, 07 Nov 2017 12:04:15 -0400
Subject: Re: Proposal to revise ISOC's mission statement
From: Lee Howard <lee@asgard.org>
To: Keith Moore <moore@network-heretics.com>
CC: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "<ietf@ietf.org>" <ietf@ietf.org>
Message-ID: <D62750A2.8B7AE%lee@asgard.org>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com>
In-Reply-To: <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DoEbdgx_JCQnHBypqQVkU-2m7Zs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 17:04:27 -0000

On 11/7/17, 12:10 PM, "Keith Moore" <moore@network-heretics.com> wrote:

>
>
>Sent from my iPhone
>
>> On Nov 7, 2017, at 9:59 AM, Lee Howard <lee@asgard.org> wrote:
>>=20
>> Another form of corporate surveillance is monitoring your employees=E2=80=99 u=
se
>> of your corporate resources. I hope we don=E2=80=99t collectively object to
>>that.
>
>That's also a heinous practice, along with drug testing, demanding
>employees' social media credentials, etc.

I disagree. If I=E2=80=99m paying someone to use my computer to communicate my
data on my network, it=E2=80=99s mine. You don=E2=80=99t get a say in it.

More to the point: I don=E2=80=99t recall an ISOC opinion on this topic, or the
identical situation of parental supervision. Also, I=E2=80=99d appreciate a
pointer to the IETF consensus statement on the topic, if there is one.

Even more to the point: nuanced position statements don=E2=80=99t belong in the
mission statement.=20

Lee



From nobody Tue Nov  7 09:08:27 2017
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3385913295C for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 09:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 497YoZyN23dB for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 09:08:24 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3658C133228 for <ietf@ietf.org>; Tue,  7 Nov 2017 09:08:23 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A583320DB3; Tue,  7 Nov 2017 12:08:21 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 07 Nov 2017 12:08:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=ZjDbHB t6Sr0MJNzxeaXEs8As/a/Yz34g2gQ/vrMXhWQ=; b=kzUQ1BTSlQUweg4SnXeQoD KbwyrAuN0foQFFQ66xpxRDg+RH2d8Y2i4zRMr+6bSxa2sYk25FwGcSBPzcM28Lx9 SJtJuTs8j49Kq2VPEN/QsTzfF0J9Jseuo3MNwtHXbaVnVQKlV7MRQzJmyYQYBCx6 w6W4SYzfecymEbY094tSEdIN9hMip1U5TLKSTUpuydeeHqlXfZgrmbgvFZZc/02J BB6wdRzuyi/hkXAmvewJbf+MG4fHiDVbqc7JzfCLuoC2t9FtssW4VUVZs5JkcM5s chjtkiI938I90WhkaOeXLi640tMPLeYHxW46y3Df8JdZQkbiZwcVY2mzW4fEi9GQ ==
X-ME-Sender: <xms:hegBWs_MhfGHynaKF2aoB-Vjc2fulIAQ-9cGqwWcw64TYEpyidkb2A>
Received: from [21.25.221.60] (99-203-15-209.pools.spcsdns.net [99.203.15.209]) by mail.messagingengine.com (Postfix) with ESMTPA id 4F8E1241BE; Tue,  7 Nov 2017 12:08:21 -0500 (EST)
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com> <D62750A2.8B7AE%lee@asgard.org>
In-Reply-To: <D62750A2.8B7AE%lee@asgard.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <5078B368-DE8A-4E2B-AD6F-28C7522D60D7@network-heretics.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-Mailer: iPhone Mail (12F70)
From: Keith Moore <moore@network-heretics.com>
Subject: Re: Proposal to revise ISOC's mission statement
Date: Tue, 7 Nov 2017 12:08:17 -0500
To: Lee Howard <lee@asgard.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kMezXJrGJI0MPcQ1Lofw0feBIK4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 17:08:25 -0000

Sent from my iPhone

> On Nov 7, 2017, at 11:04 AM, Lee Howard <lee@asgard.org> wrote:
>=20
>=20
>=20
>> On 11/7/17, 12:10 PM, "Keith Moore" <moore@network-heretics.com> wrote:
>>=20
>>=20
>>=20
>> Sent from my iPhone
>>=20
>>> On Nov 7, 2017, at 9:59 AM, Lee Howard <lee@asgard.org> wrote:
>>>=20
>>> Another form of corporate surveillance is monitoring your employees=E2=80=
=99 use
>>> of your corporate resources. I hope we don=E2=80=99t collectively object=
 to
>>> that.
>>=20
>> That's also a heinous practice, along with drug testing, demanding
>> employees' social media credentials, etc.
>=20
> I disagree. If I=E2=80=99m paying someone to use my computer to communicat=
e my
> data on my network, it=E2=80=99s mine. You don=E2=80=99t get a say in it.

I suppose you have their houses searched too?

Keith


From nobody Tue Nov  7 09:41:36 2017
Return-Path: <henry@callistohouse.club>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 484B2132193 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 09:41:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 tS4NXeCGLkBC for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 09:41:33 -0800 (PST)
Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (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 C9CE5124B18 for <ietf@ietf.org>; Tue,  7 Nov 2017 09:41:32 -0800 (PST)
Date: Tue, 07 Nov 2017 12:41:22 -0500
Authentication-Results: mail2.protonmail.ch; dkim=none
To: Lee Howard <lee@asgard.org>, Keith Moore <moore@network-heretics.com>
From: henry <henry@callistohouse.club>
Cc: ietf@ietf.org, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Reply-To: henry <henry@callistohouse.club>
Subject: Re: Proposal to revise ISOC's mission statement
Message-ID: <rRe5eYT5W8EWHm1Q1XBsjy6IA5fElDTHq5yVxKvaKTZpI8RD2zi9dhrkT-K986dDQTFmKGW39nG7oCEZVbAb9wskKvuPytdsVBnyxcXtViA=@callistohouse.club>
In-Reply-To: <D62750A2.8B7AE%lee@asgard.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com> <D62750A2.8B7AE%lee@asgard.org>
Feedback-ID: vEY7k4yIhKH60ezyh_ewYb5cBh9lM6d5hXuAKmMcj-2yeFvumZUf2Q6AIaPs9viRuOL95Jg0-5_mTgpMVWHl3Q==:Ext:ProtonMail
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="b1_8b4cb79a6475b08ac683ae227c8e9c5c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OGNrDMg4KRLKfmVeEnfo4QH_KzE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 17:41:35 -0000

This is a multi-part message in MIME format.

--b1_8b4cb79a6475b08ac683ae227c8e9c5c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

WW91ciBlbXBsb3llZSBpcyBiZXN0IHZpZXdlZCBhcyBhIGNvbnRyYWN0ZWQgc292ZXJlaWduIGxh
Ym9yLCB3aXRoIHJpZ2h0IHRvIGxpYmVydHkgdG8gZW5nYWdlIGluIHByaXZhdGUgYW5kIHByb3Rl
Y3RlZCBjb21tdW5pY2F0aW9ucyBvdmVyIHRoZSBjb250cmFjdHVhbCBlcXVpcG1lbnQgYW5kIHNl
cnZpY2UgYWxsb2NhdGlvbiB0byBzdXBwb3J0IHlvdXIgbGFib3IuIEp1c3QgYXMgaWYgaXQgd2Vy
ZSBhbiBhdXRvbW9iaWxlLCBzaGUgd2lsbCBzdG9wIHRvIGdldCBncm9jZXJpZXMgYW5kIGRyaXZl
IGhlciBraWRzIHRvIHNvY2NlciwgaW4gdGhlIGNvbXBhbnkgY2FyLgoKU2FtZSBkaWZmZXJlbmNl
IHdpdGhvdXQgbnVhbmNlLiBZZXMsIGFsbGVnb3JpY2FsIGNhdGVnb3J5Li4uCgpTZW50IGZyb20g
UHJvdG9uTWFpbCBNb2JpbGUKCk9uIFR1ZSwgTm92IDcsIDIwMTcgYXQgMTE6MDQsIExlZSBIb3dh
cmQgPGxlZUBhc2dhcmQub3JnPiB3cm90ZToKCj4gT24gMTEvNy8xNywgMTI6MTAgUE0sICJLZWl0
aCBNb29yZSIgd3JvdGU6ID4gPiA+U2VudCBmcm9tIG15IGlQaG9uZSA+ID4+IE9uIE5vdiA3LCAy
MDE3LCBhdCA5OjU5IEFNLCBMZWUgSG93YXJkIHdyb3RlOiA+PiA+PiBBbm90aGVyIGZvcm0gb2Yg
Y29ycG9yYXRlIHN1cnZlaWxsYW5jZSBpcyBtb25pdG9yaW5nIHlvdXIgZW1wbG95ZWVz4oCZIHVz
ZSA+PiBvZiB5b3VyIGNvcnBvcmF0ZSByZXNvdXJjZXMuIEkgaG9wZSB3ZSBkb27igJl0IGNvbGxl
Y3RpdmVseSBvYmplY3QgdG8gPj50aGF0LiA+ID5UaGF0J3MgYWxzbyBhIGhlaW5vdXMgcHJhY3Rp
Y2UsIGFsb25nIHdpdGggZHJ1ZyB0ZXN0aW5nLCBkZW1hbmRpbmcgPmVtcGxveWVlcycgc29jaWFs
IG1lZGlhIGNyZWRlbnRpYWxzLCBldGMuIEkgZGlzYWdyZWUuIElmIEnigJltIHBheWluZyBzb21l
b25lIHRvIHVzZSBteSBjb21wdXRlciB0byBjb21tdW5pY2F0ZSBteSBkYXRhIG9uIG15IG5ldHdv
cmssIGl04oCZcyBtaW5lLiBZb3UgZG9u4oCZdCBnZXQgYSBzYXkgaW4gaXQuIE1vcmUgdG8gdGhl
IHBvaW50OiBJIGRvbuKAmXQgcmVjYWxsIGFuIElTT0Mgb3BpbmlvbiBvbiB0aGlzIHRvcGljLCBv
ciB0aGUgaWRlbnRpY2FsIHNpdHVhdGlvbiBvZiBwYXJlbnRhbCBzdXBlcnZpc2lvbi4gQWxzbywg
SeKAmWQgYXBwcmVjaWF0ZSBhIHBvaW50ZXIgdG8gdGhlIElFVEYgY29uc2Vuc3VzIHN0YXRlbWVu
dCBvbiB0aGUgdG9waWMsIGlmIHRoZXJlIGlzIG9uZS4gRXZlbiBtb3JlIHRvIHRoZSBwb2ludDog
bnVhbmNlZCBwb3NpdGlvbiBzdGF0ZW1lbnRzIGRvbuKAmXQgYmVsb25nIGluIHRoZSBtaXNzaW9u
IHN0YXRlbWVudC4gTGVlIEBhc2dhcmQub3JnPiBAbmV0d29yay1oZXJldGljcy5jb20+


--b1_8b4cb79a6475b08ac683ae227c8e9c5c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PGRpdj5Zb3VyIGVtcGxveWVlIGlzIGJlc3Qgdmlld2VkIGFzIGEgY29udHJhY3RlZCBzb3ZlcmVp
Z24gbGFib3IsJm5ic3A7d2l0aCByaWdodCB0byBsaWJlcnR5IHRvIGVuZ2FnZSBpbiBwcml2YXRl
IGFuZCBwcm90ZWN0ZWQgY29tbXVuaWNhdGlvbnMgb3ZlciB0aGUgY29udHJhY3R1YWwmbmJzcDtl
cXVpcG1lbnQgYW5kIHNlcnZpY2UgYWxsb2NhdGlvbiB0byBzdXBwb3J0IHlvdXIgbGFib3IuIEp1
c3QgYXMgaWYgaXQgd2VyZSBhbiBhdXRvbW9iaWxlLAogICAgc2hlIHdpbGwgc3RvcCB0byBnZXQg
Z3JvY2VyaWVzIGFuZCBkcml2ZSBoZXIga2lkcyB0byBzb2NjZXIsIGluIHRoZSBjb21wYW55IGNh
ci48L2Rpdj4KPGRpdj4KICAgIDxiciAvPgo8L2Rpdj4KPGRpdj5TYW1lIGRpZmZlcmVuY2Ugd2l0
aG91dCBudWFuY2UuIFllcywgYWxsZWdvcmljYWwgY2F0ZWdvcnkuLi48L2Rpdj4KPGRpdj4KICAg
IDxiciAvPgo8L2Rpdj4KPGRpdiBpZD0icHJvdG9ubWFpbF9tb2JpbGVfc2lnbmF0dXJlX2Jsb2Nr
Ij5TZW50IGZyb20gUHJvdG9uTWFpbCBNb2JpbGU8L2Rpdj4KPGRpdj4KICAgIDxiciAvPgogICAg
PGRpdj4KICAgICAgICA8ZGl2PgogICAgICAgICAgICA8YnIgLz4KICAgICAgICA8L2Rpdj5PbiBU
dWUsIE5vdiA3LCAyMDE3IGF0IDExOjA0LCBMZWUgSG93YXJkICZsdDs8YSBocmVmPSJtYWlsdG86
bGVlQGFzZ2FyZC5vcmciIGNsYXNzPSIiPmxlZUBhc2dhcmQub3JnPC9hPiZndDsgd3JvdGU6PC9k
aXY+CiAgICA8YmxvY2txdW90ZSBjbGFzcz0icHJvdG9ubWFpbF9xdW90ZSIgdHlwZT0iY2l0ZSI+
CgogICAgICAgIE9uIDExLzcvMTcsIDEyOjEwIFBNLCAiS2VpdGggTW9vcmUiCiAgICAgICAgPG1v
b3JlQG5ldHdvcmstaGVyZXRpY3MuY29tPndyb3RlOiAmZ3Q7ICZndDsgJmd0O1NlbnQgZnJvbSBt
eSBpUGhvbmUgJmd0OyAmZ3Q7Jmd0OyBPbiBOb3YgNywgMjAxNywgYXQgOTo1OSBBTSwgTGVlIEhv
d2FyZAogICAgICAgICAgICA8bGVlQGFzZ2FyZC5vcmc+d3JvdGU6ICZndDsmZ3Q7ICZndDsmZ3Q7
IEFub3RoZXIgZm9ybSBvZiBjb3Jwb3JhdGUgc3VydmVpbGxhbmNlIGlzIG1vbml0b3JpbmcgeW91
ciBlbXBsb3llZXPigJkgdXNlICZndDsmZ3Q7IG9mIHlvdXIgY29ycG9yYXRlIHJlc291cmNlcy4g
SSBob3BlIHdlIGRvbuKAmXQgY29sbGVjdGl2ZWx5IG9iamVjdCB0byAmZ3Q7Jmd0O3RoYXQuICZn
dDsgJmd0O1RoYXQncyBhbHNvIGEgaGVpbm91cyBwcmFjdGljZSwgYWxvbmcgd2l0aAogICAgICAg
ICAgICAgICAgZHJ1ZyB0ZXN0aW5nLCBkZW1hbmRpbmcgJmd0O2VtcGxveWVlcycgc29jaWFsIG1l
ZGlhIGNyZWRlbnRpYWxzLCBldGMuIEkgZGlzYWdyZWUuIElmIEnigJltIHBheWluZyBzb21lb25l
IHRvIHVzZSBteSBjb21wdXRlciB0byBjb21tdW5pY2F0ZSBteSBkYXRhIG9uIG15IG5ldHdvcmss
IGl04oCZcyBtaW5lLiBZb3UgZG9u4oCZdCBnZXQgYSBzYXkgaW4gaXQuIE1vcmUgdG8gdGhlIHBv
aW50OiBJIGRvbuKAmXQgcmVjYWxsIGFuCiAgICAgICAgICAgICAgICBJU09DIG9waW5pb24gb24g
dGhpcyB0b3BpYywgb3IgdGhlIGlkZW50aWNhbCBzaXR1YXRpb24gb2YgcGFyZW50YWwgc3VwZXJ2
aXNpb24uIEFsc28sIEnigJlkIGFwcHJlY2lhdGUgYSBwb2ludGVyIHRvIHRoZSBJRVRGIGNvbnNl
bnN1cyBzdGF0ZW1lbnQgb24gdGhlIHRvcGljLCBpZiB0aGVyZSBpcyBvbmUuIEV2ZW4gbW9yZSB0
byB0aGUgcG9pbnQ6IG51YW5jZWQgcG9zaXRpb24gc3RhdGVtZW50cyBkb27igJl0IGJlbG9uZwog
ICAgICAgICAgICAgICAgaW4gdGhlIG1pc3Npb24gc3RhdGVtZW50LiBMZWUKCgogICAgICAgICAg
ICA8L2xlZUBhc2dhcmQub3JnPgogICAgICAgIDwvbW9vcmVAbmV0d29yay1oZXJldGljcy5jb20+
CiAgICA8L2Jsb2NrcXVvdGU+CjwvZGl2Pg==



--b1_8b4cb79a6475b08ac683ae227c8e9c5c--


From nobody Tue Nov  7 10:19:56 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 5549D127522 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 10:19:54 -0800 (PST)
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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uV8bYaeU_FvG for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 10:19:52 -0800 (PST)
Received: from atl4mhob05.registeredsite.com (atl4mhob05.registeredsite.com [209.17.115.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E3211204DA for <ietf@ietf.org>; Tue,  7 Nov 2017 10:19:52 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob05.registeredsite.com (8.14.4/8.14.4) with ESMTP id vA7IJnZ0009515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 7 Nov 2017 13:19:49 -0500
Received: (qmail 28249 invoked by uid 0); 7 Nov 2017 18:19:49 -0000
X-TCPREMOTEIP: 174.204.13.217
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?172.20.10.2?) (lee@asgard.org@174.204.13.217) by 0 with ESMTPA; 7 Nov 2017 18:19:49 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Tue, 07 Nov 2017 13:19:44 -0400
Subject: Re: Proposal to revise ISOC's mission statement
From: Lee Howard <lee@asgard.org>
To: Keith Moore <moore@network-heretics.com>
CC: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "<ietf@ietf.org>" <ietf@ietf.org>
Message-ID: <D6276267.8B8B5%lee@asgard.org>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com> <D62750A2.8B7AE%lee@asgard.org> <5078B368-DE8A-4E2B-AD6F-28C7522D60D7@network-heretics.com>
In-Reply-To: <5078B368-DE8A-4E2B-AD6F-28C7522D60D7@network-heretics.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QZipuuk8AqSpC8Fd1cpZmPEW2t8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 18:19:54 -0000

On 11/7/17, 1:08 PM, "Keith Moore" <moore@network-heretics.com> wrote:

>
>
>Sent from my iPhone
>
>> On Nov 7, 2017, at 11:04 AM, Lee Howard <lee@asgard.org> wrote:
>>=20
>>=20
>>=20
>>> On 11/7/17, 12:10 PM, "Keith Moore" <moore@network-heretics.com> wrote:
>>>=20
>>>=20
>>>=20
>>> Sent from my iPhone
>>>=20
>>>> On Nov 7, 2017, at 9:59 AM, Lee Howard <lee@asgard.org> wrote:
>>>>=20
>>>> Another form of corporate surveillance is monitoring your employees=E2=80=99
>>>>use
>>>> of your corporate resources. I hope we don=E2=80=99t collectively object to
>>>> that.
>>>=20
>>> That's also a heinous practice, along with drug testing, demanding
>>> employees' social media credentials, etc.
>>=20
>> I disagree. If I=E2=80=99m paying someone to use my computer to communicate my
>> data on my network, it=E2=80=99s mine. You don=E2=80=99t get a say in it.
>
>I suppose you have their houses searched too?

Well, in my child=E2=80=99s case, I most certainly do.

In the business case, not unless I paid for the house, the network, the
work they=E2=80=99re doing there, and the devices they=E2=80=99re doing it on.

If you walk out of my office carrying a large box, I certainly have the
right to check what=E2=80=99s inside it. If you send email out of my office
servers with a large attachment, I have the right to check what=E2=80=99s inside.

What=E2=80=99s confusing about this concept? How is this even contentious? And ho=
w
can we bring it back around to the actual topic of conversation?


Lee



From nobody Tue Nov  7 10:51:39 2017
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF26A132031 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 10:51:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zsdn-24IboZX for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 10:51:36 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 767EF132199 for <ietf@ietf.org>; Tue,  7 Nov 2017 10:51:36 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id C528A20D11; Tue,  7 Nov 2017 13:51:35 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute6.internal (MEProxy); Tue, 07 Nov 2017 13:51:35 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=UyOgsc c5cnHwiCskrqGOSc9rZX39xslt5o2NYGC7iac=; b=Nn2bQAgYUl9g0pSWK/KzqY junQgOAEyDLKrtIf9XRB08Vbp18T7IMPlDhjiUg1xKu5SzHYbaOYM/Wk3O+akUkU 0Nov1enidGxt7z+Kt5WDgWfW9urPEICf+PzfWCHo2+QhkrdyR5ygbm+A/0M47Mhh A7dL2tkbrIKJTNWE5cXSX7Vk5uQxB+nkwps2t5s3tErUGsOHEJI3eGVioIAwBeq4 VkbQgdkIanZGiA6a8jgyqLjN8J0v2DtVs4pYoaQw0RR5X5r9TsfNBz9wMkhM6UWY 0cg7OrknbcBFazFs3/gCtbobnU8Eq6vBGCkAlyhuiBsUi0HbDag6knpa8EWYH2RQ ==
X-ME-Sender: <xms:twACWgNqIs2qx454P36BriuaS2jPDFUXIqJo4S_XrP3GumZ-2R2VWA>
Received: from [21.25.221.60] (99-203-15-209.pools.spcsdns.net [99.203.15.209]) by mail.messagingengine.com (Postfix) with ESMTPA id B55BA24A8B; Tue,  7 Nov 2017 13:51:34 -0500 (EST)
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com> <D62750A2.8B7AE%lee@asgard.org> <5078B368-DE8A-4E2B-AD6F-28C7522D60D7@network-heretics.com> <D6276267.8B8B5%lee@asgard.org>
In-Reply-To: <D6276267.8B8B5%lee@asgard.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <3A67265C-8E1A-4982-9B09-AF2AC7377326@network-heretics.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-Mailer: iPhone Mail (12F70)
From: Keith Moore <moore@network-heretics.com>
Subject: Re: Proposal to revise ISOC's mission statement
Date: Tue, 7 Nov 2017 13:51:31 -0500
To: Lee Howard <lee@asgard.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5vFtb6ADNndyfZLgXKzWrqoHwGg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 18:51:38 -0000

You're the one arguing for spying on your employees.

Sent from my iPhone

> On Nov 7, 2017, at 12:19 PM, Lee Howard <lee@asgard.org> wrote:
>=20
>=20
>=20
>> On 11/7/17, 1:08 PM, "Keith Moore" <moore@network-heretics.com> wrote:
>>=20
>>=20
>>=20
>> Sent from my iPhone
>>=20
>>> On Nov 7, 2017, at 11:04 AM, Lee Howard <lee@asgard.org> wrote:
>>>=20
>>>=20
>>>=20
>>>> On 11/7/17, 12:10 PM, "Keith Moore" <moore@network-heretics.com> wrote:=

>>>>=20
>>>>=20
>>>>=20
>>>> Sent from my iPhone
>>>>=20
>>>>> On Nov 7, 2017, at 9:59 AM, Lee Howard <lee@asgard.org> wrote:
>>>>>=20
>>>>> Another form of corporate surveillance is monitoring your employees=E2=
=80=99
>>>>> use
>>>>> of your corporate resources. I hope we don=E2=80=99t collectively obje=
ct to
>>>>> that.
>>>>=20
>>>> That's also a heinous practice, along with drug testing, demanding
>>>> employees' social media credentials, etc.
>>>=20
>>> I disagree. If I=E2=80=99m paying someone to use my computer to communic=
ate my
>>> data on my network, it=E2=80=99s mine. You don=E2=80=99t get a say in it=
.
>>=20
>> I suppose you have their houses searched too?
>=20
> Well, in my child=E2=80=99s case, I most certainly do.
>=20
> In the business case, not unless I paid for the house, the network, the
> work they=E2=80=99re doing there, and the devices they=E2=80=99re doing it=
 on.
>=20
> If you walk out of my office carrying a large box, I certainly have the
> right to check what=E2=80=99s inside it. If you send email out of my offic=
e
> servers with a large attachment, I have the right to check what=E2=80=99s i=
nside.
>=20
> What=E2=80=99s confusing about this concept? How is this even contentious?=
 And how
> can we bring it back around to the actual topic of conversation?
>=20
>=20
> Lee
>=20
>=20


From nobody Tue Nov  7 10:56:41 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 E8ED5132C3F for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 10:56:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (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 G7d-zzsCZ9rR for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 10:56:37 -0800 (PST)
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 06C451326DF for <ietf@ietf.org>; Tue,  7 Nov 2017 10:56:37 -0800 (PST)
Received: by mail-pf0-x22f.google.com with SMTP id b6so154585pfh.7 for <ietf@ietf.org>; Tue, 07 Nov 2017 10:56:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NtjvvBG3gWLESAXlxUBYvV1hdDcChovT/4r2CyQpHQQ=; b=gOxEBjC3tSZcnTV4RB6tChI1FLlIOGk6mPiNCjnZQRteWWXtVkoVHgSInRDd4UTQQi dpkpArPI0YaTzPw+dee4hAzCBhlq3uSHrUfhJZXvXTelckDTm/i5FBXnCck6Np7Yc7+f kGFvDtM6TVon1hdIQcR73QitiZqO80HIixnPb8vqUpN2p1XgQoq7BFdyQuI+k7gEzZ2o LUgnKqTnNsTm62EjFMqHEr+gdIzQaFe1YVJXuKfbjEaiwvK4u0g1sWFfSZjd70Q7X2FX 37qa0ZOY6VEhbef3xPpukQh91ypN33wFKGM+xhkZ73s/xqtIvtb4T74TLuvFYCyPnrWn VooQ==
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=NtjvvBG3gWLESAXlxUBYvV1hdDcChovT/4r2CyQpHQQ=; b=KwlpZX7Z1XYIJYR6kvvFc5oV2VYVr6oH2mI0I7mVWGwfW8HE9HzU9NDttX3fEA3HZV UB5MZFAzl1w9QTeodwVsLXzryXntv5Is35EF5T3Yukp3LhiVAQwbe6RFsiwL1cZ06G8P NvnZ9ApPKu1ETJFRQYy+nOLQUESjJHJv9Qf9nNUr8vHkWx+43AVjwkINH+4DlglrHuCt T/XDhDRgkh1b6eKTdKyr14PzJB7UlFI//vp/mtZaMGSn1VtXARPK08+BU1YnZfDg0een ADzlp/5NidXPKSovZjUy+2lnLIJOn4WG5+9i3chR0ke8hfGcVyTECDajqo4X4C9xmiH5 tRGw==
X-Gm-Message-State: AJaThX5pIp7a705BH+F5JVROaIzTKGRmYfJwZMc1hEKzmK7mMeEuVsyD hFwdPsyqeioz0rL9ANaHwS2c8Q==
X-Google-Smtp-Source: ABhQp+QIbJB0xfmSy7YrM302MJPuaz68PqdS63fhHA8eRR1Xdk8RQACC+TSnNW3T052Avvim+i6TvA==
X-Received: by 10.84.213.136 with SMTP id g8mr287748pli.339.1510080996423; Tue, 07 Nov 2017 10:56:36 -0800 (PST)
Received: from ?IPv6:2620::10e7:10:12b:e10e:fc9e:4f69? ([2620:0:10e7:10:12b:e10e:fc9e:4f69]) by smtp.gmail.com with ESMTPSA id 125sm4182489pff.14.2017.11.07.10.56.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 10:56:35 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A4EF439-90B9-47F2-8F0D-A08F0076A921"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Proposal to revise ISOC's mission statement
Date: Tue, 7 Nov 2017 10:56:34 -0800
In-Reply-To: <D6274256.8B776%lee@asgard.org>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
To: Lee Howard <Lee@asgard.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oYmCiqLN0pw41zwAE-JBi80GhxU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 18:56:39 -0000

--Apple-Mail=_5A4EF439-90B9-47F2-8F0D-A08F0076A921
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Nov 7, 2017, at 06:59, Lee Howard <Lee@asgard.org> wrote:
> On 11/7/17, 4:59 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie =
<mailto:stephen.farrell@cs.tcd.ie>> wrote:
>> [=E2=80=A6] While the latter may have some fig-leaf of so-called =
"consent" or clicked-EULA, it's the same information being =
gathered/centralised etc. (And of course the latter form of surveillance =
can nicely feed the former when companies are compelled.)
>=20
>=20
> Another form of corporate surveillance is monitoring your employees=E2=80=
=99 use of your corporate resources. I hope we don=E2=80=99t =
collectively object to that. Similarly, parents may surveill their =
childrens=E2=80=99 use of family resources.


Those are dissimilar with respect to the issue of consent. It=E2=80=99s =
one thing to use surveillance technologies in the role of legal guardian =
for dependents without capacity for consent, and it=E2=80=99s an =
entirely different thing to use a contract of adhesion to coerce =
subordinates into =E2=80=9Cconsenting=E2=80=9D to give up their rights =
to intimate privacy.

And there=E2=80=99s a lot of dirty business hiding under that phrase =
=E2=80=9Cmonitoring your employees=E2=80=99 use of your corporate =
resources=E2=80=9D when you consider that your employees have personal =
identities in social media that can, at any moment, become involved in a =
viral public relations disaster. When corporations regard the personal =
online activity of their employees, using personal resources at home on =
their own time, as bearing on the public brand identity, using that to =
justify surveilling their employees private social activity, and further =
insist on employees =E2=80=9Cconsenting=E2=80=9D to this surveillance as =
terms of their employment, that=E2=80=99s hardly similar to a parent =
monitoring their kids=E2=80=99 porn habits.


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




--Apple-Mail=_5A4EF439-90B9-47F2-8F0D-A08F0076A921
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 Nov 7, 2017, at 06:59, Lee Howard &lt;<a =
href=3D"mailto:Lee@asgard.org" class=3D"">Lee@asgard.org</a>&gt; =
wrote:<br class=3D""><div><blockquote type=3D"cite" =
class=3D"">On&nbsp;<span style=3D"font-family: Menlo-Regular; font-size: =
11px;" class=3D"">11/7/17, 4:59 AM</span>, Stephen Farrell &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; =
wrote:</blockquote><blockquote type=3D"cite" class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D"" style=3D"font-family: =
Menlo-Regular; font-size: 11px;">[=E2=80=A6]&nbsp;While the =
latter&nbsp;may have some fig-leaf of so-called "consent" or =
clicked-EULA,&nbsp;it's the same information being gathered/centralised =
etc. (And&nbsp;of course the latter form of surveillance can nicely feed =
the&nbsp;former when companies are compelled.)</blockquote></div><div =
class=3D""><br class=3D""></div></blockquote><blockquote type=3D"cite" =
class=3D""><div class=3D""><span style=3D"font-family: Menlo-Regular; =
font-size: 11px; 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"">Another form of corporate surveillance is =
monitoring your employees=E2=80=99 use&nbsp;</span><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; 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"">of your corporate =
resources. I hope we don=E2=80=99t collectively object to =
that.&nbsp;</span><span style=3D"font-family: Menlo-Regular; font-size: =
11px; 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"">Similarly, parents may surveill their =
childrens=E2=80=99 use of family =
resources.</span></div></blockquote></div><div class=3D""><br =
class=3D""></div><div class=3D"">Those are dissimilar with respect to =
the issue of consent. It=E2=80=99s one thing to use surveillance =
technologies in the role of legal guardian for dependents without =
capacity for consent, and it=E2=80=99s an entirely different thing to =
use a contract of adhesion to coerce subordinates into =E2=80=9Cconsenting=
=E2=80=9D to give up their rights to intimate privacy.</div><div =
class=3D""><br class=3D""></div><div class=3D"">And there=E2=80=99s a =
lot of dirty business hiding under that phrase =E2=80=9Cmonitoring your =
employees=E2=80=99 use of your corporate resources=E2=80=9D when you =
consider that your employees have personal identities in social media =
that can, at any moment, become involved in a viral public relations =
disaster. When corporations regard the personal online activity of their =
employees, using personal resources at home on their own time, as =
bearing on the public brand identity, using that to justify surveilling =
their employees private social activity, and further insist on employees =
=E2=80=9Cconsenting=E2=80=9D to this surveillance as terms of their =
employment, that=E2=80=99s hardly similar to a parent monitoring their =
kids=E2=80=99 porn habits.</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=_5A4EF439-90B9-47F2-8F0D-A08F0076A921--


From nobody Tue Nov  7 11:57:35 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37FC613235C for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 11:57:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=OqqmGfSe; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=FJpRs4vY
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SPtinLdA6f3Q for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 11:57:32 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7118F1201F8 for <ietf@ietf.org>; Tue,  7 Nov 2017 11:57:32 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.225.245.43]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA7JvCRP015836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Nov 2017 11:57:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510084646; x=1510171046; bh=gtUnYfuu+zFzQBB2L+HjqYagxFJB5+7MbyQ2XYfMnl4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OqqmGfSe50sbHUaVPGpLsD4i+maRR4yLZieyRV0Ohk88G2iQ6DZ4apbvbrIlZGjwG DktP1OlrzAa5cs4m3flBaqJXrGeldxR1IaHMoCncCUJmbRvWQst8r9NX3E5pb26bom EPxGyoW0n7b5Ryctlmr7tQ1ApNV9deKML26w+nK0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510084646; x=1510171046; i=@elandsys.com; bh=gtUnYfuu+zFzQBB2L+HjqYagxFJB5+7MbyQ2XYfMnl4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FJpRs4vYzaFXhwyHb0mBTpg6t/Zxx/xYv3yfB3LJ0ByB1SO0AUphSAKxCaEvsfJcG BEakeGhcoHRBoGoiftc37tk51HdCKnJqI03Nhv9own5NgSvZXfER5vn/PgkdRJYUWf n7W1bosNP8Nx4m/s0pXLYAbDhfylOXUnc0X0JyfQ=
Message-Id: <6.2.5.6.2.20171107114103.100cb140@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 07 Nov 2017 11:56:22 -0800
To: Lee Howard <lee@asgard.org>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Proposal to revise ISOC's mission statement
Cc: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, Keith Moore <moore@network-heretics.com>
In-Reply-To: <D62750A2.8B7AE%lee@asgard.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <B8CA3BED-63CC-4070-AE7E-B5ADFCB10FFD@network-heretics.com> <D62750A2.8B7AE%lee@asgard.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DBz1nKdkKiD8HN4u7O6CTH7lmRQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 19:57:33 -0000

Hi Lee,
At 08:04 AM 07-11-2017, Lee Howard wrote:
>More to the point: I don't recall an ISOC opinion on this topic, or the
>identical situation of parental supervision. Also, I'd appreciate a
>pointer to the IETF consensus statement on the topic, if there is one.

I don't recall seeing an IETF consensus statement about an ISOC 
opinion.  The topic of child protection has been discussed in 
internet governance forums.

Regards,
S. Moonesamy 


From nobody Tue Nov  7 12:06:45 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 2C7AB133075 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 12:06:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.897
X-Spam-Level: 
X-Spam-Status: No, score=-4.897 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, 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 1mrCZTAq6dHJ for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 12:06:41 -0800 (PST)
Received: from atl4mhob11.registeredsite.com (atl4mhob11.registeredsite.com [209.17.115.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14F721330B3 for <ietf@ietf.org>; Tue,  7 Nov 2017 12:06:41 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob11.registeredsite.com (8.14.4/8.14.4) with ESMTP id vA7K6aAU001275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 7 Nov 2017 15:06:36 -0500
Received: (qmail 8166 invoked by uid 0); 7 Nov 2017 20:06:36 -0000
X-TCPREMOTEIP: 184.185.35.18
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.2.160?) (lee@asgard.org@184.185.35.18) by 0 with ESMTPA; 7 Nov 2017 20:06:36 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Tue, 07 Nov 2017 15:06:32 -0400
Subject: Re: Proposal to revise ISOC's mission statement
From: Lee Howard <lee@asgard.org>
To: james woodyatt <jhw@google.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <D6277B2F.8B95A%lee@asgard.org>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com>
In-Reply-To: <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3592911996_10602376"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xbdyx6yEehJkmsdSFBLM2gVGKqM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 20:06:43 -0000

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

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



From:  james woodyatt <jhw@google.com>
Date:  Tuesday, November 7, 2017 at 2:56 PM
To:  Lee Howard <lee@asgard.org>
Cc:  IETF Discussion Mailing List <ietf@ietf.org>
Subject:  Re: Proposal to revise ISOC's mission statement

> On Nov 7, 2017, at 06:59, Lee Howard <Lee@asgard.org> wrote:
>> On 11/7/17, 4:59 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>>> [=E2=80=A6] While the latter may have some fig-leaf of so-called "consent" or
>>> clicked-EULA, it's the same information being gathered/centralised etc.=
 (And
>>> of course the latter form of surveillance can nicely feed the former wh=
en
>>> companies are compelled.)
>>=20
>> Another form of corporate surveillance is monitoring your employees=E2=80=99 u=
se of
>> your corporate resources. I hope we don=E2=80=99t collectively object to that.
>> Similarly, parents may surveill their childrens=E2=80=99 use of family resourc=
es.
>=20
> Those are dissimilar with respect to the issue of consent. It=E2=80=99s one thi=
ng to
> use surveillance technologies in the role of legal guardian for dependent=
s
> without capacity for consent, and it=E2=80=99s an entirely different thing to u=
se a
> contract of adhesion to coerce subordinates into =E2=80=9Cconsenting=E2=80=9D to give=
 up their
> rights to intimate privacy.

You have no right to =E2=80=9Cintimate privacy=E2=80=9D at work on your company-owned
computer on the company network on company time.

>=20
> And there=E2=80=99s a lot of dirty business hiding under that phrase =E2=80=9Cmonitor=
ing your
> employees=E2=80=99 use of your corporate resources=E2=80=9D when you consider that yo=
ur
> employees have personal identities in social media that can, at any momen=
t,
> become involved in a viral public relations disaster. When corporations r=
egard
> the personal online activity of their employees, using personal resources=
 at
> home on their own time, as bearing on the public brand identity, using th=
at to
> justify surveilling their employees private social activity, and further
> insist on employees =E2=80=9Cconsenting=E2=80=9D to this surveillance as terms of the=
ir
> employment, that=E2=80=99s hardly similar to a parent monitoring their kids=E2=80=99 =
porn
> habits.

Who said anything about =E2=80=9Cpersonal resources at home on their own time=E2=80=9D?
Trying to expand my statement to include that is more than simply
disingenuously building a straw man to throw down a slippery slope, it=E2=80=99s
dishonest.

Lee




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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif;"><div><br></div><div><br></div><spa=
n id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-family:Calibri; font-size:11pt;=
 text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medi=
um none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-=
TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span s=
tyle=3D"font-weight:bold">From: </span> james woodyatt &lt;<a href=3D"mailto:jhw=
@google.com">jhw@google.com</a>&gt;<br><span style=3D"font-weight:bold">Date: =
</span> Tuesday, November 7, 2017 at 2:56 PM<br><span style=3D"font-weight:bol=
d">To: </span> Lee Howard &lt;<a href=3D"mailto:lee@asgard.org">lee@asgard.org=
</a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> IETF Discussion Maili=
ng List &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br><span st=
yle=3D"font-weight:bold">Subject: </span> Re: Proposal to revise ISOC's missio=
n statement<br></div><div><br></div><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><meta http-equiv=3D"Content-Type" content=3D"text/html charset=3Dutf-8=
"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-=
break: after-white-space;" class=3D"">On Nov 7, 2017, at 06:59, Lee Howard &lt=
;<a href=3D"mailto:Lee@asgard.org" class=3D"">Lee@asgard.org</a>&gt; wrote:<br c=
lass=3D""><div><blockquote type=3D"cite" class=3D"">On&nbsp;<span style=3D"font-fami=
ly: Menlo-Regular; font-size: 11px;" class=3D"">11/7/17, 4:59 AM</span>, Steph=
en Farrell &lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" class=3D"">stephen.f=
arrell@cs.tcd.ie</a>&gt; wrote:</blockquote><blockquote type=3D"cite" class=3D""=
><div class=3D""><blockquote type=3D"cite" class=3D"" style=3D"font-family: Menlo-Re=
gular; font-size: 11px;">[&#8230;]&nbsp;While the latter&nbsp;may have some =
fig-leaf of so-called "consent" or clicked-EULA,&nbsp;it's the same informat=
ion being gathered/centralised etc. (And&nbsp;of course the latter form of s=
urveillance can nicely feed the&nbsp;former when companies are compelled.)</=
blockquote></div><div class=3D""><br class=3D""></div></blockquote><blockquote t=
ype=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: Menlo-Regular; f=
ont-size: 11px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-tr=
ansform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-w=
idth: 0px; float: none; display: inline !important;" class=3D"">Another form o=
f corporate surveillance is monitoring your employees&#8217; use&nbsp;</span=
><span style=3D"font-family: Menlo-Regular; font-size: 11px; font-style: norma=
l; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; t=
ext-align: start; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">of your corporate resources. I hope we don&#821=
7;t collectively object to that.&nbsp;</span><span style=3D"font-family: Menlo=
-Regular; font-size: 11px; font-style: normal; font-variant-caps: normal; fo=
nt-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0=
px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-te=
xt-stroke-width: 0px; float: none; display: inline !important;" class=3D"">Sim=
ilarly, parents may surveill their childrens&#8217; use of family resources.=
</span></div></blockquote></div><div class=3D""><br class=3D""></div><div class=3D=
"">Those are dissimilar with respect to the issue of consent. It&#8217;s one=
 thing to use surveillance technologies in the role of legal guardian for de=
pendents without capacity for consent, and it&#8217;s an entirely different =
thing to use a contract of adhesion to coerce subordinates into &#8220;conse=
nting&#8221; to give up their rights to intimate privacy.</div></div></div><=
/blockquote></span><div><br></div><div>You have no right to &#8220;intimate =
privacy&#8221; at work on your company-owned computer on the company network=
 on company time.</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><block=
quote 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 style=3D"word-wrap: break-w=
ord; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=
=3D""><div class=3D""><br class=3D""></div><div class=3D"">And there&#8217;s a lot o=
f dirty business hiding under that phrase &#8220;monitoring your employees&#=
8217; use of your corporate resources&#8221; when you consider that your emp=
loyees have personal identities in social media that can, at any moment, bec=
ome involved in a viral public relations disaster. When corporations regard =
the personal online activity of their employees, using personal resources at=
 home on their own time, as bearing on the public brand identity, using that=
 to justify surveilling their employees private social activity, and further=
 insist on employees &#8220;consenting&#8221; to this surveillance as terms =
of their employment, that&#8217;s hardly similar to a parent monitoring thei=
r kids&#8217; porn habits.</div></div></div></blockquote></span><div><br></d=
iv><div>Who said anything about &#8220;personal resources at home on their o=
wn time&#8221;?</div><div>Trying to expand my statement to include that is m=
ore than simply disingenuously building a straw man to throw down a slippery=
 slope, it&#8217;s dishonest.</div><div><br></div><div>Lee</div><span id=3D"OL=
K_SRC_BODY_SECTION"><div><div style=3D"word-wrap: break-word; -webkit-nbsp-mod=
e: space; -webkit-line-break: after-white-space;" class=3D""><br class=3D""></di=
v></div></span></body></html>

--B_3592911996_10602376--



From nobody Tue Nov  7 12:24:04 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 A3C20126C83 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 12:24:02 -0800 (PST)
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, 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 l94Q-d-0gJTT for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 12:24:00 -0800 (PST)
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 80864126BF7 for <ietf@ietf.org>; Tue,  7 Nov 2017 12:24:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id A9290BDCC; Tue,  7 Nov 2017 20:23:58 +0000 (GMT)
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 mufVOQ8qJUBn; Tue,  7 Nov 2017 20:23:57 +0000 (GMT)
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 45748BE38; Tue,  7 Nov 2017 20:23:57 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1510086237; bh=K6qOkLdETjnOgQkE3ZfDCG9Mk+ewaTCaAzmzObd5uUU=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=BnrbDMnc+9iB5zxTkeIdyOYyFaVBRaWS/lLgK9PJ67aBoVBKsjxbxQbR18ZscEQ8t tbAwmwqzY+dOsPw1G4yKiAdIXL+5hXhQPZPKJVlBCVUKL5MyrKC9993T67nb3HVr0y hGzIarVSftdCAX8jh1cfI/nAhAJkUhhLw7iasS1g=
Subject: Re: Proposal to revise ISOC's mission statement
To: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
Date: Tue, 7 Nov 2017 20:23:56 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <D6277B2F.8B95A%lee@asgard.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pDLACvU34x1oAbcEr0NVnW1ftAI4Kjjam"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HNVXvLOI_eg5sq-V740uO0LAeSo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 20:24:03 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--pDLACvU34x1oAbcEr0NVnW1ftAI4Kjjam
Content-Type: multipart/mixed; boundary="8999PbhRJwudPkflbm0d8oSXAL2ONqEnx";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
Subject: Re: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com>
 <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com>
 <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com>
 <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com>
 <6.2.5.6.2.20171029130937.113d0e80@elandnews.com>
 <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com>
 <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
 <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com>
 <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com>
 <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com>
 <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>
 <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
 <D6274256.8B776%lee@asgard.org>
 <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com>
 <D6277B2F.8B95A%lee@asgard.org>
In-Reply-To: <D6277B2F.8B95A%lee@asgard.org>

--8999PbhRJwudPkflbm0d8oSXAL2ONqEnx
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable


Hi Lee,

On 07/11/17 19:06, Lee Howard wrote:
> You have no right to =C3=A2=E2=82=AC=C5=93intimate privacy=C3=A2=E2=82=AC=
=C2=9D at work on your company-owned
> computer on the company network on company time.

First, I don't think there's any need to (nor liklihood of)
reaching consensus as to the above. FWIW, I don't agree
with you, and nor would various court judgements in some
places in the world. I fully accept that your position is
one shared by a bunch of folks though.

But in any case, there are many other forms of corporate
surveillance (e.g. kid's toys calling home to the manuf
for dodgy reasons) so I hope you'd agree that we don't
have to have 100% agreement about all of that to agree
that surveillance is not an issue that always involves a
government actor.

S.


--8999PbhRJwudPkflbm0d8oSXAL2ONqEnx--

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

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

iQEcBAEBCAAGBQJaAhZcAAoJEC88hzaAX42iK44H/0UwUgD5IZFTQ18xFJoVrjuD
yfwY1r6ukIWA8jncgjttDhEXtXMaFUBYBd9/7fgD/lzueFafcvzRVkjOb98rY5q0
Jc2DF3kAVbY2MBdv06TvDkBvPeSOlN/mjyy6a3BpSmrewlmJLRmtmBCUE60MJpFx
xnFbBBcrhBJ0Ct0MZwfqEj0SDLtj1lzHjIBEfKVvoDUg365YTxI7QSuvVqTKkXrx
8sydHOa4i5HBXjn9vc0RVTV6tLVWyPqbxJyj8EaBIlnCqezi80xLbEWaBl590T5p
lngcq9fc/47Wkwx+N/hURcJdDv50HV1gGG33usdJKkCrwTrhboMW0SeVO1QM66E=
=8q6Z
-----END PGP SIGNATURE-----

--pDLACvU34x1oAbcEr0NVnW1ftAI4Kjjam--


From nobody Tue Nov  7 12:46:29 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 1BA5C126BF7 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 12:46:28 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdrynbhyqIbM for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 12:46:25 -0800 (PST)
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 9ECE61201F8 for <ietf@ietf.org>; Tue,  7 Nov 2017 12:46:25 -0800 (PST)
Received: from xsmtp02.mail2web.com ([168.144.250.215]) by mx19.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1eCAlJ-0003DO-R6 for ietf@ietf.org; Tue, 07 Nov 2017 21:46:23 +0100
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1eCAlH-0004qH-K7 for ietf@ietf.org; Tue, 07 Nov 2017 15:46:20 -0500
Received: (qmail 22884 invoked from network); 7 Nov 2017 20:46:17 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.56.42.39]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 7 Nov 2017 20:46:17 -0000
To: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <1520ee9b-9591-ae22-c9ae-8183d686ce14@huitema.net>
Date: Tue, 7 Nov 2017 12:46:16 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <D6277B2F.8B95A%lee@asgard.org>
Content-Type: multipart/alternative; boundary="------------BB960351680A8A059856989F"
Content-Language: en-US
Subject: Re: Proposal to revise ISOC's mission statement
X-Originating-IP: 168.144.250.215
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.16)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5okwtIf15ombPhCs2I6DowYXv9krsgRhBn0ayn6qsUc7A/WvCPr15FZJ Lv3b+YLl4bgNzB/4Jkrw1eDLcif59fvlnzUbURnIRIitOa5RuwAyB98yDTitFWvbHwz9vKZpm4b3 Kv7PcFSfRyFbnU/eNYfVCZ1my7qTGj+pYSPpnV3tZsQEbaxxISMHgJxrdMdSS4B6hVJPXxgisa+g wkHvC+OlqTWdUBHTyoJG+mqGBYi8bWhnKPmUW/oWx9V3wTBfG4Y+ZnfomCI+rgOtA8u12EwuwjY+ quNh23liqqeOwMwwqy4lE5s79uoGaeHjfOqnzPcqs5RcLqZ0NIAm9sCHr2eyNIkhDia+jiI1x+25 WhJqOf3+cMSJJ9Vk8Y6lSpImWOFtQUIkkMAnR5eEArf6zd8XhA0UizXQaOxPdjju+1r1qq9IJIue NdZ12JJe7t4cD3McN6qoXPjenLhIOF1oeRZebuqHUdnKNk8pbKYPjXJ7HUXBZ+ybkmDgxFSX9KYD 2E4Nh2Txbpkfdfu+XbiOcSDGvVLPSj+Hlyh2mculO/W8NktFVcl6hrIDm43UklXgo0rGkb5OztVl OoF8rUUHwR1JLObs/ksVBOHvEAgSr8kAncmvtvEdUlxbJvi/fXE8UUONoJfh+XjGSeeT90H/uIGG sJKxuAdOESrEnA686Fn/OROS3ygXtoq2KmWOkKRtBWbjO41FyBEqIaDudcVplPEfgkCmu0AbpCDt lYGBUhlWYs7lDW5ylWmc/a8vvFzKcPfFcHV2tQAVqGdj/zM7G/G/SWpFaZhl6XgNy1goGNwk5ft9 Iz0WDtXlRni5HCCJM9Qvlo9UV7vdWttsewtXKowaEO652uo+6xHVEn43gl09gN9PtOEBx/RKpFEr HkJ0VfjEzm1SsR8v3aJbN/NZfa/pGyl0Yc/hSh4fhbFqiL7w
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Lx-uHLY-N_RC2fLM5laFIF_MsV0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 20:46:28 -0000

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



On 11/7/2017 11:06 AM, Lee Howard wrote:
=C2=A0(Responding to James Woodyatt)
>
>     Those are dissimilar with respect to the issue of consent. It=E2=80=
=99s
>     one thing to use surveillance technologies in the role of legal
>     guardian for dependents without capacity for consent, and it=E2=80=99=
s an
>     entirely different thing to use a contract of adhesion to coerce
>     subordinates into =E2=80=9Cconsenting=E2=80=9D to give up their rig=
hts to intimate
>     privacy.
>
>
> You have no right to =E2=80=9Cintimate privacy=E2=80=9D at work on your=
 company-owned
> computer on the company network on company time.

Lee, you are making here a legal statement, "you have no right". As a
matter of fact, that statement depends on which laws apply in the place
of business. I understand that most US courts will consider that
employers have a right to monitor employees' communications, although
there are gray areas when employers allow private use of corporate
email. But then, German courts will take the opposite view.

The opinion of the European Court of Human Rights, as reported here by
the
NYT(https://www.nytimes.com/2017/09/05/business/european-court-employers-=
workers-email.html),
is rather nuanced. The very high level summary of that opinion is that
expectations should be set clearly, so that employees understand what is
monitored and what is not. The opinion also states that enterprises
should be reasonable, and limit their monitoring to work relevant issues.=


Bottom line, the situation is much more nuanced than "you have no
right". Although of course I always advise my friends to not conduct
private conversations using corporate email, and use their own personal
account instead.

-- Christian Huitema

--------------BB960351680A8A059856989F
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 11/7/2017 11:06 AM, Lee Howard
      wrote:<br>
       (Responding to James Woodyatt)<br>
    </div>
    <blockquote type="cite" cite="mid:D6277B2F.8B95A%25lee@asgard.org"><span
        id="OLK_SRC_BODY_SECTION">
        <blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
          style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div style="word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space;" class="">
              <div class="">Those are dissimilar with respect to the
                issue of consent. It’s one thing to use surveillance
                technologies in the role of legal guardian for
                dependents without capacity for consent, and it’s an
                entirely different thing to use a contract of adhesion
                to coerce subordinates into “consenting” to give up
                their rights to intimate privacy.</div>
            </div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>You have no right to “intimate privacy” at work on your
        company-owned computer on the company network on company time.</div>
    </blockquote>
    <br>
    Lee, you are making here a legal statement, "you have no right". As
    a matter of fact, that statement depends on which laws apply in the
    place of business. I understand that most US courts will consider
    that employers have a right to monitor employees' communications,
    although there are gray areas when employers allow private use of
    corporate email. But then, German courts will take the opposite
    view. <br>
    <br>
    The opinion of the European Court of Human Rights, as reported here
    by the
NYT(<a class="moz-txt-link-freetext" href="https://www.nytimes.com/2017/09/05/business/european-court-employers-workers-email.html">https://www.nytimes.com/2017/09/05/business/european-court-employers-workers-email.html</a>),
    is rather nuanced. The very high level summary of that opinion is
    that expectations should be set clearly, so that employees
    understand what is monitored and what is not. The opinion also
    states that enterprises should be reasonable, and limit their
    monitoring to work relevant issues. <br>
    <br>
    Bottom line, the situation is much more nuanced than "you have no
    right". Although of course I always advise my friends to not conduct
    private conversations using corporate email, and use their own
    personal account instead.<br>
    <br>
    -- Christian Huitema<br>
  </body>
</html>

--------------BB960351680A8A059856989F--


From nobody Tue Nov  7 13:17:03 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 F26E41274D2 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 13:17:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (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 3KjJp7duqpeK for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 13:16:59 -0800 (PST)
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 60A0D126C2F for <ietf@ietf.org>; Tue,  7 Nov 2017 13:16:59 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id e64so416035pfk.9 for <ietf@ietf.org>; Tue, 07 Nov 2017 13:16:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=KPce+N3VoH9t/0d9xOZ7fqM7EEOIGkcvQU8MN+Y3e4w=; b=uScT+VsNsY3xCNJhinls6ZxdNvbQW1u4zltz5U0y2jQPLMxFQnuECg8+LvJRhu2Aj1 v7eGjU/VOjpR3VVBkIu5oyN5E1ecTwN1xkGsL5b9A96bKt/A1ZeQ6xGnVbJ5o+WBPUTx +AiZViJQXeuTNIzBi2ZeENyxBdTTCGrmTlZdQNFhEcG9EU4I2mpR0YehKb6sMj7ud6T0 hqyJwsYaa18aBmdw/A84McKbVWGxmEOVMWqPKmP0SNPRgDNLtFEuCduJSNEPWhTaQEqA zU4FP+k6km4Lvs041gh5W/Hba3sisJhFEo8xhkl66b50yee6YegMCaMf1jhDu3QHH4S6 BHIQ==
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=KPce+N3VoH9t/0d9xOZ7fqM7EEOIGkcvQU8MN+Y3e4w=; b=OUtFYX1glwBAY6JmIG41cV12iahOzWT+4hjdug3AKZscsYthM2TsZ5gldO8FHMbNqF tvCQhc1B3WAueeAUyEWKk6srQB6UhtvVvspzzZpJ/7hcNANqZXaK4L+VcBV/sk2NuY69 r1mzuoVcSp+beZgGliOix51NlKwaQqFXy1EjXm9/DR7HwOuK7a1pM44OlJYWrTdO47sg AXt73ZDx/vC+9wmLvqlrQEQnO1YvxQ6JXRlaGZpxkfHCC+QJf+Vy3hlxK4k176CJ0G/7 IKkgOYPI9JDtQQlNCSUKVIrL5XlGCsjSCF6buS+E49gAF4guWiFcqqcR035LiWllMDfi mksA==
X-Gm-Message-State: AJaThX5EFyNLM/ZPxXThHjc73HvYGW0aJYEzVhLc8X7cXfPw9vg1gq5a EGG3qqpK/8ScW/JcPQxB6/CALGZ6YXA=
X-Google-Smtp-Source: ABhQp+R/X+TOafM32rPDF5LDIdSiKmP0R+GTC2LVeDSxEKzvALmvCGfOsXOqQmQCmFV0UUZHIy2h0w==
X-Received: by 10.159.255.70 with SMTP id u6mr76271pls.41.1510089418640; Tue, 07 Nov 2017 13:16:58 -0800 (PST)
Received: from ?IPv6:2620::10e7:10:2d7e:1874:c224:61c4? ([2620:0:10e7:10:2d7e:1874:c224:61c4]) by smtp.gmail.com with ESMTPSA id a7sm3638196pgt.39.2017.11.07.13.16.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 13:16:57 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <63B79BF1-F2C6-447F-94A3-6515C83AAF02@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D09B7261-5142-4A0F-87A9-F2084F29AE92"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Proposal to revise ISOC's mission statement
Date: Tue, 7 Nov 2017 13:16:57 -0800
In-Reply-To: <1520ee9b-9591-ae22-c9ae-8183d686ce14@huitema.net>
Cc: Lee Howard <lee@asgard.org>, IETF Discussion Mailing List <ietf@ietf.org>
To: Christian Huitema <huitema@huitema.net>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <1520ee9b-9591-ae22-c9ae-8183d686ce14@huitema.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3d6bG8AXTW4EDZ5RPrrAvz-47J4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 21:17:01 -0000

--Apple-Mail=_D09B7261-5142-4A0F-87A9-F2084F29AE92
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On Nov 7, 2017, at 12:46, Christian Huitema <huitema@huitema.net> wrote:
> [I wrote:]
>> ...it=E2=80=99s an entirely different thing to use a contract of =
adhesion to coerce subordinates...
>=20
> Bottom line, the situation is much more nuanced than "you have no =
right"


Yes, and the reason I used that technical phrase =E2=80=9Ccontract of =
adhesion=E2=80=9D there is to set down a marker observing that various =
arguments about the unconscionability (and therefore the =
unenforceability) of various standard form contract provisions commonly =
observed in the wild remain basically untested. I contend it would be =
within the ambit of ISOC to take public positions on some of those =
questions.


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




--Apple-Mail=_D09B7261-5142-4A0F-87A9-F2084F29AE92
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 Nov 7, 2017, at 12:46, =
Christian Huitema &lt;huit<a href=3D"mailto:ema@huitema.net" =
class=3D"">ema@huitema.net</a>&gt; wrote:</div><div class=3D""><blockquote=
 type=3D"cite" class=3D"">[I wrote:]</blockquote><blockquote type=3D"cite"=
 cite=3D"mid:D6277B2F.8B95A%25lee@asgard.org" style=3D"background-color: =
rgb(255, 255, 255);" class=3D""><span id=3D"OLK_SRC_BODY_SECTION" =
class=3D""><blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"padding: 0px 0px 0px 5px; margin: 0px 0px 0px 5px;" =
class=3D""><div class=3D"" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div =
class=3D""><blockquote type=3D"cite" class=3D"">...it=E2=80=99s an =
entirely different thing to use a contract of adhesion to coerce =
subordinates...</blockquote></div></div></blockquote></span></blockquote><=
/div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div 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; =
background-color: rgb(255, 255, 255); float: none; display: inline =
!important;" class=3D"">Bottom line, the situation is much more nuanced =
than "you have no right"</span></div></blockquote></div><div =
class=3D""><br class=3D""></div><div class=3D"">Yes, and the reason I =
used that technical phrase =E2=80=9Ccontract of adhesion=E2=80=9D there =
is to set down a marker observing that various arguments about the =
unconscionability (and therefore the unenforceability) of various =
standard form contract provisions commonly observed in the wild remain =
basically untested. I contend it would be within the ambit of ISOC to =
take public positions on some of those questions.</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=_D09B7261-5142-4A0F-87A9-F2084F29AE92--


From nobody Tue Nov  7 13:49:26 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 23481127ABE for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 13:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 PSimd8tUBkv3 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 13:49:24 -0800 (PST)
Received: from alcoop-m-mx19.fios-router.home (pool-108-48-166-97.washdc.fios.verizon.net [108.48.166.97]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id ADA4C126C19 for <ietf@ietf.org>; Tue,  7 Nov 2017 13:49:24 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_42A75443-DBB4-477E-9EB6-AB74CE919E66"
Subject: IETF 100: Preview and Report
Message-Id: <B1E151ED-84A3-4587-8291-7E0F7AAFB038@ietf.org>
Date: Tue, 7 Nov 2017 16:49:22 -0500
To: IETF Discussion <ietf@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/r9QP775lef-JKkMadoy-EM8RMkM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Nov 2017 21:49:26 -0000

--Apple-Mail=_42A75443-DBB4-477E-9EB6-AB74CE919E66
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

There is a new post up on the IETF blog highlighting some upcoming =
activities at IETF 100: =
<https://www.ietf.org/blog/2017/11/ietf-100-preview/ =
<https://www.ietf.org/blog/2017/11/ietf-100-preview/>>

The pre-meeting report from the IESG and IETF Chair has also been =
posted: =
<https://datatracker.ietf.org/meeting/100/materials/slides-100-ietf-sessa-=
ietf-chair-and-iesg-report-ietf-100/ =
<https://datatracker.ietf.org/meeting/100/materials/slides-100-ietf-sessa-=
ietf-chair-and-iesg-report-ietf-100/>>. The written report is provided =
in advance to reduce reporting at the plenary.

Comments, questions, and suggestions are welcome as always.

Alissa Cooper
IETF Chair


--Apple-Mail=_42A75443-DBB4-477E-9EB6-AB74CE919E66
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"">There is a new post up on the IETF blog highlighting some =
upcoming activities at IETF 100: &lt;<a =
href=3D"https://www.ietf.org/blog/2017/11/ietf-100-preview/" =
class=3D"">https://www.ietf.org/blog/2017/11/ietf-100-preview/</a>&gt;<div=
 class=3D""><br class=3D""></div><div class=3D"">The pre-meeting report =
from the IESG and IETF Chair has also been posted: &lt;<a =
href=3D"https://datatracker.ietf.org/meeting/100/materials/slides-100-ietf=
-sessa-ietf-chair-and-iesg-report-ietf-100/" =
class=3D"">https://datatracker.ietf.org/meeting/100/materials/slides-100-i=
etf-sessa-ietf-chair-and-iesg-report-ietf-100/</a>&gt;. The written =
report is provided in advance to reduce reporting at the =
plenary.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Comments, questions, and suggestions are welcome as =
always.</div><div class=3D""><br class=3D""></div><div class=3D"">Alissa =
Cooper</div><div class=3D"">IETF Chair<br class=3D""><div class=3D""><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_42A75443-DBB4-477E-9EB6-AB74CE919E66--


From nobody Tue Nov  7 20:36:53 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 5C8EF129BF3 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 20:36:51 -0800 (PST)
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, MIME_QP_LONG_LINE=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 KOTSkXYgvzAx for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 20:36:50 -0800 (PST)
Received: from atl4mhob17.registeredsite.com (atl4mhob17.registeredsite.com [209.17.115.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AADB12773A for <ietf@ietf.org>; Tue,  7 Nov 2017 20:36:49 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob17.registeredsite.com (8.14.4/8.14.4) with ESMTP id vA84akNp024558 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 7 Nov 2017 23:36:46 -0500
Received: (qmail 3380 invoked by uid 0); 8 Nov 2017 04:36:46 -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; 8 Nov 2017 04:36:46 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Tue, 07 Nov 2017 23:36:42 -0400
Subject: Re: Proposal to revise ISOC's mission statement
From: Lee Howard <lee@asgard.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, james woodyatt <jhw@google.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <D627F266.8B9C3%lee@asgard.org>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
In-Reply-To: <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qb6uuare2UuNxxRT3vBHhEgafTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 04:36:51 -0000

On 11/7/17, 4:23 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

>
>Hi Lee,
>
>On 07/11/17 19:06, Lee Howard wrote:
>> You have no right to =C3=A2=E2=82=AC=C5=93intimate privacy=C3=A2=E2=82=AC=C2=9D at work on your
>>company-owned
>> computer on the company network on company time.
>
>First, I don't think there's any need to (nor liklihood of)
>reaching consensus as to the above. FWIW, I don't agree
>with you, and nor would various court judgements in some
>places in the world. I fully accept that your position is
>one shared by a bunch of folks though.

Great summary: I am in the minority here, but it is not clear that there
is consensus.
Out of curiosity, can you point me to courts that have found a right to
privacy where all three conditions existed (company device, company
network, company time)?

>
>But in any case, there are many other forms of corporate
>surveillance (e.g. kid's toys calling home to the manuf
>for dodgy reasons) so I hope you'd agree that we don't
>have to have 100% agreement about all of that to agree
>that surveillance is not an issue that always involves a
>government actor.

Yes, that=E2=80=99s where we started. I was pointing out an additional vector of
surveillance, which might not be as easily dismissed. Your example is
another one (whether the reasons are dodgy or noble). Surveillance does
not always involve a government actor, and I think there=E2=80=99s consensus on
that. I further assert that there are conditions under which surveillance
is not evil, but that statement does not have consensus support.

Lee

>
>S.
>



From nobody Tue Nov  7 20:59:07 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 C5CE6129BF3 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 20:59:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.698
X-Spam-Level: 
X-Spam-Status: No, score=-4.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 ASBFZ880ZcG6 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 20:59:03 -0800 (PST)
Received: from atl4mhob23.registeredsite.com (atl4mhob23.registeredsite.com [209.17.115.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C53812945F for <ietf@ietf.org>; Tue,  7 Nov 2017 20:59:03 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob23.registeredsite.com (8.14.4/8.14.4) with ESMTP id vA84wx9U010393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 7 Nov 2017 23:58:59 -0500
Received: (qmail 20198 invoked by uid 0); 8 Nov 2017 04:58:59 -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; 8 Nov 2017 04:58:59 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Tue, 07 Nov 2017 23:58:55 -0400
Subject: Re: Proposal to revise ISOC's mission statement
From: Lee Howard <lee@asgard.org>
To: Christian Huitema <huitema@huitema.net>, james woodyatt <jhw@google.com>
CC: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <D627F4D7.8B9D2%lee@asgard.org>
Thread-Topic: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <1520ee9b-9591-ae22-c9ae-8183d686ce14@huitema.net>
In-Reply-To: <1520ee9b-9591-ae22-c9ae-8183d686ce14@huitema.net>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3592943939_11934079"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M4iMjazy-lgHuXmDuWJE1FQfi8c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 04:59:06 -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_3592943939_11934079
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable



From:  Christian Huitema <huitema@huitema.net>
Date:  Tuesday, November 7, 2017 at 4:46 PM
To:  Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>
Cc:  IETF Discussion Mailing List <ietf@ietf.org>
Subject:  Re: Proposal to revise ISOC's mission statement

>    =20
> =20
>=20
>=20
> =20
> =20
> =20
> On 11/7/2017 11:06 AM, Lee Howard wrote:
>   (Responding to James Woodyatt)
> =20
> =20
>> =20
>>> =20
>>> =20
>>> =20
>>> Those are dissimilar with respect to the issue of consent. It=E2=80=99s one t=
hing to
>>> use surveillance technologies in the role of legal guardian for depende=
nts
>>> without capacity for consent, and it=E2=80=99s an entirely different thing to=
 use a
>>> contract of adhesion to coerce subordinates into =E2=80=9Cconsenting=E2=80=9D to gi=
ve up
>>> their rights to intimate privacy.
>>> =20
>>> =20
>>> =20
>>  =20
>>=20
>> =20
>> =20
>> You have no right to =E2=80=9Cintimate privacy=E2=80=9D at work on your company-owne=
d
>> computer on the company network on company time.
>> =20
> =20
>  Lee, you are making here a legal statement, "you have no right". As a ma=
tter
> of fact, that statement depends on which laws apply in the place of busin=
ess.
> I understand that most US courts will consider that employers have a righ=
t to
> monitor employees' communications, although there are gray areas when
> employers allow private use of corporate email. But then, German courts w=
ill
> take the opposite view.
> =20
>  The opinion of the European Court of Human Rights, as reported here by t=
he
> NYT(https://www.nytimes.com/2017/09/05/business/european-court-employers-=
worke
> rs-email.html), is rather nuanced. The very high level summary of that op=
inion
> is that expectations should be set clearly, so that employees understand =
what
> is monitored and what is not. The opinion also states that enterprises sh=
ould
> be reasonable, and limit their monitoring to work relevant issues.

Thanks for that link; that article was interesting and illuminating. The
nuance is that in affected jurisdictions, employers must disclose the exten=
t
to which they might inspect employees=E2=80=99 communication. That seems like a
reasonable constraint (although one that would have been better articulated
before the fact, rather than inferring the requirement).

I think rights, though, are not just a legal matter, but a philosophical
one. And when examining rights, it=E2=80=99s always interesting to examine the
inverse, and look at who is compelled to safeguard those rights.

>=20
> =20
>  Bottom line, the situation is much more nuanced than "you have no right"=
.
> Although of course I always advise my friends to not conduct private
> conversations using corporate email, and use their own personal account
> instead.

That=E2=80=99s prudent advice. Even if they weren=E2=80=99t permitted to produce your e=
mail
in court, trusting that your employer isn=E2=80=99t monitoring your activity is
asking for trouble. Firewalls can=E2=80=99t tell the difference between mSexChang=
e
and MSExchange (real example), and employee can do many things short of
legal action.

Practical example: I was firewall administrator at a previous employer. So
when they asked about employee activity, and I did some analysis, I could
say, =E2=80=9CThis person is spending 4-6 hours a day on Local University site, a=
nd
this person spends 40 minutes around lunch time on porn sites.=E2=80=9D Rumor was
(though I was not privy to personnel records) that the first person had bee=
n
billing that time to clients, and was fired for fraud. Second person=E2=80=99s
activity suddenly stopped appearing in logs a couple weeks later.
Even if the employer didn=E2=80=99t have the ability to produce those logs in cou=
rt,
management might have suddenly been a lot more visible with those employees=
.


Lee

>=20
> =20
>  -- Christian Huitema
> =20



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

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif;"><div><br></div><div><br></div><spa=
n id=3D"OLK_SRC_BODY_SECTION"><div style=3D"font-family:Calibri; font-size:11pt;=
 text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medi=
um none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-=
TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span s=
tyle=3D"font-weight:bold">From: </span> Christian Huitema &lt;<a href=3D"mailto:=
huitema@huitema.net">huitema@huitema.net</a>&gt;<br><span style=3D"font-weight=
:bold">Date: </span> Tuesday, November 7, 2017 at 4:46 PM<br><span style=3D"fo=
nt-weight:bold">To: </span> Lee Howard &lt;<a href=3D"mailto:lee@asgard.org">l=
ee@asgard.org</a>&gt;, james woodyatt &lt;<a href=3D"mailto:jhw@google.com">jh=
w@google.com</a>&gt;<br><span style=3D"font-weight:bold">Cc: </span> IETF Disc=
ussion Mailing List &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;=
<br><span style=3D"font-weight:bold">Subject: </span> Re: Proposal to revise I=
SOC's mission statement<br></div><div><br></div><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>
  
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8">
  
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">On 11/7/2017 11:06 AM, Lee Howard
      wrote:<br>
      &nbsp;(Responding to James Woodyatt)<br>
    </div>
    <blockquote type=3D"cite" cite=3D"mid:D6277B2F.8B95A%25lee@asgard.org"><spa=
n id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-L=
EFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div>
            <div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space;" class=3D"">
              <div class=3D"">Those are dissimilar with respect to the
                issue of consent. It&#8217;s one thing to use surveillance
                technologies in the role of legal guardian for
                dependents without capacity for consent, and it&#8217;s an
                entirely different thing to use a contract of adhesion
                to coerce subordinates into &#8220;consenting&#8221; to giv=
e up
                their rights to intimate privacy.</div>
            </div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>You have no right to &#8220;intimate privacy&#8221; at work on y=
our
        company-owned computer on the company network on company time.</div=
>
    </blockquote>
    <br>
    Lee, you are making here a legal statement, "you have no right". As
    a matter of fact, that statement depends on which laws apply in the
    place of business. I understand that most US courts will consider
    that employers have a right to monitor employees' communications,
    although there are gray areas when employers allow private use of
    corporate email. But then, German courts will take the opposite
    view. <br>
    <br>
    The opinion of the European Court of Human Rights, as reported here
    by the
NYT(<a class=3D"moz-txt-link-freetext" href=3D"https://www.nytimes.com/2017/09/=
05/business/european-court-employers-workers-email.html">https://www.nytimes=
.com/2017/09/05/business/european-court-employers-workers-email.html</a>),
    is rather nuanced. The very high level summary of that opinion is
    that expectations should be set clearly, so that employees
    understand what is monitored and what is not. The opinion also
    states that enterprises should be reasonable, and limit their
    monitoring to work relevant issues. </div></div></blockquote></span><di=
v><br></div><div>Thanks for that link; that article was interesting and illu=
minating. The nuance is that in affected jurisdictions, employers must discl=
ose the extent to which they might inspect employees&#8217; communication. T=
hat seems like a reasonable constraint (although one that would have been be=
tter articulated before the fact, rather than inferring the requirement).&nb=
sp;</div><div><br></div><div>I think rights, though, are not just a legal ma=
tter, but a philosophical one. And when examining rights, it&#8217;s always =
interesting to examine the inverse, and look at who is compelled to safeguar=
d those rights.</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><blockqu=
ote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df 5 so=
lid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><div text=3D"#000000" bgcolor=3D"#FF=
FFFF"><br>
    <br>
    Bottom line, the situation is much more nuanced than "you have no
    right". Although of course I always advise my friends to not conduct
    private conversations using corporate email, and use their own
    personal account instead.</div></div></blockquote></span><div><br></div=
><div>That&#8217;s prudent advice. Even if they weren&#8217;t permitted to p=
roduce your email in court, trusting that your employer isn&#8217;t monitori=
ng your activity is asking for trouble. Firewalls can&#8217;t tell the diffe=
rence between mSexChange and MSExchange (real example), and employee can do =
many things short of legal action.</div><div><br></div><div>Practical exampl=
e: I was firewall administrator at a previous employer. So when they asked a=
bout employee activity, and I did some analysis, I could say, &#8220;This pe=
rson is spending 4-6 hours a day on Local University site, and this person s=
pends 40 minutes around lunch time on porn sites.&#8221; Rumor was (though I=
 was not privy to personnel records) that the first person had been billing =
that time to clients, and was fired for fraud. Second person&#8217;s activit=
y suddenly stopped appearing in logs a couple weeks later.&nbsp;</div><div>E=
ven if the employer didn&#8217;t have the ability to produce those logs in c=
ourt, management might have suddenly been a lot more visible with those empl=
oyees.</div><div><br></div><div><br></div><div>Lee</div><div><br></div><span=
 id=3D"OLK_SRC_BODY_SECTION"><blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOT=
E" style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><d=
iv><div text=3D"#000000" bgcolor=3D"#FFFFFF"><br>
    <br>
    -- Christian Huitema<br>
  </div></div></blockquote></span></body></html>

--B_3592943939_11934079--



From nobody Tue Nov  7 21:47:55 2017
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41DA512EBF7 for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 21:47:54 -0800 (PST)
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=softarmor.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qif9Yp_CNtG for <ietf@ietfa.amsl.com>; Tue,  7 Nov 2017 21:47:52 -0800 (PST)
Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::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 8F9E012EBEC for <ietf@ietf.org>; Tue,  7 Nov 2017 21:47:52 -0800 (PST)
Received: by mail-ot0-x22f.google.com with SMTP id 18so1376563oty.9 for <ietf@ietf.org>; Tue, 07 Nov 2017 21:47:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=oWMW1gtTiQ+TtJsUZ4ecihXx8YU/LzCzJRInOaniFl0=; b=B8NTmEKQ/4yk7oL3unO+8DaxVZG+sE486TcbD5egJUnP+4a7HQwfWM3H9d7o6UbtXE DufX9YIgldv3Yu7uV0yHahN1bmhTH4yS2nA3CsmE307w6yyacQuU8820OvLwg0ecYLuY UDJvZ0bsz7GMjc2aDIy3TiFl/w2pp0lx9/Qus=
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 :content-language; bh=oWMW1gtTiQ+TtJsUZ4ecihXx8YU/LzCzJRInOaniFl0=; b=TQ8uLY/puPV/Id0Mi0iuiSP4p/A75zWtWnthPUglICwLp7nuegfai6j7H5r3L/aV8i uFOdai4dXfCbGvyaC/9bh8hBUGzqVVbcUOaVIYCkHIJNpjFUktllXbaoGuAvCFjAhKGS /fbyYqNxcytCFeNByioL+mzea/s6p8OIXMYyIE/FAOYT7UbFokNmG5iWFrTogP8Ob3W8 2ByST4iYVGeWQoSqhsMpQztBrgOmWL6O/NR54b+NEiqkukd6cvZcHlX4ciAwtkrDp2aA rQD2KNR/0c1rNR8Uw14yNZglCLjmfRGGATpcz35IefmaF3SEDPqwxNqRQ7ZAg5oSzddO t2pA==
X-Gm-Message-State: AJaThX5Niq4c0y/7OBBiVJygH7usZtEAyF0+ZvxBEYb7YGsp29QfHHwC fYywjjoBAB9+oARs9e6WBDWNtgbOpZs=
X-Google-Smtp-Source: AGs4zMZTjyBEpmYSFEleoMzdOPuLgxC5FTX6eGoFROUR+HrIFIKFDLjCd8RnhsWrky9Bn5hqXsc3tg==
X-Received: by 10.157.85.65 with SMTP id h1mr758646oti.381.1510120071357; Tue, 07 Nov 2017 21:47:51 -0800 (PST)
Received: from [192.168.2.2] ([104.50.220.72]) by smtp.gmail.com with ESMTPSA id u16sm1470689otd.78.2017.11.07.21.47.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Nov 2017 21:47:50 -0800 (PST)
Subject: Re: Last Call: <draft-atarius-dispatch-meid-urn-as-instanceid-05.txt> (Using the Mobile Equipment Identity (MEID) Uniform Resource Name (URN) as an Instance ID) to Informational RFC
To: ietf@ietf.org, stephen.farrell@cs.tcd.ie
References: <150966262028.32040.15224707222922251846.idtracker@ietfa.amsl.com> <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
From: Dean Willis <dean.willis@softarmor.com>
Message-ID: <c6e69b9c-8eb0-6080-9335-9752b19fd1f8@softarmor.com>
Date: Tue, 7 Nov 2017 23:47:48 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <f00e4c27-2a49-ac21-7579-0d810d2b9499@cs.tcd.ie>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SE5FVl45rLLpktTpig2emLDBkqQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 05:47:54 -0000

On 11/02/2017 08:17 PM, Stephen Farrell wrote:
> Hiya,
>
> I don't claim to fully understand the usage of this ID,
> but I'm quite sure that I have no clue what this text
> is supposed to mean (as a piece of specification):
>
>    "In particular, the "sip.instance" media feature tag
>     containing the 3GPP2 MEID URN MUST NOT be included in requests or
>     responses intended to convey any level of anonymity, as this could
>     violate the users privacy."
>
> I guess this is either an existing problem with whatever
> a "'sip.instance' media feature tag" really is or else this
> draft creates a new problem, but the quoted text seems to
> me to be non-deterministic impossible-to-program-for words
> seemingly about (but not actually helping with) privacy.
>
> Am I confused?
>
> Cheers,
> S.
>
Given that the MEID is a long-lived (permanent) identifier for the 
specific mobile equipment, it can be correlated with user identity (and 
it has cryptographic identity support at the SIM level). Thus it is 
potentially leaky. If you do NOT wish your message to give away your 
identity, don't send an MEID in it.

Of course this security consideration is patently bogus, as they're no 
doubt planning to send it all the time. Don't do this at home, kids.

Why use it? Because when a user simultaneously has multiple devices and 
one might be moving call legs betwixt them, having a persistent label 
for each of these devices (instances) is terribly handy. There are more 
reasonable ways of doing this, such as using OAuth to transiently 
instance-identify/authorize  the device. But the mobile folks (and most 
explicitly, the SIM folks) have a lot already invested in MEID, so 
that's what they want to do, even if it is probably long-term 
self-defeating because it builds them into the sort of silo that 
WhatsApp and others live to tear down. But hey, they live in a world of 
government wire taps and cheap APIs for tracking users, so why should 
they care? They're "only going to use it on a secure and trusted 
network", as usual. Right...


--
Dean Willis


From nobody Wed Nov  8 01:16:52 2017
Return-Path: <ietf@trammell.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 9139C131878 for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:16:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNqtm_NzZtns for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:16:47 -0800 (PST)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 859F6131479 for <ietf@ietf.org>; Wed,  8 Nov 2017 01:16:47 -0800 (PST)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 2C01034025C; Wed,  8 Nov 2017 10:16:46 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/18338.8220);  Wed,  8 Nov 2017 10:16:45 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed,  8 Nov 2017 10:16:44 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.5]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 35292588; Wed, 08 Nov 2017 10:16:44 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_5771BD54-F094-469D-AD11-436364135879"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Proposal to revise ISOC's mission statement
Date: Wed, 8 Nov 2017 10:16:46 +0100
In-Reply-To: <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
Cc: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>, IETF Discussion Mailing List <ietf@ietf.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8vsV1bOAYmdVx2FHlKEuO5qolOs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 09:16:50 -0000

--Apple-Mail=_5771BD54-F094-469D-AD11-436364135879
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

hi Stephen, Lee,

> On 7 Nov 2017, at 21:23, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
>=20
>=20
> Hi Lee,
>=20
> On 07/11/17 19:06, Lee Howard wrote:
>> You have no right to =C3=A2=E2=82=AC=C5=93intimate privacy=C3=A2=E2=82=AC=
=C2=9D at work on your company-owned
>> computer on the company network on company time.
>=20
> First, I don't think there's any need to (nor liklihood of)
> reaching consensus as to the above. FWIW, I don't agree
> with you, and nor would various court judgements in some
> places in the world. I fully accept that your position is
> one shared by a bunch of folks though.

Yeah, (IANAL but) ISTM surveillance on corporate networks is a pretty =
well settled point of disagreement between US and EU legal precedent, =
which is a tiny little branch of a great big fork in the way each =
jurisdiction approaches labor law and labor relations, and is at his =
point probably just one of those things organizations doing business on =
both sides of the pond have to tolerate. Know you rights and =
responsibilities in the jurisdictions in which you operate, same as it =
ever was...

> But in any case, there are many other forms of corporate
> surveillance (e.g. kid's toys calling home to the manuf
> for dodgy reasons) so I hope you'd agree that we don't
> have to have 100% agreement about all of that to agree
> that surveillance is not an issue that always involves a
> government actor.

This is something we *absolutely* need to engage with as a community. =
There's a very clear line between "I have copies of emails you send and =
receive on the corporate account" and "there's a camera in your bedroom =
sharing on-demand video with our marketing affiliates", and we can =
discuss how bad the second is without ratholing on the first.

Indeed, I've been disappointed and perplexed that so much of the =
rhetoric around encryption post-Snowden (as epitomized by 7258) has =
focused exclusively on a nation-state or co-opted/evil =
large-network-operator attacker model, which is certainly a point of =
concern but not really where the biggest threat to collective privacy =
lies these days. I'm concerned that in our drive to Encrypt All The =
Things, absolutely the correct response when your only concern is a =
nation-state on the wire, we risk making it difficult to understand and =
defend against (what I'll call) the corporate-data-hording attacker =
model. To date, most of the evil toys phoning home and other such =
nastiness that I've heard of has been discoverable in part because said =
evil toys were using circumventable, crap, or no crypto.

If we do our job well against attackers on the wire, we make the job of =
those "attackers" on the wire whose goal it is to discover and document =
corporate-data-hoarding attacks more difficult. In a world where all =
client endpoints are using exclusively signed binaries on locked down =
systems with pinned certificates, it could become practically =
impossible.

But that's probably a different thread on a different mailing list, and =
I'm not sure how to (or whether it's a good idea to) phrase that at ISOC =
mission statement level.

Cheers,

Brian

--Apple-Mail=_5771BD54-F094-469D-AD11-436364135879
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-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAloCy34ACgkQihK3vwvq
RqOZixAAqgcnIErV/r54d8yxmLmYf2aHA/O/4RQrJez7DBAdh9ZqcqxdrHkaFcOe
hTbH/HrB99Dldw87qb/e8ar+uApNDOoj1a7apVieMQA/E6ec5kB1i/pxwzcORHMR
GJoXmLz026ef381daD2YVcOtSkvIT1/SavcryCeXwW7c1s0WkYIT8GGR8m5d1tNN
/fzpFjCqikiyYRjms4kEc6d+3zVqph0/4AyPTn+vWk1jZeFtO611RF5vbTb5WnvH
5shVX0hBCcpoN7NbZUVcsSTmHWVcrR2mNDtZWZxOZoXOSKmulCie+iMK8q7t5fzp
na2l+0xYU+rYGe8P9Rb1VFudALml3E6/ZG53ewvezS4GkJEE8+PAulrQ28vTTbeJ
zr7N5ocvWCts4OjhfviWXgPXOWBEP06Fz02sJop/R+5g94MXQ5Pl2ZR9/4sv45Sx
ynENdsp+7Ug7gxjTI6m/ZM4eKrQOL/nBdr/7HYWnxpeV66rfd0ZDsTarXt8oZWB8
18iAHvHQz+j0N9Y0PEH+0CZUP+01xMr76eGejrhkQLZsaxqZoP0uBS0470dDWPx/
mOlSd0mB9Bol/ju6qlcXRaUEZy5KFIh0jH2P+QZOaJYNUbM3AB+s2+vnVv7EKbMM
/3JzLAwevkOTDY7+ehEbYS6YWzt47/yT10LNFNMYtIy+G9gPtfc=
=Q+Pk
-----END PGP SIGNATURE-----

--Apple-Mail=_5771BD54-F094-469D-AD11-436364135879--


From nobody Wed Nov  8 01:20:27 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 4396A13187E for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:20:25 -0800 (PST)
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, 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=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 r48a_kxsN_0C for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:20:23 -0800 (PST)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55CBF1318A9 for <ietf@ietf.org>; Wed,  8 Nov 2017 01:20:23 -0800 (PST)
Received: by mail-it0-x233.google.com with SMTP id 72so6009379itl.5 for <ietf@ietf.org>; Wed, 08 Nov 2017 01:20:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=osLlEUIVnIXBoIKmPpVWeK3y/busKaeRToxBqqNTU78=; b=JkcsA+3rx3aK0XjtGxIiUo5+KEMkwtM5HGwWlx17e0Co8dDLPV2zPE1xte2pgmgsp3 8ZlNyl+ptyiE0AWfTlQGpwVY+SmmCKfa6i+PvQ56quqKMeTIe//xnyoJPVeZXfBhfrfi 1MKl/g5LBCMyvCrTmwt+/dYHbWvC7eA/PhvHH7HnbuCDdxIbaxEjPIjyJtzlfTLaiF/H pK+RPKUsq6eLPJgKdhOtRUA7v10037U0qRltV6wU0xcKsffPmRB3C3X2kgw6FKcF2IXe dQiqQ8MBPW2NiwKmJxTj2pgtyzckmaNaVuiJV3wDTdZLuWSQxWs0DOAueoHS/3CsHJhP cPxg==
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=osLlEUIVnIXBoIKmPpVWeK3y/busKaeRToxBqqNTU78=; b=SBNj23tTOVY7G/AKw/J4GxGgxE6rwZhwr92ds9tQik6d1ghPO6DMGzuIIuramZl/dL L8glfTPaL6HvLHNG9Jq5lfEdmdQ5vyBSc6tClkm6A3pOQDzU+VVTKR1qRDQF9CcQGUXr V2QlKhKeLNPgV9XSgOQLImrPhhhGMYaPc9RJHkAhbvEXBuYU0DBXA0O+t8OEnZ8J/vOS DQD39x9EvyIZRfhxwnHUe3FJBdEuysIjcbtH5+U6k85JRlrXDKaGiXt8kbtjFGgoBcXE 9uKy3/uMp58lTHraZC9WDX0sLxR2hhQPlrTiyyWMelMWIXVZhxBnGNjJYoiF254eX8Ot 9u9Q==
X-Gm-Message-State: AJaThX5PKP7FNFFjTqH0K+iWPU6f9orUILicQkmuou+2eMNfjHlVnRHA g9rmKp30rfIGz6jU+wR6x72lDRtVALEzNigbtSH/zA==
X-Google-Smtp-Source: ABhQp+SNNDsTnY21EWkvoWm2h+bBFzbPPWLz0cb0c2wV/9+FpgHzfLV3LRXC9hIgZZg8pCWVDQ59TOK5wpZGQvZFfa4=
X-Received: by 10.36.185.21 with SMTP id w21mr2892239ite.35.1510132822577; Wed, 08 Nov 2017 01:20:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.15.203 with HTTP; Wed, 8 Nov 2017 01:20:21 -0800 (PST)
Received: by 10.79.15.203 with HTTP; Wed, 8 Nov 2017 01:20:21 -0800 (PST)
In-Reply-To: <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie> <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 8 Nov 2017 04:20:21 -0500
Message-ID: <CAPt1N1=E-Pb2+YhGXk1HJfHwtVQAWahnxELBEdENi5u9NSPPDg@mail.gmail.com>
Subject: Re: Proposal to revise ISOC's mission statement
To: Brian Trammell <ietf@trammell.ch>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, james woodyatt <jhw@google.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045d9c20742f3c055d75322d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zusrpE4pyUqKKKrfA-5X-vSXvyQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 09:20:25 -0000

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

Making the packets on the wire unprotected in order to foil corporate data
gathering doesn't help, though. I agree that this is a problem, but the
solution has to be secure.

On Nov 8, 2017 10:17, "Brian Trammell (IETF)" <ietf@trammell.ch> wrote:

> hi Stephen, Lee,
>
> > On 7 Nov 2017, at 21:23, Stephen Farrell <stephen.farrell@cs.tcd.ie>
> wrote:
> >
> >
> > Hi Lee,
> >
> > On 07/11/17 19:06, Lee Howard wrote:
> >> You have no right to =C3=A2=E2=82=AC=C5=93intimate privacy=C3=A2=E2=82=
=AC  at work on your
> company-owned
> >> computer on the company network on company time.
> >
> > First, I don't think there's any need to (nor liklihood of)
> > reaching consensus as to the above. FWIW, I don't agree
> > with you, and nor would various court judgements in some
> > places in the world. I fully accept that your position is
> > one shared by a bunch of folks though.
>
> Yeah, (IANAL but) ISTM surveillance on corporate networks is a pretty wel=
l
> settled point of disagreement between US and EU legal precedent, which is=
 a
> tiny little branch of a great big fork in the way each jurisdiction
> approaches labor law and labor relations, and is at his point probably ju=
st
> one of those things organizations doing business on both sides of the pon=
d
> have to tolerate. Know you rights and responsibilities in the jurisdictio=
ns
> in which you operate, same as it ever was...
>
> > But in any case, there are many other forms of corporate
> > surveillance (e.g. kid's toys calling home to the manuf
> > for dodgy reasons) so I hope you'd agree that we don't
> > have to have 100% agreement about all of that to agree
> > that surveillance is not an issue that always involves a
> > government actor.
>
> This is something we *absolutely* need to engage with as a community.
> There's a very clear line between "I have copies of emails you send and
> receive on the corporate account" and "there's a camera in your bedroom
> sharing on-demand video with our marketing affiliates", and we can discus=
s
> how bad the second is without ratholing on the first.
>
> Indeed, I've been disappointed and perplexed that so much of the rhetoric
> around encryption post-Snowden (as epitomized by 7258) has focused
> exclusively on a nation-state or co-opted/evil large-network-operator
> attacker model, which is certainly a point of concern but not really wher=
e
> the biggest threat to collective privacy lies these days. I'm concerned
> that in our drive to Encrypt All The Things, absolutely the correct
> response when your only concern is a nation-state on the wire, we risk
> making it difficult to understand and defend against (what I'll call) the
> corporate-data-hording attacker model. To date, most of the evil toys
> phoning home and other such nastiness that I've heard of has been
> discoverable in part because said evil toys were using circumventable,
> crap, or no crypto.
>
> If we do our job well against attackers on the wire, we make the job of
> those "attackers" on the wire whose goal it is to discover and document
> corporate-data-hoarding attacks more difficult. In a world where all clie=
nt
> endpoints are using exclusively signed binaries on locked down systems wi=
th
> pinned certificates, it could become practically impossible.
>
> But that's probably a different thread on a different mailing list, and
> I'm not sure how to (or whether it's a good idea to) phrase that at ISOC
> mission statement level.
>
> Cheers,
>
> Brian
>

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

<div dir=3D"auto">Making the packets on the wire unprotected in order to fo=
il corporate data gathering doesn&#39;t help, though. I agree that this is =
a problem, but the solution has to be secure.=C2=A0</div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Nov 8, 2017 10:17, &quot;Brian T=
rammell (IETF)&quot; &lt;<a href=3D"mailto:ietf@trammell.ch">ietf@trammell.=
ch</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">hi=
 Stephen, Lee,<br>
<br>
&gt; On 7 Nov 2017, at 21:23, Stephen Farrell &lt;<a href=3D"mailto:stephen=
.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; Hi Lee,<br>
&gt;<br>
&gt; On 07/11/17 19:06, Lee Howard wrote:<br>
&gt;&gt; You have no right to =C3=A2=E2=82=AC=C5=93intimate privacy=C3=A2=
=E2=82=AC=C2=A0 at work on your company-owned<br>
&gt;&gt; computer on the company network on company time.<br>
&gt;<br>
&gt; First, I don&#39;t think there&#39;s any need to (nor liklihood of)<br=
>
&gt; reaching consensus as to the above. FWIW, I don&#39;t agree<br>
&gt; with you, and nor would various court judgements in some<br>
&gt; places in the world. I fully accept that your position is<br>
&gt; one shared by a bunch of folks though.<br>
<br>
Yeah, (IANAL but) ISTM surveillance on corporate networks is a pretty well =
settled point of disagreement between US and EU legal precedent, which is a=
 tiny little branch of a great big fork in the way each jurisdiction approa=
ches labor law and labor relations, and is at his point probably just one o=
f those things organizations doing business on both sides of the pond have =
to tolerate. Know you rights and responsibilities in the jurisdictions in w=
hich you operate, same as it ever was...<br>
<br>
&gt; But in any case, there are many other forms of corporate<br>
&gt; surveillance (e.g. kid&#39;s toys calling home to the manuf<br>
&gt; for dodgy reasons) so I hope you&#39;d agree that we don&#39;t<br>
&gt; have to have 100% agreement about all of that to agree<br>
&gt; that surveillance is not an issue that always involves a<br>
&gt; government actor.<br>
<br>
This is something we *absolutely* need to engage with as a community. There=
&#39;s a very clear line between &quot;I have copies of emails you send and=
 receive on the corporate account&quot; and &quot;there&#39;s a camera in y=
our bedroom sharing on-demand video with our marketing affiliates&quot;, an=
d we can discuss how bad the second is without ratholing on the first.<br>
<br>
Indeed, I&#39;ve been disappointed and perplexed that so much of the rhetor=
ic around encryption post-Snowden (as epitomized by 7258) has focused exclu=
sively on a nation-state or co-opted/evil large-network-operator attacker m=
odel, which is certainly a point of concern but not really where the bigges=
t threat to collective privacy lies these days. I&#39;m concerned that in o=
ur drive to Encrypt All The Things, absolutely the correct response when yo=
ur only concern is a nation-state on the wire, we risk making it difficult =
to understand and defend against (what I&#39;ll call) the corporate-data-ho=
rding attacker model. To date, most of the evil toys phoning home and other=
 such nastiness that I&#39;ve heard of has been discoverable in part becaus=
e said evil toys were using circumventable, crap, or no crypto.<br>
<br>
If we do our job well against attackers on the wire, we make the job of tho=
se &quot;attackers&quot; on the wire whose goal it is to discover and docum=
ent corporate-data-hoarding attacks more difficult. In a world where all cl=
ient endpoints are using exclusively signed binaries on locked down systems=
 with pinned certificates, it could become practically impossible.<br>
<br>
But that&#39;s probably a different thread on a different mailing list, and=
 I&#39;m not sure how to (or whether it&#39;s a good idea to) phrase that a=
t ISOC mission statement level.<br>
<br>
Cheers,<br>
<br>
Brian<br>
</blockquote></div></div>

--f403045d9c20742f3c055d75322d--


From nobody Wed Nov  8 01:27:40 2017
Return-Path: <ietf@trammell.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 214711318CC for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yFeiOxqCV0R9 for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:27:37 -0800 (PST)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08E8713188A for <ietf@ietf.org>; Wed,  8 Nov 2017 01:27:37 -0800 (PST)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id A3718340195; Wed,  8 Nov 2017 10:27:35 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/18338.10654); Wed,  8 Nov 2017 10:27:34 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed,  8 Nov 2017 10:27:34 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.5]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 35295233; Wed, 08 Nov 2017 10:27:33 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <9BD9905D-6906-40D5-8ED9-C83AC2F6EFD4@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_F88C09CA-7F6F-4F2C-9805-EBB418B1EA26"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Proposal to revise ISOC's mission statement
Date: Wed, 8 Nov 2017 10:27:32 +0100
In-Reply-To: <CAPt1N1=E-Pb2+YhGXk1HJfHwtVQAWahnxELBEdENi5u9NSPPDg@mail.gmail.com>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, james woodyatt <jhw@google.com>, IETF Discussion Mailing List <ietf@ietf.org>
To: Ted Lemon <mellon@fugue.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie> <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch> <CAPt1N1=E-Pb2+YhGXk1HJfHwtVQAWahnxELBEdENi5u9NSPPDg@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JYh8JipiHTYJHXwA6i9sftlXVBQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 09:27:39 -0000

--Apple-Mail=_F88C09CA-7F6F-4F2C-9805-EBB418B1EA26
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 8 Nov 2017, at 10:20, Ted Lemon <mellon@fugue.com> wrote:
>=20
> Making the packets on the wire unprotected in order to foil corporate =
data gathering doesn't help, though. I agree that this is a problem, but =
the solution has to be secure.

Agree completely. If I had a *solution* for this that I thought would =
work, I'd be proposing it. I'm simply raising the point that there's a =
tradeoff that the current discussions around the applicability and role =
of encryption in our protocols seem to me to be obscuring, and a threat =
model we're not paying adequate attention to.

Cheers,

Brian

> On Nov 8, 2017 10:17, "Brian Trammell (IETF)" <ietf@trammell.ch> =
wrote:
> hi Stephen, Lee,
>=20
> > On 7 Nov 2017, at 21:23, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> >
> >
> > Hi Lee,
> >
> > On 07/11/17 19:06, Lee Howard wrote:
> >> You have no right to =C3=A2=E2=82=AC=C5=93intimate privacy=C3=A2=E2=82=
=AC  at work on your company-owned
> >> computer on the company network on company time.
> >
> > First, I don't think there's any need to (nor liklihood of)
> > reaching consensus as to the above. FWIW, I don't agree
> > with you, and nor would various court judgements in some
> > places in the world. I fully accept that your position is
> > one shared by a bunch of folks though.
>=20
> Yeah, (IANAL but) ISTM surveillance on corporate networks is a pretty =
well settled point of disagreement between US and EU legal precedent, =
which is a tiny little branch of a great big fork in the way each =
jurisdiction approaches labor law and labor relations, and is at his =
point probably just one of those things organizations doing business on =
both sides of the pond have to tolerate. Know you rights and =
responsibilities in the jurisdictions in which you operate, same as it =
ever was...
>=20
> > But in any case, there are many other forms of corporate
> > surveillance (e.g. kid's toys calling home to the manuf
> > for dodgy reasons) so I hope you'd agree that we don't
> > have to have 100% agreement about all of that to agree
> > that surveillance is not an issue that always involves a
> > government actor.
>=20
> This is something we *absolutely* need to engage with as a community. =
There's a very clear line between "I have copies of emails you send and =
receive on the corporate account" and "there's a camera in your bedroom =
sharing on-demand video with our marketing affiliates", and we can =
discuss how bad the second is without ratholing on the first.
>=20
> Indeed, I've been disappointed and perplexed that so much of the =
rhetoric around encryption post-Snowden (as epitomized by 7258) has =
focused exclusively on a nation-state or co-opted/evil =
large-network-operator attacker model, which is certainly a point of =
concern but not really where the biggest threat to collective privacy =
lies these days. I'm concerned that in our drive to Encrypt All The =
Things, absolutely the correct response when your only concern is a =
nation-state on the wire, we risk making it difficult to understand and =
defend against (what I'll call) the corporate-data-hording attacker =
model. To date, most of the evil toys phoning home and other such =
nastiness that I've heard of has been discoverable in part because said =
evil toys were using circumventable, crap, or no crypto.
>=20
> If we do our job well against attackers on the wire, we make the job =
of those "attackers" on the wire whose goal it is to discover and =
document corporate-data-hoarding attacks more difficult. In a world =
where all client endpoints are using exclusively signed binaries on =
locked down systems with pinned certificates, it could become =
practically impossible.
>=20
> But that's probably a different thread on a different mailing list, =
and I'm not sure how to (or whether it's a good idea to) phrase that at =
ISOC mission statement level.
>=20
> Cheers,
>=20
> Brian


--Apple-Mail=_F88C09CA-7F6F-4F2C-9805-EBB418B1EA26
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-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAloCzgUACgkQihK3vwvq
RqPN9hAAttEiQWoIMNNxQau+480oaBw1uggkOsmDksuRrtNbCFBe1hABDSgRHWch
KzDxw1/WNUhfBGz7JcFdvllaIhljyqeBaBB4ODlERhlKq60B/xmgGvMwyQnM6v/T
f1GSCMCa0V9irDHmVKh9clLCpi7v06/AZoWd2f/lULCMqWa08zlNKCrggZYj0wB/
3L1auMpkygKeIXjpHyycL+wfKlHM9B7ILdrIuiFt8zlriCwy2fwPSVeksvT9uJtF
IGIKR2zCO4TmPDu3YlAdgWBAlp9KBORQ3wvHNqxCcMahrNzPdqNnxyDiHadVf/dC
Nvp/+F6Y543MVUr3XGhqUHxd09ctIkedqTw52fXn6oyygj6C790H1cvc9YDpfKpm
BUvYBMzHeGZfKk/ClZGc0LAL6GKGNAF8n++tSjEiGmJ0hJHiP0ZjoayNH5h2Thii
56H5iERJBk2/4ywb23K2BraWbvC+72g+PhoqBX2iF1TwmhbwEs/fWHqpRRWPsgmF
IAD+F8RdiqhqqN8q9fRgo7rdSnE6+rKCqeey3Qc2p/OJDowZeJeeGRVe9BDJkd6z
I4jFNuW0HaGqPRIA2mPfA8frT/uwqxxHplpE0DL0oTOdkMeT7YE+5LAbdshiEOHD
sA8arWkzlT0wIDqBDYARBMt+ROFK87Q3D6oL96VGjcs0annk9HU=
=KbXV
-----END PGP SIGNATURE-----

--Apple-Mail=_F88C09CA-7F6F-4F2C-9805-EBB418B1EA26--


From nobody Wed Nov  8 01:36:53 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 C481E1318C6 for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:36:51 -0800 (PST)
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, 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 e_wsq4AF8kHT for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 01:36:50 -0800 (PST)
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 D28E61318A9 for <ietf@ietf.org>; Wed,  8 Nov 2017 01:36:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 69831BE38; Wed,  8 Nov 2017 09:36:47 +0000 (GMT)
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 OMhiKIUwFJQM; Wed,  8 Nov 2017 09:36:46 +0000 (GMT)
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 0B3D6BE39; Wed,  8 Nov 2017 09:36:46 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1510133806; bh=IYvQmAJMJ7t2QNNEjB/5KecGv8PcSEeycO3rBKV7z6I=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=crQZlCmgPSIGIxSKS3RVAl12CXLfpmaPlAanwdR4juoKxT37FK+4hm3KEL7ANEc0d fKrshkcu4y4MCL+q59/rk+vZ9FGCn/2zq6UvqYVgkNoem74kXptN05PIGEIWCZQyTP 7Eo7x7oaynxKl/3SbmLTl+ZaaIuGg3FqrE+VMdjU=
Subject: Re: Proposal to revise ISOC's mission statement
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>, IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie> <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <1ba3b565-3bcf-2493-0f79-36ca3bf6a933@cs.tcd.ie>
Date: Wed, 8 Nov 2017 09:36:43 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="HH0D9Wn8verjXP12rrUm42d6m9fDA9U83"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WZ1zJ2CLTIefUbYcQaQ4e34ZXmc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 09:36:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--HH0D9Wn8verjXP12rrUm42d6m9fDA9U83
Content-Type: multipart/mixed; boundary="Untn8s8xQXlEVOKFk9enDjxg5gPmmE0d2";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>,
 IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <1ba3b565-3bcf-2493-0f79-36ca3bf6a933@cs.tcd.ie>
Subject: Re: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com>
 <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com>
 <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com>
 <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com>
 <6.2.5.6.2.20171029130937.113d0e80@elandnews.com>
 <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com>
 <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
 <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com>
 <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com>
 <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com>
 <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>
 <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
 <D6274256.8B776%lee@asgard.org>
 <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com>
 <D6277B2F.8B95A%lee@asgard.org>
 <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
 <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch>
In-Reply-To: <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch>

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



On 08/11/17 09:16, Brian Trammell (IETF) wrote:
> Indeed, I've been disappointed and perplexed that so much of the
> rhetoric around encryption post-Snowden (as epitomized by 7258) has
> focused exclusively on a nation-state=20

Ahem:-) 7258 says:

  "The
   motivation for PM can range from non-targeted nation-state
   surveillance, to legal but privacy-unfriendly purposes by commercial
   enterprises, to illegal actions by criminals. "

I think we got that right. I agree that there has been too little
focus put on the non-state actor cases.

> or co-opted/evil
> large-network-operator attacker model, which is certainly a point of
> concern but not really where the biggest threat to collective privacy
> lies these days. I'm concerned that in our drive to Encrypt All The
> Things, absolutely the correct response when your only concern is a
> nation-state on the wire, we risk making it difficult to understand
> and defend against (what I'll call) the corporate-data-hording
> attacker model. To date, most of the evil toys phoning home and other
> such nastiness that I've heard of has been discoverable in part
> because said evil toys were using circumventable, crap, or no
> crypto.

Yea, a different thread. I agree with Ted though, our job is partly
to ensure that the bits on the wire don't give the game away in all
cases. I'd also note that those exfiltrating data have plenty of
standard and non-standard tools available to try hide their actions
so us making standards such that exfiltration seems easier to spot
doesn't change the problem much for the exfiltrator.

So I don't agree that the tension here is between standard crypto
protocols and spotting exfiltration as the latter can be done via
stego or covert channels or other non crypto ways of hiding data.

The following may well work regardless of crypto: "I'll send you
the marketing slides, in one of which will be an image that you
can zoom until you can read the paper the actor is holding and on
that you'll find the secret formula":-)

I do however think it could be worthwhile someone documenting
the myriad ways in which exfiltration can be done or has been done
(esp. from home/enterprise networks) but I don't recall one of
those. Anyone know of a good survey that is not aiming to sell
some specific product/service?

But yes,

S.




--Untn8s8xQXlEVOKFk9enDjxg5gPmmE0d2--

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

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

iQEcBAEBCAAGBQJaAtAsAAoJEC88hzaAX42ijzAIAJyvIo/uRlZeXTZ/4b0r648B
5RqNuEq/gjXHxLogbY+k2AUZlqm9EUkkfx77kj1r6FKxKFBr2QMcYOQKGBu4Gk0b
7hxPAm16p6Lv8n3tpSZewEq4BtigJKJkWVPnJXFwM6XxCDd4SaJD1OoFdmSj6jJk
wFbqVNe7foIn0qtlXz9SMfs/i+ZkY+1mrXwGtWFZhjLLCp8WqGH+hyYMlBiTl/0D
BZcDpPQLC6WfyaR6PPLSL2XpSKkF82oO0iIQbSpbp0uquzvx4U1oGlnOGMpuhhr4
KgG9T4RXAPOZWuIA7eb3coXjmBeddy/biKQaQPGX57Ju8DoOfcOc0A1iABYXBUE=
=nvbr
-----END PGP SIGNATURE-----

--HH0D9Wn8verjXP12rrUm42d6m9fDA9U83--


From nobody Wed Nov  8 02:46:01 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 5408C1319EF for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 02:45:59 -0800 (PST)
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, 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 ewRFeJzzgMLa for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 02:45:56 -0800 (PST)
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 5E9151319F9 for <ietf@ietf.org>; Wed,  8 Nov 2017 02:45:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 2E2D6BE3E; Wed,  8 Nov 2017 10:45:53 +0000 (GMT)
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 M77_DSZQiuY0; Wed,  8 Nov 2017 10:45:53 +0000 (GMT)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D8882BE39; Wed,  8 Nov 2017 10:45:52 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1510137952; bh=RGR3k98wo8tkRy3r1OisXHK2dbMpDDNNKWG1Jr5Cw9E=; h=From:Subject:To:Cc:References:Date:In-Reply-To:From; b=gQh8MeRrfzMuTUdlNCzRJIvZIuwqWPi5Eqo3SMj1g6EyYljlGWx9PwRgGEQA4yByY 8p6q/zuyGQsTTyqtnsKfoJRyN9GPABfsB3r16Gum+KQseKVzvOzKP99hhiOBD5oTGW jj5O6XRB/WZLktjB5b4rXQr5wR6/YncTGvsAarF4=
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Proposal to revise ISOC's mission statement
To: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie> <D627F266.8B9C3%lee@asgard.org>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <f8742f2b-3cd3-ca2d-c4f1-dfd428dda3d4@cs.tcd.ie>
Date: Wed, 8 Nov 2017 10:45:51 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <D627F266.8B9C3%lee@asgard.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="VfCh3cFEuo3bqIIIaQFD4AtagVrB4lsWu"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ct2c0dNdDg4xUykZzLDVILBl7xg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 10:45:59 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--VfCh3cFEuo3bqIIIaQFD4AtagVrB4lsWu
Content-Type: multipart/mixed; boundary="35XRqHjMLmjvmODSDe5S0F3l8AhBScFUD";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Lee Howard <lee@asgard.org>, james woodyatt <jhw@google.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <f8742f2b-3cd3-ca2d-c4f1-dfd428dda3d4@cs.tcd.ie>
Subject: Re: Proposal to revise ISOC's mission statement
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com>
 <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com>
 <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com>
 <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com>
 <6.2.5.6.2.20171029130937.113d0e80@elandnews.com>
 <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com>
 <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
 <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com>
 <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com>
 <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com>
 <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com>
 <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie>
 <D6274256.8B776%lee@asgard.org>
 <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com>
 <D6277B2F.8B95A%lee@asgard.org>
 <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie>
 <D627F266.8B9C3%lee@asgard.org>
In-Reply-To: <D627F266.8B9C3%lee@asgard.org>

--35XRqHjMLmjvmODSDe5S0F3l8AhBScFUD
Content-Type: text/plain; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: quoted-printable



On 08/11/17 03:36, Lee Howard wrote:
> Out of curiosity, can you point me to courts that have found a right to=

> privacy where all three conditions existed (company device, company
> network, company time)?

First, IANAL etc. but I had a quick look.

There's the recent ECHR case, [1,2] (which I assume is the same as the
story behind the NYT paywall that Christian sent:-) On that one, I'd
not be surprised if advance notice is insufficient to allow employers
to try snarf everything - there's also a requirement for proportionality
that I'd bet will come back into play as we go along. There's a similar
sounding article about a Canadian case [3] as well. Our local data
protection commission guidance [4] also says similar things about not
being covert etc. And Germany as usual seems more protective of worker's
rights [5] saying a "concrete suspicion" is needed, for at least some
forms of monitoring, though that case involved a keylogger.

If I'm reading those right I think they all involve all 3 of your
conditions being satisfied and also all place further constraints on
what it's ok for employers to do.

Cheers,
S.


[1]
https://www.helpnetsecurity.com/2017/09/06/workplace-surveillance-privacy=
/
[2]
https://medium.com/@privacyint/privacy-international-response-to-grand-ch=
amber-of-the-european-court-for-human-rights-barbulescu-v-cc722b73086b
[3]
http://www.mondaq.com/canada/x/226944/Data+Protection+Privacy/Courts+Reco=
gnize+Employee+Privacy+Rights+In+Workplace
[4]
https://www.dataprotection.ie/docs/Guidance-Notes-Monitoring-of-Staff/m/2=
08.htm
[5]
https://www.hldataprotection.com/2017/08/articles/international-eu-privac=
y/new-case-law-on-restrictions-for-employee-monitoring-in-the-workplace-i=
n-germany/




--35XRqHjMLmjvmODSDe5S0F3l8AhBScFUD--

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

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

iQEcBAEBCAAGBQJaAuBgAAoJEC88hzaAX42icHMH/0vykeQVKFGRLc/SJW2mRIFD
uDNw6BavRc9seRq+lUOo7pU+xTQmY+UHEgq/Igj0EQyGIB6JgTMp5lo/E5PmI7DO
d+Z42i9Yf/mPU45QyoumbbW1fKvFZcYem8Abb7/KJz15QMHo5X/kt2LRv95pmqTU
0O6z9X/W63cU/xahG7JSyr7hOS/B7TAZ+hNCVxgUcYWqKvrBQECcC6FAS+2hyAWZ
KHzK2qnor8BupOtGZOYOQYLbso/II/9ki7CdbxnJrGeg8IpMME/hwU23AExEYjQP
D0VJs1a/oy3ONxrHAL2pum34QZukpuuCVntTFuKh5XJ3z75wA/UfRxTNsYnCPl0=
=/Fjq
-----END PGP SIGNATURE-----

--VfCh3cFEuo3bqIIIaQFD4AtagVrB4lsWu--


From nobody Wed Nov  8 03:19:48 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 CA191131972 for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 03:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tiEC1HIedxeu for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 03:19:45 -0800 (PST)
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 46C0C131962 for <ietf@ietf.org>; Wed,  8 Nov 2017 03:19:45 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eCOOL-0008RF-3z; Wed, 08 Nov 2017 11:19:33 +0000
Date: Wed, 08 Nov 2017 19:19:29 +0800
Message-ID: <m260al81by.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Cc: "Brian Trammell (IETF)" <ietf@trammell.ch>, james woodyatt <jhw@google.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Proposal to revise ISOC's mission statement
In-Reply-To: <1ba3b565-3bcf-2493-0f79-36ca3bf6a933@cs.tcd.ie>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie> <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch> <1ba3b565-3bcf-2493-0f79-36ca3bf6a933@cs.tcd.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 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/bhR6r1DGmDl86rxysfz2KDr1tGI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 11:19:47 -0000

> Ahem:-) 7258 says:
> 
>   "The motivation for PM can range from non-targeted nation-state
>    surveillance, to legal but privacy-unfriendly purposes by
>    commercial enterprises, to illegal actions by criminals. "
> 
> I think we got that right. I agree that there has been too little
> focus put on the non-state actor cases.

it is costing money/jobs.  the state actors are often costing lives.
e.g. for many, the tls 1.3 discussion is about people with guns at your
door at 3am.  we sell them both the guns and the spyware; a real market
opportunity.

bill's bait and sushi often controlls the employee's laptops, ... bill
has the hire and fire authority over the facility use.  this is a false
flag.

randy


From nobody Wed Nov  8 07:58:37 2017
Return-Path: <ietf@trammell.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 AE235127909 for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 07:58:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koG5auQraXlB for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 07:58:34 -0800 (PST)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C43CC127867 for <ietf@ietf.org>; Wed,  8 Nov 2017 07:58:33 -0800 (PST)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 8845A340D8E for <ietf@ietf.org>; Wed,  8 Nov 2017 16:58:32 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/18338.20933); Wed,  8 Nov 2017 16:58:32 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS for <ietf@ietf.org>; Wed,  8 Nov 2017 16:58:32 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.5]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 35350839 for ietf@ietf.org; Wed, 08 Nov 2017 16:58:28 +0100
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_3E58D28D-9152-44F6-B756-2801525F9CE8"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Technical Plenary Panel at IETF100: The Internet, a look forward: social, political, and technical perspectives
Message-Id: <76DE7C57-54FD-49AC-8474-9AE0E48BBFF0@trammell.ch>
Date: Wed, 8 Nov 2017 16:58:27 +0100
To: IETF Discussion Mailing List <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k-sL-EE0tmGdpgCglcF5PhQNgqk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 15:58:36 -0000

--Apple-Mail=_3E58D28D-9152-44F6-B756-2801525F9CE8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Greetings, all,

The Plenary Session at IETF 100 in Singapore  (Wednesday, 15 November =
2017, 17:10-19:40 Singapore time (UTC + 8)) includes a panel discussion, =
entitled:

The Internet, a look forward: Social, political, and technical =
perspectives

Adding a digit to count IETF meetings invites introspection and =
prognostication. For the IETF100 Plenary, three prominent strategists =
will share their unique perspectives on what the Internet will look like =
in thirty years. They will consider how the Internet=E2=80=99s influence =
on our lives and social systems will change, and how our influence on =
the Internet will also change, socially, politically, and technically.

I'll moderate the panel; the panelists include:

- Monique Morrow, President and Co-Founder of the Humanized Internet, a =
non-profit organization focused on providing digital identity for those =
individuals most under-served

- Jun Murai, Professor at Keio University with a research focus in =
global computer networking and communication, and known as the "Father =
of Japan=E2=80=99s Internet"

- Henning Schulzrinne, Professor in the Department of Electrical =
Engineering and chair of the Department of Computer Science at Columbia =
University, New York

The plenary will also include presentation of the Internet Society =
Jonathan B. Postel Service Award.

Cheers,

Brian (for the IAB and the Technical Plenary Planning Program)

--Apple-Mail=_3E58D28D-9152-44F6-B756-2801525F9CE8
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-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAloDKaMACgkQihK3vwvq
RqO+DQ//VzblBDO2+B8h96pcTinAH7ENizdl4MFqLjyZzlClEyPdGNX3k/6B+6yf
7pQEvq3ptBgPPZR8k68o+Wq3vbQcd3dW4fiRUPzFxYXqu+J+6IuB6XAfIt1gqlCA
STN3LvoolRb8uorFuYWrzqvHBlVzdqr9qvSlVNYgx/OpdNRAEVPn6NYPF1xxoZ96
5WaE/3dxQuh4M3pwZBDhV0S47QrNYQrJCqUz9kAGqxcckP/W/fmoslivQnIWbwWf
jr45Bfs5R3ULQK2wwz0NaE3SJOCEj8ftYIoveCcuhuOhTgDa1FcOvKHqrRD6uAu1
khD3W8y2McRZtF12r0doyBw483Y3BWehNTYfco1UzYMzuLfxrWCUVyrI9BgpCbKe
kHcOYZ7x9gAcfugcy6Qse3ep6l5YMwhmJ/IxUMByXRdXZeYy3uTi4ebPk63zmfGK
NHd3yeOX5GRpWeij61NWaOi1+jFVXKqG1Js1uFyPes2YMwN0e15Ij2yM9hPiiMO5
49b2jrZ9F9LsSRsnZgCBqlFRHHK/GsT6loyrGqWfCBkFeTa7sCM1buLc38loTT1q
Cj3cChBJP856+8YLlLJfNxBIa47COAlilLNNKWyeIF7iD7sJTxJOqiIZJtkJoQLa
Vpt9QmDHraagIMoERDFHDPS9PK/syBoHgAdYKf88Dp+5m3PpIYo=
=Yq/T
-----END PGP SIGNATURE-----

--Apple-Mail=_3E58D28D-9152-44F6-B756-2801525F9CE8--


From nobody Wed Nov  8 08:22:34 2017
Return-Path: <ietf@trammell.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 C633212878D for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 08:22:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OGkObj_-VnEn for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 08:22:30 -0800 (PST)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DB3D128768 for <ietf@ietf.org>; Wed,  8 Nov 2017 08:22:30 -0800 (PST)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 371A9340D88; Wed,  8 Nov 2017 17:22:29 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/18338.26655); Wed,  8 Nov 2017 17:22:29 +0100 (CET)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Wed,  8 Nov 2017 17:22:29 +0100 (CET)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.5]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 35354388; Wed, 08 Nov 2017 17:22:29 +0100
From: Brian Trammell (IETF) <ietf@trammell.ch>
Message-Id: <20264F85-19D3-4CFD-859E-5CF0978B45F2@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_212FE71A-1F59-4A20-AF3B-AF56B045B386"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: detecting exfiltration
Date: Wed, 8 Nov 2017 17:22:28 +0100
In-Reply-To: <1ba3b565-3bcf-2493-0f79-36ca3bf6a933@cs.tcd.ie>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, privsec-discuss@iab.org
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <37687bbf-4c06-0542-8efa-b3cd8a016c4a@network-heretics.com> <4450ac76-f3d4-96c7-7df6-bc424d9cfd3b@ericsson.com> <EBD240D1-A363-4237-BAFF-044987B0D760@network-heretics.com> <c62c4d03-abf8-d418-7097-7aaa3477a1ba@ericsson.com> <9edf410b-54dd-66a6-12f0-6b65cbe7a32a@cs.tcd.ie> <D6274256.8B776%lee@asgard.org> <55B7E8CA-A4E7-4A74-A10B-21FBD56DCFCF@google.com> <D6277B2F.8B95A%lee@asgard.org> <0d41ecbf-f0a8-d4d5-fdaf-94251d2cabaa@cs.tcd.ie> <88CBE84D-6BF8-4540-A7FF-FA1EF35E580C@trammell.ch> <1ba3b565-3bcf-2493-0f79-36ca3bf6a933@cs.tcd.ie>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EiNtyrFv8Fv4IuLmyOptzDG4RuQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 16:22:33 -0000

--Apple-Mail=_212FE71A-1F59-4A20-AF3B-AF56B045B386
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

hi Stephen,

trimming CC, proposing we move this to privsec-discuss to stop =
accumulating Narten points... :)

> On 8 Nov 2017, at 10:36, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
>=20
>=20
>=20
> On 08/11/17 09:16, Brian Trammell (IETF) wrote:
>> Indeed, I've been disappointed and perplexed that so much of the
>> rhetoric around encryption post-Snowden (as epitomized by 7258) has
>> focused exclusively on a nation-state
>=20
> Ahem:-) 7258 says:
>=20
>  "The
>   motivation for PM can range from non-targeted nation-state
>   surveillance, to legal but privacy-unfriendly purposes by commercial
>   enterprises, to illegal actions by criminals. "
>=20
> I think we got that right. I agree that there has been too little
> focus put on the non-state actor cases.

7258-the-document is fine. It's the simplification of the discussion =
following 7258 that I'm disappointed with.

>> or co-opted/evil
>> large-network-operator attacker model, which is certainly a point of
>> concern but not really where the biggest threat to collective privacy
>> lies these days. I'm concerned that in our drive to Encrypt All The
>> Things, absolutely the correct response when your only concern is a
>> nation-state on the wire, we risk making it difficult to understand
>> and defend against (what I'll call) the corporate-data-hording
>> attacker model. To date, most of the evil toys phoning home and other
>> such nastiness that I've heard of has been discoverable in part
>> because said evil toys were using circumventable, crap, or no
>> crypto.
>=20
> Yea, a different thread.

...here is that thread...

> I agree with Ted though, our job is partly
> to ensure that the bits on the wire don't give the game away in all
> cases. I'd also note that those exfiltrating data have plenty of
> standard and non-standard tools available to try hide their actions
> so us making standards such that exfiltration seems easier to spot
> doesn't change the problem much for the exfiltrator.
>=20
> So I don't agree that the tension here is between standard crypto
> protocols and spotting exfiltration as the latter can be done via
> stego or covert channels or other non crypto ways of hiding data.

There are two and a half exfiltration models here which are technically =
similar but operationally distinct, and it might make sense to tease =
them apart to see if that sheds some light on ways to approach this =
problem:

(1) Corporate exfil (your "marketing slides" example below). Here, in =
most cases, the data exfiltrated is stored on systems owned by the data =
owner, and is accessed using credentials issued by the data owner, =
usually by an employee, contractor, or other natural person =
intentionally given access to some of those systems, if not to the =
specific data owned. A lot of the "we need to see content" argument is =
based on this model. In any case, best practices in enterprise IT =
prescribe a defense-in-depth approach, with a network perimeter =
(currently with cleartext inspection, in the future hopefully without) =
as well as endpoint security on servers and clients, and there is an IT =
security department/organization with a clear responsibility to detect =
and prevent exfiltration. In this envrionment, we're probably already =
down the stego rathole, and as in most things human intelligence, though =
expensive and difficult, is the best way to prevent the insider threat.

=46rom a technical standpoint, in almost all of these cases, the =
exfiltration can *could* be detected on the endpoint, before it's sent, =
though to my knowledge most of the systems research in this space (doing =
things like trying to taint RAM, files, and sockets that *could have =
seen* information content derived from a given object) has results that =
cannot currently be made to apply to most practically usable systems. =
Trying to close the gap between theoretical and applicable in terms of =
endpoint exfil detection is certainly worth effort here.

(2) IoT exfil (a lazy characterization, but let's run with it for the =
headline potential). Here, the data exfiltrated is generated by a device =
owned by the data owner, but the data owner has no access to that data =
without exceptional means -- for these purposes I'm going to go ahead =
and make a stretch that the law hasn't universally yet, and say that =
pictures of you taken in your house by a teddybear you bought belong to =
you.

Most consumers don't have a corporate IT department behind them, so the =
defense now is some researcher notices that teddybear X is sending a =
*whole lot* of data to some AWS instance somewhere, hacks the crap =
crypto and figures out that, yeah, that's video of what the teddybear =
sees. There might be stego here already, too, but we wouldn't know about =
it without treating all IoT firmware as malware and analyzing it as =
such. Come to think of it, that might be a promising (if high-risk) =
career direction for young malware researchers.

(2.5) Platform/app exfil: stuff like apps keeping full mobility traces, =
even when the app isn't focused or the trace isn't necessary for the =
app's function. Here, you have a lot of the same properties as IoT =
exfil, with the caveat that the platform owner steps into the IT =
security management role. It can restrict apps' access to information =
through app store restrictions, API restrictions, and a system of =
permissions (though we all know how well that works in practice on =
Android) and user prompts ("do you want TrackMeEverywhere to see your =
location even when you aren't using it?"). This works better than (2) =
above as long as you have absolute trust in the platform, and decays to =
(2) above when you don't.

I think that (1) and (2/2.5) are fundamentally different beasts, in =
terms of who's doing the detecting and maybe in terms of how.

> The following may well work regardless of crypto: "I'll send you
> the marketing slides, in one of which will be an image that you
> can zoom until you can read the paper the actor is holding and on
> that you'll find the secret formula":-)
>=20
> I do however think it could be worthwhile someone documenting
> the myriad ways in which exfiltration can be done or has been done
> (esp. from home/enterprise networks) but I don't recall one of
> those. Anyone know of a good survey that is not aiming to sell
> some specific product/service?

Argh, no. Adding it to my list of things I'd like to have time to think =
more about.

Cheers,

Brian

--Apple-Mail=_212FE71A-1F59-4A20-AF3B-AF56B045B386
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-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAloDL0QACgkQihK3vwvq
RqPSsxAAgFfNJRJohKfUoyaO3Kq/7b1R5sLjjHsk6h00Rb6XxlTafyh5+eJtBek2
ckmtBS8MaQqRHpyR6qC1MoXMFOiTf5tSZc4cwFmL7FjQZpuUqNouyygfv+8KMdKv
mHa3a0KH6UcWwSZpeNP+8yQpMRDiMSInaBpg5rn/LeR7kwxLUBw5NRlJ6Qh/n4Lf
QXIG8TUlqeQ7e6ij7ficBKvAmn3HQYEzCa2PnMksUZWwq4jiq8a2/b63IeKMFyPF
bbn9rnO6iyUV/iCDNXFM9B36uO0AoEQ6w5eWeXIQWv+WjjC0TQr31409x9FVRyWn
8C7JXy/Jh+22PgGEHxV3OxdBRsJ5ZD26sayxy1cy5tNeW6O3eQPqsxya/6XYp9bO
lJt3NzRwvcPaF4Zo3Rc3l6vI09YhwdSXEBHR3HyzDjNO8/Xs7VYvZnDnDuvJkR/l
ce8PS+0sqaupDjlxcluR06/2VN3gC5offIdWN050hJW3HQjFmKifoWurU7GUOOzI
yjdNGfiqFJpf6W3b6we2VvI+Az/0U4pYHrPHfr6C/bXXfP1fxmBK6JRAAJ5WXLuU
D1peE2Zxu1ZAT2j1axD3JCiNib0HeVLDwZpCWWYBRxP5JsVzjRsGMzFfNN5fIv8J
4uHQyfTADiG5cvd2NO78Ea++GjHIDnX1qoHfqwkbOovm2ZCfN5s=
=qj/F
-----END PGP SIGNATURE-----

--Apple-Mail=_212FE71A-1F59-4A20-AF3B-AF56B045B386--


From nobody Wed Nov  8 12:07:41 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 02180129B9A for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 12:07:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.972
X-Spam-Level: *
X-Spam-Status: No, score=1.972 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, HTTPS_HTTP_MISMATCH=1.989, URI_HEX=1.122, URI_NOVOWEL=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 LRbYhdJZ0Nb2 for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 12:07:38 -0800 (PST)
Received: from thornhill.mtv.corp.google.com (unknown [IPv6:2620:0:1000:4200:6ace:bd71:da72:3b5f]) (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 3A3E0129B98 for <ietf@ietf.org>; Wed,  8 Nov 2017 12:07:38 -0800 (PST)
To: ietf@ietf.org
From: IAB Chair <iab-chair@iab.org>
Subject: Report from the IAB
Message-ID: <2efd7871-ec3a-8e91-3268-8bc764f0bf1e@iab.org>
Date: Wed, 8 Nov 2017 12:07:38 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------7BEE3A974559EB425AB1068F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L-DXMAdsW_jPia8ov0v6fK_5XJo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Nov 2017 20:07:40 -0000

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

Dear colleagues,

Continuing the tradition started by Andrew Sullivan, here is the IAB 
report to the community about our activities, submitted so thatyou 
can prepare topics you might want to discuss during the upcoming open 
mic time.  Of course, if you have issues you want to discuss by email, 
feel free to send your comments to architecture-discuss@iab.org 
<mailto:architecture-discuss@iab.org> (our public discussion list) or 
iab@iab.org <mailto:iab@iab.org> (to reach just the IAB).

The IAB has a few chartered roles. We confirm the appointments to 
theIESG and perform standards process oversight and handle appeals. 
Wealso perform architectural oversight (including appointing the 
IRTFChair), we manage the RFC series and the IETF's relationship 
withIANA, and we handle liaisons and appointments both to ISOC and 
toother organizations. We try to ensure that anything we do is part 
ofone of these areas of responsibility, and we try to make sure theseare 
all covered.

Here's what we've been doing since our last report at IETF 99.  You can 
find mention of each of these on the IAB pages 
at<https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org%26sa%3DD%26ust%3D1499729646369000%26usg%3DAFQjCNH6p-BoTNhGWeIQkBw_cwy1YOnsPQ&sa=D&ust=1510012353443000&usg=AFQjCNGl2c2LTG9wz-ya4ctlGcI9XWP9YQ>https://www.iab.org 
<https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org%26sa%3DD%26ust%3D1499729646369000%26usg%3DAFQjCNH6p-BoTNhGWeIQkBw_cwy1YOnsPQ&sa=D&ust=1510012353443000&usg=AFQjCNGl2c2LTG9wz-ya4ctlGcI9XWP9YQ> (where 
there's more background, too).

First, I’m happy to note that there were no appeals during this period.

Prior to IETF 99, the IAB formed a search committee to seek a successor 
for Nevil Brownlee as Independent Series Editor, as documented in RFC 
6548. There was a very strong field of candidates, to whom the IAB again 
extends its thanks.  In October, the IAB appointed Adrian Farrel, who 
will take up the role in February of 2018.

In August, the RSOC issued a request for proposals as part of the RFC 
Series Editor search, and it then reviewed the resulting candidates. 
  They recommended the reappointment of Heather Flanagan, and the IAB as 
a whole confirmed her for a new two year term in October.

Again in August, the IAB solicited community feedback on the four 
candidates who volunteered to serve on the ICANN NomCom.  In October, 
after reviewing the candidate statements and that feedback, the IAB 
appointed Ole Jacobsen to the role and thanked Tim Wicinski for his 
previous service.

The IAB is currently soliciting volunteers for the ICANN TLG; you can 
see the call for volunteers 
<https://www.google.com/url?q=https://www.iab.org/2017/11/01/volunteer-needed-for-icann-technical-liaison-group-2/%23more-9677&sa=D&ust=1510012353445000&usg=AFQjCNEEoEDGGnp5xy840e1mcV8wttgEHA>on 
the IAB web site.

We will also be issuing a call for volunteers to serve on the Internet 
Society’s Board of Trustees around the beginning of IETF 100.  As the 
Trustees are meeting in Singapore after IETF 100, there will be several 
members of the Board attending the IETF.  If you are interested in the 
work of the board, please reach out to the IAB or one of the current 
Trustees.


        DOCUMENTS

You can always find the documents the IAB has adopted and is 
workingonat<https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://datatracker.ietf.org/stream/iab%26sa%3DD%26ust%3D1499729646374000%26usg%3DAFQjCNE4d2eOp4YF2DvgK_chZ0M85l8JsA&sa=D&ust=1510012353446000&usg=AFQjCNE_YgrZSWSjabvos3nzAPtOGG1wHA>https://datatracker.ietf.org/stream/iab 
<https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://datatracker.ietf.org/stream/iab%26sa%3DD%26ust%3D1499729646374000%26usg%3DAFQjCNE4d2eOp4YF2DvgK_chZ0M85l8JsA&sa=D&ust=1510012353446000&usg=AFQjCNE_YgrZSWSjabvos3nzAPtOGG1wHA>.

One RFC has been published since the last report:

RFC 8240: Report from the Internet of Things Software Update (IoTSU) 
Workshop 2016 
<https://www.google.com/url?q=https://www.iab.org/2017/09/11/rfc-8240-on-report-from-the-internet-of-things-software-update-iotsu-workshop-2016/&sa=D&ust=1510012353447000&usg=AFQjCNHqj8f6Sh4QGSrOaH8knjjjMgQVoQ>

There are some workshop reports still in process:

draft-iab-marnew-report-00

     IAB Workshop on Managing Radio Networks in an Encrypted World

     (MaRNEW) Report (awaiting update after undergoing community review)


        PROGRAMS

The IAB organizes its work, for the most part, into programs.  Thereare 
basically two classes: management programs and architecturalprograms. 
  The former are how we handle the oversight of variousthings, and the 
latter are where we do architectural work.  The former

are expected to last as long as the IAB continues to have thatoversight 
function; the latter last until the IAB has come to aconclusion on the 
relevant group of topics or has decided that the topic needs to be 
reframed.  Programs are listed 
athttps://www.iab.org/activities/programs/ 
<https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org/activities/programs/%26sa%3DD%26ust%3D1499729646378000%26usg%3DAFQjCNGkKp8ztdI5msUBj1qAcMD9RRQ4gA&sa=D&ust=1510012353448000&usg=AFQjCNF2Lx67xPMLPWFjafLw0LcQD-FZ5g>. 
As a general rule, eacharchitectural program has a public mailing list, 
as well as amember-specific list.  For subscription instructions, 
seehttps://www.iab.org/iab-mailing-lists/ 
<https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org/iab-mailing-lists/%26sa%3DD%26ust%3D1499729646378000%26usg%3DAFQjCNFcbFJ8gHhtyvc1w38rdjpTVRdpow&sa=D&ust=1510012353449000&usg=AFQjCNH0BbpWi_Q7GNQUKhF57MPN_FPXLw>.

We review these programs periodically, and we will be reviewing the 
Privacy and Security program during the upcoming meeting.


        WORKSHOPS

In June, the IAB sent out a call for participation in a workshop on 
Internet naming systems that explicitly called out their resolution 
method or context 
<https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org/2017/06/22/call-for-participation-iab-workshop-on-explicit-internet-naming-systems/%26sa%3DD%26ust%3D1499729646380000%26usg%3DAFQjCNEQ9MMG6z1dlnmsl0zb3zR4HVK3zg&sa=D&ust=1510012353450000&usg=AFQjCNExrB87f7ngMZ81H2Ag0EhSqNBpxw>. 
  The workshop was held in October in Vancouver, Canada.  A blog post 
giving some early impressions 
<https://www.google.com/url?q=https://www.ietf.org/blog/2017/10/ename-workshop/&sa=D&ust=1510012353450000&usg=AFQjCNHhu9suxRXufc93TtNDjMCbIfqjrA> is 
available, and a workshop report will be available in due course.

Respectfully submitted,

Ted Hardie

for the IAB


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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div>
      <p><span>Dear colleagues,</span></p>
      <p><span></span></p>
      <p><span>Continuing the tradition started by Andrew Sullivan, here
          is the IAB report to the community about our activities,
          submitted so that</span><span> </span><span>you </span><span>can</span><span> prepare
          topics you might want to discuss during the upcoming open mic
          time.  Of course, if you have issues you want to discuss by
          email, feel free to send your comments to <a
            href="mailto:architecture-discuss@iab.org" target="_blank">architecture-discuss@iab.org</a>
          (our public discussion list) or <a href="mailto:iab@iab.org"
            target="_blank">iab@iab.org</a> (to reach just the IAB).</span></p>
      <p><span></span></p>
      <p><span>The IAB has a few chartered roles. We confirm the
          appointments to the</span><span> </span><span>IESG and perform
          standards process oversight and handle appeals. We</span><span> </span><span>also
          perform architectural oversight (including appointing the IRTF</span><span> </span><span>Chair),
          we manage the RFC series and the IETF's relationship with</span><span> </span><span>IANA,
          and we handle liaisons and appointments both to ISOC and to</span><span> </span><span>other
          organizations. We try to ensure that anything we do is part of</span><span> </span><span>one
          of these areas of responsibility, and we try to make sure
          these</span><span> </span><span>are all covered.</span></p>
      <p><span></span></p>
      <p><span>Here's what we've been doing since our last report at
          IETF 9</span><span>9</span><span>.  You can find mention of
          each of these on the IAB pages at</span><span><a
href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org%26sa%3DD%26ust%3D1499729646369000%26usg%3DAFQjCNH6p-BoTNhGWeIQkBw_cwy1YOnsPQ&amp;sa=D&amp;ust=1510012353443000&amp;usg=AFQjCNGl2c2LTG9wz-ya4ctlGcI9XWP9YQ"
            target="_blank"> </a></span><span><a
href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org%26sa%3DD%26ust%3D1499729646369000%26usg%3DAFQjCNH6p-BoTNhGWeIQkBw_cwy1YOnsPQ&amp;sa=D&amp;ust=1510012353443000&amp;usg=AFQjCNGl2c2LTG9wz-ya4ctlGcI9XWP9YQ"
            target="_blank">https://www.iab.org</a></span><span> (where
          there's more background, too).  </span></p>
      <p><span></span></p>
      <p><span>First, I’m happy to note that there were no appeals
          during this period.  </span></p>
      <p><span></span></p>
      <p><span>Prior to IETF 99, t</span><span>he IAB formed a search
          committee to seek a successor for Nevil Brownlee as
          Independent Series Editor, as documented in RFC 6548. </span><span> 
          There was a very strong field of candidates, to whom the IAB
          again extends its thanks.  In October, the IAB appointed
          Adrian Farrel, who will take up the role in February of 2018.</span></p>
      <p><span></span></p>
      <p><span>In August, the RSOC issued a request for proposals as
          part of the RFC Series Editor search, and it then reviewed the
          resulting candidates.  They recommended the reappointment of
          Heather Flanagan, and the IAB as a whole confirmed her for a
          new two year term in October.</span></p>
      <p><span></span></p>
      <p><span>Again in August, the IAB solicited community feedback on
          the four candidates who volunteered to serve on the ICANN
          NomCom.  In October, after reviewing the candidate statements
          and that feedback, the IAB appointed Ole Jacobsen to the role
          and thanked Tim Wicinski for his previous service.</span></p>
      <p><span></span></p>
      <p><span>The IAB is currently soliciting volunteers for the ICANN
          TLG; you can see </span><span><a
href="https://www.google.com/url?q=https://www.iab.org/2017/11/01/volunteer-needed-for-icann-technical-liaison-group-2/%23more-9677&amp;sa=D&amp;ust=1510012353445000&amp;usg=AFQjCNEEoEDGGnp5xy840e1mcV8wttgEHA"
            target="_blank">the call for volunteers </a></span><span>on
          the IAB web site. </span></p>
      <p><span></span></p>
      <p><span>We will also be issuing a call for volunteers to serve on
          the Internet Society’s Board of Trustees around the beginning
          of IETF 100.  As the Trustees are meeting in Singapore after
          IETF 100, there will be several members of the Board attending
          the IETF.  If you are interested in the work of the board,
          please reach out to the IAB or one of the current Trustees.</span></p>
      <h4><span>DOCUMENTS</span></h4>
      <p><span>You can always find the documents the IAB has adopted and
          is working</span><span> </span><span>on</span><span> </span><span>at</span><span><a
href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://datatracker.ietf.org/stream/iab%26sa%3DD%26ust%3D1499729646374000%26usg%3DAFQjCNE4d2eOp4YF2DvgK_chZ0M85l8JsA&amp;sa=D&amp;ust=1510012353446000&amp;usg=AFQjCNE_YgrZSWSjabvos3nzAPtOGG1wHA"
            target="_blank"> </a></span><span><a
href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://datatracker.ietf.org/stream/iab%26sa%3DD%26ust%3D1499729646374000%26usg%3DAFQjCNE4d2eOp4YF2DvgK_chZ0M85l8JsA&amp;sa=D&amp;ust=1510012353446000&amp;usg=AFQjCNE_YgrZSWSjabvos3nzAPtOGG1wHA"
            target="_blank">https://<wbr>datatracker.ietf.org/stream/<wbr>iab</a></span><span>.</span></p>
      <p><span></span></p>
      <p><span>One RFC has been </span><span>published since the last
          report:</span></p>
      <p><span><a
href="https://www.google.com/url?q=https://www.iab.org/2017/09/11/rfc-8240-on-report-from-the-internet-of-things-software-update-iotsu-workshop-2016/&amp;sa=D&amp;ust=1510012353447000&amp;usg=AFQjCNHqj8f6Sh4QGSrOaH8knjjjMgQVoQ"
            target="_blank">RFC 8240: Report from the Internet of Things
            Software Update (IoTSU) Workshop 2016</a></span></p>
      <p><span></span></p>
      <p><span></span></p>
      <p><span>There are some workshop reports still in process:</span></p>
      <p><span></span></p>
      <p><span>draft-iab-marnew-report-00</span></p>
      <p><span>    IAB Workshop on Managing Radio Networks in an
          Encrypted World</span></p>
      <p><span>    (MaRNEW) Report (awaiting update after undergoing
          community review)</span></p>
      <p><span></span></p>
      <h4><span></span><span>PROGRAMS</span></h4>
      <p><span></span></p>
      <p><span>The IAB organizes its work, for the most part, into
          programs.  There</span><span> </span><span>are basically two
          classes: management programs and architectural</span><span> </span><span>programs.
           The former are how we handle the oversight of various</span><span> </span><span>things,
          and the latter are where we do architectural work.  The former</span></p>
      <p><span>are expected to last as long as the IAB continues to have
          that</span><span> </span><span>oversight function; the latter
          last until the IAB has come to a</span><span> </span><span>conclusion
          on the relevant group of topics or has decided that the topic
          needs to be reframed.  Programs are listed at</span><span> </span><span><a
href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org/activities/programs/%26sa%3DD%26ust%3D1499729646378000%26usg%3DAFQjCNGkKp8ztdI5msUBj1qAcMD9RRQ4gA&amp;sa=D&amp;ust=1510012353448000&amp;usg=AFQjCNF2Lx67xPMLPWFjafLw0LcQD-FZ5g"
            target="_blank">https://www.iab.org/<wbr>activities/programs/</a></span><span>.
          As a general rule, each</span><span> </span><span>architectural
          program has a public mailing list, as well as a</span><span> </span><span>member-specific
          list.  For subscription instructions, see</span><span> </span><span><a
href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org/iab-mailing-lists/%26sa%3DD%26ust%3D1499729646378000%26usg%3DAFQjCNFcbFJ8gHhtyvc1w38rdjpTVRdpow&amp;sa=D&amp;ust=1510012353449000&amp;usg=AFQjCNH0BbpWi_Q7GNQUKhF57MPN_FPXLw"
            target="_blank">https://www.iab.org/iab-<wbr>mailing-lists/</a></span><span>.</span></p>
      <p><span></span></p>
      <p><span>We review these programs periodically</span><span>, and
          we will be reviewing the Privacy and Security program during
          the upcoming meeting.</span></p>
      <h4><span>WORKSHOPS</span></h4>
      <p><span>In June, the IAB sent out a call for participation in a </span><span><a
href="https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://www.iab.org/2017/06/22/call-for-participation-iab-workshop-on-explicit-internet-naming-systems/%26sa%3DD%26ust%3D1499729646380000%26usg%3DAFQjCNEQ9MMG6z1dlnmsl0zb3zR4HVK3zg&amp;sa=D&amp;ust=1510012353450000&amp;usg=AFQjCNExrB87f7ngMZ81H2Ag0EhSqNBpxw"
            target="_blank">workshop on Internet naming systems that
            explicitly called out their resolution method or context</a></span><span>.
           The workshop was held in October in Vancouver, Canada.  A
          blog post giving </span><span><a
href="https://www.google.com/url?q=https://www.ietf.org/blog/2017/10/ename-workshop/&amp;sa=D&amp;ust=1510012353450000&amp;usg=AFQjCNHhu9suxRXufc93TtNDjMCbIfqjrA"
            target="_blank">some early impressions</a></span><span> is
          available, and a workshop report will be available in due
          course.</span></p>
      <p><span></span></p>
      <p><span>Respectfully submitted,</span></p>
      <p><span></span></p>
      <p><span>Ted Hardie</span></p>
      <p><span>for the IAB</span></p>
    </div>
  </body>
</html>

--------------7BEE3A974559EB425AB1068F--


From nobody Wed Nov  8 20:49:04 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 6CDA812EB41 for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 20:49:02 -0800 (PST)
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=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 MKvNmLJTQD9M for <ietf@ietfa.amsl.com>; Wed,  8 Nov 2017 20:49:01 -0800 (PST)
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 69FD112E055 for <ietf@ietf.org>; Wed,  8 Nov 2017 20:49:01 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3yXW0B5fx5z3Vy; Thu,  9 Nov 2017 05:48:58 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1510202938; bh=OSmjU3M4+Z1CghM0iLgfvEW9h3ib7LJESaXg7wqKuzE=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=mhIzZX+XGu+jaKg6L8X11MfPmvoJvvudIubGX4D+qvkn5sWrUFNsNEqDxuhktOBdc fWfHnVdUiwTb0Kurb4MBRA3n3WbIz7CPqGXosqLkumYb+sKvLmPNtJIAL6wFH0sF63 KLQnA/aAwOZDsYaqmzpaai9BlOVl/+xxZPiEatxw=
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 P8P5e1mszKlh; Thu,  9 Nov 2017 05:48:57 +0100 (CET)
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,  9 Nov 2017 05:48:57 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 0383B62D29; Wed,  8 Nov 2017 23:48:56 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 0383B62D29
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id EF99240D35AF; Wed,  8 Nov 2017 23:48:56 -0500 (EST)
Date: Wed, 8 Nov 2017 23:48:56 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: IAB Chair <iab-chair@iab.org>
cc: ietf@ietf.org
Subject: Re: Report from the IAB
In-Reply-To: <2efd7871-ec3a-8e91-3268-8bc764f0bf1e@iab.org>
Message-ID: <alpine.LRH.2.21.1711082346340.18444@bofh.nohats.ca>
References: <2efd7871-ec3a-8e91-3268-8bc764f0bf1e@iab.org>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-15
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VATnamaODmXpmEVhmTy2g3vH6GA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Nov 2017 04:49:02 -0000

On Wed, 8 Nov 2017, IAB Chair wrote:

> Continuing the tradition started by Andrew Sullivan, here is the IAB report to the community about our activities,
> submitted so that you can prepare topics you might want to discuss during the upcoming open mic time.  Of course,
> if you have issues you want to discuss by email, feel free to send your comments to architecture-discuss@iab.org
> (our public discussion list) or iab@iab.org (to reach just the IAB).

Note the included links all redirect via google.com search links and my
mail client warns me it is full of maliciously looking links......

Paul


From nobody Thu Nov  9 01:29:01 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3279612ECF5 for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 01:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=YHygbJ4E; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=p3W73Ehu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1uHO2NNi8oXi for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 01:28:58 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 654CF1201F8 for <ietf@ietf.org>; Thu,  9 Nov 2017 01:28:58 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.226.54.205]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA99Sfe8017640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Nov 2017 01:28:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510219734; x=1510306134; bh=bqqJCGesWww2IVxEB7hL/nQO0nJ1XqOGP9pjQC4cElU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YHygbJ4E8nSUrCs87Nbv7fC3sLYiJ24XBcO6uhIB2vWKU5NeyOA5hHCNIHI2UoIH1 XY8j7TMnMSKIiqSTxCp51xp6C+OuMjyXGClbkgICS1Hxwsi3NjYjMfi52ghJL2o9AO XZ6QJOYg6BW5b4CnX8SnV0Gu7i4IOjsj8tgt/34o=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510219734; x=1510306134; i=@elandsys.com; bh=bqqJCGesWww2IVxEB7hL/nQO0nJ1XqOGP9pjQC4cElU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=p3W73EhufcmP/5MpylxuOVh5tOQuefaM4UeSyz3o3ZxHhO2/Hg2MGnDbZJ0SqxAgV Mvo2BwPCKjbnAfy8LZdzU1d9QQeRZ9buHQQjvMSY8BMGktQW2lfONJkhsG7K0EuP6a wOpJ3cX8K/k1MF3+Ge/2pDokmjgqBDf8Acee+V2I=
Message-Id: <6.2.5.6.2.20171109003151.10f38ce0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Nov 2017 01:27:07 -0800
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Proposal to revise ISOC's mission statement
Cc: Keith Moore <moore@network-heretics.com>
In-Reply-To: <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ovUgDrLokdBZa00yJbabHFo70Ew>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Nov 2017 09:28:59 -0000

Hi Gonzalo,
At 02:34 AM 06-11-2017, Gonzalo Camarillo wrote:
>With respect to capturing this in the mission statement, the proposed
>text reads as follows: The Internet as "a force for good in society".
>That sentence tries to capture the social benefits we are after (as
>opposed to just wanting connectivity for the sake of it, without any
>"higher" purpose).

The first four words in the second line also appear in the title of a 
book written by a spiritual leader.  What social benefits are being 
sought?  What about societal issues which are attributed to the Internet?

Regards,
S. Moonesamy 


From nobody Thu Nov  9 01:36:48 2017
Return-Path: <gonzalo.camarillo@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 CD62E1201F8 for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 01:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 WvqKmBuRjVIT for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 01:36:44 -0800 (PST)
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 135A512ECC0 for <ietf@ietf.org>; Thu,  9 Nov 2017 01:36:43 -0800 (PST)
X-AuditID: c1b4fb2d-fc3a89c00000268d-5e-5a0421aa7b0c
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.183.69]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id F3.60.09869.AA1240A5; Thu,  9 Nov 2017 10:36:42 +0100 (CET)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.69) with Microsoft SMTP Server (TLS) id 14.3.352.0; Thu, 9 Nov 2017 10:36:40 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=WH6P7h9eWtR+rtWE8RBafs/jNZbzIRf8rM/ibsKnd4k=; b=TThO5ImSVq79Ff9zTrsTKNweIBDTvhxxlM34EAkv+GvnMTfWvn7ouiiydZD66g13A5N6ugD7VhbnGz6IkgAV1D+pYv61yOG9/cxsQ6X4snEE10uM+2te2M4cXN0Yr3y0bihfivGx9EVmsN5q0m/CWU19XfpTD1smvIINda/1j9s=
Received: from [192.168.1.7] (37.136.86.88) by AM3PR07MB0632.eurprd07.prod.outlook.com (2a01:111:e400:8837::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.239.4; Thu, 9 Nov 2017 09:36:39 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: S Moonesamy <sm+ietf@elandsys.com>, <ietf@ietf.org>
CC: Keith Moore <moore@network-heretics.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <6.2.5.6.2.20171109003151.10f38ce0@elandnews.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <67861dfe-8768-f80a-d33f-fb2d904790d4@ericsson.com>
Date: Thu, 9 Nov 2017 17:36:34 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20171109003151.10f38ce0@elandnews.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR0301CA0014.eurprd03.prod.outlook.com (2603:10a6:3:76::24) To AM3PR07MB0632.eurprd07.prod.outlook.com (2a01:111:e400:8837::12)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 246f6ef1-9d71-4a13-17bd-08d527556155
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603249); SRVR:AM3PR07MB0632; 
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0632; 3:iPbQDVTE/sGt0fV0LcrACzqCskCPIxJ7mo8fUXuLgurt+9BGNjBNi0H8ZWl6BnRyoGTUNXX1sgCu9pBHlyE63qr/9l64l/NAOu9x5gAyDyhpYTw8mQjkH3JS24g01ec8xGejAq6iqTtjctr9/Ckb59nVBLVD0CZPtwQpmmeVmf14RFCD9lsIeKgTE4KCwMiK9PQDWGabDXfYzzuA4YBXQ6ul8/iZ7LdLfMcndswnO2s7OgI4KtOgdMr00kzDk6Dp; 25:BlRjUQiXQlNUbSn1KZthPSIOOMuyCHuI9AH05IkdfMaLrNSq/2N4xNpor1FQz15G7sujiyXPw1ZzFBD60D6I4xsQf3J5gtQgvlQaZrweem2g197k6i9ft0hgEUVwGyBlInIiRj8N/afM1EQNkUoR5dO/vWv13CM4IE8UMlvlsPEK1iYgZBhf6pQ9v2QPP6pLxQNI0sH0LXo7viUSZlyzPbWCXCGQSqy3wymi6cKkrZyrDloxVnvOBDgb3F11nENeqbrvUtBHKwMFcqfnyvTB+XADIAd4fATxnNy1w7G9En6qqnBokoMuubVsAo1HOxSg2lgOwIcJCIpOunLMqfYODw==; 31:oEgHng+u+MRjpxR430W/CgsJzMgeMci4wvlKZ9az2SU6Uso5oEyabp5T2A6hOWxoOl57Mq4t6xQV08TrD0TOWTQTRVmDhUiPgcAbPh9ZJJShTKbO35HMD1jLh+D1C9eTsUQLRfISXdzNeEB+SH99DXA9djW87GLtL0jWSt3ARL62kkJT+OxsxEUjd1wPjp0/A8+p5JbMjhzdIUzC+wkgkpHjvd0kpEBacfrxtuumD94=
X-MS-TrafficTypeDiagnostic: AM3PR07MB0632:
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0632; 20:fx+6jtYzxBwTjwLlpShjBdgJ8pFt/RE/c9q0IYNhI5p3nNYJHHXR010JHF0kPTFWjIXU7ZEL3jhNZEWHcxRaTP59lDRMJDHQZaYD/iObicrYLcM7EiwMBIEmkpgzT4M/d7pXHaOHJvJSNrT6zMN9WMm/rdnmq7OAKKyw9jYEFXQAYiPumVmCHixUA0tF6eArJZpuK4jQJZDHstMzHyTBBMFcqyNcHo7emymoiTf3ZluYkzgK2+Hm4w9giC9rWnIaKlznzCu5zu30JRLvV1NkIeVJau9SkfEYH9Ju44gF/kPkRTBpMj1J4UjX9QW/ekC1Llblu8AM6LDrNUtfW4RAR8keqzQHlHgdayFagq10txKwsqp4dPcm63e7rwoPEn2eZWyKPWLeU5w3pubK+QVyy8WSmr1zzUZrozokCi1zTC2be0PjP9tf81F1jvSfgxs/S2GFIxkNuVx688Z4PtKWsj87FT+7Vh8eW+iZFhchuniXcesRaGrvbPdzBmifl1Tb; 4:TWxEzpFK8T017eI0GcOUgbpDJsjEONBRNwBQyFmG5q9o38TTKeyb3WcDqPMSjqPnnJSZYb+F95JSd/m1cOjbvbZ4GEg7DXVK05Ls+81gTuyo815uJmJNG5ns2Wub2ZfgkKFLX/Ts7nJV9rWbzwqVnS9BOATxRPNZdv8GeyLW25CWJ4x9b3ySazJmocbn2SYUmVHPWqP6RTjlawAIzJ9M01WB2ZoWBc3l5iEzImDrZkTG+ot+lWhnljscX6CrCBCsKxR1mj9L5Yd0i4ctsuIYjQ==
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <AM3PR07MB0632CF60BC4D51A577AA07AA83570@AM3PR07MB0632.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(3231021)(100000703101)(100105400095)(6041248)(20161123558100)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM3PR07MB0632; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM3PR07MB0632; 
X-Forefront-PRVS: 0486A0CB86
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(6049001)(346002)(376002)(39860400002)(24454002)(199003)(377424004)(52164004)(189002)(305945005)(97736004)(5660300001)(53936002)(77096006)(93886005)(23676003)(6486002)(58126008)(53546010)(50466002)(16576012)(6666003)(66066001)(189998001)(3846002)(2906002)(7736002)(16526018)(8936002)(316002)(65956001)(65806001)(6116002)(4326008)(2870700001)(47776003)(2950100002)(478600001)(65826007)(229853002)(106356001)(68736007)(81156014)(64126003)(54356999)(76176999)(50986999)(31686004)(81166006)(117156002)(25786009)(36756003)(83506002)(33646002)(86362001)(31696002)(105586002)(6246003)(8676002)(101416001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB0632; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTNQUjA3TUIwNjMyOzIzOmhraDlvOHcrVS9jTmY2b2h3MzdTd0Y3VUJj?= =?utf-8?B?MXVLZFNCMExUWUp1U1NJTnZYNnhBVjk3VDZOajE4WkcvdVc5SmtsU0M5TjNk?= =?utf-8?B?ejJnZDdHczJWZktXalRxNi8wMTVJcGMvRXcxbGxyQUh2RHVSeGx3cHlLNitk?= =?utf-8?B?bkpxS053bmxUMkhwVmJha09vSVhDMjUzRm1GcjlEUW9IbldKNkpIeFpuaHdO?= =?utf-8?B?M0hEL2xzLzdHOTRpL1IwN3RibjlVYlFmMTNFNzVTaCt3MWJpL2M3ZE9UcUtW?= =?utf-8?B?dDRpMnE2U2NQaENEYUpIdWdZZzR0bHI4eUhrRnB0MUM1ZUYraE1Vak51WVNV?= =?utf-8?B?RE9iN2JrZGEzSGJibzNUTnROU2x6aVc5N2phdVlwZTBQU3VEelNtYjZVMHpv?= =?utf-8?B?bTJtZm5oSHdaSyt5L1pFU3JSRWtJMW5nSG4xLzJTdFV5R0NmREw0dUI3dnk3?= =?utf-8?B?VWg5aVJzMXVjTXRDbE9ydGNnRnBUbnNxVmpDYlF6N2tKaDFrRDMrZ3lncEJ0?= =?utf-8?B?bTNqNVhDdXg4M0IvaEdMWDlxTFkxcEJtVVFuZmp6RVdDcXNNYzV2cEQ2UzBt?= =?utf-8?B?QTJlOVVINVovd3ZyaWpRNnhDa2UzM0h4VDU5TnBJQnlOQmk1WnhzTkxUTmRN?= =?utf-8?B?TFdMdVdvc1doa3Y3YkVkdzRxNGFyeUEzSEVKRlhqQ0Zrd3hJVjZlRWE0Ukdp?= =?utf-8?B?ZkhLVm1VQWRObnZQUmFzOEtZMVdOSzBaNnVaM2Fhb3c5eUdDLzdvRy9tUlQ2?= =?utf-8?B?Mmg0czRoeTlBRzJLRFJFdTd2bzh0ZkQzS2xJdjJXRCtpYTkzdDE2dFJZeGtn?= =?utf-8?B?T0pJUjViYU8ralJ0YTY0bzl3WTdYMzBEemRtQmlWUjd3Z3JNRTNVQ1NaTGZl?= =?utf-8?B?dFcyUDlDYy9mVXdES0t2emdtUFk2NmlMeGlQc1BRN1Z5SHBxLzcvNXB6bElH?= =?utf-8?B?K3p4WmRXR3B3RnZYTTJNeVFaMm1hMDVnVGp2T04xaEFobHlLOXFSRFk4YVgw?= =?utf-8?B?RlhoUEhWNGJKeXlXMGJBMlZBMEdXTyt0OGNhM2FSVVdYWHIyTGZXWlM5SitQ?= =?utf-8?B?MWgySXFzbmgxRHZQK2txdlRra0pONjJDaVJDSFdNM3UzbWtETTRjQnpHWkZ2?= =?utf-8?B?YmRPQTN3TVFVSlZwdWwzdGZqSGlvTHZHK25JNDIxMjhkRE9nQnYwaDJPSHhP?= =?utf-8?B?clVUOU9CQytQaGZ3OS8zN2tFRnBKNGtveHBIS0E2alJjMmdISW84TC9DdTdC?= =?utf-8?B?aFZpVkM1Sk9JeWdPeDFGNzRBZTcxZE9HM3FQTWhyN2MwOWlXWnJva2R2eWVR?= =?utf-8?B?N0xIV1RId2xLby94RUIwdnl2NnAyS1hZN2JlTDNyMEpVajVzbGF3ZS9sWUtJ?= =?utf-8?B?TkRtSEJoQ200b0IwWm1zVDZ4cVBqZnBydDh1UUlaY01OOEZoR2U4QTFsR0Y2?= =?utf-8?B?NVhGeWR6UGNsTmZsUmtoMWNOWEthYkY4WGs1KytMMGw0M3NLVjVZSGxPRVlM?= =?utf-8?B?NDRGZ3d1ZFh1YTgwcjNMQ3krSUtUd1lKc0RRZEY3NHN3SHpjRkVLNXF6UGNZ?= =?utf-8?B?R0h0amR3elU0aDdrZXVGcVdoaGVzVGM5ZTUzSVAvUXZtMy9HNXkzL09tNVhX?= =?utf-8?B?SlUrVll1Y2ROWC80b1FlRmNWY2grV3VjL0dsRHArVlhnbWxINUJwaEZGT2l4?= =?utf-8?B?dkdHQ3Z6eTV5OG1obGQ2OTNOc0ZPZVE5OUxmNGQ2UzhZNVFBUWlwcjZtWjFO?= =?utf-8?B?Y1c4K002dEh1eDBkK2tJNHJnakZiaWU2SERsR2FWUnhMSnpzMzlKbTN6THZF?= =?utf-8?B?eUsvSUVzcHk2ZmR4MVV3YnNtanZGbHF4ek1EMXJZdElCd3dYRHlhZGZKaFB5?= =?utf-8?B?SFQ5bGkwODVjd09OajllbVBWZmJvaEtVNnVyc2liSk90S1M4ZlhRN01QbEsz?= =?utf-8?B?WkF2RHdUVEZ3PT0=?=
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0632; 6:ehba+1a/3yEqeQfqEF4TQ2azL24YAJL6RKl0SUmsKYrSw19Ny8LP7CHQQxM8iKxSHyk4UrSO5hTTNcoT8lRsPHZbb7TO5cnmNDDB4PT3AvyuzqcS1DQvoWB2+Swm4PpEIJ9bVPCDMFK5C+EGlhWjymDK9Tblp+W9W+10aL9JY/tbB54QldtZWtmZ5IKup+pF6Pm18jlyM1L6REF3tFWwU8hp1hnRd/QXt9YpEd9AIo/QdT6DkUyEBtUPtXXA5BWBVXG/uFcWQCOPMl2Yfz/xrGfluxZcYc9uMmXcrzeTGIl7zwStB5L7KsOGV/AljAmCW2snUydTkCPE3i1t6p/DHh1ATco45naGuniQWFLWP/Y=; 5:lU+Tv5r9GYpMUDz5KbYC1JaJwsYn78Y5X7wLR7/4d0zDRhi40CHXPotSNzBsG9fs0WVG1KoexkQFAkVa7mIlbXx/HCaHFo4Dso4jKZxtEUb8bNF72O9Rzz/zhm0r1yyc8BOo73MWV7NNQ7Aw7nhGEvgxAioNPkDqbB22QtElUnI=; 24:5+63DZ32IhfVRcmlN1MvNpC1TsbOJMYA73ZjlnFYbfki8QLXv7QTk6f+O7Gq2vKASr/Sf7A4dqodxK603kiV3p/6mvgFdIaq7jawMn3dI88=; 7:28Q4nBJeveITJz6lLya+P8HtO7hloBcPB2Cesc8EsnaWyD+k+xh0em/R5zq92OfYwtmCActG45PY/G2vn1Rk8u9Use38aUUQow9YcCwvjcqnSPN8QKSqCXlajC6yN8Avr1Yz1aILeGujE9+rPiQr747swPazVYB5i8Yr/Xho7m4V55yvqWCLn9hWrmlHGlnvqV+M2dNYjJQXJ92Fvt9RkzLFV/ce37txuhbgsAuNx2YUu837169XXJNhyz6oGU+4
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Nov 2017 09:36:39.7869 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 246f6ef1-9d71-4a13-17bd-08d527556155
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB0632
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42KZGbHdVXeVIkuUwZFHYhbPNs5nsZj09Ryb xav+m6wOzB733nxk8liy5CeTx6QTYQHMUVw2Kak5mWWpRfp2CVwZ7z+XFCxgrzi99i9LA+Nj 1i5GTg4JAROJLfdfAdlcHEIChxklri/5zgThHGeUWPKzgR3EYRHoZZa4+/oDI0SmlUli+c29 jCD9wgIWEg8u/AObJSJgLrHx7jM2EJtZQEdi+sPN7CC2kMBpZokjX9VBbDag+i237rOA2LwC 9hIrl3wEq2ERUJGY9OItWFxUIEZi4oOLjBA1ghInZz4Bi3MK2Em0TFwBFOcAmq8psX6XPsQq cYlbT+YzQdjyEs1bZzNDvKYgsf/HSjaQmyUEZjJKXHnzhgniHm2J5c9aWCCKZCWOnp0DZftK fFl4hxGu4cDH3ewQTgO7xNonSxghqrQkPl3qghp7gU1ixdKJrDCJdVc/Qu3OlpiwaTITRNEV VomNLw9DdctIfNl1DmrfP1aJT/8SJzDqzELy6iyE92YheW8WkvcWMLKsYhQtTi0uzk03MtZL LcpMLi7Oz9PLSy3ZxAhMJQe3/Nbdwbj6teMhRgEORiUe3ueMLFFCrIllxZW5hxglOJiVRHhF 3jJHCfGmJFZWpRblxxeV5qQWH2KU5mBREud12HchQkggPbEkNTs1tSC1CCbLxMEp1cAoMX9u /WV3kZ9mLzIXmrV2PJPbxJW2+OHvSi6v4hmfCjNLlwQnOYmeVW/Ynj/XcjJDwakfc/dyqmVf Kt5Wm/Z43qxquduB3nL3yrrFS6zX3OyV/qvbeLWb8bj2F2/7V3scI8zWsa42VrQ5dz5f7oNv M5Nfj/6F8OATQi2XP27ZuS9cVN5qmacSS3FGoqEWc1FxIgDDiGWgIQMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xEB6NvGqbBns_4aiSdG6rE8qbgI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Nov 2017 09:36:46 -0000

Hi,

ISOC does a lot of so-called development work in different communities.
In our last board meeting in Kenya, for instance, we saw a few examples
of improvements in communities as a result of getting connected.

Cheers,

Gonzalo

On 09/11/2017 5:27 PM, S Moonesamy wrote:
> Hi Gonzalo,
> At 02:34 AM 06-11-2017, Gonzalo Camarillo wrote:
>> With respect to capturing this in the mission statement, the proposed
>> text reads as follows: The Internet as "a force for good in society".
>> That sentence tries to capture the social benefits we are after (as
>> opposed to just wanting connectivity for the sake of it, without any
>> "higher" purpose).
> 
> The first four words in the second line also appear in the title of a
> book written by a spiritual leader.  What social benefits are being
> sought?  What about societal issues which are attributed to the Internet?
> 
> Regards,
> S. Moonesamy


From nobody Thu Nov  9 11:19:20 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 8ACB512954E for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 11:19:19 -0800 (PST)
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 fVTkEL1J2Yk2 for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 11:19:17 -0800 (PST)
Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::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 19CAC129557 for <ietf@ietf.org>; Thu,  9 Nov 2017 11:19:16 -0800 (PST)
Received: by mail-pf0-x22b.google.com with SMTP id d28so4952582pfe.2 for <ietf@ietf.org>; Thu, 09 Nov 2017 11:19:16 -0800 (PST)
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-language:content-transfer-encoding; bh=NNjTdVyO083Y+3cr62mj+CiOUBBc8dDxWby2zwqDoEY=; b=nsoKzkinaKOYxBTjTQlS0W3wiNoZDlMIplOxKrqu9sOvq+UOxOlL85UnmScsYu/oIk O2+QUp090ltOFkW1MvxVqJ24FyIS3H6GFc/4T+IxY3vEpvO8FobrcCUbwjni2+ufLEEc 9vPkZ0SULl7lG8HH/PiL7Uh7TtdA4h9WmxGhLU4HhU1RP3qlp1Zjx/4SUk2mTXPo/eaH P7JzBddgeyO/ICPXCh/be2/tXbmqUTA1w1vTZKoaBp80OwBY3Z5sCbzkThM960sVj6gS S5thlGs5VJ/dULtD3lU97u69S3AZ7IHK41vgqvG3ijvJthfua/lZenAgifCvNJW8HZsm iEGw==
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-language:content-transfer-encoding; bh=NNjTdVyO083Y+3cr62mj+CiOUBBc8dDxWby2zwqDoEY=; b=EB4RNP4sSA+hyvSkr9igsPexVjOZSKekpxUpQ6gD6BkyTLcf0UbTLKcYsgvq5WP4Ge 4UKrkP5O2pOlqL8jxnkOqzDScjPa26Sd3Jk5eT0kLOYqQeTwf9KFbFZv5RE1bVeIhNWl gcwGCYZAKAFwV5LwdZ4hYACx/qHu7HtwV/N+p9/uKlaTo+3G1y3Dc9NamEFY4eyEHMGm UJwFJZqr2an7M8DGL+9EAg1n/XJwTRso0IUh3nI+Beem/gvJl6thQ+h9PvVeoupyHuF7 jvGFjrMmXWf1smy7Ql75IRlCZoqPx66qGzdyJoWi5q5iymy50JSInYkNm0zoifqRAm4Q JgqQ==
X-Gm-Message-State: AJaThX5wFyJJh/5C74tFutIPmc1hZVo6UX0QKDquupRZRKUAblTRPcE1 GxNZ8T2zdX1ZHMIKLqk+4czY7g==
X-Google-Smtp-Source: ABhQp+QAif6N6SfAm2lqtUNVAZgf8gvaD9NQx9py5jYZZNtPvM8Hn13Q9q5M7BRAU14szsWaJhlPrQ==
X-Received: by 10.101.81.197 with SMTP id i5mr1458219pgq.260.1510255156270; Thu, 09 Nov 2017 11:19:16 -0800 (PST)
Received: from ?IPv6:2406:e001:3d21:1:28cc:dc4c:9703:6781? ([2406:e001:3d21:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id j1sm15230740pfj.108.2017.11.09.11.19.14 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2017 11:19:15 -0800 (PST)
Subject: Re: IETF Journal - November 2017
To: IETF discussion list <ietf@ietf.org>
References: <0D.4C.42155.96C740A5@mta3>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com>
Date: Fri, 10 Nov 2017 08:19:21 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <0D.4C.42155.96C740A5@mta3>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Pf4comXdft0ZyBsESdpb2agDBLk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Nov 2017 19:19:19 -0000

Hi,

I read in this issue that:

>  We look forward to closing our print version and launching ourselves fully into the digital world in 2018.

However, BCP 9/RFC 2026 section 6.1.3 states that:

>    An official summary of standards actions completed and pending shall
>    appear in each issue of the Internet Society's newsletter.  This
>    shall constitute the "publication of record" for Internet standards
>    actions.

When the IETF Journal started, it took over as the medium for this requirement.
Are we happy that this will become an on-line only publication?

Also - the latest issue is already in breach of this requirement; I can't see
the summary of standards actions anywhere. It used to be at the back.
When was this dropped?

(I don't really think that "IESG Protocol and Document Actions: 57" satisfies
the intent of RFC 2026!)

If we don't think such a summary is needed any more, we need to publish yet
another small update to RFC 2026, similar to RFC 7100.

Regards
   Brian Carpenter


From nobody Thu Nov  9 11:38:44 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F2BC129AF2 for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 11:38:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.39
X-Spam-Level: 
X-Spam-Status: No, score=-0.39 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, 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=opendkim.org header.b=B7WSrShY; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=eFBRjmYT
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C86MXGOQDF6Y for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 11:38:41 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7989E129AF9 for <ietf@ietf.org>; Thu,  9 Nov 2017 11:38:41 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.86.160]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vA9JcOol016772 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Nov 2017 11:38:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510256316; x=1510342716; bh=PI4ne3D8X+UkRxuU6l/6hUCzdgke+BruA55eUvDf/dY=; h=Date:To:From:Subject:In-Reply-To:References; b=B7WSrShYYATvH7/5zfZpwC/MMZTQ9ON7243/LtCgJ/xhrTd8C+1nBB7rSs01VvXPW d17BpCHbxD9sWJbO2oxJSqrbH9ngBKXCPk0i0FeMV/xuQm0AYVJi7lhsRJ4pU9lgb4 emuxou+m1ItLtvocqYJMPkbc6y6QGqsdKvi3cZqI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510256316; x=1510342716; i=@elandsys.com; bh=PI4ne3D8X+UkRxuU6l/6hUCzdgke+BruA55eUvDf/dY=; h=Date:To:From:Subject:In-Reply-To:References; b=eFBRjmYTuYjPCSzYeHDIJqUCEOt3+SWljBg9rgfoz5gnX1fXiqyj+EOppCsSJunCM 8DuL/prcEOgi8Kd5GNRcod9FE2kGb7e8RTcW3tquwczoawTcjnoCJd5FP90Fsj/i7I hdjaCMv10yCb5OVLdRm8bWU7TUyvLRjiN5rZrxQk=
Message-Id: <6.2.5.6.2.20171109113527.12107a68@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Nov 2017 11:38:09 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF Journal - November 2017
In-Reply-To: <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com>
References: <0D.4C.42155.96C740A5@mta3> <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ywh1PUUwNGa_p26vccbCSdsKJ-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: Thu, 09 Nov 2017 19:38:42 -0000

Hi Brian,
At 11:19 AM 09-11-2017, Brian E Carpenter wrote:
>I read in this issue that:
>
> >  We look forward to closing our print version and launching 
> ourselves fully into the digital world in 2018.
>
>However, BCP 9/RFC 2026 section 6.1.3 states that:
>
> >    An official summary of standards actions completed and pending shall
> >    appear in each issue of the Internet Society's newsletter.  This
> >    shall constitute the "publication of record" for Internet standards
> >    actions.
>
>When the IETF Journal started, it took over as the medium for this 
>requirement.
>Are we happy that this will become an on-line only publication?

The matter was discussed during the RFC 7100 discussion.  Section 
6.1.3 was removed from RFC 2026.

Regards,
S. Moonesamy 


From nobody Thu Nov  9 12:41:23 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 7D2F1129B5C for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 12:41:21 -0800 (PST)
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 XYm0nhh06tip for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 12:41:20 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::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 EB84F124D37 for <ietf@ietf.org>; Thu,  9 Nov 2017 12:41:19 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id 207so2842432pgc.12 for <ietf@ietf.org>; Thu, 09 Nov 2017 12:41:19 -0800 (PST)
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-language:content-transfer-encoding; bh=8aH6jhOtmzjWch/E6V2uiN9u5SxkmkAfuLDgZ5jNPXc=; b=FfTDDKYbdg4rzb9+OYidRmpUjgpGd5kiACWru2FRF0FQCYPoZC91Aw+leeaaKAarmM 8q9qZfzdOhGtfBSvAeoBEKKgYrB44lxfF2vFBFXt9M/0+DwTzjOTvFWX0YKowz4xifM8 rZPkvSqX1v4hgQ8cvsfZmtkT8b1VHNHQflAu++Ms+90X+MFGdmLg/Rm/u4FcQeB09Dja z7+fPmxfHo7WzXpGAT2jCBa0Tk//6wm3HkCPYT56pzlInR+4CUgXD0x/QGGG7pd/6HzU sMyuzG/5+DrFqTVxKt0s6BX3+7aqPcxh6skc9XFtSn4WmUKw9/mZSKSobXYeJVCGKe6x lZJw==
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-language:content-transfer-encoding; bh=8aH6jhOtmzjWch/E6V2uiN9u5SxkmkAfuLDgZ5jNPXc=; b=hx7pGJiFZTF51sQ6Zwe2QGX10OopdGf1MnZcBLavhmob/KywTNPkAuzq/C7RvaQUga BP7DdMAzGeiF93kHzPQZ+YsefoBTHbJDFXC+pkSn2m6jIkZoy4+7oD52owTs8UC87RCS bOizB9Z9OmBWCblLm5PG+7m8+U/9/OCQXmCBWrkZvaZ55jnSTOtk9I3WnQAt2ZDoxyLW Nlx/zOEFRYc2vVrLxzYhhICi+ZZFzXgyh2Tup02d63zwy56uCitn2J/RDWhPT2QkRHWs 4Uyk7G0vFuK24WZV0n/miiI/4zT//c+SsVZy0uXHXb2TGrDrxLg58FHhCvHNzcd+rXmY iFeQ==
X-Gm-Message-State: AJaThX7jmKOIhaiHV4/lNeth6WdPUC49zfArXhrSjTSjo7mG7kEu3qyl PqF2kRLk4WZOqnxiFp2iV9aInA==
X-Google-Smtp-Source: ABhQp+SpAji4mbMchuuE6EmyTBCl/mqi+aD3C3IxARelOyCmRGe/dPdkYNIXoo7KpQf5KSFKfD38Aw==
X-Received: by 10.84.139.129 with SMTP id 1mr1636183plr.167.1510260079161; Thu, 09 Nov 2017 12:41:19 -0800 (PST)
Received: from ?IPv6:2406:e001:3d21:1:28cc:dc4c:9703:6781? ([2406:e001:3d21:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id d23sm10810727pfk.106.2017.11.09.12.41.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2017 12:41:18 -0800 (PST)
Subject: Re: IETF Journal - November 2017
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
References: <0D.4C.42155.96C740A5@mta3> <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com> <6.2.5.6.2.20171109113527.12107a68@elandnews.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <945229cd-f341-0600-d0e9-438549d7b2aa@gmail.com>
Date: Fri, 10 Nov 2017 09:41:23 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20171109113527.12107a68@elandnews.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fBWz_TK3zeOnpRmcshjuVUfQWK4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Nov 2017 20:41:21 -0000

Ah, silly me, I missed that bit in 7100. More coffee needed, apparently.

Thanks
   Brian

On 10/11/2017 08:38, S Moonesamy wrote:
> Hi Brian,
> At 11:19 AM 09-11-2017, Brian E Carpenter wrote:
>> I read in this issue that:
>>
>>>  We look forward to closing our print version and launching 
>> ourselves fully into the digital world in 2018.
>>
>> However, BCP 9/RFC 2026 section 6.1.3 states that:
>>
>>>    An official summary of standards actions completed and pending shall
>>>    appear in each issue of the Internet Society's newsletter.  This
>>>    shall constitute the "publication of record" for Internet standards
>>>    actions.
>>
>> When the IETF Journal started, it took over as the medium for this 
>> requirement.
>> Are we happy that this will become an on-line only publication?
> 
> The matter was discussed during the RFC 7100 discussion.  Section 
> 6.1.3 was removed from RFC 2026.
> 
> Regards,
> S. Moonesamy 
> 
> 


From nobody Thu Nov  9 13:03: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 BD924129B6C for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 13:03:02 -0800 (PST)
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 cF_M92jCKOKx for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 13:03:01 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 47FD8129B65 for <ietf@ietf.org>; Thu,  9 Nov 2017 13:03:01 -0800 (PST)
Received: (qmail 90054 invoked from network); 9 Nov 2017 21:02:59 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 9 Nov 2017 21:02:59 -0000
Date: 9 Nov 2017 21:02:37 -0000
Message-ID: <20171109210237.4601.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: paperless journals, was IETF Journal - November 2017
In-Reply-To: <46991942-1e08-cb7a-3777-4cb4f11ff0fb@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/KbZuNQRfnTptETx3U2vKKqUlSxE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Nov 2017 21:03:03 -0000

In article <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com> you write:
>>  We look forward to closing our print version and launching ourselves fully into the digital world in 2018.
>
>However, BCP 9/RFC 2026 section 6.1.3 states that:
>
>>    An official summary of standards actions completed and pending shall
>>    appear in each issue of the Internet Society's newsletter.  This
>>    shall constitute the "publication of record" for Internet standards
>>    actions.
>
>When the IETF Journal started, it took over as the medium for this requirement.
>Are we happy that this will become an on-line only publication?

Do any libraries actually keep paper newsletters any more?

Down the road at Cornell University which has a well regarded
engineering school, they closed the engineering library, moved the
paper books to the storage annex, and the space is now a largely
book-free reading room.  It has public wifi which is on the Cornell
network so you get access to all of the online material to which
Cornell subscribes.  Even when all the books were there, I spent far
more time looking at online material than at the old paper journals.

R's,
John


From nobody Thu Nov  9 14:48:15 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 17625127ABE for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 14:48:13 -0800 (PST)
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 YDdpeD3OOYHT for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 14:48:11 -0800 (PST)
Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::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 7EF661279EB for <ietf@ietf.org>; Thu,  9 Nov 2017 14:48:11 -0800 (PST)
Received: by mail-pg0-x22a.google.com with SMTP id s75so5905993pgs.0 for <ietf@ietf.org>; Thu, 09 Nov 2017 14:48:11 -0800 (PST)
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-language:content-transfer-encoding; bh=E+VTkrGNzVTO8g6hXzX+YjkGFZxJHxhUMkFCLd8ZjwE=; b=s+AtY/3qKGM2HhstkSEu1K/tWZsI4+D11o9QDIV8QgPra69Gcry+ci+mE9gu07/eis TMtTIFRGeNOZXM54QrFlqmGkyEP2LeKAVlNn4fWdOm9+RFTNMcnBzlL+tO/Z3pSYLfXX Q9zlVrFhjHmkYEsaq/46uuYc9cIV2VqHIn7v+SpOT9/fTkOstC9hfOqB/S1jYuOy2ey8 jv8CuudOhV0C74MwICHrZ6LHttIp2YwdnHsngHQZ/0gWuvWww3OxazkO3BI4oCF2JOwQ CYOtGkCEAbryQxqZ5fCIeR8Tvig0b50Jmysobxa3362r4XrhJObx8ew/vKtU3PMQDpkl IzYg==
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-language:content-transfer-encoding; bh=E+VTkrGNzVTO8g6hXzX+YjkGFZxJHxhUMkFCLd8ZjwE=; b=KvIWx+yD9aG/8nlS5E28DY/gKH3umyAoXetn1Brr3DY1fuaHICJYHdqQpKblJ+0An/ bpamaYp8EYafonKxY1lWbSOTFro4OxCxnB1gtNMeePFMt7gt9N6hF5TLub/BBHZOMd4I TH8/XHw4EUCH6s8JoMSqkc6QfGxBC545lwXjzh1w6wG3kZ5b6YIwC/XxIRrHzKbMyB9q KUcLtVt07D3lETyCcjsNfITTgCyQVF11zh6SZydJF6oFn8Ru9j7LG1D4NwEFw4oXWbV9 2n+5xAXbrSFcDJoms3hHy2ujsHqlyW4Tx5gmme7ip3/ZTO2Mvk8bSj+fXQ6eivdKyfqL Tupw==
X-Gm-Message-State: AJaThX5OT1MO4CKZCC+OuVYIB0kFhU5NoHh6cGb83tSB5ILMbAJ57M2x g5xbzYDie9uRs+O3gZD68+4d9g==
X-Google-Smtp-Source: ABhQp+RurBk3PWcGpw0EJHlgKSDmSxXq4/1wVtbsePe+xKjdU1KGw49Q01IBykF4ce49Tf4/CZSBpw==
X-Received: by 10.99.189.65 with SMTP id d1mr2028448pgp.48.1510267690588; Thu, 09 Nov 2017 14:48:10 -0800 (PST)
Received: from ?IPv6:2406:e001:3d21:1:28cc:dc4c:9703:6781? ([2406:e001:3d21:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id f70sm7629222pfc.84.2017.11.09.14.48.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2017 14:48:09 -0800 (PST)
Subject: Re: paperless journals, was IETF Journal - November 2017
To: John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20171109210237.4601.qmail@ary.lan>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6a729de0-290c-0b44-a03c-8aabc3baa8b2@gmail.com>
Date: Fri, 10 Nov 2017 11:48:14 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171109210237.4601.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dDG3-ONHc6iI-uQ42ydaWeeqDq4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Nov 2017 22:48:13 -0000

On 10/11/2017 10:02, John Levine wrote:
> In article <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com> you write:
>>>  We look forward to closing our print version and launching ourselves fully into the digital world in 2018.
>>
>> However, BCP 9/RFC 2026 section 6.1.3 states that:
>>
>>>    An official summary of standards actions completed and pending shall
>>>    appear in each issue of the Internet Society's newsletter.  This
>>>    shall constitute the "publication of record" for Internet standards
>>>    actions.
>>
>> When the IETF Journal started, it took over as the medium for this requirement.
>> Are we happy that this will become an on-line only publication?
> 
> Do any libraries actually keep paper newsletters any more?

Very few. I'm not sure it will turn out to be such a good decision 100 years
from now - historians often use ephemera of this kind - but that's the
way things are going.

Now that SM has set me straight, I am not suggesting any action
at all.

    Brian

> 
> Down the road at Cornell University which has a well regarded
> engineering school, they closed the engineering library, moved the
> paper books to the storage annex, and the space is now a largely
> book-free reading room.  It has public wifi which is on the Cornell
> network so you get access to all of the online material to which
> Cornell subscribes.  Even when all the books were there, I spent far
> more time looking at online material than at the old paper journals.
> 
> R's,
> John
> 


From nobody Thu Nov  9 16:37:57 2017
Return-Path: <cmorgan@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF80812702E for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 16:37:55 -0800 (PST)
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 Ja9IiLgEN-J0 for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 16:37:54 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AD3B1242F5 for <ietf@ietf.org>; Thu,  9 Nov 2017 16:37:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 169371C3447 for <ietf@ietf.org>; Thu,  9 Nov 2017 16:37:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HLd-pm8kSTig for <ietf@ietf.org>; Thu,  9 Nov 2017 16:37:25 -0800 (PST)
Received: from dhcp-98ce.meeting.ietf.org (dhcp-98ce.meeting.ietf.org [31.133.152.206]) by c8a.amsl.com (Postfix) with ESMTPSA id 9A5871C2B64 for <ietf@ietf.org>; Thu,  9 Nov 2017 16:37:24 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Report from the IAB
From: Cindy Morgan <cmorgan@amsl.com>
In-Reply-To: <mailman.3822.1510220206.4117.ietf@ietf.org>
Date: Fri, 10 Nov 2017 08:37:52 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <56DE3FA4-1D87-4639-B9F0-A10418DF9837@amsl.com>
References: <mailman.3822.1510220206.4117.ietf@ietf.org>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xrjQB2mGjVth82ZSq_P4Oa5oQ6w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 00:37:56 -0000

On Nov 9, 2017, at12:48:56 PM GMT+8, paul@nohats.ca wrote:
> On Wed, 8 Nov 2017, IAB Chair wrote:
>=20
>> Continuing the tradition started by Andrew Sullivan, here is the IAB =
report to the community about our activities,
>> submitted so that you can prepare topics you might want to discuss =
during the upcoming open mic time.  Of course,
>> if you have issues you want to discuss by email, feel free to send =
your comments to architecture-discuss@iab.org
>> (our public discussion list) or iab@iab.org (to reach just the IAB).
>=20
> Note the included links all redirect via google.com search links and =
my
> mail client warns me it is full of maliciously looking links......
>=20
> Paul

A clean version of this, with fixed links, is available on the IAB =
website at =
https://www.iab.org/2017/11/09/iab-report-to-the-community-for-ietf-100/.

Best regards,
Cindy=


From nobody Thu Nov  9 16:46:42 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 02F4C127286 for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 16:46:40 -0800 (PST)
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=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 SWVmlb-cY4OC for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 16:46:37 -0800 (PST)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::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 AF14D1242F5 for <ietf@ietf.org>; Thu,  9 Nov 2017 16:46:37 -0800 (PST)
Received: by mail-pg0-x22d.google.com with SMTP id g6so6111566pgn.6 for <ietf@ietf.org>; Thu, 09 Nov 2017 16:46:37 -0800 (PST)
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=6EmrFYxs9yut6zwdVFTWUc6cZoCIjKc8U/39XFBfGXk=; b=ZXV8KfOax6LqUVJ7c5NXq7mIL3+JZqUsXDMpca31F8iB3CPiwn0ymoDeI8oyMSS4ZH f6OUkLxvm+YKI0A8hBm6UgFdxr0u9jsOW8sQfm7lyF0MZmTb9g6B+GZo2o4lYIzUd07U hELFizS8w8PWB5r8Mlt7tF53avMSndjYEx8yAYlGS+Kd+1XvQqdk2QS0ygqqHCI3Navj uwN2XHqJnsqY0UUQ6h+0p7FaZMu4zvs/Rpx/HNqaht8YSR0s/roGgtHSpoOq76dxU+1u MVrPJW8grLYMLqjqp9KtO7jtAPZ83nqgvvZPCDH2OFz7Mm4Vu9+Cts6aMJoEM+iSmmMx 9rjA==
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=6EmrFYxs9yut6zwdVFTWUc6cZoCIjKc8U/39XFBfGXk=; b=i2Lhm3Fy9xpQ0hCKi8d0V/6V+CJoLY0bxJbeuBZBuAoerfGC8OHb8Ww1ybzGeVb5DT MqITwXruCGZrRDM1DE5ZXzIsCWvz0Xq8/QSM25a4eVxqwOSA1NkVOtZDXBmPnYNNLVyc KrgE3qTxxwmBSV4YIRFr3cDUmta3E4gp1XieSTy7GtrecB7UsHKIx+BaxTgryjZrrnZ/ 3VLJogRBXjNrtHur8qUhFy5QPRYEfeDCi7uKj+SKneEB6LnqB7hosFzvYKBLtwv57Ekj ojnLBPQz//Oxc/dHi1klqBJSwG919mfD1lasvz5DIfnXgZ/zBGZOrhOvDzj7EqtQIUg8 qTFQ==
X-Gm-Message-State: AJaThX5CSY6yfwtLFkqJxnj3GbCI4d4uQR6OMmc+qzVveuPuwXwNOaNe titNq46q6Do2x+hQ08b8kEsmxw==
X-Google-Smtp-Source: ABhQp+TmtX+yBR7QwnhAh3oAx3Rus9nch+eE8+gYRf1p5ln3RBETGgunyu5X+6V4R0mYFlRHCs19ng==
X-Received: by 10.98.10.21 with SMTP id s21mr2360238pfi.119.1510274797213; Thu, 09 Nov 2017 16:46:37 -0800 (PST)
Received: from [172.20.24.96] ([101.127.234.130]) by smtp.gmail.com with ESMTPSA id 189sm12699415pge.26.2017.11.09.16.46.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Nov 2017 16:46:36 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <63947835-627C-441B-8F2B-9F21DE0A62E1@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_876AC929-B89A-4C4A-A6A6-69FCFCF82367"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF Journal - November 2017
Date: Fri, 10 Nov 2017 08:46:32 +0800
In-Reply-To: <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <0D.4C.42155.96C740A5@mta3> <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n7rEcq8wX-YtiEHWYWIexkrAYWw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 00:46:40 -0000

--Apple-Mail=_876AC929-B89A-4C4A-A6A6-69FCFCF82367
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 10, 2017, at 3:19 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> When the IETF Journal started, it took over as the medium for this =
requirement.
> Are we happy that this will become an on-line only publication?

Yes.   Waste of paper otherwise.


--Apple-Mail=_876AC929-B89A-4C4A-A6A6-69FCFCF82367
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 Nov 10, 2017, at 3:19 AM, Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com" =
class=3D"">brian.e.carpenter@gmail.com</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"">When the IETF Journal started, it took =
over as the medium for this requirement.</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""><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"">Are we happy that =
this will become an on-line only publication?</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"">Yes. =
&nbsp; Waste of paper otherwise.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_876AC929-B89A-4C4A-A6A6-69FCFCF82367--


From nobody Thu Nov  9 17:00:03 2017
Return-Path: <zhenghaomian@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 B553D1293D9 for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 17:00:01 -0800 (PST)
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, 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] 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 SLjo4lrz-3NL for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 17:00:00 -0800 (PST)
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 3C01F124D68 for <ietf@ietf.org>; Thu,  9 Nov 2017 16:59:59 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DSH36092; Fri, 10 Nov 2017 00:59:57 +0000 (GMT)
Received: from DGGEML402-HUB.china.huawei.com (10.3.17.38) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.361.1; Fri, 10 Nov 2017 00:59:56 +0000
Received: from DGGEML511-MBS.china.huawei.com ([169.254.4.204]) by DGGEML402-HUB.china.huawei.com ([fe80::fca6:7568:4ee3:c776%31]) with mapi id 14.03.0361.001; Fri, 10 Nov 2017 08:59:51 +0800
From: Zhenghaomian <zhenghaomian@huawei.com>
To: Ted Lemon <mellon@fugue.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: IETF discussion list <ietf@ietf.org>
Subject: =?gb2312?B?tPC4tDogSUVURiBKb3VybmFsIC0gTm92ZW1iZXIgMjAxNw==?=
Thread-Topic: IETF Journal - November 2017
Thread-Index: AQHTWY+0DzaWkIU8K0qz5zzdn+UlWaMMQXgAgACI/9A=
Date: Fri, 10 Nov 2017 00:59:51 +0000
Message-ID: <E0C26CAA2504C84093A49B2CAC3261A43B614C20@dggeml511-mbs.china.huawei.com>
References: <0D.4C.42155.96C740A5@mta3> <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com> <63947835-627C-441B-8F2B-9F21DE0A62E1@fugue.com>
In-Reply-To: <63947835-627C-441B-8F2B-9F21DE0A62E1@fugue.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.57.78.212]
Content-Type: multipart/alternative; boundary="_000_E0C26CAA2504C84093A49B2CAC3261A43B614C20dggeml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020206.5A04FA0D.00D4, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.204, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c2faed5e3e6d8b678f296689bb250f7a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_2Q2XM7khTM0_EU3787tIS1QKTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 01:00:02 -0000

--_000_E0C26CAA2504C84093A49B2CAC3261A43B614C20dggeml511mbschi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

UGVyc29uYWxseSBJIGtlcHQgY29sbGVjdGluZyBvbmUgcGh5c2ljYWwgY29weSBpbiBlYWNoIElF
VEYgbWVldGluZyBmcm9tIGxhc3QgeWVhciwgaXQgd291bGQgYmUgoa5zdWRkZW6hryBpZiBJIGxv
c2UgdGhpcyBvcHBvcnR1bml0eS4NCg0KSXMgaXQgcG9zc2libGUgdG8gcmVkdWNlIHRoZSBudW1i
ZXIgb2YgcGFwZXIgY29waWVzIGluc3RlYWQgb2YgZGlyZWN0bHkgY2FuY2VsbGluZyB0aGUgcHVi
bGljYXRpb24/IFRoYW5rIHlvdSBmb3IgdGhlIGNvbnNpZGVyYXRpb24uDQoNCkJlc3Qgd2lzaGVz
LA0KSGFvbWlhbg0KDQq3orz+yMs6IGlldGYgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmdd
ILT6se0gVGVkIExlbW9uDQq3osvNyrG85DogMjAxN8TqMTHUwjEwyNUgODo0Nw0KytW8/sjLOiBC
cmlhbiBFIENhcnBlbnRlciA8YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tPg0Ks63LzTogSUVU
RiBkaXNjdXNzaW9uIGxpc3QgPGlldGZAaWV0Zi5vcmc+DQrW98ziOiBSZTogSUVURiBKb3VybmFs
IC0gTm92ZW1iZXIgMjAxNw0KDQpPbiBOb3YgMTAsIDIwMTcsIGF0IDM6MTkgQU0sIEJyaWFuIEUg
Q2FycGVudGVyIDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb208bWFpbHRvOmJyaWFuLmUuY2Fy
cGVudGVyQGdtYWlsLmNvbT4+IHdyb3RlOg0KV2hlbiB0aGUgSUVURiBKb3VybmFsIHN0YXJ0ZWQs
IGl0IHRvb2sgb3ZlciBhcyB0aGUgbWVkaXVtIGZvciB0aGlzIHJlcXVpcmVtZW50Lg0KQXJlIHdl
IGhhcHB5IHRoYXQgdGhpcyB3aWxsIGJlY29tZSBhbiBvbi1saW5lIG9ubHkgcHVibGljYXRpb24/
DQoNClllcy4gICBXYXN0ZSBvZiBwYXBlciBvdGhlcndpc2UuDQoNCg==

--_000_E0C26CAA2504C84093A49B2CAC3261A43B614C20dggeml511mbschi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Microsoft YaHei";
	panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
	{font-family:"Microsoft YaHei";
	panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
	{font-family:Menlo-Regular;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Personally I kept collecting one physical copy in eac=
h IETF meeting from last year, it would be =A1=AEsudden=A1=AF if I lose thi=
s opportunity.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Is it possible to reduce the number of paper copies i=
nstead of directly cancelling the publication? Thank you for the considerat=
ion.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Best wishes,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif">Haomian<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Cali=
bri&quot;,sans-serif"><o:p>&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;=CE=A2=C8=ED=D1=C5=BA=DA&quot;,sans-serif">=B7=A2=BC=FE=C8=CB<span lang=3D=
"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D"font-size:11.0pt;f=
ont-family:&quot;=CE=A2=C8=ED=D1=C5=BA=DA&quot;,sans-serif"> ietf [mailto:i=
etf-bounces@ietf.org]
</span><b><span style=3D"font-size:11.0pt;font-family:&quot;=CE=A2=C8=ED=D1=
=C5=BA=DA&quot;,sans-serif">=B4=FA=B1=ED </span>
</b><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family:&quot;=CE=A2=
=C8=ED=D1=C5=BA=DA&quot;,sans-serif">Ted Lemon<br>
</span><b><span style=3D"font-size:11.0pt;font-family:&quot;=CE=A2=C8=ED=D1=
=C5=BA=DA&quot;,sans-serif">=B7=A2=CB=CD=CA=B1=BC=E4<span lang=3D"EN-US">:<=
/span></span></b><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-family=
:&quot;=CE=A2=C8=ED=D1=C5=BA=DA&quot;,sans-serif"> 2017</span><span style=
=3D"font-size:11.0pt;font-family:&quot;=CE=A2=C8=ED=D1=C5=BA=DA&quot;,sans-=
serif">=C4=EA<span lang=3D"EN-US">11</span>=D4=C2<span lang=3D"EN-US">10</s=
pan>=C8=D5<span lang=3D"EN-US">
 8:47<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Brian E Carpenter &lt;brian.e.carpenter@gmail.com&gt;<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> IETF discussion list &lt;ietf@ietf.org&gt;<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Re: IETF Journal - November 2017<o:p></o:p></span></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Nov 10, 2017, at 3:19 AM, Br=
ian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.=
carpenter@gmail.com</a>&gt; wrote:<o:p></o:p></span></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:13.5pt;font-=
family:&quot;Menlo-Regular&quot;,serif">When the IETF Journal started, it t=
ook over as the medium for this requirement.<br>
Are we happy that this will become an on-line only publication?</span><span=
 lang=3D"EN-US"><o:p></o:p></span></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Yes. &nbsp; Waste of paper othe=
rwise.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_E0C26CAA2504C84093A49B2CAC3261A43B614C20dggeml511mbschi_--


From nobody Thu Nov  9 21:53:20 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 DE4DA12EAFA for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 21:53:18 -0800 (PST)
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 QbSrl55kqnAY for <ietf@ietfa.amsl.com>; Thu,  9 Nov 2017 21:53:15 -0800 (PST)
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 CE13812EAA4 for <ietf@ietf.org>; Thu,  9 Nov 2017 21:53:14 -0800 (PST)
Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vAA5meIk070057 for <ietf@ietf.org>; Fri, 10 Nov 2017 00:53:11 -0500
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by mx0b-001b2d01.pphosted.com with ESMTP id 2e53p9ympc-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 10 Nov 2017 00:53:10 -0500
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, 9 Nov 2017 22:53:09 -0700
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, 9 Nov 2017 22:53:07 -0700
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 vAA5r7dF64159820 for <ietf@ietf.org>; Thu, 9 Nov 2017 22:53:07 -0700
Received: from b03ledav006.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 1413FC603C for <ietf@ietf.org>; Thu,  9 Nov 2017 22:53:07 -0700 (MST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav006.gho.boulder.ibm.com (Postfix) with ESMTPS id E2951C6042 for <ietf@ietf.org>; Thu,  9 Nov 2017 22:53:06 -0700 (MST)
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 vAA5r41p012823 for <ietf@ietf.org>; Fri, 10 Nov 2017 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id vAA5r3DX012742 for ietf@ietf.org; Fri, 10 Nov 2017 00:53:03 -0500
From: narten@us.ibm.com
Date: Fri, 10 Nov 2017 00:53:03 -0500
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: 17111005-0020-0000-0000-00000CF9C043
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00008042; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000239; SDB=6.00943720; UDB=6.00476169; IPR=6.00724003;  BA=6.00005683; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00017948; XFM=3.00000015; UTC=2017-11-10 05:53:08
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17111005-0021-0000-0000-00005ED8B3BB
Message-Id: <201711100553.vAA5r3DX012742@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-11-10_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=13 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-1707230000 definitions=main-1711100083
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BsbL9b0Ymc5FA5vhlTIDjeW1sfo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 05:53:19 -0000

Total of 75 messages in the last 7 days.
 
script run at: Fri Nov 10 00:53:03 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.00% |    9 | 16.66% |   168462 | gonzalo.camarillo@ericsson.com
  8.00% |    6 |  7.08% |    71580 | lee@asgard.org
  8.00% |    6 |  6.09% |    61594 | moore@network-heretics.com
  8.00% |    6 |  5.07% |    51303 | sm+ietf@elandsys.com
  5.33% |    4 |  5.17% |    52265 | stephen.farrell@cs.tcd.ie
  5.33% |    4 |  5.11% |    51649 | ietf@trammell.ch
  4.00% |    3 |  2.91% |    29448 | brian.e.carpenter@gmail.com
  2.67% |    2 |  3.36% |    33991 | aaron.falk@gmail.com
  2.67% |    2 |  2.95% |    29824 | samitac.ietf@gmail.com
  2.67% |    2 |  2.81% |    28448 | jhw@google.com
  2.67% |    2 |  2.80% |    28330 | tte@cs.fau.de
  2.67% |    2 |  2.78% |    28092 | mellon@fugue.com
  2.67% |    2 |  2.32% |    23443 | eckelcu@cisco.com
  2.67% |    2 |  2.21% |    22346 | ben@nostrum.com
  1.33% |    1 |  2.93% |    29640 | rstruik.ext@gmail.com
  1.33% |    1 |  2.89% |    29230 | iab-chair@iab.org
  1.33% |    1 |  2.61% |    26394 | tobias.gondrom@gondrom.org
  1.33% |    1 |  2.32% |    23444 | r_atarius@yahoo.com
  1.33% |    1 |  1.61% |    16321 | hannes.tschofenig@arm.com
  1.33% |    1 |  1.60% |    16192 | ramkri123@gmail.com
  1.33% |    1 |  1.55% |    15667 | cbowers@juniper.net
  1.33% |    1 |  1.50% |    15177 | huitema@huitema.net
  1.33% |    1 |  1.46% |    14756 | zhenghaomian@huawei.com
  1.33% |    1 |  1.45% |    14653 | ietf-secretariat@ietf.org
  1.33% |    1 |  1.36% |    13747 | tom@herbertland.com
  1.33% |    1 |  1.33% |    13454 | narten@us.ibm.com
  1.33% |    1 |  1.18% |    11966 | henry@callistohouse.club
  1.33% |    1 |  1.05% |    10633 | dean.willis@softarmor.com
  1.33% |    1 |  1.01% |    10257 | chair@ietf.org
  1.33% |    1 |  1.01% |    10246 | phill@hallambaker.com
  1.33% |    1 |  0.98% |     9881 | mfidelman@meetinghouse.net
  1.33% |    1 |  0.84% |     8458 | john-ietf@jck.com
  1.33% |    1 |  0.83% |     8427 | paul@nohats.ca
  1.33% |    1 |  0.81% |     8237 | randy@psg.com
  1.33% |    1 |  0.81% |     8222 | cmorgan@amsl.com
  1.33% |    1 |  0.76% |     7668 | nomcom-chair-2017@ietf.org
  1.33% |    1 |  0.75% |     7558 | johnl@taugh.com
--------+------+--------+----------+------------------------
100.00% |   75 |100.00% |  1011003 | Total


From nobody Fri Nov 10 01:55:04 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46EB412EC1B for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 01:55:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, 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=opendkim.org header.b=g4K5JUqr; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=yo+VM/60
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZBR5c3sF14G for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 01:55:02 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE24B12EC19 for <ietf@ietf.org>; Fri, 10 Nov 2017 01:55:02 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.86.160]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vAA9slxT015391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Nov 2017 01:54:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510307699; x=1510394099; bh=pAGaGI8aH7ra8Kh3Plcy/eem04WjOYYYqPfPXJlD6HM=; h=Date:To:From:Subject:In-Reply-To:References; b=g4K5JUqrjTbxMV166aSJmbLB+sj2HvdbXZjohU+0uhwz9dxF/FOF0CDdauw10tBLh e0lB/6MsK1oomeJYQqReZ0iSMhxIzm0vgHJi3fZl3mkAyhT7PanE4IqqaFsPYGJyy7 1GqnQujQNw2VV7PIbtHd1cXoonz26AliTyT5dhi4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510307699; x=1510394099; i=@elandsys.com; bh=pAGaGI8aH7ra8Kh3Plcy/eem04WjOYYYqPfPXJlD6HM=; h=Date:To:From:Subject:In-Reply-To:References; b=yo+VM/60amb3gosCcyLVVtowJFubXReDZwqX1s5GTAFZO0Yp7cjFP1GgG1KF3BmBJ 83ZqX3Sxd76yxH3RaptITUgfkv4L6k3ro7Zv1+aOy1U5iYBUi4XSEiCpXl2JlIbqe3 DHPRJ0F3zVTLDDgAzp9+8ApCSyhRQeXBIOC6gAKs=
Message-Id: <6.2.5.6.2.20171110005054.10038f50@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 10 Nov 2017 01:51:39 -0800
To: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Proposal to revise ISOC's mission statement
In-Reply-To: <67861dfe-8768-f80a-d33f-fb2d904790d4@ericsson.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <6.2.5.6.2.20171109003151.10f38ce0@elandnews.com> <67861dfe-8768-f80a-d33f-fb2d904790d4@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fUPhfhZySmVsUAJS2iexe7tlk7A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 09:55:03 -0000

Hi Gonzallo,
At 01:36 AM 09-11-2017, Gonzalo Camarillo wrote:
>ISOC does a lot of so-called development work in different communities.
>In our last board meeting in Kenya, for instance, we saw a few examples
>of improvements in communities as a result of getting connected.

The only information in the above is that ISOC had a board meeting in Kenya.

I'll make an off-topic comment about "connectivity".  I used "Zoom" 
for a conference call with a few persons located in Africa.  The 
audio quality was bad.  To avoid any misunderstanding I'll mention 
that I do not expect ISOC to fix the problem.  Is that acceptable 
given that it has been like that in the past?

I see Internet stuff which is a copy and paste of what is done in 
developed countries without any understanding of the local 
context.  What are the results of the so-called development work?

Regards,
S. Moonesamy


From nobody Fri Nov 10 04:08:08 2017
Return-Path: <gonzalo.camarillo@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 9E1991289C3 for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 04:08:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 8Y5FL2MDqGrH for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 04:08:06 -0800 (PST)
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 57CF4128959 for <ietf@ietf.org>; Fri, 10 Nov 2017 04:08:06 -0800 (PST)
X-AuditID: c1b4fb30-a0dff70000002554-bd-5a0596a48022
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id D8.53.09556.4A6950A5; Fri, 10 Nov 2017 13:08:04 +0100 (CET)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.78) with Microsoft SMTP Server (TLS) id 14.3.352.0; Fri, 10 Nov 2017 13:08:03 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ApY9K+BmB+oNfb1kBJAGqaJUybCf2y4YngRktxEJPlQ=; b=VUyZMzH9vG0S3FSWo49yO8Ar03RObB3QsNnIkSdEErY79piOnWEwAHEp5tRLgFTALkMSZ+eIK2ka8zoUB9W3hTIr9IQkCCcyH0+IKFXibyH/iUuQ5k+kzUXZYvbccF+76re/hApC4PlO8no74udVDhPSOWpc535Gp7PDkBCrkUc=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
Received: from [IPv6:2001:67c:1232:144:2117:4342:753a:8484] (2001:67c:1232:144:2117:4342:753a:8484) by DB4PR07MB0639.eurprd07.prod.outlook.com (2a01:111:e400:984a::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.218.6; Fri, 10 Nov 2017 12:08:01 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: S Moonesamy <sm+ietf@elandsys.com>, <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <77bb17eb-abd2-f611-b737-f5b9d8b5188e@network-heretics.com> <6.2.5.6.2.20171029112156.11bf51e8@elandnews.com> <02fd9185-eb3b-80bb-9b09-536b6120e911@network-heretics.com> <6.2.5.6.2.20171029130937.113d0e80@elandnews.com> <d9288b89-a7b8-a510-2c01-d1284b10dbdf@network-heretics.com> <9a7f241c-e8ad-18eb-392f-276c62af287c@ericsson.com> <6.2.5.6.2.20171109003151.10f38ce0@elandnews.com> <67861dfe-8768-f80a-d33f-fb2d904790d4@ericsson.com> <6.2.5.6.2.20171110005054.10038f50@elandnews.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <f62bcb61-9e9b-4f63-d90a-965ed31a85b9@ericsson.com>
Date: Fri, 10 Nov 2017 20:07:52 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20171110005054.10038f50@elandnews.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [2001:67c:1232:144:2117:4342:753a:8484]
X-ClientProxiedBy: BN6PR1801CA0012.namprd18.prod.outlook.com (2603:10b6:405:5f::25) To DB4PR07MB0639.eurprd07.prod.outlook.com (2a01:111:e400:984a::26)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f831f822-8f3b-4bc9-3157-08d52833b1b0
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:DB4PR07MB0639; 
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0639; 3:sRCsrV0YwZVaItsim7XruWOYc1YL1Jm8SOW4wVf9EpEf4RNwk8QzyNcmExMwM1zA/VnHE/E0V47Q+muRJE106Z2xaQx3gWl7ajVso9PqpTFn4RLuHiml2gBvTEnlOLH9To5pk3oGuh+vVbFrtosi+4TwQt+isb3ULgA4+QVMHG7qjxidlfEl8lOS2MdCq/kAViRd4XWG7EZBR+Zu/8Eao/J9TCRBgjlf4z2a5yOzJJ0mwn0kf4mit0YjTZwIb3yx; 25:bG9uMyii3dPcdF/je9BNKwMvM991IF5PnjhqxzmmWwoy98LnHpqYMgyPcgs7xPX4PUY8LEI1TmeRYL+g8rFXZnykgHLJb5YnihmS4C13+KM6nqhJ4rPmrvRwzX71EJrtrxPnpbUgfOF691tVSAn2doHRIWL8+uEnA2UvYZAdccMO5wciK6H2QEcNIbNv2McKha57ZaLt/LtEU556I7LGnIdl63LyvTjTH4jGXYbPHFfvbviPCk8XAG7QYczupXHIFJkEGVsnX6QjunFFeLrS75PMB567HJ0tt13ElCG42SCB//Jby4OZM7vwCHzTAdfpw7TzXEucg1+su//tqDEnN8fylbE1A3fVyhyEQubREYA=; 31:zs1Dj9Dvh9hI/EZbytySnmtK2yY+KQjx3Cu+dcDVufbLHHDrDsg7TZfovn2P60qjXXRe1OXGXtVDRw/kYPFCLpoXaXJM5ENmeZEdklIY6uvpNxFLUszgrXGsnbry7mhrkolsUkZPnJzNV/D2KIlTcjSrAoZ9mqSkcBNTF5q+t6x4/dWfw/g1+4lO8h7qE6iX4VvdnGDnMf5TXI6Hia1GRUmWxXcS1bMJmy7OxOn9E9w=
X-MS-TrafficTypeDiagnostic: DB4PR07MB0639:
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0639; 20:vVxegVnbBGV2TnI0TTYWnLW8nk2+4T8ADKtnimvGnj5rt2iEMbw1QTWIAluFFANUHJK5BbfhoE/mkAMa35YUtO+MjTHkrGcNunrdP2TtvLY6GhI77dyu8/7uSf4BUSa84zkFdIrshGaBfqdFT3chBdQshJiGp6CuucQOTLLaS5wkFl8KWWyZa7v8wBTruzBP5a5ZFo8UnO4HBMDBDosIEMqx+bN6LorOUlp7CifPDZsJxx3VC5u1MUVwsRqfgKJbHOnW94vt2LWUnO/h7jGTCBlipDSVQ9z5lBR9zugBdANZgnDjhqrMlS9qsjFKCoD9WbMxyIYjxZy9uORvk/O7vhE71ptFENJlpBuw2FqPf4CGwWtU3g7BSGpC6zt/Upd7n7WvGBtA1MW3BOrmbB1HzIibNsKWOlAa9ZpEYHfKnD9ly7E2sCTLmdzXOhSOiuu7jk2cx6OTzKYx+dPwGJZ3nwf1TjJez98ObiWvMq+0o07F6FzOWzZQgc0Bl/wgenkP; 4:C5Rcf4EahPoy34SmCK/z8IgYyuzUqAhOyXurxrnv/ID+WsdQ6vmPA9EnqzTc/x+9rGHCONYj9h28x6B42oWI9FzgIo/NbyhWZu4WhcQp4cVBacPsp9tAQ7t84LTjO0uGfOFqdaYFtNf/ANkDlsKbGxZZlhkA3hZI4CUoxr/qbvAFZLjuZhk3LnG/oUF92DKLrsV4dZYlNx1zLU+yFolIri4KsgjozMH5YKX+aImrmHCUUdMqcKTsTLuo9DFOSIcRtPiobmJnT3UVyhd6lRBfRA==
X-Exchange-Antispam-Report-Test: UriScan:;
X-Microsoft-Antispam-PRVS: <DB4PR07MB0639F4D4287DB638FE7FE36483540@DB4PR07MB0639.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(100000703101)(100105400095)(3231021)(10201501046)(6041248)(20161123560025)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB4PR07MB0639; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB4PR07MB0639; 
X-Forefront-PRVS: 0487C0DB7E
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(346002)(39860400002)(376002)(24454002)(52164004)(199003)(189002)(377424004)(50986999)(6116002)(54356999)(65826007)(6246003)(58126008)(53936002)(106356001)(305945005)(316002)(5660300001)(105586002)(36756003)(478600001)(76176999)(6666003)(189998001)(1706002)(2950100002)(83506002)(31686004)(47776003)(65956001)(65806001)(50466002)(23676003)(2870700001)(2906002)(93886005)(81156014)(101416001)(6486002)(97736004)(53546010)(64126003)(7736002)(68736007)(33646002)(81166006)(8936002)(229853002)(86362001)(25786009)(31696002)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR07MB0639; H:[IPv6:2001:67c:1232:144:2117:4342:753a:8484]; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjRQUjA3TUIwNjM5OzIzOkdzSkNtR2hMOWFlcWFoYXFHc045SVBJdWI0?= =?utf-8?B?NzBhM01UM05jcWgzRi9HaC9aV3FROVVhbHoyVG1PZ3FCYURjYXBuZEdXRVhT?= =?utf-8?B?UzBvRnV5cHRuWWpMK1loeDY5K0NZSzl6MzZ2bVRVWHNveVlUT0dWNzUzZHNZ?= =?utf-8?B?VWxUY1BUQlZZam1UQjR5L2x6Y0QwZElVcG12RnhBUVZ4YW83UkdOZ04xenNZ?= =?utf-8?B?L3gwWmtXcVB6ZkxVbFkrY1pzcUt1T2FhQkpQSk42WU1JTWY2TVVBUmpXRjZR?= =?utf-8?B?a2N0M1QrZVpybERyZjNCS3RjT3JrWWNLQUtwN3lKZ3E2aGJML3hhdDR6QWR6?= =?utf-8?B?YXZKMFdlRSt0SktxWVRkdnBXUkc5NVFXd3EzMWVDUllNcUVLZUFHbVNGMktI?= =?utf-8?B?dDdHTHljaUg2aHpVeUVIYzZGdnVOT2UrUkRvQjZKRVpiLzBQNVFCallpV3Fl?= =?utf-8?B?c3EzbFpGUXZYeHBVSXJJZEVGWnZWS1FtZGFhcGZzMjI0R2pUYnlKbG01ZDBF?= =?utf-8?B?cFZER01DNGJpRUNQQWZ6Z0tqNmswT29jVkNiYVp6WGNsSWgzakhNQkVHL29P?= =?utf-8?B?OEZ1TE1tOC9uZE8zZkZySFB2RS84ZW5mTFYxNWFURzd5ZVl2YjJyeVRLNGly?= =?utf-8?B?YlJmbkFKR0w3SGpYeHZ2RmI2Z1dMcXpLczFGOHhkK3Q5aTl0cm1QQkZCLzBx?= =?utf-8?B?b2U2d2RZKytWNkF1VXdEU2lXMmprVzNRZmkzVUZwOGNvaUtTR3VMelJRcTZK?= =?utf-8?B?ZmxJcitpaWJHMHF0YXdNUmg3MXhBN2F0MG9TUG5KbndQV1FvZytXTVM0YXg0?= =?utf-8?B?Vk1LSGMwWlNlL3VaMEkxS0lDYk1ZV3hhZUpkcy84OUpUK0J0U1NZTkhsYTZp?= =?utf-8?B?Q2ROekFwSEhxQjFqa3ZVNGo4L3UyRklGQjdoNXMrN25DcGs3MmxJdzlYWjNG?= =?utf-8?B?NG40Uk1qZElVQ3NnQWVNV3pMWFBWNjVmRlIzSnE4R2VlcG1ZMEtMWWdxcVlI?= =?utf-8?B?VG1uMXVOaXRwTXdHRnV4WGt3SG1pbGdyR0lyUmpsRjAyeUJMOWx2TmdmVEc1?= =?utf-8?B?VHhsUEtRVmI4YUsvb3NLd3BtSzhJUWQzL2FObXE3TU1McWQ3cTJDWWVwWmxQ?= =?utf-8?B?ZEJQOUE2YXRmdFhRaXZWcVkxcmZGMCs2TUFEOHRsaE9kN1ljdnNjNUV5K21z?= =?utf-8?B?enVDYzBCcUdRMHpOVzVaSXNvMjhwSHJZNHp3UktxMFg5dXJPUEFpV1BXODdC?= =?utf-8?B?ZWY5WVlNMHE1SExrUGNPcytQU2FzaWtpd3cyUW4zWXZLc1RxdThISTZPdkNv?= =?utf-8?B?K1lWNHhjakxnUDBaVDEvRTdSUEQwa0psVkt5eTNMS3NEYXZMTmxBL2IrVTRU?= =?utf-8?B?SjFzUVpUbkp1ekpNM0NSVmp6aWE3ZldRTXZqdTJHa1JjNVhTdnNieXJOMFFl?= =?utf-8?B?bktiUHhaS096TWJ0OENjK1JvT2NwWVFWR0paL253QTJIZm1nWHZwMmJmSEZW?= =?utf-8?B?Vkk3YW92MEUxWWE4RkdhN2dtdVc2SzNJSDlNbVBxSGh3NjVpdXB5ZWxpemxN?= =?utf-8?B?L0c2Y2FyVGR4eDExUGdYZm5obzJpcytyQTY4b2hLb29GdVMrcHh6aXY0dmZM?= =?utf-8?B?UVB3UlRrOHI5Y2FTRVFtZmZJZXg3OG1hcUNiZmIvV0w0VElEUW9mVGJUcUJW?= =?utf-8?Q?P0G+uTIgemn56dbAPdZVCWKSJdWVzCqRTFtQc69?=
X-Microsoft-Exchange-Diagnostics: 1; DB4PR07MB0639; 6:v5fV7GjHEY6RJHkVeS9jQjoOyivb1wA2Ka2TS8SoGV9R43BzhFxuZdFsFvHaPUoyCfUYBmM4DFrT+nldzF8NhrDU3b2QHtij0r41IbVPTD1EODZj7XJckYb8+LJv7VgnSAyUg2Pg1d7M+pjHYq7WBVVK2wZ7VtY5SfQKc1GW2KGZID7gk4sUFkiUuRNJiGzx3NSrdwIE+UoT/57PH8lEQIkWNJUBewe0q+RC16PDLC+NPWt9z43jr/aBnJpYx+V+AOn5GHBM97S9sbJrJrc7y5reFmqpf9l1Q8DshOQ8uV0QCSBLammvUPSWphuBX3Xp8fyxj7LTBEZPOwiaxiocBHdrw6STOYIP7EEabkDsiWA=; 5:etwYcveB25wVByMtcIE5oTdx8fNr67m49PSocBjRR8qZrrxjuI4OzxTLuxf78K4wu4m06IOxGGgijjNx6IEoLfKAm9ctp2QLq54mPgChIbwEUZFq89KXWTaXIfXFV3HL91km3wRGogbTWr1qdwOCU5ULy0YF9hSPCq3ByhliGbk=; 24:7H7FPe2NI4lzWpEI0W1m3SmooQBOkUQrZtEfefHWyFBy1Sa+tQ2Bzgt1uX/YABKekQooSNl1g+GQdYdrF8XX4HYKCfB4fXppMB7MDcvMiSs=; 7:hjfM4x+KjfKJlaBfKDRDqdinszHzMiY4/cWzNYvYL4ZRMH2GfNLtwVi+6Q5XFMqTSX4rSYSppVtcv7z+WCox2s1Jv8AwYzZrD724nbxASJhQuMjmL04NtYFna5lmWjS0Mz/duIotUsnDhD27rkbwkkagi36GEZmh1wvDNfXCaXmGfaSk9+wY5djubbhFy4gPwAJc2IJjstMieU08174iqUDbS+jpZRPugxcxqt5yJQLiEougGeXUErA8/gLVtyac
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Nov 2017 12:08:01.7819 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: f831f822-8f3b-4bc9-3157-08d52833b1b0
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB4PR07MB0639
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphleLIzCtJLcpLzFFi42KZGbHdT3fJNNYogzd/tCyebZzPYvGq/yar A5PHvTcfmTyWLPnJFMAUxWWTkpqTWZZapG+XwJXx5sxB9oJ5XBUvH01jb2Ds5uhi5OCQEDCR mNiQ18XIySEkcJhR4sFOYwj7BKPEwif+XYxcHCwCvcwSs7ufsoMkGAUSJf7ee8sGkhASOMAk 8eHHNGaQhLCAhcSDC/9YQWwRAXOJjXefQRVtZZFYs+o3WBEbUNGWW/dZQGxeAXuJydd+MIHY LAKqEnOObAeLiwrESEx8cJERokZQ4uTMJ2BxTgE7idVTbjKDXM0soCmxfpc+SJhZQFzi1pP5 TBC2vETz1tlgqyQELCXe/dvEDHKDhMBsRokJ804xQrymLbH8WQsLRJGsxNGzc6BsX4m7/f3s EA0zGSU+/dvGBuFMYZfoe/KYHaJKS6JhyWYmCPsCm8SRz5Iw8XVXP0KtzpbY9GAJE0TzFVaJ L6emsUIkZCTWn3jPApG4wSpxfslu1gmM2rOQvDoL4b1ZSN6bheS9BYwsqxhFi1OLk3LTjYz0 Uosyk4uL8/P08lJLNjEC08bBLb8NdjC+fO54iFGAg1GJh7e7lTVKiDWxrLgy9xCjBAezkgiv vjxQiDclsbIqtSg/vqg0J7X4EKM0B4uSOK/jvgsRQgLpiSWp2ampBalFMFkmDk6pBkZug7g1 eQ9b298KK+1Ymmu89x9jEZMkjzjvX52+sr5M5eKmnP6Is9MOfrIUf/OXoVAz7Hzestc2niL/ 1J0/r7/aHKt+6WQWN4PiW6UfEo5KVZadV11F2+yvvJN9IM16vnlmp7a35PRLh/2Z2BblN/2f LD433nyvgpfAYtabik7vFec/fyT+Q4mlOCPRUIu5qDgRAOAWknUXAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ds9fx8YDE9PVA7jTyT6otAJH2h0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 12:08:07 -0000

Hi,

to provide a different point of view, although this does not seem to be
the right mailing list to discuss tools used by ISOC, the ISOC board
uses zoom extensively and have been very happy with the audio and video
quality so far. Obviously, YMMV depending on local network issues.

Cheers,

Gonzalo

On 10/11/2017 5:51 PM, S Moonesamy wrote:
> Hi Gonzallo,
> At 01:36 AM 09-11-2017, Gonzalo Camarillo wrote:
>> ISOC does a lot of so-called development work in different communities.
>> In our last board meeting in Kenya, for instance, we saw a few examples
>> of improvements in communities as a result of getting connected.
> 
> The only information in the above is that ISOC had a board meeting in
> Kenya.
> 
> I'll make an off-topic comment about "connectivity".  I used "Zoom" for
> a conference call with a few persons located in Africa.  The audio
> quality was bad.  To avoid any misunderstanding I'll mention that I do
> not expect ISOC to fix the problem.  Is that acceptable given that it
> has been like that in the past?
> 
> I see Internet stuff which is a copy and paste of what is done in
> developed countries without any understanding of the local context. 
> What are the results of the so-called development work?
> 
> Regards,
> S. Moonesamy
> 


From nobody Fri Nov 10 09:57:41 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 126F51286B2 for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 09:57:40 -0800 (PST)
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.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=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 RbglmYS2TPZG for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 09:57:38 -0800 (PST)
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 09A99127868 for <ietf@ietf.org>; Fri, 10 Nov 2017 09:57:38 -0800 (PST)
Received: by mail-oi0-x22f.google.com with SMTP id h81so1807361oib.8 for <ietf@ietf.org>; Fri, 10 Nov 2017 09:57:38 -0800 (PST)
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:content-transfer-encoding; bh=81d9U0Up43lJO7hEb2/REUxEEqoGwVLAvM6hKq66EBI=; b=JBB9JdQUEPS1/hfq9dJItIUg8FE9pK9uoTkNTTH5FSNuGzkeIZHLfuwSqr6T5oxGqi VXQ7dSQoFlr24RM5Q05GZEUxMofKUWUPq/YXFGiVxQaJy0dqmqIq3mPmILVk2hokoY6h eKTFTcXhqXr9QVoPWomZopxHsJSEpezk7GFNqSjZnjJONvFTONMCibR+y46GdpOpOl6U FmzPIQA0Wygnnsl/1FS5fO+/f6l2xdQJn1fninAU9AXIqi7EsQJAoqTUQh0lChh5indf oUe9elHyIrQG0VOKIt9+dvw02YGY7xs9xfV4wqBQJLBbdkkIanVNpf+sFM42uQhsQtS5 +5HA==
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:content-transfer-encoding; bh=81d9U0Up43lJO7hEb2/REUxEEqoGwVLAvM6hKq66EBI=; b=BhOZmkQZ19ZMuer16gFdHKyM8nD6Tmi/d6o7vfWgpomQdgUMF5zg7RXOBn/fzjMuig jxqOt1tNMU12fwLQDU1X8bRzeThPp31jCDml029nijseHVqKW42S9dHAbpFJaLc8bFYZ J/N/h+PCiiPkZqREmalKOsCrc/x4qIEN126OHht3l3m6tsTEpL9/6MDEpAOPj4HRyWgU PsLxGx8JTXF5PoS93gnNMheY3A20L8fELzG7pe/UvCY4D07rQOPKQk0dmh03AY0n7eFV 4vO6H9esNkYQYn8/YMpM9WKmlOuPNgDaJrS3IcDJUmL6swXnVNbZIwvEsQC4jPEULfuk ld6A==
X-Gm-Message-State: AJaThX61DqzbmYawVFDUiuG+AYQ7NLYD+/ITjKjboFbwjAXT1Rsve3qK Kvh8PT0un91rm5jMYnCI2rdDHqc3xoe1LtlT1gQ=
X-Google-Smtp-Source: AGs4zMaZSjCRNS7CilTrWlFjE7BZBD2eDUFPWcVd0C4OEzlPpissjSgh873st4iYteD42sOlTWlMyFNES3G/Hu9cSE4=
X-Received: by 10.202.171.13 with SMTP id u13mr698377oie.391.1510336657298; Fri, 10 Nov 2017 09:57:37 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.157.66.145 with HTTP; Fri, 10 Nov 2017 09:57:36 -0800 (PST)
In-Reply-To: <E0C26CAA2504C84093A49B2CAC3261A43B614C20@dggeml511-mbs.china.huawei.com>
References: <0D.4C.42155.96C740A5@mta3> <46991942-1e08-cb7a-3777-4cb4f11ff0fb@gmail.com> <63947835-627C-441B-8F2B-9F21DE0A62E1@fugue.com> <E0C26CAA2504C84093A49B2CAC3261A43B614C20@dggeml511-mbs.china.huawei.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 10 Nov 2017 12:57:36 -0500
X-Google-Sender-Auth: VLPVQ_oCPAG69a7h7Tk2mXQJaAA
Message-ID: <CAMm+Lwi-MTWq7UPLY9qOvDHcGGWgzEB92A3NP7nsZqTEQ_s-iQ@mail.gmail.com>
Subject: =?UTF-8?B?UmU6IOetlOWkjTogSUVURiBKb3VybmFsIC0gTm92ZW1iZXIgMjAxNw==?=
To: Zhenghaomian <zhenghaomian@huawei.com>
Cc: Ted Lemon <mellon@fugue.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>,  IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H5kxHECeBiYx4SIXBRsarJ539SA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 17:57:40 -0000

I think that this demonstrates an instance of an important use case
that is widely felt. It is also a problem that IETF cannot solve on
its own, nor can any institution nor even any single country (I met a
traveler in an antique land...).

Back in the 1990s, disk space was expensive. Archiving technology
primitive. Today disk is cheap but the ratio of signal to noise is
vastly lower. And it is not just digital media that are affected this
way. Any picture from the 1800s is likely to be an important
historical document. We don't need to keep every selfie taken with a
cell phone.

There are basically two approaches to preserving anything, one is to
have one hypersecure vault and protect it, the second is to have a
vast number of copies and a social infrastructure that replaces copies
when some are lost.

Consider 'the long now' and Danny Hillis's clock. Sure you can build a
clock that will run for a thousand years (maybe). But the way that we
have maintained an unbroken time sequence of increasing accuracy since
the 1950s is through a federation of national labs. There is no single
source of time. There are many that produce COORDINATED time.


The problem is not really preserving the bits. The problem is that the
bits are liable to get lost. If you don't know you have it, you might
as well not have it. Atoms fall victim to the same problem.

What we need to solve this problem is some consortium of interests who
can provide a modest level of resources (a few machines, a few TB of
storage, some network capacity) and some sort of gating mechanism to
make sure that we are applying those resources to preserve as much
signal as possible.

The technical requirements are not great: Merkle Tree, HashGraph,
Wingardium Leviosa. The real obstacle is establishing the social
infrastructure to get the project to critical mass. If one person ran
a node, the project could die any moment. If a dozen people ran nodes
then we have probably reached a large enough critical mass for some
people to think it worthwhile taking a copy for their archives.

There are in fact many folk who are archiving parts of the Web, they
are just not coordinated or even aware of the others.

The secondary set of issues are to do with copyright and IPR. But
those are fixable when you lay out the requirements.


I have been building something of the sort for managing Mathematical
Mesh profiles:

http://www.prismproof.org/Documents/draft-hallambaker-jbcd-container.html




On Thu, Nov 9, 2017 at 7:59 PM, Zhenghaomian <zhenghaomian@huawei.com> wrot=
e:
> Personally I kept collecting one physical copy in each IETF meeting from
> last year, it would be =E2=80=98sudden=E2=80=99 if I lose this opportunit=
y.
>
>
>
> Is it possible to reduce the number of paper copies instead of directly
> cancelling the publication? Thank you for the consideration.
>
>
>
> Best wishes,
>
> Haomian
>
>
>
> =E5=8F=91=E4=BB=B6=E4=BA=BA: ietf [mailto:ietf-bounces@ietf.org] =E4=BB=
=A3=E8=A1=A8 Ted Lemon
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2017=E5=B9=B411=E6=9C=8810=E6=97=A5=
 8:47
> =E6=94=B6=E4=BB=B6=E4=BA=BA: Brian E Carpenter <brian.e.carpenter@gmail.c=
om>
> =E6=8A=84=E9=80=81: IETF discussion list <ietf@ietf.org>
> =E4=B8=BB=E9=A2=98: Re: IETF Journal - November 2017
>
>
>
> On Nov 10, 2017, at 3:19 AM, Brian E Carpenter <brian.e.carpenter@gmail.c=
om>
> wrote:
>
> When the IETF Journal started, it took over as the medium for this
> requirement.
> Are we happy that this will become an on-line only publication?
>
>
>
> Yes.   Waste of paper otherwise.
>
>


From nobody Fri Nov 10 15:01: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 9ED37127058 for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 15:01:04 -0800 (PST)
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 DaBDZVvcWPqT for <ietf@ietfa.amsl.com>; Fri, 10 Nov 2017 15:01:02 -0800 (PST)
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 B187C126579 for <ietf@ietf.org>; Fri, 10 Nov 2017 15:01:02 -0800 (PST)
Received: by mail-pf0-x235.google.com with SMTP id d28so7672126pfe.2 for <ietf@ietf.org>; Fri, 10 Nov 2017 15:01:02 -0800 (PST)
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-language:content-transfer-encoding; bh=9V3b2MMWN2BoUB/IZkMcZNEqk4bv6xJn9hpskmN9+gg=; b=j89eScpJ8Q+abe8CazaNs9+wMBQbgdrDnRrYvwKBySICtN+CbXaLVadP4dje0hVEgF 3I4wDCYqeCQx+cvlc47u+QAfMp1gNu6GQdm3H8iuv/415rAYzAnBnHSaEQcBbdp8MtGD cu4/30y75akI/nt5l7Wowl8fVrR/CqZyDE8tbRcglJ2b2ITWlTuFf/EpgcryWQfwe2Fr Erdi41MSC8UMfcul+nBEgJ+ta0EK6bzp4UsUaeHe+Zc0zss5lCEtkiJ5XYHNnaCOd+Fs gA73my+EWEoYSrIIpCEBBzkkCxxO6A/wys8ffrEYLubEqYrTOkUOi9zlcLVnRlDWmHzG QjJw==
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-language:content-transfer-encoding; bh=9V3b2MMWN2BoUB/IZkMcZNEqk4bv6xJn9hpskmN9+gg=; b=CmhmszdUDMiFlmyfN0kud9c3eMLMNnNt9s7QBsBzP1RBJImVQ5ujA3TJubbtbLggqW yCJ5P5OzzbBf8DBZDiAWvtWo8Nu5tjArhW9C5ULWQ6pkMrUp5eznVrPCMUoqYM20K7Lx wQFFvfUKXsEarkh1n9UJHuN8KhVdSA2BtC2dPyTttITzpHn11BOche1BxYv/+gfplrRb AG6cg8zP77itdglkYTj9fPrD8JFvHjqpXGKCQmp9o+QBtu9OEJ2vBvBLMe6f/xsf4vZP B6Lx0yJZoo0zjGbZYx1LTXsU3IsqQ7HkYiuafvCwQLHybYILLohpjVZt55tj1rJcYniw Dnqw==
X-Gm-Message-State: AJaThX5ZdTEMqQVB3VsBxKutyR55wV6Nb5IKwXm67YEnp6tRKX3GtI6Q i6F81NQLhQSsGthQiW3SqqTNzg==
X-Google-Smtp-Source: AGs4zMZbwVqP48SarXOdo7wdv5G07mXUZJbhZ/HKeQlu/yfbqMDdgQWiWasx/ytZjsCV3fVk1MXNWg==
X-Received: by 10.99.96.87 with SMTP id u84mr1750069pgb.407.1510354861841; Fri, 10 Nov 2017 15:01:01 -0800 (PST)
Received: from [192.168.41.64] (219-88-101-13.adsl.xtra.co.nz. [219.88.101.13]) by smtp.gmail.com with ESMTPSA id k8sm17458907pgt.22.2017.11.10.15.00.58 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Nov 2017 15:01:00 -0800 (PST)
Subject: Re: IETF Website Status Update
To: ietf@ietf.org
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7930fd9b-3c06-7b5a-2a28-5198604af5de@gmail.com>
Date: Sat, 11 Nov 2017 12:01:04 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AehC0OuASrnGjnZLYuE1F-LJb1c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Nov 2017 23:01:05 -0000

On 01/11/2017 10:36, Russ Housley wrote:
> I want to share an update on progress on the IETF website revamp projec=
t. In particular I=E2=80=99d like to highlight what has been done to resp=
ond to feedback from the IETF community received around IETF 99.
>=20
> A. Provide a landing page dedicated to current IETF participants
>=20
> A draft is currently posted at https://beta.ietf.org/links/
>=20
> That page includes links to:
> - items on the left-side at www.ietf.org (or a subset thereof)
> - information about the next IETF meeting=20
> - links to functions at datatracker.ietf.org=20
>=20
> The goal is to make this page:
> - viewable in a single screen on a desktop/laptop display

In that, it fails, compared to https://www.ietf.org/content.html :
a) at least 5cm vertical space is wasted with pointless blurb.
b) because of the lack of columns and empty space, it is much
harder to spot individual items.

On the other hand, it's usable on a smartphone, which the old
page hardly is.

So there's the basic question: do we want to make the site
harder to use on a laptop or desktop so that it's easier to use
on a smartphone? That goes for pretty much every page on the beta
site, I think, although it seems to be a rather noticeable issue
for this particular page.

Regards
    Brian

> - reachable via a short, memorable URL
>=20
> The current content includes changes implemented based on suggestions r=
eceived via email after IETF 99. Of course, this page will be updated fur=
ther based on input from the community.
>=20
> B. Ensure WCAG 2.0 compliance
>=20
> Since IETF 99, we have worked with the website developer to improve com=
pliance. This is a requirement of the Statement of Work (https://iaoc.iet=
f.org/documents/IETF-Website-SOW-20140604-Final.pdf). We believe that has=
 been accomplished. However, ensuring and improving accessibility must be=
 part of ongoing editorial practices, so it will continue to be an area o=
f focus for the website.
>=20
> C. Conduct review with other key audiences, especially potential partic=
ipants and non-participants
>=20
> Additional interviews with members of the key audiences have been condu=
cted to gather input. In general, response to the beta.ietf.org site was =
positive.  IETF newcomers say that the new site makes it easier to unders=
tand what the IETF is all about. Some specific suggestions have been inco=
rporated into the project, and they are included at https://github.com/ie=
tf/www.ietf.org/issues =20
>=20
> D. Improve data use and load times
>=20
> Since IETF 99, the beta.ietf.org site was placed behind the Cloudflare =
CDN. This has significantly improved load times. Of note, in interviews (=
see item C above), new or non-IETF participants located in Latin America =
and Africa did not report load time as a significant issue. However, as t=
he new site moves to production, the editorial process will continue to f=
ine tune how images and other elements are handled to further improve per=
formance. =20
>=20
> Next steps:
>=20
> We are continuing to fine tune content and are aiming to move to produc=
tion after IETF 100. One significant task remaining is to ensure continui=
ty for important URLs, as specified in the Statement of Work. We expect t=
o tackle that after IETF 100.
>=20
> We welcome input and suggestions. We held "office hours" at IETF 98 and=
 IETF 99, and we will hold "office hours=E2=80=9D at IETF 100.  If you wi=
ll be in Singapore, please take this opportunity to share feedback in per=
son. Details will be posted on a sign around the IETF meeting registratio=
n desk. And, of course, questions or issues can always be raised at https=
://github.com/ietf/www.ietf.org/issues =20
>=20
> Sincerely,
>   Russ Housley
>   IETF Website Revamp Project Manager
>=20


From nobody Sat Nov 11 05:35:58 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 C5129129544; Sat, 11 Nov 2017 05:35:50 -0800 (PST)
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 DrgrjWwHJphP; Sat, 11 Nov 2017 05:35:49 -0800 (PST)
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 2951E129541; Sat, 11 Nov 2017 05:35:49 -0800 (PST)
Received: by mail-pg0-x22c.google.com with SMTP id t10so8437232pgo.3; Sat, 11 Nov 2017 05:35:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=mzPCkTO+xtphkZp/oj6XwbYJgu0LRLGEw4jwOBH9vtA=; b=mredeV9iXR/m6fcAXD5k8rT7nRhivgwH1R/vi+wxVwb9nE9dLYKR1GvrkCQEp5EWwI ZzUWEjqIvzgdlx0abWJQa+D2Ig/Om72184QbuePthhglGNllE7F9gg7cRZMDKBwQyWXd TuqFsyOiUqvbWcDQgAQ5U2Wm0tzThmgMPssx3Q4bmYstoLEr4bCgR7A03UGpSgi+L86w wVG6Ns83067gHltn9b9x1JXy2rNRZ/dOVVCk+RR25oN6cMBPsvrPzulEtpCBxeCkqp/O 1XA1R7nE+otHZh7CWkPVixApVFbsRCWxNfre1HZp31Ano+3F700e5C1iquTJ+/Siz5PS DVzw==
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:in-reply-to :references:mime-version; bh=mzPCkTO+xtphkZp/oj6XwbYJgu0LRLGEw4jwOBH9vtA=; b=jKcZ2Fo7gcG50cet619mQLVsF3mVrQfPnPSyBpIAFVk2YvDW9ptKiDelb0eZxBrj9W 5jqKOv4tvXTqG9MeK8dNHr0dU2nne7uCoPzH9uAHEWsmv3Ls5+qGhsqN/L0aNsXlZN1J msU8KI1jm/+b0tKTeer2Sxgn1w0Lxuhlnh5VqX/8WpQPAJtWXypsppjJU1QK0MBpyNaK D1zHJkEP2P5aAfgHIs6FoNMzCOfH9Yo65Q0rCp+4E3/6AHwRuaVaVS+tbMshOQBIUHPC JvhskjfAkeaRI4Gc/bq1wutflGmTQ9hvF1HIDox6ltytlgILMS9qTZZWW1yis+ROn9xI Yq/A==
X-Gm-Message-State: AJaThX7Gm7EJ916zMJb28hqS0glxlCyqAiR/3hrkcFZNVRcLi8q+I87z 0pRhDhy2V6F0ULnWcnTnRGnbSCFa
X-Google-Smtp-Source: AGs4zMaVBqrb8GBrP7CtBKBybEzGudGIc6YLPPl6jTLM6Ox5PmzWiuotrYXiBFs00QzZs26H2iNUyg==
X-Received: by 10.99.67.195 with SMTP id q186mr3351546pga.186.1510407348120; Sat, 11 Nov 2017 05:35:48 -0800 (PST)
Received: from [31.133.153.109] ([2001:67c:1232:144:810:b372:3225:d31b]) by smtp.gmail.com with ESMTPSA id w9sm23530255pfl.19.2017.11.11.05.35.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 Nov 2017 05:35:46 -0800 (PST)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "100attendees@ietf.org" <100attendees@ietf.org>
Subject: Re: CFP: PechaKucha at IETF-100
Date: Sat, 11 Nov 2017 18:47:42 +0800
Message-ID: <E54340C7-361E-4917-9EDC-6228851EA3EB@gmail.com>
In-Reply-To: <399B1F51-1C36-4F6D-B1ED-2F293707A6BF@gmail.com>
References: <9B50505D-A7E7-40E0-B789-419DA14C6021@gmail.com> <399B1F51-1C36-4F6D-B1ED-2F293707A6BF@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_555B3968-F3FE-4072-BA9B-1AD52C856E2D_="
X-Mailer: MailMate (1.9.7r5425)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3u9-GISXvxyjqXDARLjQj6dez_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: Sat, 11 Nov 2017 13:35:51 -0000

--=_MailMate_555B3968-F3FE-4072-BA9B-1AD52C856E2D_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

The PechaKucha will be Thursday evening, 9:30 - 11pm in the Olivia Room. =

  Bar availability is TBD.  Ten presenters are signed up so far =

(thanks!!) and still room for a couple more.  Hope to see you there!

=E2=80=94aaron

On 7 Nov 2017, at 22:38, Aaron Falk wrote:

> Should have mentioned this yesterday: we=E2=80=99re a bit under critica=
l =

> mass to hold a pechakucha in Singapore.  If you are on the fence, be =

> brave and step up.  It=E2=80=99s fun and you=E2=80=99ll get as friendly=
 a =

> reception as possible at an IETF (although this is not an IETF event).
>
> =E2=80=94aaron
>
> On 6 Nov 2017, at 12:36, Aaron Falk wrote:
>
>> Thinking about doing a PechaKucha in the past and never had time.  =

>> **NOW IS THE TIME!**
>>
>> Come share your favorite stories, rants, or calls to action with your =

>> colleagues at IETF-100.  If you have a topic about which you are =

>> passionate, you can give a PechaKucha. (Here are two of my personal =

>> favorites by =

>> [Pete](http://snaggletooth.akam.ai/Prague-videos/07-pete-resnick-8.mp4=
) =

>> and =

>> [Brian](http://snaggletooth.akam.ai/Berlin-videos/2_trammel-8.mp4), =

>> although there are many other excellent examples.)
>>
>> What is a PechaKucha, you ask? A PechaKucha is a lightning-talk =

>> presentation format, originating in Japan, where a speaker presents =

>> 20 image-only slides that are each on the screen for 20 seconds and =

>> advance automatically.  With each talk lasting for 6:40, it has the =

>> feature of forcing presentations -- good or bad -- to be focused and =

>> brief.
>>
>> This is an unofficial event. Topics are encouraged to be a =

>> IETF-related and satirical or controversial in some way, although not =

>> mean-spirited.  Anyone can participate in this social event.
>>
>> Video from the Berlin, Seoul, Chicago, and Prague PKs can be found =

>> [here](http://snaggletooth.akam.ai).
>>
>> Format Details:
>>
>> * Presentation slots are open to all, assigned first come, first =

>> served.
>> * To reserve a presentation slot, send a name and title to =

>> aaron.falk@gmail.com and receive confirmation.
>> * Presenters must agree to adhere to the Pecha Kucha format (20 =

>> slides, primarily image-only, automatically advancing every 20 =

>> seconds).
>> * There are lots of online tutorials and suggestions for how to make =

>> a good PechaKucha.  Here are a few: =

>> [[1](http://www.pechakucha.org/)], =

>> [[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pe=
cha.html)], =

>> [[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].

--=_MailMate_555B3968-F3FE-4072-BA9B-1AD52C856E2D_=
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">The PechaKucha will be Thursday evening, 9:30 - 11pm in t=
he Olivia Room.  Bar availability is TBD.  Ten presenters are signed up s=
o far (thanks!!) and still room for a couple more.  Hope to see you there=
!</p>

<p dir=3D"auto">=E2=80=94aaron  </p>

<p dir=3D"auto">On 7 Nov 2017, at 22:38, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">Should have mentioned this yesterday: we=E2=80=99re a bit=
 under critical mass to hold a pechakucha in Singapore.  If you are on th=
e fence, be brave and step up.  It=E2=80=99s fun and you=E2=80=99ll get a=
s friendly a reception as possible at an IETF (although this is not an IE=
TF event).</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<p dir=3D"auto">On 6 Nov 2017, at 12:36, Aaron Falk 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">Thinking about doing a PechaKucha in the past and never h=
ad time.  <strong>NOW IS THE TIME!</strong></p>

<p dir=3D"auto">Come share your favorite stories, rants, or calls to acti=
on with your colleagues at IETF-100.  If you have a topic about which you=
 are passionate, you can give a PechaKucha. (Here are two of my personal =
favorites by <a href=3D"http://snaggletooth.akam.ai/Prague-videos/07-pete=
-resnick-8.mp4" style=3D"color:#999">Pete</a> and <a href=3D"http://snagg=
letooth.akam.ai/Berlin-videos/2_trammel-8.mp4" style=3D"color:#999">Brian=
</a>, although there are many other excellent examples.)</p>

<p dir=3D"auto">What is a PechaKucha, you ask? A PechaKucha is a lightnin=
g-talk presentation format, originating in Japan, where a speaker present=
s 20 image-only slides that are each on the screen for 20 seconds and adv=
ance automatically.  With each talk lasting for 6:40, it has the feature =
of forcing presentations -- good or bad -- to be focused and brief.</p>

<p dir=3D"auto">This is an unofficial event. Topics are encouraged to be =
a IETF-related and satirical or controversial in some way, although not m=
ean-spirited.  Anyone can participate in this social event.</p>

<p dir=3D"auto">Video from the Berlin, Seoul, Chicago, and Prague PKs can=
 be found <a href=3D"http://snaggletooth.akam.ai" style=3D"color:#999">he=
re</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#999">aaron.falk@gmail.com</a>=
 and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good PechaKucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/"=
 style=3D"color:#999">1</a>], [<a href=3D"http://blog.indezine.com/2012/0=
5/10-tips-to-create-and-present-pecha.html" style=3D"color:#999">2</a>], =
[<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/=
" style=3D"color:#999">3</a>].</li>
</ul>
</blockquote>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_555B3968-F3FE-4072-BA9B-1AD52C856E2D_=--


From nobody Sat Nov 11 14:37:52 2017
Return-Path: <allison.mankin@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 5896D1200C5 for <ietf@ietfa.amsl.com>; Sat, 11 Nov 2017 14:37:50 -0800 (PST)
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=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 NZoTCR-Oo57T for <ietf@ietfa.amsl.com>; Sat, 11 Nov 2017 14:37:48 -0800 (PST)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::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 32C93124B17 for <ietf@ietf.org>; Sat, 11 Nov 2017 14:37:48 -0800 (PST)
Received: by mail-pf0-x236.google.com with SMTP id d28so9212306pfe.2 for <ietf@ietf.org>; Sat, 11 Nov 2017 14:37:48 -0800 (PST)
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=Sphmego5lOwRmcKe/n75SdHTCHkv0FrjPmsDLGnsBWs=; b=KMhdAWVd+AWV4MyDtvmkRFkG6kn4aHyN7lQB6p9tZOEJAnIuOc8hfPHNclG6zsqv7T dbABPrbjVqDQlNQTDctQe1J3Oaxpn12K/RVD6HwzjO69zPo51NQArOt7qtv/uJ2yOIJI eZxCQuZZlkLZXnglzT8K/WWmk1CTOEl/89RUAWKBVKtdcObnmNmkPx4nG1Fw8K7M7NFb CjgKPVHZBzUWJTdnuW/K0X6LOrIc0zq+9BWvqk4SeusPmAqQR8PnSiJGKjpCkTZqTXwT vSml1RF9qzdcxYVWMfLQdM7AK0bS8Nx+EbG1h7oLNUtlU52fpVTBxwjX7njUpBRjqJUS f48Q==
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=Sphmego5lOwRmcKe/n75SdHTCHkv0FrjPmsDLGnsBWs=; b=Udw/i5cj9wINguyR/c+EWjfQmyDnjAOgYjz7CTEOjTtVYJ21t8YiRGJdhxco89nXDb B3csnE7//Mvh1PTawgykDRzQ+t3/D38LCbjznCxBsvUvc4SA4tDNgZaXzHEmYstbn2P/ lHh3vF5qsQjU22UMju4gyWuIWxY/o/zWPqfDoyEafGXbEwSdz6eq71tVH9o/Asocijzh CvqNe7qo3p/sTFeqj8CwB+fFiMwy7Ey3aS52kUDwlAb/BJYxoD0s7wEejOfeTKKsyIXi UH9rvAeKQKhc30MLrkbY/ggwcn6XM9oQijIseNtw7zKVrWr174X3a2lZm0n1pjQ8b+Ba 1ybg==
X-Gm-Message-State: AJaThX4y4+JmMCi8rDrdtvlMHEYV98loYzf0L0QbsO+a4ZZAz1xJ5Hpc EMJhnPU8cb9N/pcB1JoH6fv976jfuOu66+K0PHI=
X-Google-Smtp-Source: AGs4zMY9Yp7iRw9gmtTS/FPpVCn0LhHcEDF/20mqOyT0IQVvvj3y2FrnTMDzOnOp0Uhcn67VU1ehJOMtnPxOg4pRPnY=
X-Received: by 10.101.66.197 with SMTP id l5mr4484859pgp.240.1510439867475; Sat, 11 Nov 2017 14:37:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.130.129 with HTTP; Sat, 11 Nov 2017 14:37:46 -0800 (PST)
In-Reply-To: <CAP8yD=v-b0Ke2Uzjs5qWKj7wod5iaD2_-Om-rHmxSQAgQEPO-w@mail.gmail.com>
References: <CAP8yD=v-b0Ke2Uzjs5qWKj7wod5iaD2_-Om-rHmxSQAgQEPO-w@mail.gmail.com>
From: Allison Mankin <allison.mankin@gmail.com>
Date: Sun, 12 Nov 2017 06:37:46 +0800
Message-ID: <CAP8yD=tB_9amS-LPwvGf4+c+4EhBTDo=yxtaWq3Myjbae75W9g@mail.gmail.com>
Subject: Fwd: Applied Networking Research Prize Awardees for IETF 100
To: IETF Discussion <ietf@ietf.org>
Cc: "Internet Research Steering Group (irsg@irtf.org)" <irsg@irtf.org>, Roland van Rijswijk-Deij <r.m.vanrijswijk@utwente.nl>, emmericp@net.in.tum.de
Content-Type: multipart/alternative; boundary="f403043e2280c16d36055dbcaf2c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h26C9KlnrEx-KGZe_7aZj_F21G8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Nov 2017 22:37:50 -0000

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

Please join us for an exciting program with the final two Applied
Networking Research Prize Awardees, during the IRTFOPEN meeting Thursday
morning, 9:30 AM.
The meeting will be streamed as well (1:30 UTC)=E2=80=8B.


The IRTF is pleased to announce that the 2017 ANRP awardees for IETF 100
are:

Paul Emmerich,  Technischen Universit=C3=A4t M=C3=BCnchen, DE
MoonGen: A Scriptable High-Speed Packet Generator

Roland van Rijswijk-Deij, University of Twente, NL
The Performance Impact of Elliptic Curve Cryptography on DNSSEC Validation

Congratulations to Paul and Roland!  They will join us in Singapore to
present their award papers during the IRTFOPEN meeting (watch for the draft
agenda soon to get the specific time).

The Applied Networking Research Prizes are a program of the IRTF and
ISOC.   The four awardees who have already presented in 2017 brought out
great conversations, and we expect great things from these final two as
well!

Allison

Allison Mankin
IRTF Chair

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div style=3D"font-family:arial=
,helvetica,sans-serif" class=3D"gmail_default">Please join us for an exciti=
ng program with the final two Applied Networking Research Prize Awardees, d=
uring the IRTFOPEN meeting Thursday morning, 9:30 AM. <br></div><div style=
=3D"font-family:arial,helvetica,sans-serif" class=3D"gmail_default">The mee=
ting will be streamed as well (1:30 UTC)=E2=80=8B.</div><div style=3D"font-=
family:arial,helvetica,sans-serif" class=3D"gmail_default"><br></div><br><d=
iv dir=3D"ltr"><div style=3D"font-family:arial,helvetica,sans-serif">The IR=
TF is pleased to announce that the 2017 ANRP awardees for IETF 100 are:</di=
v><div style=3D"font-family:arial,helvetica,sans-serif"><br></div><div styl=
e=3D"font-family:arial,helvetica,sans-serif">Paul Emmerich,=C2=A0 Technisch=
en Universit=C3=A4t M=C3=BCnchen, DE<br>
<span class=3D"m_-8341058331849465739gmail-il">MoonGen</span>: A Scriptable=
 High-Speed Packet Generator</div><div style=3D"font-family:arial,helvetica=
,sans-serif"><br></div><div style=3D"font-family:arial,helvetica,sans-serif=
">Roland van Rijswijk-Deij, University of Twente, NL<br></div><div style=3D=
"font-family:arial,helvetica,sans-serif">The Performance Impact of Elliptic=
 Curve Cryptography on DNSSEC Validation</div><div style=3D"font-family:ari=
al,helvetica,sans-serif"><br></div><div style=3D"font-family:arial,helvetic=
a,sans-serif">Congratulations to Paul and Roland!=C2=A0 They will join us i=
n Singapore to present their award papers during the IRTFOPEN meeting (watc=
h for the draft agenda soon to get the specific time).</div><div style=3D"f=
ont-family:arial,helvetica,sans-serif"><br></div><div style=3D"font-family:=
arial,helvetica,sans-serif">The Applied Networking Research Prizes are a pr=
ogram of the IRTF and ISOC.=C2=A0=C2=A0 The four awardees who have already =
presented in 2017 brought out great conversations, and we expect great thin=
gs from these final two as well!<br></div><div style=3D"font-family:arial,h=
elvetica,sans-serif"><br></div><div style=3D"font-family:arial,helvetica,sa=
ns-serif">Allison</div><span class=3D"HOEnZb"><font color=3D"#888888"><div =
style=3D"font-family:arial,helvetica,sans-serif"><br></div><div style=3D"fo=
nt-family:arial,helvetica,sans-serif">Allison Mankin</div><div style=3D"fon=
t-family:arial,helvetica,sans-serif">IRTF Chair<br></div><div style=3D"font=
-family:arial,helvetica,sans-serif"><br></div><div style=3D"font-family:ari=
al,helvetica,sans-serif"><br></div></font></span></div>
</div><br></div>

--f403043e2280c16d36055dbcaf2c--


From nobody Sat Nov 11 15:36:37 2017
Return-Path: <allison.mankin@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 A37EA126D73; Sat, 11 Nov 2017 15:36:35 -0800 (PST)
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 zMZPTppU3kN6; Sat, 11 Nov 2017 15:36:33 -0800 (PST)
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 CC6AB1201F2; Sat, 11 Nov 2017 15:36:33 -0800 (PST)
Received: by mail-pg0-x22b.google.com with SMTP id g6so10044442pgn.6; Sat, 11 Nov 2017 15:36:33 -0800 (PST)
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=SWHs5/Ok7jaX6CYkJ8GGwNsl5t02y6ZLQ8tBQuBH99A=; b=OEEKiFMrn4E52dN+22LvxFmcu9+CVA9uCpsd+eIEuNI+1o8LYkwryZwKK+GJ3pjRQB t/LMtTsujNkbNb7yTYkngpxdXUSjQZKXLSC3c83FjortkGdc0cZTadPj71vMtZWMX0pg gqKfqWxUz3yvMWKgdUBQPauk7YR1Ez3r8yMjBGY/8Y5R07jbpPsYEB6Thjg9rYjNOlri m49cPewCWCOjKIAkFcamXpG7J4ikFfaHjQZs2yFdq0CCQe9Pm41EITHqRn6wGr0jna38 gU2OEvkEjMcVZDUSP3xrPg9Bz71t5FvCxZAdrvcek3lnaM8qf6j1pogwfF4ibCbmP9do JrOg==
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=SWHs5/Ok7jaX6CYkJ8GGwNsl5t02y6ZLQ8tBQuBH99A=; b=HnJ6wKNusZKK7j+WckMOwpC1vXLYaCMF8ClZkzE15zeLqDuxIgfiJkUIrxt3m1EX5Q WW3vXyIMLp163WLNmXLnmPh6pf0+X2sJeu4Q2cV8y93vcpP+AsTOh1UFIGCTXh3pY2xT YG8kgZuUBMMT7ne2fSzaXkvJkbmHGhuKFZaVtXYb0tZlhWopV/YXblNP2k3tMyaq+oun rd+Uu+i8JY+MyR2erZdPG2EqZUqLDy9LusFYhnkcMuvHQU8+EKwVpBHvhk5C+PD+yKsY kEpd2iKERI7mOla6wcz73w/SSwxD/lOXljyw02vfwCN4XEcHEP/RCPw5a9aBZ8XOMY+q HM9g==
X-Gm-Message-State: AJaThX5kdXizoQkyTdHBekfcFCsTokm+NuknC/bmEl+QCBP9HY80ouLd YhRbE22bx28WMexutarKoI09MdUYqWCdKT8HbMzMSQ==
X-Google-Smtp-Source: AGs4zMa6ETVKfvIPGEzIAyF/b0zpc1RBozTX+wO68cpLbYdDgPLJFiJCQBs3DVOXz9NtEQ1ymT5LJLsqDD+1UnLFl9g=
X-Received: by 10.99.64.5 with SMTP id n5mr4479998pga.244.1510443393192; Sat, 11 Nov 2017 15:36:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.130.129 with HTTP; Sat, 11 Nov 2017 15:36:32 -0800 (PST)
From: Allison Mankin <allison.mankin@gmail.com>
Date: Sun, 12 Nov 2017 07:36:32 +0800
Message-ID: <CAP8yD=seWQxf_A+S6AcDP-8qEFYiBDbYp2FMp9EGE83CxNOCfA@mail.gmail.com>
Subject: Systers at IETF 100
To: IETF Discussion <ietf@ietf.org>
Cc: "systers@ietf.org" <systers@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c076d2ae79908055dbd8120"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d1jgh2EH3C2pt_L_S3nF3sivI94>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Nov 2017 23:36:35 -0000

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

For the women at IETF, we are holding the networking lunch in one of the
conference rooms (Hullet) on Thursday, noon-13:30.

In case you are unaware, we are an official community of the AnitaB.org
Systers, and this gathering of women at IETF started in the mid-90s.  Our
lunches are very generously sponsored by Cisco, Comcast, Dell and, new
sponsor Fastly! Many thanks to our sponsors!

Please join in.  Add yourself to the headcount at
https://doodle.com/poll/nmqxdbirm7z3gkc8

We are looking forward to your joining and to seeing you in the meetings at
at the mics all week.

--94eb2c076d2ae79908055dbd8120
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">For the women at IETF, we are holding the networking lu=
nch in one of the conference rooms (Hullet) on Thursday, noon-13:30.<br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif">In case you are unaware, we are an official community of=
 the AnitaB.org Systers, and this gathering of women at IETF started in the=
 mid-90s.=C2=A0 Our lunches are very generously sponsored by Cisco, Comcast=
, Dell and, new sponsor Fastly! Many thanks to our sponsors!<br></div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><b=
r></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif">Please join in.=C2=A0 Add yourself to the headcount at <a href=
=3D"https://doodle.com/poll/nmqxdbirm7z3gkc8">https://doodle.com/poll/nmqxd=
birm7z3gkc8</a></div><div class=3D"gmail_default" style=3D"font-family:aria=
l,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif">We are looking forward to your joining=
 and to seeing you in the meetings at at the mics all week.</div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br></d=
iv><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-s=
erif"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,hel=
vetica,sans-serif"><br></div></div>

--94eb2c076d2ae79908055dbd8120--


From nobody Sat Nov 11 21:16:29 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 5FBC1128D8B; Sat, 11 Nov 2017 21:16:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba <barryleiba@computer.org>
To: <secdir@ietf.org>
Cc: draft-ietf-tcpinc-tcpcrypt.all@ietf.org, tcpinc@ietf.org, ietf@ietf.org
Subject: Secdir telechat review of draft-ietf-tcpinc-tcpcrypt-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.65.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151046377334.30804.5873766900092971520@ietfa.amsl.com>
Date: Sat, 11 Nov 2017 21:16:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xTkXWPnTzpRbNCmmUGqN4NRfrl0>
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, 12 Nov 2017 05:16:13 -0000

Reviewer: Barry Leiba
Review result: Has Issues

I’ve looked at Stephen Kent’s review and the discussion thereof, and have
little to add to that.  A couple of small things:

1. Section 3 says that the subsections “describes the tcpcrypt protocol at an
abstract level.”  There is no sense in which this description is abstract, and
I’d prefer that we not try to say it is, because that gives a reader an
expectation that it will be high-level, and perhaps even non-normative.  Maybe
this?:

NEW
   This section provides details of the operation of the tcpcrypt protocol.
   The wire format of all messages is specified in Section 4.
END

2. In Section 7 (IANA), you say:

   Tcpcrypt's TEP identifiers will need to be incorporated in IANA's
   "TCP encryption protocol identifiers" registry under the
   "Transmission Control Protocol (TCP) Parameters" registry

I can find no such registry.  Can you help me here, maybe give me a URL?

Also, with respect to the new “tcpcrypt AEAD Algorithm" registry:

   Future assignments are to be made under the "RFC Required" policy

Note that that policy allows for assignments to be made in any RFC stream,
which includes the IRTF, the IAB, and the Independent Stream.  Do you really
want people to be able to send documents to the Independent Stream Editor, and
to have them published and make assignments with minimal review?

You might consider whether “IETF Review” is more appropriate.  That allows RFCs
of any type (Standards Track, Informational, Experimental, BCP), but requires
that they be in the IETF stream and have a formal IETF last call.

It will also help IANA if you make it clear what the valid range of values is
for the “Value” column.  Is 0x0000 valid?  Is 0xFFFF the maximum?  Explicitly
saying that values must be in the range 0x0001 to 0xFFFF inclusive will be
helpful.  (I say this with particular note that you changed how the Value field
is specified between -07 and -09, so this clearly has not even been clear to
the spec developers.)


From nobody Sat Nov 11 21:19:47 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 2EA4A128B91; Sat, 11 Nov 2017 21:19:31 -0800 (PST)
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 VJGjUdtB_E1s; Sat, 11 Nov 2017 21:19:29 -0800 (PST)
Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::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 95B56128D3E; Sat, 11 Nov 2017 21:19:29 -0800 (PST)
Received: by mail-pg0-x233.google.com with SMTP id l19so7784937pgo.2; Sat, 11 Nov 2017 21:19:29 -0800 (PST)
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=5VpjUPYYERkVocaodmXPQR6SmYvPX70PyPIlHugKAOo=; b=ParOv9H3AIdhNpNeHqce1QnmVKIkwXTG1JgDbQcCgacP3KCuQzZrXdlu1gPUXCIXz4 ajJ+O8qtBeMp1vjfZ+zzfpiFAJnN9aWsmb2PwEEBJC+Fz3AWYs1e9go2qo6bs9S06iuB QPllVRh4WZvMo8NAPG4C7TVPqIEMkMjxnC/ACt/pg1llRwdpBu52Tdx4CSq+rmkBUD6+ NlnswiRLIxT0Rff6u2x8QO0yCKDoutyQTArgI1IWOdVkc6Rvo0J5PJZsgX/A9SPo8gd8 Rv8l1vBoR4SEh5RFwcNdaeVUUaQ20bbzZT1Jrfsz+7RnOeJrJaA7cFC9m7LTM5gk8fiF qOJw==
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=5VpjUPYYERkVocaodmXPQR6SmYvPX70PyPIlHugKAOo=; b=GRFtK4Dtf6JwkgOKUoBj8+L9hnBkD9pkxdi2FDkeDbWsztphdYv/jsRIMJLOtQavOg DRiYIG8AhND3Qo8TlIhAaTheEdh+pV2IrN+FY+LzfWsGaknGup32XFzn8QghoINhVkbe edAKkVdl+aLKflCJ1xK0wPA/JVsDRRG0IiT2ysplYKKDSxwjeup5+6yWBLUBlHHzr3bR QNw91GzVmcmva7E4lq/NtsIBMgzoCYtcVECgs+A1CGb2M/tZYWeIrxtb4TDm6XWQLj6F yAC11aAsf3w9aX4v9laMcr+g9SwKXsvEnX9Kwoct+Q6n/f7hgUdZJ4/xZ5/YQM0YzgM4 U+Ug==
X-Gm-Message-State: AJaThX7tzjM0AsiFOhW4IDhqrEq6jmQrxzUv9QTfdpcBNxxtsjjtoa+E UWA6IvFhyqEEQH9tZBhoLxd8vnBBFxmIYmlYsQk=
X-Google-Smtp-Source: AGs4zMbYT8WqH4t1dIj5eBcC4JVoS8nTzmESYgs7T53gDAMnPfwWkQnsVZkEhB01Vx+vWQ7RehkeCvCUwGRZaCZ5pag=
X-Received: by 10.99.117.70 with SMTP id f6mr1725266pgn.339.1510463968997; Sat, 11 Nov 2017 21:19:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.155.9 with HTTP; Sat, 11 Nov 2017 21:18:48 -0800 (PST)
In-Reply-To: <151046377334.30804.5873766900092971520@ietfa.amsl.com>
References: <151046377334.30804.5873766900092971520@ietfa.amsl.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Sun, 12 Nov 2017 00:18:48 -0500
Message-ID: <CAHbuEH6Cthy8FAXL2ftJHTV7sWMN46EP1wMSmGATep4=_7syhw@mail.gmail.com>
Subject: Re: [tcpinc] Secdir telechat review of draft-ietf-tcpinc-tcpcrypt-09
To: Barry Leiba <barryleiba@computer.org>, "iesg@ietf.org" <iesg@ietf.org>
Cc: "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-tcpinc-tcpcrypt.all@ietf.org,  tcpinc@ietf.org, 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/d0PfayhGxCsL6r9Zoca7l9_rJrc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Nov 2017 05:19:31 -0000

Barry,

Thank you for your review.

Kathleen

On Sun, Nov 12, 2017 at 12:16 AM, Barry Leiba <barryleiba@computer.org> wro=
te:
> Reviewer: Barry Leiba
> Review result: Has Issues
>
> I=E2=80=99ve looked at Stephen Kent=E2=80=99s review and the discussion t=
hereof, and have
> little to add to that.  A couple of small things:
>
> 1. Section 3 says that the subsections =E2=80=9Cdescribes the tcpcrypt pr=
otocol at an
> abstract level.=E2=80=9D  There is no sense in which this description is =
abstract, and
> I=E2=80=99d prefer that we not try to say it is, because that gives a rea=
der an
> expectation that it will be high-level, and perhaps even non-normative.  =
Maybe
> this?:
>
> NEW
>    This section provides details of the operation of the tcpcrypt protoco=
l.
>    The wire format of all messages is specified in Section 4.
> END
>
> 2. In Section 7 (IANA), you say:
>
>    Tcpcrypt's TEP identifiers will need to be incorporated in IANA's
>    "TCP encryption protocol identifiers" registry under the
>    "Transmission Control Protocol (TCP) Parameters" registry
>
> I can find no such registry.  Can you help me here, maybe give me a URL?
>
> Also, with respect to the new =E2=80=9Ctcpcrypt AEAD Algorithm" registry:
>
>    Future assignments are to be made under the "RFC Required" policy
>
> Note that that policy allows for assignments to be made in any RFC stream=
,
> which includes the IRTF, the IAB, and the Independent Stream.  Do you rea=
lly
> want people to be able to send documents to the Independent Stream Editor=
, and
> to have them published and make assignments with minimal review?
>
> You might consider whether =E2=80=9CIETF Review=E2=80=9D is more appropri=
ate.  That allows RFCs
> of any type (Standards Track, Informational, Experimental, BCP), but requ=
ires
> that they be in the IETF stream and have a formal IETF last call.
>
> It will also help IANA if you make it clear what the valid range of value=
s is
> for the =E2=80=9CValue=E2=80=9D column.  Is 0x0000 valid?  Is 0xFFFF the =
maximum?  Explicitly
> saying that values must be in the range 0x0001 to 0xFFFF inclusive will b=
e
> helpful.  (I say this with particular note that you changed how the Value=
 field
> is specified between -07 and -09, so this clearly has not even been clear=
 to
> the spec developers.)
>
> _______________________________________________
> Tcpinc mailing list
> Tcpinc@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpinc



--=20

Best regards,
Kathleen


From nobody Sun Nov 12 04:02:32 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 308FD12940E for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 04:02:31 -0800 (PST)
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 UNxRdxikAgLX for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 04:02:28 -0800 (PST)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) (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 6051F1292D3 for <ietf@ietf.org>; Sun, 12 Nov 2017 04:02:28 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id B8CD231D12; Sun, 12 Nov 2017 13:02:25 +0100 (CET)
Received: by godin (Postfix, from userid 1000) id A861BEC0B85; Sun, 12 Nov 2017 12:55:10 +0100 (CET)
Date: Sun, 12 Nov 2017 19:55:10 +0800
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive  Encryption on Operators) to Informational RFC
Message-ID: <20171112115510.GA29392@laperouse.bortzmeyer.org>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com>
X-Transport: UUCP rules
X-Operating-System: Ubuntu 16.04 (xenial)
X-Charlie: Je suis Charlie
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5NSillnJFlg8vopJYugAF2B2D7Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Nov 2017 12:02:31 -0000

On Mon, Nov 06, 2017 at 06:06:50AM -0800,
 The IESG <iesg-secretary@ietf.org> wrote 
 a message of 37 lines which said:

> The IESG has received a request from an individual submitter to
> consider the following document: - 'Effect of Pervasive Encryption
> on Operators' <draft-mm-wg-effect-encrypt-13.txt> as Informational
> RFC

I'm quite concerned by this document. Basically, it seems to me it
deviates a lot from a simple description of current practices, and
goes into promoting them. The overall effect seems to me very
dangerous. One can easily read this document as "encryption is a pain
for the operators, we should not promote it too agressively".

My opinion is that its publication as it is would inflict real harm to
the efforts of IETF to promote privacy (which implies, among other
things, a lot of encryption).

The document also completely ignores network neutrality, not to
mention the end-to-end principle.

More precisely:

> This document discusses practices currently used by network
> operators to manage, operate, and secure their networks

Actually, it does not "discuss": it describes them, using only the
arguments of the operators that use these practices, rarely
questioning them.

> the impact of pervasive encryption

Note that we are far from "pervasive encryption". For instance, the
DNS traffic is almost entirely in clear (RFC 7858). 

> For example, the traffic patterns between server and browser are
> dependent on browser supplier and version

That's a good example of why HTTP sessions must be encrypted: the
User-Agent: field is very revealing, among other infos sent by the
browser, as exemplified by the Panopticlick
<https://panopticlick.eff.org/>

> Network operators use packet captures and protocol-dissecting
> analyzers when responding to customer problems,

Not all network operators are so benevolent. I doubt that many 30 $ or
25 € / month ISP use tcpdump when the customer has a
problem :-) Seriously, this sentence is very dangerous because of:

> The ability to identify the problem application's traffic is
> important and deep packet inspection (DPI) is often used for this
> purpose

This really looks like an attempt to "sell" DPI by explaining that it
may benefit the users. Actually, I would like to see my ISP going into
such efforts to help me but I doubt it will be the case. 

Note that no ISP document the practices it actually use against user
flows. This is sufficient proof that they are not done in the interest
of the users.

> For example, by investigating packet loss (from TCP sequence and
> acknowledgement numbers), round-trip-time (from TCP timestamp
> options or application-layer transactions, e.g., DNS or HTTP
> response time), TCP receive-window size, packet corruption,
> inefficient fragmentation, or application-layer problems, the
> operator can narrow the problem

Almost all of these investigations can be performed even if TLS or SSH
is used. Again, it really seems an effort to make DPI acceptable.

> Because of this, application server operators using increased
> encryption should expect to be called upon more frequently to assist
> with debugging and troubleshooting

Hard to read this as something else than a threat "do not use
encryption or your business will suffer".

> A common, early trigger for DDoS mitigation includes observing
> uncharacteristic traffic volumes or sources; congestion; or
> degradation of a given network or service.  One approach to mitigate
> such an attack involves distinguishing attacker traffic from
> legitimate user traffic.

Are there really dDoS attacks using encryption? Hard data welcome.

> Mobile networks especially rely on content/application based
> prioritization of Over-the-Top (OTT) services

This is a very important point: if encryption really prevents
prioritization of some services over the others, then it means we need
more encryption, not less. If encryption can help preserve network
neutrality, this is a good reason to use it even more.

> Due to the characteristics of the mobile link, performance-enhancing
> TCP proxies may perform local retransmission at the mobile edge.  In
> TCP, duplicated ACKs are detected and potentially concealed when the
> proxy retransmits a segment

Again, TLS or SSH do not prevent this sort of hacks.

> In addition to caching, various applications exist to provide data
> compression in order to conserve the life of the user's mobile data
> plan and optimize delivery over the mobile link

I know that some mobile operators (see, in french,
<https://www.hteumeuleu.fr/la-compression-dimages-par-les-operateurs/>)
apply a LOSSY compression without the user consent or even
knowledge. Again, if end-to-end encryption prevents this, this is a
very good reason to deploy encryption.

> These regulations include Lawful Intercept, adherence to Codes of
> Practice on content filtering, and application of court order
> filters.  Such regulations assume network access to provide content
> filtering and accounting, as discussed below.

It seems to me that RFC 1984 already replies to this reasoning.

> This type of granular filtering could occur at the endpoint.
> However, the lack of ability to efficiently manage endpoints as a
> service reduces providers' ability to offer parental control.

I would be specially unhappy if IETF were to publish a RFC with such a
sentence without follow-up comments. Filtering MUST be done at the
endpoint, otherwise it is not a service, it is censorship.

If we assume that the subscriber wants parental control, then we must
conclude that he/she will have no problem sending the traffic to a
filtering proxy. No need to break encryption for that.

> Some mobile carriers use HTTP header insertion (see section 3.2.1 of
> [RFC7230]) to provide information about their customers to third
> parties or to their own internal systems [Enrich].

Again, this technique, which has very serious privacy consequences
(see the mentioned reference [Enrich] with for example Vodafone which
added the phone number and the IMEI in HTTP headers) MUST NOT be done
and, if encryption stops it, great.

Editorial issues:

> Currently, some mobile network service providers redirect the
> customer using HTTP redirect to a page that explains to those
> customers the reason for the blockage and the steps to proceed

A mention of RFC 6108 would be cool here.

> monitor incoming mail to remove SPAM

Why is spam uppercased?


From nobody Sun Nov 12 05:02:20 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 303F912778D for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 05:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jiIFUck2vSCa for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 05:02:16 -0800 (PST)
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 90B221200F1 for <ietf@ietf.org>; Sun, 12 Nov 2017 05:02:16 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3yZYnx1gHLz37q; Sun, 12 Nov 2017 14:02:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1510491733; bh=XBHO8WbRQRZn0VYj+g9PU3dUdhMf47tOQk6HpWs2yTo=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=Y+m5aoeS6Gq4/5YM1mVmN/uhlt9zY3hSFF3CWebOVvr+yReTnldFOmeyrz5a4JdnM rUS76rc8IOghWn+Bbllb01z1nRuuEA+kuK8nOsBpM1LjHRTbwdCc5oZUoeeji6qELQ EBZ70MzPIridHj8kC65UuXr90KW9VG7Tbj+2WvEI=
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 6Sr2B9cQGmOh; Sun, 12 Nov 2017 14:02:10 +0100 (CET)
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; Sun, 12 Nov 2017 14:02:10 +0100 (CET)
Received: from [10.10.12.218] (unknown [103.26.221.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id A2D5062D29; Sun, 12 Nov 2017 08:02:08 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca A2D5062D29
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (15A432)
In-Reply-To: <20171112115510.GA29392@laperouse.bortzmeyer.org>
Date: Sun, 12 Nov 2017 21:02:04 +0800
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IT0-BB1gZwAl7160spzFm-H7hgk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Nov 2017 13:02:19 -0000

I concur with most of Stephane=E2=80=99s comments. And I find the use of the=
 term =E2=80=9Cpervasive encryption=E2=80=9D very problematic. Pervasive mea=
ns:

=E2=80=9C(especially of an unwelcome influence or physical effect) spreading=
 widely throughout an area or a group of people.=E2=80=9D

More encryption is never unwelcome to the enduser.

If this document listed these practises, along with valid methods for operat=
ors to switch to, i could be convinced the document is useful. But as Stepha=
ne pointed out, a lot of these problems are desired features. That the opera=
tor has less networking debugging tools is an unavoidable side effect, but s=
hould not be used as an argument against more encryption.

But in its current form, it seems this document would be prime candidate for=
 operator misbehaviour justification =E2=80=9Csanctioned=E2=80=9D by the IET=
F.=20

Note that I _do_ believe in the authors=E2=80=99 good intention of just docu=
menting the new problems operators face. But the IETF will have taken these i=
ssues into consideration already before it published the RFCs.

This documents feels (unintentionally) that we need to go back to be drawing=
 board to reconsider these operator issues.

Paul

> On Nov 12, 2017, at 19:55, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>=20
> On Mon, Nov 06, 2017 at 06:06:50AM -0800,
> The IESG <iesg-secretary@ietf.org> wrote=20
> a message of 37 lines which said:
>=20
>> The IESG has received a request from an individual submitter to
>> consider the following document: - 'Effect of Pervasive Encryption
>> on Operators' <draft-mm-wg-effect-encrypt-13.txt> as Informational
>> RFC
>=20
> I'm quite concerned by this document. Basically, it seems to me it
> deviates a lot from a simple description of current practices, and
> goes into promoting them. The overall effect seems to me very
> dangerous. One can easily read this document as "encryption is a pain
> for the operators, we should not promote it too agressively".
>=20
> My opinion is that its publication as it is would inflict real harm to
> the efforts of IETF to promote privacy (which implies, among other
> things, a lot of encryption).
>=20
> The document also completely ignores network neutrality, not to
> mention the end-to-end principle.
>=20
> More precisely:
>=20
>> This document discusses practices currently used by network
>> operators to manage, operate, and secure their networks
>=20
> Actually, it does not "discuss": it describes them, using only the
> arguments of the operators that use these practices, rarely
> questioning them.
>=20
>> the impact of pervasive encryption
>=20
> Note that we are far from "pervasive encryption". For instance, the
> DNS traffic is almost entirely in clear (RFC 7858).=20
>=20
>> For example, the traffic patterns between server and browser are
>> dependent on browser supplier and version
>=20
> That's a good example of why HTTP sessions must be encrypted: the
> User-Agent: field is very revealing, among other infos sent by the
> browser, as exemplified by the Panopticlick
> <https://panopticlick.eff.org/>
>=20
>> Network operators use packet captures and protocol-dissecting
>> analyzers when responding to customer problems,
>=20
> Not all network operators are so benevolent. I doubt that many 30 $ or
> 25 =E2=82=AC / month ISP use tcpdump when the customer has a
> problem :-) Seriously, this sentence is very dangerous because of:
>=20
>> The ability to identify the problem application's traffic is
>> important and deep packet inspection (DPI) is often used for this
>> purpose
>=20
> This really looks like an attempt to "sell" DPI by explaining that it
> may benefit the users. Actually, I would like to see my ISP going into
> such efforts to help me but I doubt it will be the case.=20
>=20
> Note that no ISP document the practices it actually use against user
> flows. This is sufficient proof that they are not done in the interest
> of the users.
>=20
>> For example, by investigating packet loss (from TCP sequence and
>> acknowledgement numbers), round-trip-time (from TCP timestamp
>> options or application-layer transactions, e.g., DNS or HTTP
>> response time), TCP receive-window size, packet corruption,
>> inefficient fragmentation, or application-layer problems, the
>> operator can narrow the problem
>=20
> Almost all of these investigations can be performed even if TLS or SSH
> is used. Again, it really seems an effort to make DPI acceptable.
>=20
>> Because of this, application server operators using increased
>> encryption should expect to be called upon more frequently to assist
>> with debugging and troubleshooting
>=20
> Hard to read this as something else than a threat "do not use
> encryption or your business will suffer".
>=20
>> A common, early trigger for DDoS mitigation includes observing
>> uncharacteristic traffic volumes or sources; congestion; or
>> degradation of a given network or service.  One approach to mitigate
>> such an attack involves distinguishing attacker traffic from
>> legitimate user traffic.
>=20
> Are there really dDoS attacks using encryption? Hard data welcome.
>=20
>> Mobile networks especially rely on content/application based
>> prioritization of Over-the-Top (OTT) services
>=20
> This is a very important point: if encryption really prevents
> prioritization of some services over the others, then it means we need
> more encryption, not less. If encryption can help preserve network
> neutrality, this is a good reason to use it even more.
>=20
>> Due to the characteristics of the mobile link, performance-enhancing
>> TCP proxies may perform local retransmission at the mobile edge.  In
>> TCP, duplicated ACKs are detected and potentially concealed when the
>> proxy retransmits a segment
>=20
> Again, TLS or SSH do not prevent this sort of hacks.
>=20
>> In addition to caching, various applications exist to provide data
>> compression in order to conserve the life of the user's mobile data
>> plan and optimize delivery over the mobile link
>=20
> I know that some mobile operators (see, in french,
> <https://www.hteumeuleu.fr/la-compression-dimages-par-les-operateurs/>)
> apply a LOSSY compression without the user consent or even
> knowledge. Again, if end-to-end encryption prevents this, this is a
> very good reason to deploy encryption.
>=20
>> These regulations include Lawful Intercept, adherence to Codes of
>> Practice on content filtering, and application of court order
>> filters.  Such regulations assume network access to provide content
>> filtering and accounting, as discussed below.
>=20
> It seems to me that RFC 1984 already replies to this reasoning.
>=20
>> This type of granular filtering could occur at the endpoint.
>> However, the lack of ability to efficiently manage endpoints as a
>> service reduces providers' ability to offer parental control.
>=20
> I would be specially unhappy if IETF were to publish a RFC with such a
> sentence without follow-up comments. Filtering MUST be done at the
> endpoint, otherwise it is not a service, it is censorship.
>=20
> If we assume that the subscriber wants parental control, then we must
> conclude that he/she will have no problem sending the traffic to a
> filtering proxy. No need to break encryption for that.
>=20
>> Some mobile carriers use HTTP header insertion (see section 3.2.1 of
>> [RFC7230]) to provide information about their customers to third
>> parties or to their own internal systems [Enrich].
>=20
> Again, this technique, which has very serious privacy consequences
> (see the mentioned reference [Enrich] with for example Vodafone which
> added the phone number and the IMEI in HTTP headers) MUST NOT be done
> and, if encryption stops it, great.
>=20
> Editorial issues:
>=20
>> Currently, some mobile network service providers redirect the
>> customer using HTTP redirect to a page that explains to those
>> customers the reason for the blockage and the steps to proceed
>=20
> A mention of RFC 6108 would be cool here.
>=20
>> monitor incoming mail to remove SPAM
>=20
> Why is spam uppercased?


From nobody Sun Nov 12 05:58:29 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 29BAC1200F1; Sun, 12 Nov 2017 05:58:18 -0800 (PST)
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 6Mse0zZDExgJ; Sun, 12 Nov 2017 05:58:14 -0800 (PST)
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 2F74612943D; Sun, 12 Nov 2017 05:58:13 -0800 (PST)
Received: by mail-lf0-x22b.google.com with SMTP id f125so15543008lff.4; Sun, 12 Nov 2017 05:58:13 -0800 (PST)
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=/naX3oES0R7Ybb4YENrJslXxhpQzCSv+HT3GwIItG8E=; b=SjSHZ7xS/RApD+eueQoxvSHvNQ+ar9xRFKVGCaEW+X4TED7JuiJKejAkcK5Ca8pvuR fBJMpaybmMAal/+DdYcneKdQUrJrLwsrNqOkkY1RyCkTZtU9XkKif/Blmwm4aLVWeckH eCpmymQxhHHEuNHymNdCL9o7lYZNK57X7ToPHoH4W16Pr2bEcJRy2cUgSQf13WUxF3zg cSdCcu3EJJwINIZzWBQ5M6b4D2otFwFScJ5a0BPRGWIhdyqM57PKJpfwp3Uo2B7Pprzf nmAEezDU3RtpuplibtrDQHvw0zn57QvPj5aMnUhQtIKPUfqAXVb2/Gg6HQ4R7lrgIvki H7Rw==
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=/naX3oES0R7Ybb4YENrJslXxhpQzCSv+HT3GwIItG8E=; b=HTXiPp0SU+JugEgs7QudbLqhJE1wEAzucfGZXH8BQQD/u64I4tLmDjisN776SoLVww /AcMVNwsYOR9eQ6osnnKI4I5WQ4LwfLUh0Nmvl6WD+8+x6AJvcld+38oNlERJ8onC93h yu0h39zVnj1NADV8L4x5FMtnIE5+XMWRX4tGau32HmLL+4eRoNNj4fH1tu8MLmKYVp1o hl9F82EglBLLaAx0+lhw3Df6E8AoiLib65EDTDMhlylPgYnUOxNgNRzFZXWyHUn6a4D3 tJoH++W4TQ5FlaZQ471St07JWvOD0FWOleoMUrOoEKoLmDt6KT7MuXhVoFz0NFT/Yf3/ WQOA==
X-Gm-Message-State: AJaThX4zUmXvqIyxM9EnkzDz/NDHYFts8LXlN+vm+THEeYT0dOq6Lsv7 03m56xVFgSxB2sC7M6I1JDVf53CyJnjTyy+Cq9Y=
X-Google-Smtp-Source: AGs4zMYWYO1BNMFH3Kigeg7Q7uWDJ1Y8dqLA7lBY6qA+shNXNHrGEB3j1G3y1xFxGJRJ81A/JW7+1WDl1MzJEp2oGHY=
X-Received: by 10.25.193.75 with SMTP id r72mr1601254lff.47.1510495090397; Sun, 12 Nov 2017 05:58:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.46.32.147 with HTTP; Sun, 12 Nov 2017 05:58:09 -0800 (PST)
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Sun, 12 Nov 2017 21:58:09 +0800
Message-ID: <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com>
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
To: Qin Wu <bill.wu@huawei.com>, "iesg@ietf.org" <iesg@ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>,  "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>,  Carlos Pignataro <cpignata@cisco.com>, Ron Bonica <rbonica@juniper.net>,  "lime-chairs@ietf.org" <lime-chairs@ietf.org>, Benoit Claise <bclaise@cisco.com>, "lime@ietf.org" <lime@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c19c5ec4c58e8055dc98b9f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cuSSmCVa1dUPzODINI7jINXeZpo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Nov 2017 13:58:18 -0000

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

Dear All,
I was under impression that that question of oam-neighboring-tps has been
discussed and since authors couldn't produce technical rationale for this
object we've agreed that it will be removed altogether from the grouping
connectionless-oam-tps. But authors just changed name from level to
position but had missed to synchronize descriptions in the model and in
section 3.3. The later still refers to vertical layers:

                     "List of related neighboring test points in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.";

while the model insists that it is peering relationship:

        description
          "The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current

           test point in the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.";

So, what is it? Perhaps it is time to remove list oam-neighboring-tps
altogether also because having it s fixed size list is plain wrong. (Sorry
for being so blunt but I commented too many times on the same to no avail
from the authors).

Regards,
Greg

On Thu, Oct 26, 2017 at 9:26 AM, Qin Wu <bill.wu@huawei.com> wrote:

> Thanks Greg, will consider that.
>
>
>
> -Qin
>
> *=E5=8F=91=E4=BB=B6=E4=BA=BA:* Greg Mirsky [mailto:gregimirsky@gmail.com]
> *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2017=E5=B9=B410=E6=9C=8825=E6=97=
=A5 20:55
> *=E6=94=B6=E4=BB=B6=E4=BA=BA:* Qin Wu
> *=E6=8A=84=E9=80=81:* ietf@ietf.org; draft-ietf-lime-yang-connectionless-=
oam@ietf.org;
> Carlos Pignataro; Ron Bonica; lime-chairs@ietf.org; Benoit Claise;
> lime@ietf.org
> *=E4=B8=BB=E9=A2=98:* Re: [Lime] Last Call: <draft-ietf-lime-yang-connect=
ionless-oam-11.txt>
> (Generic YANG Data Model for Connectionless Operations, Administration, a=
nd
> Maintenance(OAM) protocols) to Proposed Standard
>
>
>
> Hi Qin,
>
> thank you for your thoughtful consideration of my comments.
>
> I agree to leave mechanism of overrun indication to implementation but I
> believe that it will be really helpful to add a sub-section that highligh=
ts
> specific of running tests in forever mode and points to issues that requi=
re
> particular attention.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Tue, Oct 24, 2017 at 8:06 PM, Qin Wu <bill.wu@huawei.com> wrote:
>
> Thanks Greg for feedback, please see my reply inline below.
>
> *=E5=8F=91=E4=BB=B6=E4=BA=BA:* Greg Mirsky [mailto:gregimirsky@gmail.com]
> *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2017=E5=B9=B410=E6=9C=8824=E6=97=
=A5 23:18
> *=E6=94=B6=E4=BB=B6=E4=BA=BA:* Qin Wu
> *=E6=8A=84=E9=80=81:* ietf@ietf.org; draft-ietf-lime-yang-connectionless-=
oam@ietf.org;
> Carlos Pignataro; Ron Bonica; lime-chairs@ietf.org; Benoit Claise;
> lime@ietf.org
>
> *=E4=B8=BB=E9=A2=98:* Re: [Lime] Last Call: <draft-ietf-lime-yang-connect=
ionless-oam-11.txt>
> (Generic YANG Data Model for Connectionless Operations, Administration, a=
nd
> Maintenance(OAM) protocols) to Proposed Standard
>
>
>
> Hi Qin,
>
> thank you for your expedient and careful consideration of my comments. I'=
m
> glad that we've already in agreement on so many. I've added notes on thos=
e
> that, in my view, need some more discussions. Please find them in-line
> tagged GIM>>.
>
>
>
> Regards,
>
> Greg
>
>
>
> On Sun, Oct 22, 2017 at 8:31 PM, Qin Wu <bill.wu@huawei.com> wrote:
>
> Thanks Greg for providing additional input to help make the model more
> extensible and reusable.
>
> Please see my reply inline below.
>
>
>
> -Qin
>
> *=E5=8F=91=E4=BB=B6=E4=BA=BA:* Greg Mirsky [mailto:gregimirsky@gmail.com]
> *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4:* 2017=E5=B9=B410=E6=9C=8820=E6=97=
=A5 20:34
> *=E6=94=B6=E4=BB=B6=E4=BA=BA:* ietf@ietf.org; draft-ietf-lime-yang-connec=
tionless-oam@ietf.org
> *=E6=8A=84=E9=80=81:* Carlos Pignataro; Ron Bonica; lime-chairs@ietf.org;=
 Benoit Claise;
> lime@ietf.org
> *=E4=B8=BB=E9=A2=98:* Re: [Lime] Last Call: <draft-ietf-lime-yang-connect=
ionless-oam-11.txt>
> (Generic YANG Data Model for Connectionless Operations, Administration, a=
nd
> Maintenance(OAM) protocols) to Proposed Standard
>
>
>
> Dear All,
>
> please kindly consider my comments on draft-ietf-lime-yang-connectionless=
-oam
> presented below:
>
>    - 1. Introduction
>
>
>    - clear and technical definitions of connection-oriented (CO) and
>       connectionless (CL) network are absent. Note that referenced RFC 72=
76 does
>       not provide that either as differentiation based on amount of confi=
guration
>       required to instantiate a network changes, decreases as result of f=
urther
>       progress in network operation automation. I propose to use definiti=
ons CO
>       and CL forwarding paradigms provided in section 6.3.1 G.800 Unified
>       functional architecture of transport networks, as these are clear,
>       technical and are broadly used in the industry.
>
> [Qin]: I believe RFC7276 and G.800 share the similar paradigms but captur=
e
> the different aspect of the key difference between CO and CL, I would
> suggest to harmonize the different aspect of these key differences togeth=
er
> and add another reference to G.800 as follows:
>
> NEW TEXT:
>
> =E2=80=9C
>
> In connection-oriented technologies,
>
>    a connection is established prior to the transmission of data.  After
>
>    connection is established, no additional control information such as
>
>    signaling or operations and maintenance information is required to
>
>    transmit the data.  In connectionless technologies, data is
>
>    typically sent between end points without prior arrangement, but
>
>    control information is required to identify destination
> [G.800][RFC7276].
>
> =E2=80=9D
>
> GIM>> If we consider, for example, MPLS-TP domain and L3VPN over IP/MPLS
> domain, then the configuration aspect, in my opinion, becomes less distin=
ct
> while the forwarding paradigm is invariant, remains the same.
>
>
>
> [Qin]: Thanks.
>
>
>    - characterization of the subject of the document as "YANG Data model
>       for connectionless OAM protocols" is not accurate considering CO/CL
>       definitions in G.800. I propose to refer to "OAM protocols for
>       connectionless networks" since the same OAM protocols may be used i=
n both
>       CO-PS and CL-PS networks, e.g. LSP Ping used in both MPLS-TP and IP=
/MPLS
>       networks.
>
>       [Qin]: Okay ,Sounds good to me.
>
>    - 3. Overview of the Connectionless OAM Model
>
>
>    - "... the 'test-point-location-info', is a common aspect of every
>       'test-point-location' - there's no YANG object test-point-location =
in the
>       presented data model.
>
>    [Qin]: It is Typo. It should be =E2=80=98test-point-locations=E2=80=99=
, fixed. Thanks.
>
>    - 3.3 OAM Neighboring Layers
>
>
>    - I find this part of the model under-developed. First, the
>       terminology - layers imply vertical, client-server relationship whi=
le
>       downstream/upstream - peering relationship on the same layer. Secon=
d, the
>       limited visibility due to technology-level limitation that supports=
 only
>       reference to the immediate neighboring layer but not to next-to-nex=
t
>       neighbor. I consider this to be major problem for common model that
>       intended for multi-layer environment.
>
> [Qin]: We discussed this before, I revisit this section and understand
> your concern now , I would like to suggest to remove layer related text
> since it introduce confusion, I would suggest to change technology-level
> into position since what we try to define are OAM Neighboring Test points
> list. We will focus on test points related to one single layer. One can u=
se
> position to capture of order of these test points and also identify test
> point at the left layer boundary and test point at the right layer
> boundary. The proposed changes as follows:
>
> =E2=80=9C
>
> 3.3.  OAM neighboring test points
>
>
>
>    As typical networks have a multi-layer architecture, the set of OAM
>
>    protocols similarly take a multi-layer structure; each layer may has
>
>    its own OAM protocol [RFC7276] and is corresponding to specific
>
>    administrative domain and has associated test points.  OAM
>
>    neighboring test points are referred to a list of neighboring test
>
>    points in the same layer that are related to current test point.
>
>    This allows users to easily navigate between related neighboring
>
>    layer to efficiently troubleshoot a defect.  In this model,
>
>    'position' leaf defines the relative position of neighboring test
>
>    point corresponding to the current test point in the same layer , and
>
>    is provided to allow correlation of faults at different location . If
>
>    there is one neighboring test point placed before the current test
>
>    point, 'position' leaf is set to -1.  If there is one neighboring
>
>    test point placed after the current test point, 'position' leaf is
>
>    set to 1.  If there is no neighboring test point placed before or
>
>    after the current test point, 'position' leaf is set to 0.
>
>
>
>                 list oam-neighboring-tps {
>
>                   key "index";
>
>                   leaf index {
>
>                      type uint16 {
>
>                         range "0..65536";
>
>                      }
>
>                     description
>
>                      "Index of a list of neighboring test points
>
>                       in the same layer ";
>
>                   }
>
>                   leaf position {
>
>                       type int8 {
>
>                            range "-1..1";
>
>                       }
>
>                       description
>
>                         "The relative position
>
>                         of neighboring test point
>
>                         corresponding to the current
>
>                         test point";
>
>                   }
>
>                   description
>
>                      "List of related neighboring test points in the same
> layer.";
>
>               }
>
> =E2=80=9D
>
> GIM>> I think that if we concentrate on OAM on particular network layer,
> then reference to multi-layer character of modern networks is unnecessary
> and somewhat artificial. As for test points in the same layer, then
> traceroute suppose to return ordered list of Test Points between the Send=
er
> and Receiver. Because there could be ECMP sub-domains along the path, mod=
el
> should be able to differentiate with some entropy key. OAM visibility int=
o
> other administrative domains obviously brings security consideration issu=
es
> and, I'd expect, be carefully controlled and try to hide identity of the
> domain. Hence, I think that 'position' is hardly usable parameter.
>
>
>
> [Qin]: Thanks for your comments on this, yes recording test point list in
> the same layer is not good use case, harmonizing with your comments and
> Gen-art review comments, we have removed same layer and rewrite this
> section based on Gen-art reviewer=E2=80=99s input and suggestions. Thanks=
 again.
>
>
>    - 3.4 Test Point Locations Information
>
>
>    - reference to non-existent "tp-tool" and "OAM-neighboring Layers"
>        groupings
>
>              [Qin]: It is typo, oam-neighboring layers should be correcte=
d
> as =E2=80=9Coam-neighboring-tps=E2=80=9D now.
>
>    - 4. YANG OAM Model
>
>
>    - I think that use of prefix 'coam' for data model of OAM in
>       connectionless networks is limiting considering that there should b=
e
>       another model of OAM in connection-oriented networks. Acronyms CL a=
nd CO
>       usually used to refer to connectionless and connection-oriented net=
works
>       respectively. Thus I suggest to use 'cl-oam' as prefix for the data=
 model
>       presented in this document and 'co-oam' instead of 'goam'
>       in draft-ietf-lime-yang-connection-oriented-oam-model.
>
>                 [Qin]:Good proposal, I like it.
>
>    - I find time-resolution to be superfluous and thus overcomplicating
>       the model. I suggest use time-interval-type instead and consider
>       for the update of yang:ietf-yang-types defined in RFC 6991.
>
>               [Qin]:  Time resolution is referred to time unit, sure we
> can change it into time-interval-type as you suggested.
>
> o    session-delay-statistics and session-jitter-statistics are too limit=
ing in many dimensions - no support to reflect one-way (far-end and near-en=
d) and round-trip measurements for the same test session, and too few metri=
cs., e.g. no report of percentile.
>
>              [Qin]: We have protocol-id and protocol-id-meta-data to be d=
efined in draft-ietf-lime-yang-connectionless-oam-methods-09 which can be u=
sed to indicate whether it is one way measurement, or two way
>
> measurements. Please see my reply for loss ration for report of percentil=
e.
>
> o    session-delay-statistics does not reflect type of delay variation be=
ing calculated. As analyzed in RFC 5481, PDV and IPDV characterize differen=
t conditions (Section 5) and at least reflecting which one being calculated=
 and reported is very informative.
>
>                 [Qin]: We have protocol-id and protocol-id-meta-data to b=
e defined in draft-ietf-lime-yang-connectionless-oam-methods-09 which can b=
e used to indicate whether IPDV is used or PDV is used, Based on Brian=E2=
=80=99s
>
>    suggestion, we could set IPDV as default for jitter measurement.
>
> o    I cannot find anything that directly reports packet loss statistics =
(packet loss and packet loss ratio) for the given test session. Is that int=
entional? ICMP ping is capable to report number of lost packets in round-tr=
ip.
>
>               [Qin]: We do have a parameter =E2=80=98packet-drops-count=
=E2=80=99 for packet-loss, we can change it into =E2=80=9Cpacket-loss-count=
=E2=80=9D as you suggested, in addition, we can add a new parameter for pac=
ket loss ration as follows:
>
> =E2=80=9C
>
>       leaf packet-loss-count {
>
>         type uint32 {
>
>         range "0..4294967295";
>
>         }
>
>        default "0";
>
>         description
>
>           "Total received packet drops count.
>
>           If the value is 4294967295, it indicates
>
>           packet drops count is overrun.";
>
>       }
>
>
>
>           leaf loss-ratio{
>
>                         type uint8{
>
>                                 range 0..100;
>
>                         }
>
>                 description
>
>                  "Loss ratio of the packets. Express as percentage
>
>                  of packets lost with respect to packets sent.";
>
>                 }
>
>
>
> =E2=80=9D
>
> GIM>> Packet loss and, as result, loss ratio in modern networks is very
> low. I suggest changing loss-ratio type from uint8 to new type percentage=
,
> defined as:
>
>    typedef percentage {
>
>         type decimal64 {
>
>                 fraction-digits 5;
>
>         }
>
>         description "Percentage";
>
>    }
>
>
>
> [Qin]: Good proposal, accepted.
>
>  GIM>> I think that counter overrun case indicator requires separate
> parameter. Using 4294967295 may produce negative false when running in
> forever mode.
>
>
>
> [Qin]: Note that counter  is unsigned integer, it will not produce
> negative false, in my understanding. I doubt we should add such complexit=
y
> to data model by introducing another parameter, we can leave this to
> implementation details.
>
>
>
>
>
> o    using uint32 in session-packet-statistics seems risking overrun of c=
ounters especially for test sessions running  forever.
>
> [Qin]: Good point, we could set up-limit for session-packet-statistics da=
ta, if statistics data reach up-lmit, it wil indicate counter overrun happe=
ns.
>
> o    I believe that using 0 to indicate that the parameter is not being r=
eported, throughout several statistics groupings, creates problem when the =
true value is 0, e.g. rx-bad-packet;
>
> [Qin]:Good point, we will remove to use 0 to indicate the parameter is no=
t being reported.
>
> o    connectionless-oam-layers - what considerations were discussed to ar=
rive to liming number of neighboring test points to 128?
>
> [Qin]: Okay, we can change uint8 into uint16 to support more test points =
that can be recorded. But please note that each test point actually only re=
cord his neighboring test points, if each test points record a complete
>
> List of test points in one test, that will result in a lot of duplicated =
data associated with each test point.
>
> o    tp-tools:continuity-check you may add RFC 8029 to the list of refere=
nces
>
> [Qin]: Accepted, thanks.
>
> o    tp-tools:path-discovery RFC 8029 obsoletes RFC 4379 as standard for =
LSP Ping
>
> [Qin]: Accepted, thanks.
>
> o    timestamp grouping is limited to PTPv2 Truncated and NTPv4 64-bit fo=
rmat [RFC5905]. What about other formats, e.g. ICMP Timestamp, NTPv4 32-bit=
, a.k.a. short, or PTPv2 80-bits long?
>
> [Qin]: Here is the proposed change to address your comments:
>
> =E2=80=9C
>
>   grouping timestamp {
>
>     description
>
>       "Grouping for timestamp.";
>
>     leaf timestamp-type {
>
>       type identityref {
>
>       base timestamp-type;
>
>       }
>
>       description
>
>         "Type of Timestamp, such as Truncated PTP, NTP.";
>
>     }
>
>     container timestamp-64bit {
>
>         when "derived-from-or-self(../type, 'cl-oam:truncated-ptp')"+
>
>        "or derived-from-or-self(../type,'cl-oam:ntp64')" {
>
>          description
>
>           "Only applies when Truncated NTP or 64bit NTP Timestamp.";
>
>         }
>
>       leaf timestamp-sec {
>
>       type uint32;
>
>       description
>
>         "Absolute timestamp in seconds as per IEEE1588v2
>
>          or seconds part in 64-bit NTP timestamp.";
>
>        }
>
>       leaf timestamp-nanosec {
>
>       type uint32;
>
>       description
>
>         "Fractional part in nanoseconds as per IEEE1588v2
>
>          or Fractional part in 64-bit NTP timestamp.";
>
>       }
>
>       description
>
>       "Container for 64bit timestamp.";
>
>     }
>
>     container timestamp-80bit {
>
>         when "derived-from-or-self(../type, 'cl-oam:ptp80')"{
>
>          description
>
>           "Only applies when 80bit PTP Timestamp.";
>
>         }
>
>           if-feature ptp-long-format;
>
>       leaf timestamp-sec {
>
>       type uint64 {
>
>      range "0..281474976710656";
>
>       }
>
>       description
>
>         "48bit Timestamp in seconds as per IEEE1588v2.";
>
>        }
>
>       leaf timestamp-nanosec {
>
>       type uint32;
>
>       description
>
>         "Fractional part in nanoseconds as per IEEE1588v2
>
>          or Fractional part in 64-bit NTP timestamp.";
>
>       }
>
>       description
>
>       "Container for 64bit timestamp.";
>
>     }
>
>        container ntp-timestamp-32bit {
>
>         when "derived-from-or-self(../type, 'cl-oam:truncated-ntp')"{
>
>          description
>
>           "Only applies when 32 bit NTP Short format Timestamp.";
>
>         }
>
>           if-feature ntp-short-format;
>
>       leaf timestamp-sec {
>
>       type uint16;
>
>       description
>
>         "Timestamp in seconds as per short format NTP.";
>
>        }
>
>       leaf timestamp-nanosec {
>
>       type uint16;
>
>       description
>
>         "Truncated Fractional part in 16-bit NTP timestamp.";
>
>       }
>
>       description
>
>       "Container for 64bit timestamp.";
>
>     }
>
>      container icmp-timestamp-32bit {
>
>         when "derived-from-or-self(../type, 'cl-oam:icmp-ntp')"{
>
>          description
>
>           "Only applies when Truncated NTP or 64bit NTP Timestamp.";
>
>         }
>
>           if-feature icmp-timestamp;
>
>       leaf timestamp-millisec {
>
>       type uint32;
>
>       description
>
>         "timestamp in milliseconds for ICMP timestamp.";
>
>        }
>
>       description
>
>       "Container for 32bit timestamp.";
>
>     }
>
>   }
>
>
>
> =E2=80=9D
>
>
>    - 5.1.1.2 Test point attributes extension
>
>
>    - reference to non-existing "test-point-location" list
>
> [Qin]: Same typo as you mentioned above, it should be =E2=80=9C
> test-point-locations=E2=80=9D.
>
>    - 5.1.2 Schema Mount
>
>
>    - reference to non-existing "test-point-location" list
>
> [Qin]: Same as above, fixed.
>
>    - 5.2.1.2 Test point attributes extension
>
>
>    - reference to non-existing "test-point-location" list
>
> [Qin]: Same as above, fixed.
>
>    - 5.2.2 Schema Mount
>
>
>    - reference to non-existing "test-point-location" list
>
> [Qin]: Same as above, fixed.
>
> In summary, I find several serious issues with the current version of the
> data model presented in the document, e.g. use of 0 to indicate unreporte=
d
> parameter and underdeveloped layering model.
>
>
>
> Regards,
>
> Greg
>
>
>
>
>
> On Wed, Oct 11, 2017 at 6:40 AM, The IESG <iesg-secretary@ietf.org> wrote=
:
>
>
> The IESG has received a request from the Layer Independent OAM Management
> in
> the Multi-Layer Environment WG (lime) to consider the following document:=
 -
> 'Generic YANG Data Model for Connectionless Operations, Administration,
>    and Maintenance(OAM) protocols'
>   <draft-ietf-lime-yang-connectionless-oam-11.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits fin=
al
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-10-25. 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.
>
> Abstract
>
>
>    This document presents a base YANG Data model for connectionless
>    Operations Administration, and Maintenance(OAM) protocols.  It
>    provides a technology-independent abstraction of key OAM constructs
>    for connectionless protocols.  The base model presented here can be
>    extended to include technology specific details.  This is leading to
>    uniformity between OAM protocols and support both nested OAM
>    workflows (i.e., performing OAM functions at different or same levels
>    through a unified interface) and interacting OAM workflows ( i.e.,
>    performing OAM functions at same levels through a unified interface).
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-lime-yang-
> connectionless-oam/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
> _______________________________________________
> Lime mailing list
> Lime@ietf.org
> https://www.ietf.org/mailman/listinfo/lime
>
>
>
>
>
>
>
>
>

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

<div dir=3D"ltr">Dear All,<div>I was under impression that that question of=
=C2=A0<span style=3D"color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-=
tps</span><span style=3D"color:rgb(0,0,0);font-size:13.3333px">=C2=A0has be=
en discussed and since authors couldn&#39;t produce technical rationale for=
 this object we&#39;ve agreed that it will be removed altogether from the=
=C2=A0</span><span style=3D"color:rgb(0,0,0);font-size:13.3333px">grouping =
connectionless-oam-tps. But authors just changed name from level to positio=
n but had missed to synchronize descriptions in the model and in section 3.=
3. The later still refers to vertical layers:</span></div><div><pre class=
=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-botto=
m:0px;color:rgb(0,0,0)">                     &quot;List of related neighbor=
ing test points in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.&quot;;
</pre></div><div>while the model insists that it is peering relationship:</=
div><div><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-t=
op:0px;margin-bottom:0px;color:rgb(0,0,0)">        description
          &quot;The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current
</pre></div><div><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;=
margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">           test point in=
 the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.&quot;;
</pre></div><div>So, what is it? Perhaps it is time to remove list=C2=A0<sp=
an style=3D"color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-tps altog=
ether also because having it s fixed size list is plain wrong. (Sorry for b=
eing so blunt but I commented too many times on the same to no avail from t=
he authors).</span></div><div><span style=3D"color:rgb(0,0,0);font-size:13.=
3333px"><br></span></div><div><span style=3D"color:rgb(0,0,0);font-size:13.=
3333px">Regards,</span></div><div><span style=3D"color:rgb(0,0,0);font-size=
:13.3333px">Greg</span></div></div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Thu, Oct 26, 2017 at 9:26 AM, Qin Wu <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:bill.wu@huawei.com" target=3D"_blank">bill.wu@huawei=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-6973581717679770107WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks Gre=
g, will consider that.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=
=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">-Qin<u></u=
><u></u></span></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><span class=3D""><b><span style=3D"font-size:10.0pt"=
>=E5=8F=91=E4=BB=B6=E4=BA=BA<span lang=3D"EN-US">:</span></span></b><span l=
ang=3D"EN-US" style=3D"font-size:10.0pt"> Greg Mirsky [mailto:<a href=3D"ma=
ilto:gregimirsky@gmail.com" target=3D"_blank">gregimirsky@gmail.com</a>]
<br>
</span></span><b><span style=3D"font-size:10.0pt">=E5=8F=91=E9=80=81=E6=97=
=B6=E9=97=B4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt"> 2017</span><span style=3D"font-size:10.0pt">=E5=
=B9=B4<span lang=3D"EN-US">10</span>=E6=9C=88<span lang=3D"EN-US">25</span>=
=E6=97=A5<span lang=3D"EN-US"> 20:55<br>
</span></span></p><div><div class=3D"h5"><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<spa=
n lang=3D"EN-US">:</span></b><span lang=3D"EN-US"> Qin Wu<br>
</span><b>=E6=8A=84=E9=80=81<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a=
>; <a href=3D"mailto:draft-ietf-lime-yang-connectionless-oam@ietf.org" targ=
et=3D"_blank">draft-ietf-lime-yang-<wbr>connectionless-oam@ietf.org</a>; Ca=
rlos Pignataro; Ron Bonica; <a href=3D"mailto:lime-chairs@ietf.org" target=
=3D"_blank">lime-chairs@ietf.org</a>; Benoit Claise; <a href=3D"mailto:lime=
@ietf.org" target=3D"_blank">lime@ietf.org</a><br>
</span><b>=E4=B8=BB=E9=A2=98<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Re: [Lime] Last Call: &lt;draft-ietf-lime-yang-<wbr>connectionless-=
oam-11.txt&gt; (Generic YANG Data Model for Connectionless Operations, Admi=
nistration, and Maintenance(OAM) protocols) to Proposed Standard<u></u><u><=
/u></span></div></div><p></p>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Qin,<u></u><u></u></span></p=
>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">thank you for your thoughtful c=
onsideration of my comments.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I agree to leave mechanism of o=
verrun indication to implementation but I believe that it will be really he=
lpful to add a sub-section that highlights specific of running tests in for=
ever mode and points to issues that
 require particular attention.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<u></u><u></u></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Greg<u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Tue, Oct 24, 2017 at 8:06 PM=
, Qin Wu &lt;<a href=3D"mailto:bill.wu@huawei.com" target=3D"_blank">bill.w=
u@huawei.com</a>&gt; wrote:<u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks Gre=
g for feedback, please see my reply inline below.</span><span lang=3D"EN-US=
"><u></u><u></u></span></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=E5=8F=91=E4=BB=
=B6=E4=BA=BA<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt"> Greg Mirsky [mailto:<a href=3D"mailto:gregimirsky=
@gmail.com" target=3D"_blank">gregimirsky@gmail.com</a>]
<br>
</span><b><span style=3D"font-size:10.0pt">=E5=8F=91=E9=80=81=E6=97=B6=E9=
=97=B4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D=
"font-size:10.0pt"> 2017</span><span style=3D"font-size:10.0pt">=E5=B9=B4<s=
pan lang=3D"EN-US">10</span>=E6=9C=88<span lang=3D"EN-US">24</span>=E6=97=
=A5<span lang=3D"EN-US"> 23:18<br>
</span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span lang=3D"EN-US">:</span></b><span=
 lang=3D"EN-US"> Qin Wu<br>
</span><b>=E6=8A=84=E9=80=81<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">
ietf@ietf.org</a>; <a href=3D"mailto:draft-ietf-lime-yang-connectionless-oa=
m@ietf.org" target=3D"_blank">
draft-ietf-lime-yang-<wbr>connectionless-oam@ietf.org</a>; Carlos Pignataro=
; Ron Bonica;
<a href=3D"mailto:lime-chairs@ietf.org" target=3D"_blank">lime-chairs@ietf.=
org</a>; Benoit Claise;
<a href=3D"mailto:lime@ietf.org" target=3D"_blank">lime@ietf.org</a></span>=
</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><b>=E4=B8=BB=E9=A2=98<span lang=3D"EN-US">:</span></=
b><span lang=3D"EN-US"> Re: [Lime] Last Call: &lt;draft-ietf-lime-yang-<wbr=
>connectionless-oam-11.txt&gt; (Generic YANG Data Model for Connectionless =
Operations, Administration, and Maintenance(OAM) protocols) to Proposed
 Standard<u></u><u></u></span></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Qin,<u></u><u></u></span></p=
>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">thank you for your expedient an=
d careful consideration of my comments. I&#39;m glad that we&#39;ve already=
 in agreement on so many. I&#39;ve added notes on those that, in
 my view, need some more discussions. Please find them in-line tagged GIM&g=
t;&gt;.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<u></u><u></u></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Greg<u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Sun, Oct 22, 2017 at 8:31 PM=
, Qin Wu &lt;<a href=3D"mailto:bill.wu@huawei.com" target=3D"_blank">bill.w=
u@huawei.com</a>&gt; wrote:<u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks Gre=
g for providing additional input to help make the model more extensible and
 reusable.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Please see=
 my reply inline below.</span><span lang=3D"EN-US"><u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">-Qin</span=
><span lang=3D"EN-US"><u></u><u></u></span></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=E5=8F=91=E4=BB=
=B6=E4=BA=BA<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt"> Greg Mirsky [mailto:<a href=3D"mailto:gregimirsky=
@gmail.com" target=3D"_blank">gregimirsky@gmail.com</a>]
<br>
</span><b><span style=3D"font-size:10.0pt">=E5=8F=91=E9=80=81=E6=97=B6=E9=
=97=B4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D=
"font-size:10.0pt"> 2017</span><span style=3D"font-size:10.0pt">=E5=B9=B4<s=
pan lang=3D"EN-US">10</span>=E6=9C=88<span lang=3D"EN-US">20</span>=E6=97=
=A5<span lang=3D"EN-US"> 20:34<br>
</span><b>=E6=94=B6=E4=BB=B6=E4=BA=BA<span lang=3D"EN-US">:</span></b><span=
 lang=3D"EN-US"> <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">
ietf@ietf.org</a>; <a href=3D"mailto:draft-ietf-lime-yang-connectionless-oa=
m@ietf.org" target=3D"_blank">
draft-ietf-lime-yang-<wbr>connectionless-oam@ietf.org</a><br>
</span><b>=E6=8A=84=E9=80=81<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Carlos Pignataro; Ron Bonica;
<a href=3D"mailto:lime-chairs@ietf.org" target=3D"_blank">lime-chairs@ietf.=
org</a>; Benoit Claise;
<a href=3D"mailto:lime@ietf.org" target=3D"_blank">lime@ietf.org</a><br>
</span><b>=E4=B8=BB=E9=A2=98<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Re: [Lime] Last Call: &lt;draft-ietf-lime-yang-<wbr>connectionless-=
oam-11.txt&gt; (Generic YANG Data Model for Connectionless Operations, Admi=
nistration, and Maintenance(OAM) protocols) to Proposed Standard</span></sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.5pt">Dear =
All,</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:9.5pt">pleas=
e kindly consider my comments on=C2=A0</span><span lang=3D"EN-US" style=3D"=
font-family:&quot;Arial&quot;,&quot;sans-serif&quot;">draft-ietf-lime-yang-=
<wbr>connectionless-oam
 presented below:</span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US" style=3D"font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;">1. Introduction</span><span lang=3D"EN-US"><u></u><u></u></span></=
li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">clear and technical definitions of connection-oriented=
 (CO) and connectionless (CL) network are absent. Note that referenced RFC =
7276 does not provide that either as differentiation based on amount of con=
figuration required to instantiate
 a network changes, decreases as result of further progress in network oper=
ation automation. I propose to use definitions CO and CL forwarding paradig=
ms provided in section 6.3.1 G.800 Unified functional architecture of trans=
port networks, as these are clear,
 technical and are broadly used in the industry.<u></u><u></u></span></li><=
/ul>
</ul>
<p class=3D"MsoNormal" style=3D"text-indent:9.0pt">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: I believe RFC7276 and G.80=
0 share the similar paradigms but capture the different aspect of the key d=
ifference between CO and CL, I would suggest to harmonize
 the different aspect of these key differences together and add another ref=
erence to G.800 as follows:</span><span lang=3D"EN-US"><u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"text-indent:9.0pt">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">NEW TEXT:</span><span lang=3D"EN-=
US"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:9.0pt">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9C</span><span lang=3D"EN-=
US"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:12.0pt">
<span lang=3D"EN-US">In connection-oriented technologies,<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 a connection is es=
tablished prior to the transmission of data.=C2=A0 After<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 connection is esta=
blished, no additional control information such as<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 signaling or opera=
tions and maintenance information is required to<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 transmit the data.=
=C2=A0 In connectionless technologies, data is<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 typically sent bet=
ween end points without prior arrangement, but<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 control informatio=
n is required to identify destination [G.800][RFC7276].<u></u><u></u></span=
></p>
<p class=3D"MsoNormal" style=3D"text-indent:9.0pt">
<span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9D</span><span lang=3D"EN-=
US"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">GIM&gt;&gt; If we consider, for=
 example, MPLS-TP domain and L3VPN over IP/MPLS domain, then the configurat=
ion aspect, in my opinion, becomes less distinct while the
 forwarding paradigm is invariant, remains the same.<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Tha=
nks.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<div>
<div>
<div>
<div>
<div>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">characterization of the subject of the document as &qu=
ot;YANG Data model for connectionless OAM protocols&quot; is not accurate c=
onsidering CO/CL definitions in G.800. I propose to refer to &quot;OAM prot=
ocols for connectionless networks&quot; since the same
 OAM protocols may be used in both CO-PS and CL-PS networks, e.g. LSP Ping =
used in both MPLS-TP and IP/MPLS networks.<u></u><u></u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 [Qin]: Okay ,Sounds good to me.</span><span lang=3D"E=
N-US"><u></u><u></u></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">3. Overview of the Connectionless OAM Model<u></u><u><=
/u></span></li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">&quot;... the &#39;test-point-location-info&#39;, is a=
 common aspect of every &#39;test-point-location&#39; - there&#39;s no YANG=
 object test-point-location in the presented data model.<u></u><u></u></spa=
n></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=
=A0 [Qin]: It is Typo. It should be =E2=80=98test-point-locations=E2=80=99,=
 fixed. Thanks.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">3.3 OAM Neighboring Layers<u></u><u></u></span></li></=
ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">I find this part of the model under-developed. First, =
the terminology - layers imply vertical, client-server relationship while d=
ownstream/upstream - peering relationship on the same layer. Second, the li=
mited visibility due to technology-level
 limitation that supports only reference to the immediate neighboring layer=
 but not to next-to-next neighbor. I consider this to be major problem for =
common model that intended for multi-layer environment.<u></u><u></u></span=
></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: We =
discussed this before, I revisit this section and understand your concern
 now , I would like to suggest to remove layer related text since it introd=
uce confusion, I would suggest to change technology-level into position sin=
ce what we try to define are OAM Neighboring Test points list. We will focu=
s on test points related to one
 single layer. One can use position to capture of order of these test point=
s and also identify test point at the left layer boundary and test point at=
 the right layer boundary. The proposed changes as follows:</span><span lan=
g=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9C<=
/span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">3.3.=C2=A0 OAM neighboring test=
 points<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 As typical network=
s have a multi-layer architecture, the set of OAM<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 protocols similarl=
y take a multi-layer structure; each layer may has<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 its own OAM protoc=
ol [RFC7276] and is corresponding to specific<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 administrative dom=
ain and has associated test points.=C2=A0 OAM<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 neighboring test p=
oints are referred to a list of neighboring test<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 points in the same=
 layer that are related to current test point.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 This allows users =
to easily navigate between related neighboring<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 layer to efficient=
ly troubleshoot a defect.=C2=A0 In this model,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 &#39;position&#39;=
 leaf defines the relative position of neighboring test<u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 point correspondin=
g to the current test point in the same layer , and<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 is provided to all=
ow correlation of faults at different location . If<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 there is one neigh=
boring test point placed before the current test<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 point, &#39;positi=
on&#39; leaf is set to -1.=C2=A0 If there is one neighboring<u></u><u></u><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 test point placed =
after the current test point, &#39;position&#39; leaf is<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 set to 1.=C2=A0 If=
 there is no neighboring test point placed before or<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0 after the current =
test point, &#39;position&#39; leaf is set to 0.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 list oam-neigh=
boring-tps {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 ke=
y &quot;index&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 le=
af index {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 type uint16 {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0range &quot;0..65536&quot;;<u></u><u></=
u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 &quot;Index of a list of neighboring test points<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 in the same layer &quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 le=
af position {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0type int8 {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 range &quot;-1..1&quot;=
;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &quot;The relative position<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 of neighboring test point<u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 corresponding to the current<u></u><u></u=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 test point&quot;;<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 de=
scription<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 &quot;List of related neighboring test points in the same l=
ayer.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=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 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9D<=
/span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">GIM&gt;&gt; I think that if we =
concentrate on OAM on particular network layer, then reference to multi-lay=
er character of modern networks is unnecessary and somewhat
 artificial. As for test points in the same layer, then traceroute suppose =
to return ordered list of Test Points between the Sender and Receiver. Beca=
use there could be ECMP sub-domains along the path, model should be able to=
 differentiate with some entropy
 key. OAM visibility into other administrative domains obviously brings sec=
urity consideration issues and, I&#39;d expect, be carefully controlled and=
 try to hide identity of the domain. Hence, I think that &#39;position&#39;=
 is hardly usable parameter.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Tha=
nks for your comments on this, yes recording test point list in the same la=
yer
 is not good use case, harmonizing with your comments and Gen-art review co=
mments, we have removed same layer and rewrite this section based on Gen-ar=
t reviewer=E2=80=99s input and suggestions. Thanks again.</span><span lang=
=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<div>
<div>
<div>
<div>
<div>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">3.4 Test Point Locations Information<u></u><u></u></sp=
an></li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">reference to non-existent &quot;tp-tool&quot; and &quo=
t;OAM-</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;color:black">ne=
ighboring Layers&quot;</span><span lang=3D"EN-US">=C2=A0groupings<u></u><u>=
</u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [Qin]: It i=
s typo, oam-neighboring layers should be corrected as =E2=80=9Coam-neighbor=
ing-tps=E2=80=9D
 now.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">4. YANG OAM Model<u></u><u></u></span></li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">I think that use of prefix &#39;coam&#39; for data mod=
el of OAM in connectionless networks is limiting considering that there sho=
uld be another model of OAM in connection-oriented networks. Acronyms CL an=
d CO usually used to refer to connectionless
 and connection-oriented networks respectively. Thus I suggest to use &#39;=
cl-oam&#39; as prefix for the data model presented in this document and &#3=
9;co-oam&#39; instead of &#39;goam&#39; in=C2=A0draft-ietf-lime-yang-<wbr>c=
onnection-oriented-oam-model.<u></u><u></u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 [Qin]:Good proposal, I like it.</span><span lang=3D"EN-US"><u></u><u=
></u></span></p>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">I find time-resolution to be superfluous and thus over=
complicating the model. I suggest use t<span style=3D"color:#1f497d">ime</s=
pan>-interval-type instead and consider for the update of yang:ietf-yang-ty=
pes defined in RFC 6991.<u></u><u></u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=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[Qin]=
:=C2=A0 Time resolution is referred to time unit, sure we can change it
 into time-interval-type as you suggested.</span><span lang=3D"EN-US"><u></=
u><u></u></span></p>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;;color:black">o</span><span lang=
=3D"EN-US" style=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;=
,&quot;serif&quot;;color:black">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:black">session-delay-statistics and session-jitter-statistics=
 are too limiting in many dimensions - no support to reflect one-way (far-e=
nd and near-end) and round-trip measurements for the same test session, and=
 too few metrics., e.g. no report of percentile. </span><span lang=3D"EN-US=
"><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=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[Qin]: We have protocol-=
id and protocol-id-meta-data to be defined in draft-ietf-lime-yang-<wbr>con=
nectionless-oam-methods-09 which can be used to indicate whether it is one =
way measurement, or two way =C2=A0=C2=A0=C2=A0</span><span lang=3D"EN-US"><=
u></u><u></u></span></pre>
<pre style=3D"text-indent:73.5pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"=
>measurements. Please see my reply for loss ration for report of percentile=
.</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;;color:black">o</span><span lang=
=3D"EN-US" style=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;=
,&quot;serif&quot;;color:black">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:black">session-delay-statistics does not reflect type of dela=
y variation being calculated. As analyzed in RFC 5481, PDV and IPDV charact=
erize different conditions (Section 5) and at least reflecting which one be=
ing calculated and reported is very informative.</span><span lang=3D"EN-US"=
><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 [Qin]: We h=
ave protocol-id and protocol-id-meta-data to be defined in draft-ietf-lime-=
yang-<wbr>connectionless-oam-methods-09 which can be used to indicate wheth=
er IPDV is used or PDV is used, Based on Brian=E2=80=99s </span><span lang=
=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"text-indent:31.5pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"=
>=C2=A0=C2=A0=C2=A0suggestion, we could set IPDV as default for jitter meas=
urement.</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;;color:black">o</span><span lang=
=3D"EN-US" style=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;=
,&quot;serif&quot;;color:black">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:black">I cannot find anything that directly reports packet lo=
ss statistics (packet loss and packet loss ratio) for the given test sessio=
n. Is that intentional? ICMP ping is capable to report number of lost packe=
ts in round-trip.</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=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 [Qin]: We do have a par=
ameter =E2=80=98packet-drops-count=E2=80=99 for packet-loss, we can change =
it into =E2=80=9Cpacket-loss-count=E2=80=9D as you suggested, in addition, =
we can add a new parameter for packet loss ration as follows:</span><span l=
ang=3D"EN-US"><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9C</span><span lang=
=3D"EN-US"><u></u><u></u></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
leaf packet-loss-count {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 type uint32 {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 range &quot;0..4294967295&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 default &quot;0&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &quot;Total received packet drops count.<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 If the value is 4294967295, it indicates<u></u><u>=
</u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0packet drops count is overrun.&quot;;<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
}<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 leaf loss-ratio{<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 type uint8{<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
<wbr>=C2=A0 range 0..100;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 description<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 &quot;Lo=
ss ratio of the packets. Express as percentage<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 of packe=
ts lost with respect to packets sent.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 }<u></u><u></u=
></span></p>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><span lang=3D"E=
N-US"><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9D</span><span lang=
=3D"EN-US"><u></u><u></u></span></pre>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">GIM&gt;&gt; Packet loss and, as=
 result, loss ratio in modern networks is very low. I suggest changing loss=
-ratio type from uint8 to new type percentage, defined as:<u></u><u></u></s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;color:black;background:#fffdf5">=C2=A0 =C2=
=A0typedef percentage {</span><span lang=3D"EN-US"><u></u><u></u></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;color:black;background:#fffdf5">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 type decimal64 {</span><span lang=3D"EN-US"><u></u><u></u=
></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;color:black;background:#fffdf5">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 fraction-digits 5;</span><spa=
n lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;color:black;background:#fffdf5">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 }</span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;color:black;background:#fffdf5">=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 description &quot;Percentage&quot;;</span><span lang=3D"E=
N-US"><u></u><u></u></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-family:&quot;Aria=
l&quot;,&quot;sans-serif&quot;;color:black;background:#fffdf5">=C2=A0 =C2=
=A0}</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Goo=
d proposal, accepted.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0GIM&gt;&gt; I think that =
counter overrun case indicator requires separate parameter. Using
</span><span lang=3D"EN-US" style=3D"font-family:&quot;Arial&quot;,&quot;sa=
ns-serif&quot;">4294967295 may produce negative false when running in forev=
er mode.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Not=
e that counter=C2=A0 is unsigned integer, it will not produce negative fals=
e, in
 my understanding. I doubt we should add such complexity to data model by i=
ntroducing another parameter, we can leave this to implementation details.<=
/span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></p>
</div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<div>
<div>
<div>
<div>
<div>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;">o</span><span lang=3D"EN-US" sty=
le=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&q=
uot;">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">using=
 uint32 in session-packet-statistics seems risking overrun of counters espe=
cially for test sessions running=C2=A0 forever. </span><span lang=3D"EN-US"=
><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Good point, we could =
set up-limit for</span><span lang=3D"EN-US" style=3D"font-size:10.0pt;font-=
family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black"> session-packe=
t-statistics data, if statistics data reach up-lmit, it wil indicate counte=
r overrun happens.</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;">o</span><span lang=3D"EN-US" sty=
le=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&q=
uot;">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">I bel=
ieve that using 0 to indicate that the parameter is not being reported, thr=
oughout several statistics groupings, creates problem when the true value i=
s 0, e.g. rx-bad-packet;</span><span lang=3D"EN-US"><u></u><u></u></span></=
pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]:Good point, we will re=
move to use 0 to indicate the parameter is not being reported.</span><span =
lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;;color:black">o</span><span lang=
=3D"EN-US" style=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;=
,&quot;serif&quot;;color:black">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:black">connectionless-oam-layers - what considerations were d=
iscussed to arrive to liming number of neighboring test points to 128?</spa=
n><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Okay, we can change u=
int8 into uint16 to support more test points that can be recorded. But plea=
se note that each test point actually only record his neighboring test poin=
ts, if each test points record a complete</span><span lang=3D"EN-US"><u></u=
><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">List of test points in one t=
est, that will result in a lot of duplicated data associated with each test=
 point.</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;;color:black">o</span><span lang=
=3D"EN-US" style=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;=
,&quot;serif&quot;;color:black">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:black">tp-tools:continuity-check you may add RFC 8029 to the =
list of references</span><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Accepted, thanks.</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;;color:black">o</span><span lang=
=3D"EN-US" style=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;=
,&quot;serif&quot;;color:black">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-=
US" style=3D"font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-seri=
f&quot;;color:black">tp-tools:path-discovery RFC 8029 obsoletes RFC 4379 as=
 standard for LSP Ping</span><span lang=3D"EN-US"><u></u><u></u></span></pr=
e>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Accepted, thanks.</sp=
an><span lang=3D"EN-US"><u></u><u></u></span></pre>
<pre style=3D"margin-left:72.0pt"><span lang=3D"EN-US" style=3D"font-size:1=
0.0pt;font-family:&quot;Courier New&quot;">o</span><span lang=3D"EN-US" sty=
le=3D"font-size:7.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&q=
uot;">=C2=A0=C2=A0=C2=A0 </span><span lang=3D"EN-US" style=3D"font-size:10.=
0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:black">times=
tamp grouping is limited to PTPv2 Truncated and NTPv4 64-bit format [RFC590=
5]. What about other formats, e.g. ICMP Timestamp, NTPv4 32-bit, a.k.a. sho=
rt, or PTPv2 80-bits long? </span><span lang=3D"EN-US"><u></u><u></u></span=
></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Here is the proposed =
change to address your comments:</span><span lang=3D"EN-US"><u></u><u></u><=
/span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9C</span><span lang=
=3D"EN-US"><u></u><u></u></span></pre>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0 grouping timestamp {<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 description<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&quot;Grouping for timestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 leaf timesta=
mp-type {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type identityref {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
base timestamp-type;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
}<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;Type of Timestamp, such as Truncated PTP, NTP.&quot;;<u>=
</u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 }<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 container ti=
mestamp-64bit {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 when &quot;derived-from-or-self(../type, &#39;cl-oam:truncated=
-ptp&#39;)&quot;+<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 &quot;or derived-from-or-self(../type,&#39;<wbr>cl-oam:ntp64&#39;)&q=
uot; {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &quot;Only applies when Truncated NTP or 64bit NTP=
 Timestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
leaf timestamp-sec {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type uint32;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;Absolute timestamp in seconds as per IEEE1588v2<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 or seconds part in 64-bit NTP timestamp.&quot;;<u></u><u=
></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=
leaf timestamp-nanosec {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type uint32;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;Fractional part in nanoseconds as per IEEE1588v2<u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 or Fractional part in 64-bit NTP timestamp.&quot;;<u></u=
><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
}<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&quot;Container for 64bit timestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 }<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 container ti=
mestamp-80bit {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 when &quot;derived-from-or-self(../type, &#39;cl-oam:ptp80&#39=
;)&quot;{<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &quot;Only applies when 80bit PTP Timestamp.&quot;=
;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 if-feature ptp-long-format;<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
leaf timestamp-sec {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type uint64 {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0r=
ange &quot;0..281474976710656&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
}<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;48bit Timestamp in seconds as per IEEE1588v2.&quot;;<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
leaf timestamp-nanosec {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type uint32;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;Fractional part in nanoseconds as per IEEE1588v2<u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0 =C2=A0=
=C2=A0=C2=A0=C2=A0or Fractional part in 64-bit NTP timestamp.&quot;;<u></u>=
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
}<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&quot;Container for 64bit timestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 }<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 container ntp-timestamp-32bit {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 when &quot;derived-from-or-self(../type, &#39;cl-oam:truncated=
-ntp&#39;)&quot;{<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 &quot;Only applies when 32 bit NTP Short format Ti=
mestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 if-feature ntp-short-format;<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
leaf timestamp-sec {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type uint16;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;Timestamp in seconds as per short format NTP.&quot;;<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
leaf timestamp-nanosec {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type uint16;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;Truncated Fractional part in 16-bit NTP timestamp.&quot;=
;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
}<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&quot;Container for 64bit timestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 }<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0 contai=
ner icmp-timestamp-32bit {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 when &quot;derived-from-or-self(../type, &#39;cl-oam:icmp-ntp&=
#39;)&quot;{<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
=C2=A0=C2=A0=C2=A0=C2=A0&quot;Only applies when Truncated NTP or 64bit NTP =
Timestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0 if-feature icmp-timestamp;<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
leaf timestamp-millisec {<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
type uint32;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 &quot;timestamp in milliseconds for ICMP timestamp.&quot;;<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 }<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
description<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
&quot;Container for 32bit timestamp.&quot;;<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0=C2=A0=C2=A0 }<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0 }<u></u><u></u></span></=
p>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=C2=A0</span><span lang=3D"E=
N-US"><u></u><u></u></span></pre>
<pre><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:#1f497d">=E2=80=9D</span><span lang=
=3D"EN-US"><u></u><u></u></span></pre>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">5.1.1.2 Test point attributes extension<u></u><u></u><=
/span></li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">reference to non-existing &quot;test-point-location&qu=
ot; list<u></u><u></u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Sam=
e typo as you mentioned above, it should be =E2=80=9C</span><span lang=3D"E=
N-US">test-point-locations</span><span lang=3D"EN-US" style=3D"font-size:10=
.5pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">=
=E2=80=9D.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">5.1.2 Schema Mount<u></u><u></u></span></li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">reference to non-existing &quot;test-point-location&qu=
ot; list<u></u><u></u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Sam=
e as above, fixed.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">5.2.1.2 Test point attributes extension<u></u><u></u><=
/span></li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">reference to non-existing &quot;test-point-location&qu=
ot; list<u></u><u></u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Sam=
e as above, fixed.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<ul type=3D"disc">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">5.2.2 Schema Mount<u></u><u></u></span></li></ul>
<ul type=3D"disc">
<ul type=3D"circle">
<li class=3D"MsoNormal">
<span lang=3D"EN-US">reference to non-existing &quot;test-point-location&qu=
ot; list<u></u><u></u></span></li></ul>
</ul>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Qin]: Sam=
e as above, fixed.</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">In summary, I find several seri=
ous issues with the current version of the data model presented in the docu=
ment, e.g. use of 0 to indicate unreported parameter
 and underdeveloped layering model.<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<u></u><u></u></span></=
p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Greg<u></u><u></u></span></p>
</div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Wed, Oct 11, 2017 at 6:40 AM=
, The IESG &lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank"=
>iesg-secretary@ietf.org</a>&gt; wrote:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
The IESG has received a request from the Layer Independent OAM Management i=
n<br>
the Multi-Layer Environment WG (lime) to consider the following document: -=
<br>
&#39;Generic YANG Data Model for Connectionless Operations, Administration,=
<br>
=C2=A0 =C2=A0and Maintenance(OAM) protocols&#39;<br>
=C2=A0 &lt;draft-ietf-lime-yang-<wbr>connectionless-oam-11.txt&gt; as Propo=
sed Standard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits final=
<br>
comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailin=
g lists by 2017-10-25. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a=
> instead. In either case, please retain the beginning of<br>
the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=C2=A0 =C2=A0This document presents a base YANG Data model for connectionle=
ss<br>
=C2=A0 =C2=A0Operations Administration, and Maintenance(OAM) protocols.=C2=
=A0 It<br>
=C2=A0 =C2=A0provides a technology-independent abstraction of key OAM const=
ructs<br>
=C2=A0 =C2=A0for connectionless protocols.=C2=A0 The base model presented h=
ere can be<br>
=C2=A0 =C2=A0extended to include technology specific details.=C2=A0 This is=
 leading to<br>
=C2=A0 =C2=A0uniformity between OAM protocols and support both nested OAM<b=
r>
=C2=A0 =C2=A0workflows (i.e., performing OAM functions at different or same=
 levels<br>
=C2=A0 =C2=A0through a unified interface) and interacting OAM workflows ( i=
.e.,<br>
=C2=A0 =C2=A0performing OAM functions at same levels through a unified inte=
rface).<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connection=
less-oam/" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/draft-ie=
tf-lime-yang-<wbr>connectionless-oam/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connection=
less-oam/ballot/" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/d=
raft-ietf-lime-yang-<wbr>connectionless-oam/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Lime mailing list<br>
<a href=3D"mailto:Lime@ietf.org" target=3D"_blank">Lime@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/lime" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<wbr>listinfo/lime</a><u></u><u></u></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</div>
</div></div></div>
</div>

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

--94eb2c19c5ec4c58e8055dc98b9f--


From nobody Sun Nov 12 06:48:57 2017
Return-Path: <strazpdj@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 934401200F1; Sun, 12 Nov 2017 06:48:55 -0800 (PST)
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 rcaMrG41nX0T; Sun, 12 Nov 2017 06:48:54 -0800 (PST)
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 E2C181288B8; Sun, 12 Nov 2017 06:48:50 -0800 (PST)
Received: by mail-lf0-x22a.google.com with SMTP id o66so7439106lfg.0; Sun, 12 Nov 2017 06:48:50 -0800 (PST)
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=qUAyhc1TpADpSCW2nG38VcfQAaxuKpvowLp9khe7O3k=; b=KCh6+Jf6e8uy/tn8CEQ7CEzxjVQ46koAWbvLZYHiIX45QThcyyutFDWhYVBCKyxu2J I7dgYPW5+VDg5dQJAxH4XvwpUgQcOqFFh3OZz5HtogDlGna1wiXvusNqdPeTmBPyIeYx NgyRlfrrY5rgfgtIseI/4EmCe29K53H7WRnxItY+2Eu7dt+ZJaCYWtHa5QxvOA901Fik MS+1GQBmLJ5yJ3JNzYG8jGCYhGrkv0b4Apas8uVB2IwRSZTs0j5GuLCiNuCtfj8vBRa4 gJnnZy2/cwdTuBAiVNWOw92cfjmrSGPXxXkbMy5AwwHJ6yh5444RoGt2GKrduGkwLgd4 wZug==
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=qUAyhc1TpADpSCW2nG38VcfQAaxuKpvowLp9khe7O3k=; b=swxUdRxQ9kjzi8jUZmO/fF9WSWxtKY7hkdf4tcgDu1q04yu4F74v7iHp27F72mnaGI /95UAWKh6kc8EAJd+iseYT/ZAl7dMjKIu/zNlI+9pILxxbwK7KL69+1clIoE6sUV7Uib reTdwP7Z6hAEeWvkAcXWG0hhDXU2wLjpHTg1yo/cUqP9o5g3y2ruO3LkwI0A4Rdb/rlg gKlKjrx//KoU0ib70OhX/9QL4K73R1FVceJcr3ipAL9ghwO1sE+MmMCXDZBacZe2Ybuy rlWUrJyk0UuaplSw6qxBPIZpltGGLP975Yju+ay/oKqzgwi6R507ZW2HodwgfiRML+xw dA0A==
X-Gm-Message-State: AJaThX7aQhf+pl20IiU83PQ75fB6y0MpHTbHu+/CZv5dQqgZTlXfNbr8 xlsMd3T4/cpdZ+8MU4lWLDRCrwBk/P7/r6QcZ5A=
X-Google-Smtp-Source: AGs4zMaCw/g+1g7XyVA1zUGgRmWVJ2iN4iJOuu+RnnlWHBCdmSZFMKEBKusN1sBwvsXSlYClu7h2TJAYMEPzirvdvmQ=
X-Received: by 10.25.31.198 with SMTP id f189mr223043lff.1.1510498129128; Sun, 12 Nov 2017 06:48:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.228.208 with HTTP; Sun, 12 Nov 2017 06:48:48 -0800 (PST)
In-Reply-To: <150807150359.12275.5646081426522886477@ietfa.amsl.com>
References: <150807150359.12275.5646081426522886477@ietfa.amsl.com>
From: John Strassner <strazpdj@gmail.com>
Date: Sun, 12 Nov 2017 06:48:48 -0800
Message-ID: <CAJwYUrGw9gh=SyUVO8YtpW2N39bVsdYDy13005XJS9YzLFez4g@mail.gmail.com>
Subject: Re: [I2nsf] Genart telechat review of draft-ietf-i2nsf-framework-08
To: Stewart Bryant <stewart.bryant@gmail.com>, John Strassner <strazpdj@gmail.com>
Cc: gen-art@ietf.org, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-framework.all@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a11403c086bb166055dca402c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UVP_l-HhLllvyHpgja4rbQ9VOA0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Nov 2017 14:48:55 -0000

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

Dear Stewart,

thank you for performing this review. All of your issues will be addressed
in version 9 of this I-D, to be released on Monday 11/13. In particular:

  1. The issue over including an RFC2119 boilerplate:


  2.  s/obtain/obtain
  DONE

  3.  Registration Categories including IPFIX
  DONE (references added to both IPFIX as well as IANA IPFIX Registry info)
  Specifically, the following text was added:

   IPFIX data [IPFIX-D] defines IP flow information and mechanisms to
   transmit such information. This includes flow attributes as well as
   information about the metering and exporting processes is also
   included. Such contain may be stored in a IPFIX registry [IPFIX-R].
   As such, IPFIX information should be considered for defining
   categories of registration information.


best regards,
John

On Sun, Oct 15, 2017 at 5:45 AM, Stewart Bryant <stewart.bryant@gmail.com>
wrote:

> Reviewer: Stewart Bryant
> 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.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-i2nsf-framework-08
> Reviewer: Stewart Bryant
> Review Date: 2017-10-15
> IETF LC End Date: 2017-10-25
> IESG Telechat date: 2017-10-26
>
> Summary: This is a well written document. There are a couple of things the
> authors need to look at, but it is ready to be published
>
> Major issues: None
>
> Minor issues: None
>
> Nits/editorial comments:
>
> The authors should consider whether the 2119 boilerplate is really needed
> as no
> RFC2119 keywords are used (something they point out to the reader) ======
>
>        a query-based interface is used by the the I2NSF Management
>        System to obatin information, whereas a report-based interface
> SB Typo - obtain
> =====
>
> 9.2.  Registration Categories
>
> SB> I would think that anything in the IPFIX registry was a candidate for
> such
> categories, after all IPFIX is designed and used  to monitor flows, often
> for
> security reasons.
>
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>



-- 
regards,
John

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

<div dir=3D"ltr"><div>Dear Stewart,</div><div><br></div><div>thank you for =
performing this review. All of your issues will be addressed</div><div>in v=
ersion 9 of this I-D, to be released on Monday 11/13. In particular:</div><=
div><br></div><div>=C2=A0 1. The issue over including an RFC2119 boilerplat=
e:</div><div><br></div><div><br></div><div>=C2=A0 2.=C2=A0 s/obtain/obtain<=
/div><div>=C2=A0 DONE</div><div><br></div><div>=C2=A0 3.=C2=A0 Registration=
 Categories including IPFIX</div><div>=C2=A0 DONE (references added to both=
 IPFIX as well as IANA IPFIX Registry info)</div><div>=C2=A0 Specifically, =
the following text was added:</div><div><br></div><div>=C2=A0=C2=A0 IPFIX d=
ata [IPFIX-D] defines IP flow information and mechanisms to<br>=C2=A0=C2=A0=
 transmit such information. This includes flow attributes as well as<br>=C2=
=A0=C2=A0 information about the metering and exporting processes is also<br=
>=C2=A0=C2=A0 included. Such contain may be stored in a IPFIX registry [IPF=
IX-R].<br>=C2=A0=C2=A0 As such, IPFIX information should be considered for =
defining<br>=C2=A0=C2=A0 categories of registration information.<br></div><=
div><br></div><div><br></div><div>best regards,</div><div>John</div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Oct 15, 2017 at =
5:45 AM, Stewart Bryant <span dir=3D"ltr">&lt;<a href=3D"mailto:stewart.bry=
ant@gmail.com" target=3D"_blank">stewart.bryant@gmail.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;=
border-left-style:solid">Reviewer: Stewart Bryant<br>
Review result: Ready with Nits<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" target=3D"_bl=
ank" rel=3D"noreferrer">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-i2nsf-framework-08<br>
Reviewer: Stewart Bryant<br>
Review Date: 2017-10-15<br>
IETF LC End Date: 2017-10-25<br>
IESG Telechat date: 2017-10-26<br>
<br>
Summary: This is a well written document. There are a couple of things the<=
br>
authors need to look at, but it is ready to be published<br>
<br>
Major issues: None<br>
<br>
Minor issues: None<br>
<br>
Nits/editorial comments:<br>
<br>
The authors should consider whether the 2119 boilerplate is really needed a=
s no<br>
RFC2119 keywords are used (something they point out to the reader) =3D=3D=
=3D=3D=3D=3D<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0a query-based interface is used by the the I2NSF=
 Management<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0System to obatin information, whereas a report-b=
ased interface<br>
SB Typo - obtain<br>
=3D=3D=3D=3D=3D<br>
<br>
9.2.=C2=A0 Registration Categories<br>
<br>
SB&gt; I would think that anything in the IPFIX registry was a candidate fo=
r such<br>
categories, after all IPFIX is designed and used=C2=A0 to monitor flows, of=
ten for<br>
security reasons.<br>
<br>
<br>
______________________________<wbr>_________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org" target=3D"_blank">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" target=3D"_blank" r=
el=3D"noreferrer">https://www.ietf.org/mailman/l<wbr>istinfo/i2nsf</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail-m_9=
143752158981148104gmail_signature"><div>regards,</div><div>John</div></div>
</div></div>

--001a11403c086bb166055dca402c--


From nobody Sun Nov 12 07:06:52 2017
Return-Path: <strazpdj@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 5961D12702E; Sun, 12 Nov 2017 07:06:46 -0800 (PST)
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 4GZ4eRx9VOAC; Sun, 12 Nov 2017 07:06:44 -0800 (PST)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::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 5B77612009C; Sun, 12 Nov 2017 07:06:33 -0800 (PST)
Received: by mail-lf0-x22e.google.com with SMTP id f134so7378281lfg.8; Sun, 12 Nov 2017 07:06:33 -0800 (PST)
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=ybKHuy1U6B3IChlNyQn9SFIr5FnzV8RDLIs9TLu0UCo=; b=VdckNSc8Wb7SkmOG3O63zgyijlBNFAYXSKo0sV7sWAN5j7QhgRj2O0EHd2GX5enAFw aaCeM3l0V4u0+gz1ShQNyfwXsHsX6+VIXg13wuvVn46temXju2r4+qJCkuOuBfrm7KnM 45S86ld4Jow7HkerpGri6CL6B+jMrMTOs0Xr/q70fgTfgxcEI0EQ7rZfuJ16oZafWLo7 dHFZqKgmTHf/6Cyou2/Vu9zVXHawRa0ZbHM8szEtqHXBSNu15Ef0i057qAqQIYWNUVtZ FpK1YGBB+gY1JqUVOjiiyRQq/tj2MTmS26j+KEQTqGofdrW+EoMQBvwgZDJUfg/OjTQA OsPw==
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=ybKHuy1U6B3IChlNyQn9SFIr5FnzV8RDLIs9TLu0UCo=; b=jDWqLFRTIiOwmEdsIFQL6el9tzlJmdaNwp5dmefLyuWx2ncsTuMdwiXItiU+OzR+sD 79tcSQ+r6dCrLluNb65oUpkyj2nPhx0Tu65jk81/RFUgPfI9oKbYdqZLyfTLc7Nka9Ku hhpcDem/co5fL1TNJFXaWktfjIqe8Ox6sTKJ5EFeNbw9I/wu1Ea4HPyO7GDu89ZkLZB/ VFjN9v4K1T7jf/s0A4iroqFXUPL0e3xhHB2bxnwnPyT3mFkY4tvWtV4bTBUOAYqB0TkD 46o7O7F5p7keKOgPgjHn0HyLjtg3fVwXuk9vDUvtAxywhC04lv5mT9jnFyLF198BlJoT c1kA==
X-Gm-Message-State: AJaThX7H6RNiLWFtXtFQqpe6cGhEagIzLVdWfEv0qxtVNWZ5PhCXiqJv AIb+KkR6eYYlUTXpcuz0lNI37vUQLUzP0/s7LKQ=
X-Google-Smtp-Source: AGs4zMbrqasC0uTNHvqko9lfvF9yROdPNU4wqHA5GC+60jFPJ/gpQ0DR3NfVfqUMeqvxeJN0Fxffii5zMYQZwr8Uq24=
X-Received: by 10.25.149.211 with SMTP id x202mr1949909lfd.139.1510499191483;  Sun, 12 Nov 2017 07:06:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.228.208 with HTTP; Sun, 12 Nov 2017 07:06:30 -0800 (PST)
In-Reply-To: <150881013474.25113.2293731255479709289@ietfa.amsl.com>
References: <150881013474.25113.2293731255479709289@ietfa.amsl.com>
From: John Strassner <strazpdj@gmail.com>
Date: Sun, 12 Nov 2017 07:06:30 -0800
Message-ID: <CAJwYUrEktTMt8DK9ZEqg7rGJAwYK+PJM3sHJi_4xC+FOQ2Ot0w@mail.gmail.com>
Subject: Re: [I2nsf] Opsdir telechat review of draft-ietf-i2nsf-framework-08
To: Carlos Martinez <carlosm3011@gmail.com>, John Strassner <strazpdj@gmail.com>
Cc: ops-dir@ietf.org, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-framework.all@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a11401c60bdf36b055dca7f55"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eMkgIH1Ag2hSD8GaMCQrhoq4Z7c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Nov 2017 15:06:46 -0000

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

Dear Carlos,

thank you for performing this review. All of your issues will be addressed
in version 9 of this I-D, to be released on Monday 11/13. In particular,
the bullet points in section 5 have been justified.

They were:

   o  Narrowly define NSF categories, or their roles, when implemented
      within a network
   o  Attempt to impose functional requirements or constraints, either
      directly or indirectly, upon NSF developers
   o  Be a limited lowest common denominator approach, where interfaces
      can only support a limited set of standardized functions, without
      allowing for developer-specific functions
   o  Be seen as endorsing a best common practice for the implementation
      of NSFs; rather, this document describes the conceptual structure
      and reference model of I2NSF

They are now:

     o  Narrowly define NSF categories, or their roles, when implemented
      within a network. Security is a constantly evolving discipline.
      The I2NSF framework relies on an object-oriented information
      model, which provides an extensible definition of NSF information
      elements and categories; it is recommended that implementations
      follow this model.
   o  Attempt to impose functional requirements or constraints, either
      directly or indirectly, upon NSF developers. Implementations
      should be free to realize  and apply NSFs in a way that best
      suits the needs of the applications and environment using them.
   o  Be a limited lowest common denominator approach, where interfaces
      can only support a limited set of standardized functions, without
      allowing for developer-specific functions. NSFs, interfaces, and
      the data communicated should be extensible, so that they can
      evolve to protect against new threats.
   o  Be seen as endorsing a best common practice for the implementation
      of NSFs; rather, this document describes the conceptual structure
      and reference model of I2NSF. The purpose of this reference model
      is to define a common set of concepts in order to facilitate the
      flexible implementation of an I2NSF system.


best regards,
John

On Mon, Oct 23, 2017 at 6:55 PM, Carlos Martinez <carlosm3011@gmail.com>
wrote:

> 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.
>
> Overall I've found this document to be READY. I do believe that some parts'
> readability could be improved however, particularly Section 5. This section
> describes some principles a potential implementation of the spec should
> follow
> but provides little or no justification for them. I believe additional text
> could help.
>
> Thank you to the authors for their great work!
>
> Carlos
>
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>



-- 
regards,
John

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

<div dir=3D"ltr"><div>Dear Carlos,</div><div><br></div><div><div>thank you =
for performing this review. All of your issues will be addressed</div><div>=
in version 9 of this I-D, to be released on Monday 11/13. In particular,</d=
iv><div>the bullet points in section 5 have been justified.</div><div><br><=
/div><div>They were:</div><div><br></div><div>=C2=A0=C2=A0 o=C2=A0 Narrowly=
 define NSF categories, or their roles, when implemented<br>=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0 within a network</div><div>=C2=A0=C2=A0 o=C2=A0 Attempt to =
impose functional requirements or constraints, either<br>=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 directly or indirectly, upon NSF developers<br></div><div>=C2=
=A0=C2=A0 o=C2=A0 Be a limited lowest common denominator approach, where in=
terfaces<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 can only support a limited set o=
f standardized functions, without<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 allowin=
g for developer-specific functions</div><div>=C2=A0=C2=A0 o=C2=A0 Be seen a=
s endorsing a best common practice for the implementation<br>=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 of NSFs; rather, this document describes the conceptual =
structure<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and reference model of I2NSF<br=
></div><div><br></div><div>They are now:</div><div><br></div><div>=C2=A0 =
=C2=A0=C2=A0 o=C2=A0 Narrowly define NSF categories, or their roles, when i=
mplemented<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 within a network. Security is =
a constantly evolving discipline.<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The I2N=
SF framework relies on an object-oriented information<br>=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 model, which provides an extensible definition of NSF informat=
ion<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 elements and categories; it is recomm=
ended that implementations<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 follow this mo=
del.</div><div>=C2=A0=C2=A0 o=C2=A0 Attempt to impose functional requiremen=
ts or constraints, either<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 directly or ind=
irectly, upon NSF developers. Implementations<br>=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 should be free to realize=C2=A0 and apply NSFs in a way that best<br=
>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 suits the needs of the applications and env=
ironment using them.</div><div>=C2=A0=C2=A0 o=C2=A0 Be a limited lowest com=
mon denominator approach, where interfaces<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 can only support a limited set of standardized functions, without<br>=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 allowing for developer-specific functions. N=
SFs, interfaces, and<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 the data communicate=
d should be extensible, so that they can<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
evolve to protect against new threats.</div><div>=C2=A0=C2=A0 o=C2=A0 Be se=
en as endorsing a best common practice for the implementation<br>=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 of NSFs; rather, this document describes the conceptu=
al structure<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 and reference model of I2NSF=
. The purpose of this reference model<br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 is =
to define a common set of concepts in order to facilitate the<br>=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 flexible implementation of an I2NSF system.<br></div>=
<div><br></div><div><br></div><div>best regards,</div><div>John</div></div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Oct=
 23, 2017 at 6:55 PM, Carlos Martinez <span dir=3D"ltr">&lt;<a href=3D"mail=
to:carlosm3011@gmail.com" target=3D"_blank">carlosm3011@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Carlos Martinez<br=
>
Review result: Ready<br>
<br>
I have reviewed this document as part of the Operational directorate&#39;s<=
br>
ongoing effort to review all IETF documents being processed by the IESG.=C2=
=A0 These<br>
comments were written with the intent of improving the operational aspects =
of<br>
the IETF drafts. Comments that are not addressed in last call may be includ=
ed<br>
in AD reviews during the IESG review.=C2=A0 Document editors and WG chairs =
should<br>
treat these comments just like any other last call comments.<br>
<br>
Overall I&#39;ve found this document to be READY. I do believe that some pa=
rts&#39;<br>
readability could be improved however, particularly Section 5. This section=
<br>
describes some principles a potential implementation of the spec should fol=
low<br>
but provides little or no justification for them. I believe additional text=
<br>
could help.<br>
<br>
Thank you to the authors for their great work!<br>
<br>
Carlos<br>
<br>
<br>
______________________________<wbr>_________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" target=3D"_blank" r=
el=3D"noreferrer">https://www.ietf.org/mailman/<wbr>listinfo/i2nsf</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature" data-smartmail=3D"gmail_signature"><div>regards,</div><div>John</di=
v></div>
</div>

--001a11401c60bdf36b055dca7f55--


From nobody Sun Nov 12 13:50:03 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 913C0128D86 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 13:50:00 -0800 (PST)
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=opendkim.org header.b=2XYO+ESj; dkim=pass (1024-bit key) header.d=elandsys.com header.b=i1CDE4Mb
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DOJXp_G4Zuqk for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 13:49:42 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0285B120725 for <ietf@ietf.org>; Sun, 12 Nov 2017 13:49:41 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.225.23.97]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vACLnUgK000755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sun, 12 Nov 2017 13:49:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510523380; x=1510609780; bh=PRtyRAVNY4vQoBFacZbEXVBZTjyE0dq0zmZ0M3Wyn0s=; h=Date:To:From:Subject:In-Reply-To:References; b=2XYO+ESjh42oFwsUOWo1TS7pxVXFhVeHJfbrJwqi/zTW4WhsDZlwPRBxSPnxMXGdU Pd+mfrXS5i2SJAeKfk2iXjlN10t/ZAM9/I74TU96EA/Zq779cel9ZC9Dbvckk2Y77z wm5r1F3QLbpalqcQGZwymcknkwbT0cmbWDXPJr8c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510523380; x=1510609780; i=@elandsys.com; bh=PRtyRAVNY4vQoBFacZbEXVBZTjyE0dq0zmZ0M3Wyn0s=; h=Date:To:From:Subject:In-Reply-To:References; b=i1CDE4MbR6SR9GaobQePV9Nw36wQr5KOAyP/pKElYrt1sC4ctDBVL9e9ZOAJEt2FW Oe+mT9csZUn8QqoHV6RtYsU2xOM2LD62IUgAX2bOzB+wIDcvQDJ4YoJFOOxm27ijcL drGIXFK8xyINl9P6ldnnK7c7wYyzub2PU0AIRDbM=
Message-Id: <6.2.5.6.2.20171112122108.10693078@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 12 Nov 2017 13:43:27 -0800
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
In-Reply-To: <150997721010.25597.12135786015002954174.idtracker@ietfa.am sl.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C225l3bes5NOcN96DiEmLkkwsJo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Nov 2017 21:50:00 -0000

Hello,
At 06:06 AM 06-11-2017, The IESG wrote:
>The IESG has received a request from an individual submitter to consider the
>following document: - 'Effect of Pervasive Encryption on Operators'
>   <draft-mm-wg-effect-encrypt-13.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-12-04. Exceptionally, comments may be

On reading the draft, I wondered whether the authors of the draft 
have an opinion about "responsible encryption".

In Section 1.1:

   "OS has been implemented as NULL Authentication with IPsec [RFC7619]
    and there are a number of infrastructure use cases such as server
    to server encryption, where this mode is deployed."

It is possible to find use cases of deployment.  That does not mean 
that it is always a good idea.

In Section 2:

   "This and other increases in the use of encryption had the immediate
    effect of helping protect the privacy of users' data, but created a
    problem for some network management functions."

Is this about privacy or is it about a security loophole?

In Section 2.1.2:

   "The ability to identify the problem application's traffic is
    important and deep packet inspection (DPI) is often used for
    this purpose."

Is debugging choppy video the main purpose of DPI?  Why should 
perversive surveillance software/hardware be used to debug application issues?

In Section 2.3:

   "These regulations include Lawful Intercept, adherence to Codes of
    Practice on content filtering, and application of court order filters."

Are the "Codes of Practices" part of regulations?  Are there 
references to those Codes of Practices?

In Section 3.2.2:

   "STARTTLS ought have zero effect on anti-SPAM efforts for SMTP traffic."

I doubt that STARTTLS cause any significant problem as the receiver 
has the ability to inspect emails.

In Section 4.1.1:

   "detect and defend against Internet DDoS attacks, including both
    volumetric and layer 7 attacks."

Does the IETF use the OSI layer (re. layer 7)?

As an overall comment, there are many uses of "many" in the 
document.  I read the entire document.  I understand that the authors 
may have put a lot of effort in this work.  However, I preferred to 
reduce the effort as it was a bit tedious to do a detailed 
review.  The title of the document is "Effect of Pervasive Encryption 
on Operators". Is this document about making the case against RFC 7258?

Regards,
S. Moonesamy  


From nobody Sun Nov 12 17:37:25 2017
Return-Path: <hsantos@isdg.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 46E1D127517 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 17:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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=isdg.net header.b=Lyj1qSri; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=CBNcgTdv
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B_OTVdZRcB8y for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 17:37:15 -0800 (PST)
Received: from dkim.winserver.com (ntbbs.winserver.com [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id B71921273B1 for <ietf@ietf.org>; Sun, 12 Nov 2017 17:37:13 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=519; t=1510537023; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=nEJg2ucJ3+c93QyOXN93K4+D1vA=; b=Lyj1qSricT/Q/InRhsv4Gqbo1EH6NiG8UJRixDRUknbp0BmKrJFjifwP7B7+Lv lFm7mNYK3eOeFMRH71t1y8AkdjCk/H8x6SzW9ZQj580N4er3gwskHepSoj/YW+SJ ZN0sLEjtsX26hV0DwujXmtoUQCsupcpGZjXfDbPN90J+s=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6) for ietf@ietf.org; Sun, 12 Nov 2017 20:37:03 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 405764218.1.3336; Sun, 12 Nov 2017 20:37:02 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=519; t=1510536891; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=cP4HaPM bdP3JlffcgBDan0OrifLwbDGQdc5Ea6g9dlk=; b=CBNcgTdvTtekju6oK0Aisae ItcVTXYnQDhQ1jEyGXv5gwIuY6irM4N2wXK6M6XZ13TecFC0JOoMW3Yr+j4W91Kl roZUo083oYLyoPNRK5HU7zPeFzgwfXrPr6zlXyqze5Z88gcAgR9m43tlxbZKPmVx MMQBpQgOSvqRFfKjRbhU=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.6) for ietf@ietf.org; Sun, 12 Nov 2017 20:34:51 -0500
Received: from [192.168.1.68] ([99.121.5.8]) by beta.winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 405731750.9.204980; Sun, 12 Nov 2017 20:34:50 -0500
Message-ID: <5A08F73B.5040602@isdg.net>
Date: Sun, 12 Nov 2017 20:36:59 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: IETF 100 MeetEcho connectivity
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cyUW7u4d4bOSTbggXCG8AT0_SnY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 01:37:23 -0000

Hi, I was perusing the IETF 100 agenda and proceeded to click a 
meeting video.

First, with javascript off (my security default), it thinks I need a 
new browser. It should just say "This site requires javascript to 
function."

Second, with javascript now enabled and the website white listed, it 
took me to a series of clicks where I think I am required to register 
even under "Read Only" mode.   I didn't click the Read/Write 
(participant mode) option.

Is this read-only registration necessary?

-- 
HLS



From nobody Sun Nov 12 17:49:54 2017
Return-Path: <akatlas@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 40534126CB6 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 17:49:52 -0800 (PST)
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 FDYSU4bummSl for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 17:49:51 -0800 (PST)
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 00B5C1241F5 for <ietf@ietf.org>; Sun, 12 Nov 2017 17:49:50 -0800 (PST)
Received: by mail-oi0-x229.google.com with SMTP id h81so4730264oib.8 for <ietf@ietf.org>; Sun, 12 Nov 2017 17:49:50 -0800 (PST)
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=4zIof1XvcVzd8Sm4/C0EPfNpcAxdMk4ux1CdRxC+B4A=; b=WS5+/MoJBim+oO3xLUCiN+MXsjd982wF0nauzPc0vDdvt4lLY6e7jMYpyo+MZDEtxv 3J/sRyMaXH6Y3SRTrJtyDmoYYPmxST+Ns+fLybWqV7MvM2PIKNEABIIHQUkDjVNeWKdL rN3iYreO6Oquy85sKq2YSgwn+Fe5MJrcvGbeytT+yaOMmlvHBastF4zeg+9Pq6Ke7Npn h/7thhKeOXDhq+6InhPxQOoU3NsiDhDSUQyABKbMSNLQssAljU59j9lXB3MhSZjoktMQ 7dQxQtcI9pYWwHS8cRSB4BWwMoburLAZY/CnI0USDDiSMBq1dIW0p9BkkpW0G3Nx9c8B EscA==
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=4zIof1XvcVzd8Sm4/C0EPfNpcAxdMk4ux1CdRxC+B4A=; b=U421jXOygI4cayURsXas0N/3rhTMGceU3qEDI9al/EKh/k1hcan1SfyY131aQMryxA bXtsU0EbS77N6FaxWv2fSutQkpqYKfw9dhD4V6DoD2qBesr+p3nUvOD0gmP1A6Fe9CJj RQb4NUXerLFS1FozOYOXvOjnWH8t1cY0GQejHuT16nE3Ww3wyC35bSfAcQ/AAIdtnVK3 mjJjX2OsjfxocJE82bpSCtBBJ7HgXG4rPYCOoQrj2zi4MSIpaV349nff2OErVwu+j8BY G/9EgsAPTZpUQ23j1zXZ5ZQspCE6oCRikp2mm0Rgtc7F8SJtuK9VZAGI55W9m9Ad1liD 4Jcg==
X-Gm-Message-State: AJaThX6iNzS6b7qoJm1bBoWkFTxwMl4SDB8ACmZvhOJEWpWkSTbyyn7p abkxk7or9tHBhyvNdfYuVPLHGQgLcc78PfRi0aBtYg==
X-Google-Smtp-Source: AGs4zMZ6FwuWyOouCBmf6X3DCjmD7hH6qGrGvaEvgAi+DROXgxMH7DZ+uXWMQzXbzkYtEWPhyGobFlid83u/Cf4JvB0=
X-Received: by 10.202.235.145 with SMTP id j139mr4577336oih.426.1510537789970;  Sun, 12 Nov 2017 17:49:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.0.143 with HTTP; Sun, 12 Nov 2017 17:49:49 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Sun, 12 Nov 2017 20:49:49 -0500
Message-ID: <CAG4d1rct7R1TFLwauXjSKs3k4gRvoM9HAW24aBFrmwPCqoim3g@mail.gmail.com>
Subject: side-meeting on IETF Outreach: Tues 12pm lunchtime in Orchard
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113cd8c4641e3a055dd37c73"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N-w-wJLwweaAGpkzqQFlcy-mXNQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 01:49:52 -0000

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

Please join me for a discussion on IETF Outreach and how to do an
IETF-focused tech-talks meet-up in your community.

How can we better grow the IETF?  What communities could you help reach
into? How do we articulate the value of participating in the IETF?

We'll be meeting in Orchard on Tuesday starting at 12pm.  It is a
bring-your-own-lunch.

I hope to see you there!

Regards,
Alia

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

<div dir=3D"ltr">Please join me for a discussion on IETF Outreach and how t=
o do an IETF-focused tech-talks meet-up in your community.<div><br></div><d=
iv>How can we better grow the IETF?=C2=A0 What communities could you help r=
each into? How do we articulate the value of participating in the IETF?</di=
v><div><br></div><div>We&#39;ll be meeting in Orchard on Tuesday starting a=
t 12pm.=C2=A0 It is a bring-your-own-lunch.</div><div><br></div><div>I hope=
 to see you there!</div><div><br></div><div>Regards,</div><div>Alia</div></=
div>

--001a113cd8c4641e3a055dd37c73--


From nobody Sun Nov 12 17:59:33 2017
Return-Path: <kaduk@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 6DABA127867 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 17:59:32 -0800 (PST)
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 S0Usp3IFz0S8 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 17:59:31 -0800 (PST)
Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 0B3FD12785F for <ietf@ietf.org>; Sun, 12 Nov 2017 17:59:30 -0800 (PST)
X-AuditID: 12074423-0e3ff70000007c25-9e-5a08fc7f6ab2
Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id EE.19.31781.08CF80A5; Sun, 12 Nov 2017 20:59:29 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id vAD1xO3m026378; Sun, 12 Nov 2017 20:59:25 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id vAD1xJKK013344 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 12 Nov 2017 20:59:23 -0500
Date: Sun, 12 Nov 2017 19:59:19 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Hector Santos <hsantos@isdg.net>
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
Message-ID: <20171113015919.GG26425@kduck.kaduk.org>
References: <5A08F73B.5040602@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A08F73B.5040602@isdg.net>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkleLIzCtJLcpLzFFi42IRYrdT0W38wxFl0H5K3OLn31ZWi2cb57M4 MHksWfKTyePt11/sAUxRXDYpqTmZZalF+nYJXBlXzk5gL2hhq7jc8IK9gfEOSxcjJ4eEgInE g83XgWwuDiGBxUwS07oOQzkbGSXOz3rEDFIlJHCVSeLqSzsQm0VAVeLgjTNsIDabgIpEQ/dl sBoRILv/x012EJtZwELiwpTfYLawgLbEmd3PGEFsXqBtS+9fZoeYqS7xbX8TK0RcUOLkzCcs EL1aEjf+vWTqYuQAsqUllv/jADE5BTQkpm2WAqkQFVCW2Nt3iH0Co8AsJM2zkDTPQmhewMi8 ilE2JbdKNzcxM6c4NVm3ODkxLy+1SNdMLzezRC81pXQTIzhEXZR3ML7s8z7EKMDBqMTDe+IK R5QQa2JZcWXuIUZJDiYlUV6Vz+xRQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4j9wHKudNSays Si3Kh0lJc7AoifNuC9oVKSSQnliSmp2aWpBaBJOV4eBQkuAt+w3UKFiUmp5akZaZU4KQZuLg BBnOAzRcEqSGt7ggMbc4Mx0if4rRkuPGw+t/mDge3bgLJJ/NfN3ALMSSl5+XKiXOqwXSIADS kFGaBzcTlHIksvfXvGIUB3pRmPcuSBUPMF3BTX0FtJAJaKEUyKe8xSWJCCmpBkYWydeTq37V C1zO8H4h8Ps01/6yiR/3V691cFXd/Jad625h0+rnomvkT6dmZOyVms8h3ah8YGmP792QFw+X 9C5vFVnyZPucGZzT9yT8k52+vU31mjSjx2wlzROKMzZW+oRV3v75q+uTPMdUrucfzR0ZftsY 7Kpd9edMj7RTZ98/xrkTN/LsVApSYinOSDTUYi4qTgQAsbbCsxQDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NTinnb4m95Iib9fTSp6tWWy0WdY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 01:59:32 -0000

On Sun, Nov 12, 2017 at 08:36:59PM -0500, Hector Santos wrote:
> Hi, I was perusing the IETF 100 agenda and proceeded to click a 
> meeting video.
> 
> First, with javascript off (my security default), it thinks I need a 
> new browser. It should just say "This site requires javascript to 
> function."
> 
> Second, with javascript now enabled and the website white listed, it 
> took me to a series of clicks where I think I am required to register 
> even under "Read Only" mode.   I didn't click the Read/Write 
> (participant mode) option.
> 
> Is this read-only registration necessary?

It was conscious choice, yes.

There was previous discussion on (IIRC) this list.

Note that the audio-only stream does not require this registration.

-Ben


From nobody Sun Nov 12 18:59:30 2017
Return-Path: <vishnupavan@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 A80C912700F; Sun, 12 Nov 2017 18:59:28 -0800 (PST)
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 Ayr0Oyg5asHP; Sun, 12 Nov 2017 18:59:25 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::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 2B266126DCA; Sun, 12 Nov 2017 18:59:22 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id i15so544687pfa.3; Sun, 12 Nov 2017 18:59:22 -0800 (PST)
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=wN9PwNPeukQHVXF7196oGGD3dGCJcmUbyQZJqvZAsxM=; b=rZ3g+GFe3zqm7JwgNxHujQJ0Fy1GCdi6ImCZ/UFnuXYzWAUJjnbUOvdnxLbSpDE5tS VrpHsgQu3R791UfC8TUsQQ6E1n8bBxMWhhe9SxGePqZXe1WleDfOK5CXC3bSegvs+F8f yMkvCGmACKupOhEXMw9LiYcvRqWqHY1VJF/9m5x1hr4BKIHvhkmlbWBaczUfyAAL9Kkb M1UadAanyTQeg6i2p7spAwRwtW+XJsHX9s+ytinK2oPBC0FLMDjeBOYar32u2NjK3ziz /+NT7XJh1BeYBIt9hIhRKykpi0xEFVvWVFpszmPv/4N8mqwwoksULskaQhi1etSnvnMv kY8g==
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=wN9PwNPeukQHVXF7196oGGD3dGCJcmUbyQZJqvZAsxM=; b=F0fWN4aUD8bown3hl7bMz072Lm9WY1cQa8Bk6zBOzajN1tw3Cl03BT2VrY/2ybOz+u x+CyEQ01Ml1whQ49BFoSGU858w2euIToBp+FRDVZ5yxNBISk3Xi+y+44kxwqvEVG5k8L MP61oYVZo/G0TfdM/9tatN0gtCWGHkxqVokj7VvvMZj4drbwI+7pEkSrvCLcw7A+cTVe JLSqKqeHMPW27JUr6i1I2VsJLD9CxOvOC4l5ihPTXPkrLUTN/WXbP0jc4BfSSCrCpJXP k2KsjDu6L4L5A18ZWoKPCBaSlnauBfUEykTLTBY4l9ofEXDWT7OqVCo9ZlJozBmYLF5M 1lxQ==
X-Gm-Message-State: AJaThX6T+drn6//T41dSHbueZ9fbKp6VkBIgmAN7LlrtEZOjNrr5ICca U4gkZGAgIHNi4hNBwmFhmgEVuyk/dMQFRpctn9o=
X-Google-Smtp-Source: AGs4zMZ91hGHxHrHIDxLxEx3Um+aqI/ITbkk/QmPtX/SRdc+xa601Gu/7bPLIspOx24qJ141E2aJ2Xd1PFzUy42hZdk=
X-Received: by 10.84.212.136 with SMTP id e8mr7515076pli.205.1510541961636; Sun, 12 Nov 2017 18:59:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.171.15 with HTTP; Sun, 12 Nov 2017 18:59:20 -0800 (PST)
In-Reply-To: <9e10fcf0-b60d-8f36-ac6f-65242c86fb07@dial.pipex.com>
References: <8wh65ldo8qkrghsf29x4nukb.1506702288623@email.android.com> <CA+YzgTuUcUxzoGHx2_mF+k0wu=X52ervTwuMk=fVEKTWNV=jjA@mail.gmail.com> <15eec201498.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net> <B1AAF8A9-FC5C-41D2-928F-F6E144C9AEFE@juniper.net> <2cdc53f9-11c4-40d7-c37c-09b747b763f6@labn.net> <CA+YzgTvt_pVQWMQ6PBBJDUAxGE4b1soJ5ePsYVA7DsK+7Xsppw@mail.gmail.com> <9e10fcf0-b60d-8f36-ac6f-65242c86fb07@dial.pipex.com>
From: Vishnu Pavan Beeram <vishnupavan@gmail.com>
Date: Sun, 12 Nov 2017 21:59:20 -0500
Message-ID: <CA+YzgTsj3jPHpN++epPF5wZbsJvHT_OG4jOU9=Fvu9SiBiP3jg@mail.gmail.com>
Subject: Re: [Teas] Genart last call review of draft-ietf-teas-rsvp-te-scaling-rec-06
To: Elwyn Davies <elwynd@dial.pipex.com>
Cc: Lou Berger <lberger@labn.net>, Vishnu Pavan Beeram <vbeeram@juniper.net>,  "gen-art@ietf.org" <gen-art@ietf.org>,  "draft-ietf-teas-rsvp-te-scaling-rec.all@ietf.org" <draft-ietf-teas-rsvp-te-scaling-rec.all@ietf.org>,  "teas@ietf.org" <teas@ietf.org>, ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045d24f60ab16f055dd475df"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/we9TeaC8PYWKPSU6LM8SG3bECEQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 02:59:29 -0000

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

Elwyn, Hi!

Apologize for the delayed reply.
We posted a new rev (-08) to address the comments that have been raised so
far. Please do take a look at the diffs and see if your concerns are
adequately addressed.

Please see inline for responses (prefixed [VPB])

Regards,
-Pavan

Snipped..

>>
>> >>     I think you should therefore make it explicit that a prerequisite
>> >>     for your extensions is an implementation of the Capability object
>> >>     as specified in RFC5063 (my proposal for s3) , making it clear
>> >>     that this does not require any of the other functionality of RFC
>> >>     5063, especially no support for the S bit in the Capabilities.
>> >>
>> >>
>> >> [Pavan] I'm not really sure that "Capability Object" needs a separate
>> >> prerequisite section. I'll let the Document-Shepherd and our AD take a
>> >> call on this. Please note that the document also talks about using
>> >> Node-ID hellos from RFC4558. Would "Node-Hellos/RFC4558" also then
>> >> need a separate prerequisite section? We added a separate section for
>> >> RFC2961 because there is a need to explicitly clarify the usage of
>> >> certain 2961 procedures. With "Capability Object" and "Node Hellos",
>> >> there isn't anything (IMHO) that needs to be explicitly clarified.
>>
> I think it would be useful to prospective implementors to have a very
> short statement either at the end of s1 or as a new section to say that you
> need to have the Capability Object implemented as this is not necessarily
> in a basic RSVP  implementation or RSVP-TE implementation.  Since this
> draft is about RSVP-TE deployments (RFC 3209) you get Node-Hellos
> automatically (and the RFC 4558 clarification is mentioned) and doesn't
> need to be called out explicitly.
>

[VPB] We added a statement in Section 1 to make this explicit.
**

Snipped..

>
> >>
>> >>     -  Your response regarding what happens if a peer initially
>> >>     acknowledges that it supports the new capabilities by setting the
>> >>     I/F bits in the Capability and sends some messages with the
>> >>     Refresh-Reduction-Capable bit set, but then stops setting the
>> >>     Refresh-Reduction-Capable bit doesn't really address the problem.
>> >>      Would this mean that the receiver should assume that the peer can
>> >>     no longer support the extensions?
>> >>
>> >>
>> >> [Pavan] Yes.
>> >>
>> >>     Is this a permanent state or could the peer start setting the
>> >>     Refresh-Reduction-Capable bit again and restore initial
>> >>     functionality - or should this just not be allowed.
>> >>
>> >>
>> >> [Pavan] The peer can set the bit again and restore the functionality.
>> >>
>> >>     I think you need to think through what happes in the various
>> >>     possible cases and explain what an implementation should do in
>> >>     each case.
>>
> What seems to be missing is what should be done if either or both of the
> two capabilities are active on the peer or some of its LSPs when the
> Refresh-Reduction-Capable bit is cleared in a message (which I think could
> be any message from the peer).  If I understand correctly it is possible
> that RI-RSVP might have to be switched off and depending on where the
> RI-RSVP process had got to in terms of sending repeat PATH messages, it
> might be necessary to revert to standard refreshing procedures from part
> way through the revised procedure - I think you probably need to be clear
> about what you would do in terms of where to enter the default refresh
> procedure and whether this means the refresh interval should revert to a
> lower value.   I am not sure whether immediately unthrottling the flow
> control would be desirable either!
>
>
[VPB] Inactivation of "Refresh-Reduction" Capability will immediately
inactivate both the "capabilities" discussed in the draft. This means that
the implementation would immediately fall back on to traditional non-2961
RSVP procedures (and stop following the procedures outlined in sections 3
and 4). We added an explicit statement to the draft saying that
"Inactivation of the RI-RSVP functionality MUST result in the use of the
traditional smaller refresh interval". We believe implementations don't
need any further guidance in order to cater to this "revert to traditional
procedures" requirement. Note that implementations today already know how
to handle "disabling/enabling" of the "Refresh-Reduction" capability knob
(this includes disabling/enabling per-session flow control). They already
know how to handle adjustments to "refresh-interval".

> >>
>> >>
>> >> [Pavan] There are only two possibilities -- Is the functionality
>> >> enabled on the peer or is it not? If the functionality is enabled, the
>> >> implementation does everything that is specified as required for the
>> >> given technique. If it is not enabled, then the implementation doesn't
>> >> employ the technique and just behaves like it does today. We'll try
>> >> and add some text to make this obvious.
>> >>
>> >>
>> >>     - So, I have done my homework and checked back on what happens
>> >>     when there is no acknowledgement of refreshes. The relevant
>> >>     parameter is the cleanup time.  However, this leaves us with a
>> >>     problem.. the cleanup time is typically set as a multiple of the
>> >>     refresh interval (9 times seems to be the default) - indeed I see
>> >>     that the interface configuration on a Juniper router (!) actually
>> >>     sets it by asking for the multiple rather than an absolute value.
>> >>     Wth the new dispensation in ths document, there are two time
>> >>     periods involved:  I think you do need to respecify how to
>> >>     calculate a sensible cleanup interval, and note that the
>> >>     retransmissions will then halt after this interval.
>> >>
>> >>
>> >> [Pavan] I think you are confusing this with the "setup retry" timer
>> >> (which comes into play when you signal the PATH setup of an LSP
>> >> instance and don't get a RESV back). Please go through
>> >> https://tools.ietf.org/html/draft-ravisingh-teas-rsvp-setup-retry-01
>> >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.
>> ietf.org_html_draft-2Dravisingh-2Dteas-2Drsvp-2Dsetup-
>> 2Dretry-2D01&d=DwMDaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-nd
>> b3voDTXcWzoCI&r=CFHVfW0WsgxSqM6wTJiWE5evUJAdlUl1fm7E0WVbiS8&
>> m=k7e-cloxf90XW9b_KRgpp7fxJRT4Q-f-_Nor0jTe8fg&s=
>> XXwwGPXiCQhVIgNDbiHxKEuHs1fkmMoiGQsHcQ33ZQE&e=>
>> >> for a detailed account of setup retry timer, issues associated with it
>> >> and recommended practices. The staged retransmission (Section 2.3)
>> >> that comes into play when there is no ACK is different from what you
>> >> are alluding to -- it is meant for any message seeking ACK (not just
>> >> PATH). This is very specific to the exponential back-off procedure
>> >> discussed in Section 6 of RFC2961. As per RFC2961, the rapid
>> >> retransmissions stop after we reach a certain retry limit. In Section
>> >> 2.3, we are clarifying what needs to be done after this Retry limit is
>> >> reached --- the recommendation is to fall back on a not so rapid
>> >> retransmission interval. As a I said in my previous email, this needs
>> >> to be done until either an ACK is received or the corresponding state
>> >> is torn down.
>>
> No.  I am not talking about the setup-retry timer.  I was thinking about
> the L value (the local state lifetime) as discussed in Section 3.7 of RFC
> 2205.  This is usually defined in terms of a multiple of the refresh timer
> - s3 of the draft suggests that the refresh timer be configured to 20
> minutes making the L value at least an hour in the default case.  This
> would mean the slower refresh retries would go on for an hour which seems
> excessive.  I suspect you need to specify an alternative algorithm for
> setting L.
>

[VPB] There is really no need to specify a new algorithm for setting L. It
is understood that having a large refresh-interval will significantly
increase the L value. With the procedures defined for "RI-RSVP", we have
completely eliminated RSVP's reliance on refreshes and refresh-timeouts. A
smaller "L" value is important only if you are relying on refresh-timeouts
to clean up state.

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

<div dir=3D"ltr"><div><div><div><div><div><div>Elwyn, Hi!<br><br></div>Apol=
ogize for the delayed reply. <br></div>We posted a new rev (-08) to address=
 the comments that have been raised so far. Please do take a look at the di=
ffs and see if your concerns are adequately addressed.<br><br></div>Please =
see inline for responses (prefixed [VPB])<br><br></div>Regards,<br></div>-P=
avan<br><br></div>Snipped..<br><div><div><div><div><div><div><div><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote"><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><div><div class=3D"gmail-h=
5"><blockquote type=3D"cite"><div class=3D"gmail_extra"><div class=3D"gmail=
_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class=
=3D"gmail-m_-5146601209790477692h5">
                &gt;&gt;<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0I think you should therefore ma=
ke it
                explicit that a prerequisite<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0for your extensions is an imple=
mentation of
                the Capability object<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0as specified in RFC5063 (my pro=
posal for
                s3) , making it clear<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0that this does not require any =
of the other
                functionality of RFC<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A05063, especially no support for=
 the S bit
                in the Capabilities.<br>
                &gt;&gt;<br>
                &gt;&gt;<br>
                &gt;&gt; [Pavan] I&#39;m not really sure that &quot;Capabil=
ity
                Object&quot; needs a separate<br>
                &gt;&gt; prerequisite section. I&#39;ll let the
                Document-Shepherd and our AD take a<br>
                &gt;&gt; call on this. Please note that the document
                also talks about using<br>
                &gt;&gt; Node-ID hellos from RFC4558. Would
                &quot;Node-Hellos/RFC4558&quot; also then<br>
                &gt;&gt; need a separate prerequisite section? We added
                a separate section for<br>
                &gt;&gt; RFC2961 because there is a need to explicitly
                clarify the usage of<br>
                &gt;&gt; certain 2961 procedures. With &quot;Capability
                Object&quot; and &quot;Node Hellos&quot;,<br>
                &gt;&gt; there isn&#39;t anything (IMHO) that needs to be
                explicitly clarified. </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote></div></div>
    I think it would be useful to prospective implementors to have a
    very short statement either at the end of s1 or as a new section to
    say that you need to have the Capability Object implemented as this
    is not necessarily in a basic RSVP=C2=A0 implementation or RSVP-TE
    implementation.=C2=A0 Since this draft is about RSVP-TE deployments (RF=
C
    3209) you get Node-Hellos automatically (and the RFC 4558
    clarification is mentioned) and doesn&#39;t need to be called out
    explicitly.<span class=3D"gmail-"><br></span></div></blockquote><div><b=
r></div><div>[VPB] We added a statement in Section 1 to make this explicit.=
 <br></div><div>**<br></div><div><br></div><div>Snipped..<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><span cl=
ass=3D"gmail-"></span><span class=3D"gmail-"><br>
    <blockquote type=3D"cite">
      <div class=3D"gmail_extra">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div class=3D"gmail-m_-5146601209790477692h5">
                &gt;&gt;<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0-=C2=A0 Your response regarding=
 what happens if
                a peer initially<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0acknowledges that it supports t=
he new
                capabilities by setting the<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0I/F bits in the Capability and =
sends some
                messages with the<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0Refresh-Reduction-Capable bit s=
et, but then
                stops setting the<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0Refresh-Reduction-Capable bit d=
oesn&#39;t
                really address the problem.=C2=A0<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0=C2=A0Would this mean that the =
receiver should
                assume that the peer can<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0no longer support the extension=
s?=C2=A0<br>
                &gt;&gt;<br>
                &gt;&gt;<br>
                &gt;&gt; [Pavan] Yes.<br>
                &gt;&gt;<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0Is this a permanent state or co=
uld the peer
                start setting the<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0Refresh-Reduction-Capable bit a=
gain and
                restore initial<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0functionality - or should this =
just not be
                allowed.<br>
                &gt;&gt;<br>
                &gt;&gt;<br>
                &gt;&gt; [Pavan] The peer can set the bit again and
                restore the functionality.<br>
                &gt;&gt;<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0I think you need to think throu=
gh what
                happes in the various<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0possible cases and explain what=
 an
                implementation should do in<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0each case.<br>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote></span>
    What seems to be missing is what should be done if either or both of
    the two capabilities are active on the peer or some of its LSPs when
    the=C2=A0 Refresh-Reduction-Capable bit is cleared in a message (which =
I
    think could be any message from the peer).=C2=A0 If I understand
    correctly it is possible that RI-RSVP might have to be switched off
    and depending on where the RI-RSVP process had got to in terms of
    sending repeat PATH messages, it might be necessary to revert to
    standard refreshing procedures from part way through the revised
    procedure - I think you probably need to be clear about what you
    would do in terms of where to enter the default refresh procedure
    and whether this means the refresh interval should revert to a lower
    value.=C2=A0=C2=A0 I am not sure whether immediately unthrottling the f=
low
    control would be desirable either!<div><div class=3D"gmail-h5"><br></di=
v></div></div></blockquote><div><br></div><div>[VPB] Inactivation of &quot;=
Refresh-Reduction&quot; Capability will immediately inactivate both the &qu=
ot;capabilities&quot; discussed in the draft. This means that the implement=
ation would immediately fall back on to traditional non-2961 RSVP procedure=
s (and stop following the procedures outlined in sections 3 and 4).<span cl=
ass=3D"gmail-insert"> We added an explicit statement to the draft saying th=
at &quot;Inactivation of the RI-</span><span class=3D"gmail-insert">RSVP fu=
nctionality MUST result in the use of the traditional smaller</span><span c=
lass=3D"gmail-insert"> refresh interval&quot;. We believe implementations d=
on&#39;t need any further guidance in order to cater to this &quot;revert t=
o traditional procedures&quot; requirement. Note that implementations today=
 already know how to handle &quot;disabling/enabling&quot; of the &quot;Ref=
resh-Reduction&quot; capability knob (this includes disabling/enabling per-=
session flow control). They already know how to handle adjustments to &quot=
;refresh-interval&quot;.</span> </div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div bgcolor=3D"#FFFFFF"><div><div class=3D"gmail-h5">
    <blockquote type=3D"cite">
      <div class=3D"gmail_extra">
        <div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div class=3D"gmail-m_-5146601209790477692h5">
                &gt;&gt;<br>
                &gt;&gt;<br>
                &gt;&gt; [Pavan] There are only two possibilities -- Is
                the functionality<br>
                &gt;&gt; enabled on the peer or is it not? If the
                functionality is enabled, the<br>
                &gt;&gt; implementation does everything that is
                specified as required for the<br>
                &gt;&gt; given technique. If it is not enabled, then the
                implementation doesn&#39;t<br>
                &gt;&gt; employ the technique and just behaves like it
                does today. We&#39;ll try<br>
                &gt;&gt; and add some text to make this obvious.<br>
                &gt;&gt; =C2=A0<br>
                &gt;&gt;<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0- So, I have done my homework a=
nd checked
                back on what happens<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0when there is no acknowledgemen=
t of
                refreshes. The relevant<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0parameter is the cleanup time.=
=C2=A0 However,
                this leaves us with a<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0problem.. the cleanup time is t=
ypically set
                as a multiple of the<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0refresh interval (9 times seems=
 to be the
                default) - indeed I see<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0that the interface configuratio=
n on a
                Juniper router (!) actually<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0sets it by asking for the multi=
ple rather
                than an absolute value.=C2=A0<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0Wth the new dispensation in ths=
 document,
                there are two time<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0periods involved:=C2=A0 I think=
 you do need to
                respecify how to<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0calculate a sensible cleanup in=
terval, and
                note that the<br>
                &gt;&gt;=C2=A0 =C2=A0 =C2=A0retransmissions will then halt =
after this
                interval.<br>
                &gt;&gt;<br>
                &gt;&gt;<br>
                &gt;&gt; [Pavan] I think you are confusing this with the
                &quot;setup retry&quot; timer<br>
                &gt;&gt; (which comes into play when you signal the PATH
                setup of an LSP<br>
                &gt;&gt; instance and don&#39;t get a RESV back). Please go
                through<br>
                &gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-ravis=
ingh-teas-rsvp-setup-retry-01" rel=3D"noreferrer" target=3D"_blank">https:/=
/tools.ietf.org/html/dr<wbr>aft-ravisingh-teas-rsvp-setup-<wbr>retry-01</a>=
<br>
              </div>
            </div>
            &gt;&gt; &lt;<a href=3D"https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dravisingh-2Dteas-2Drsvp-2Dsetup=
-2Dretry-2D01&amp;d=3DDwMDaQ&amp;c=3DHAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXc=
WzoCI&amp;r=3DCFHVfW0WsgxSqM6wTJiWE5evUJAdlUl1fm7E0WVbiS8&amp;m=3Dk7e-cloxf=
90XW9b_KRgpp7fxJRT4Q-f-_Nor0jTe8fg&amp;s=3DXXwwGPXiCQhVIgNDbiHxKEuHs1fkmMoi=
GQsHcQ33ZQE&amp;e=3D" rel=3D"noreferrer" target=3D"_blank">https://urldefen=
se.proofpoint<wbr>.com/v2/url?u=3Dhttps-3A__tools.<wbr>ietf.org_html_draft-=
2Dravising<wbr>h-2Dteas-2Drsvp-2Dsetup-<wbr>2Dretry-2D01&amp;d=3DDwMDaQ&amp=
;c=3D<wbr>HAkYuh63rsuhr6Scbfh0UjBXeMK-nd<wbr>b3voDTXcWzoCI&amp;r=3DCFHVfW0W=
sgxSqM<wbr>6wTJiWE5evUJAdlUl1fm7E0WVbiS8&amp;<wbr>m=3Dk7e-cloxf90XW9b_<wbr>=
KRgpp7fxJRT4Q-f-_Nor0jTe8fg&amp;s=3D<wbr>XXwwGPXiCQhVIgNDbiHxKEuHs1fkmM<wbr=
>oiGQsHcQ33ZQE&amp;e=3D</a>&gt;<br>
            <div>
              <div class=3D"gmail-m_-5146601209790477692h5">&gt;&gt; for a =
detailed account of setup
                retry timer, issues associated with it<br>
                &gt;&gt; and recommended practices. The staged
                retransmission (Section 2.3)<br>
                &gt;&gt; that comes into play when there is no ACK is
                different from what you<br>
                &gt;&gt; are alluding to -- it is meant for any message
                seeking ACK (not just<br>
                &gt;&gt; PATH). This is very specific to the exponential
                back-off procedure<br>
                &gt;&gt; discussed in Section 6 of RFC2961. As per
                RFC2961, the rapid<br>
                &gt;&gt; retransmissions stop after we reach a certain
                retry limit. In Section<br>
                &gt;&gt; 2.3, we are clarifying what needs to be done
                after this Retry limit is<br>
                &gt;&gt; reached --- the recommendation is to fall back
                on a not so rapid<br>
                &gt;&gt; retransmission interval. As a I said in my
                previous email, this needs<br>
                &gt;&gt; to be done until either an ACK is received or
                the corresponding state<br>
                &gt;&gt; is torn down.<br>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote></div></div>
    No.=C2=A0 I am not talking about the setup-retry timer.=C2=A0 I was thi=
nking
    about the L value (the local state lifetime) as discussed in Section
    3.7 of RFC 2205.=C2=A0 This is usually defined in terms of a multiple o=
f
    the refresh timer - s3 of the draft suggests that the refresh timer
    be configured to 20 minutes making the L value at least an hour in
    the default case.=C2=A0 This would mean the slower refresh retries woul=
d
    go on for an hour which seems excessive.=C2=A0 I suspect you need to
    specify an alternative algorithm for setting L.<span class=3D"gmail-"><=
br></span></div></blockquote><div><br></div><div>[VPB] There is really no n=
eed to specify a new algorithm for setting L. It is understood that having =
a large refresh-interval will significantly increase the L value. With the =
procedures defined for &quot;RI-RSVP&quot;, we have completely eliminated R=
SVP&#39;s reliance on refreshes and refresh-timeouts. A smaller &quot;L&quo=
t; value is important only if you are relying on refresh-timeouts to clean =
up state. <br></div></div><br></div></div></div></div></div></div></div></d=
iv></div>

--f403045d24f60ab16f055dd475df--


From nobody Sun Nov 12 19:59:29 2017
Return-Path: <strazpdj@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 C07D21293FF; Sun, 12 Nov 2017 19:59:26 -0800 (PST)
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 58x1C7RwZ9ck; Sun, 12 Nov 2017 19:59:24 -0800 (PST)
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 D20B7129427; Sun, 12 Nov 2017 19:59:23 -0800 (PST)
Received: by mail-lf0-x22d.google.com with SMTP id a2so16774152lfh.11; Sun, 12 Nov 2017 19:59:23 -0800 (PST)
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=nOte95HlFVLDZeT/ERPpWyqP1+tnyCFmPOntrceGXXc=; b=LijmmCJWEkiSknYeEKCvFUyXSbmOd1SU8cO2vUC/nodC86rhmBfJoIazRdJ4vrNyW0 kgnKX7JVxeqelkn83Y2ePkQQ3Nbs9oZbj8GagDv1G9Apb6oxaU0G+lZymzYwUrrVon53 HGGV+dQM6NW5gk/cNmtZdrYq7uqnxA/Dl9Gnvxy3Lkgcs3bty57U+zlHEQMKGc2vjmwH bIUz8C7XkbiBQfAZ2pxfS+UkiWdIXHCGUmJm8k6jQ5O2d/DjDHqFwmM0BNYUF3kwJ/gn vMUQ19HHRAs46DAygnEloKsWU18D8uG4RM2zSXxfnZdW6wFNvd6RGJZgj3UzDyoVUXQ8 xPtg==
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=nOte95HlFVLDZeT/ERPpWyqP1+tnyCFmPOntrceGXXc=; b=IR9yUw07sr9XWfAWiAcfgbbZis9uimXV3LyhwcH8sVXnnXq+EwZfKyOIOHinLIM+qX XjInk+uTv1mnYc5EKYViuTdbvxWpM+89N/8WfXn+Rvk09brPuEIKh62wNaOOfRszgdFm nLy9SyFaCUpsu3IwqPulg3hDr6T2yuRJMWTvuBRdE44fV6KOlPsgTGTBXISydIWmELxh 2xfxwZ3FsavXmehmdKbvCP/0dMtZTM9sWFnBZIHGr+3muTGk5Zhxh6VVsTp97Y6IOUpa FGvTvdhIKje2aKIKMf85a85gBBD4TPj5vekizIiFf+38WP6RUM2ju4BLHU9Tf6qxUWeh VKdg==
X-Gm-Message-State: AJaThX7FryhA9kqlxlNaproOEQljSArdjGcxYm2NO/DWleUQOdicj5P3 2AQ8uz8MYL1b0SIm4BpD4Cftj15zE8hgbnaKvy8=
X-Google-Smtp-Source: AGs4zMaaOz4jvheqG6SMRHkrOAUCanPiHxOpQteRQENfyWmOHu2LuForC2476CEf7KNQz4V60vWSuRo5+1JTv+e2rZ0=
X-Received: by 10.25.80.87 with SMTP id z23mr2358692lfj.60.1510545562005; Sun, 12 Nov 2017 19:59:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.228.208 with HTTP; Sun, 12 Nov 2017 19:59:21 -0800 (PST)
In-Reply-To: <150888532124.4802.13758793569414682089@ietfa.amsl.com>
References: <150888532124.4802.13758793569414682089@ietfa.amsl.com>
From: John Strassner <strazpdj@gmail.com>
Date: Sun, 12 Nov 2017 19:59:21 -0800
Message-ID: <CAJwYUrFsMJ1BA+UF5vDNEZXS05rKJhgSQTJiw9mF_dtfhXqkSQ@mail.gmail.com>
Subject: Re: [I2nsf] Secdir telechat review of draft-ietf-i2nsf-framework-08
To: Daniel Franke <dafranke@akamai.com>, John Strassner <strazpdj@gmail.com>
Cc: secdir@ietf.org, "i2nsf@ietf.org" <i2nsf@ietf.org>,  draft-ietf-i2nsf-framework.all@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c1cb042a3f7ae055dd54b49"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ItdNrwQwOP_4HqRZPsKpj-k3H8M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 03:59:27 -0000

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

Dear Daniel,

thank you for performing this review. The following changes will be
implemented in version 9 of this I-D, to be released on Monday 11/13.
In particular,


Change the last paragraph in section 4,
from:
   The above threats may be mitigated by requiring the use of an AAA
   framework for all users to access the I2NSF environment. This could
   be further enhanced by requiring attestation to be used to detect
   changes to the I2NSF environment by authorized parties.

to:
   The use of authentication, authorization, accounting, and audit
   mechanisms is recommended for all users and applications to access
   the I2NSF environment. This can be further enhanced by requiring
   attestation to be used to detect changes to the I2NSF environment
   by authorized parties. The characteristics of these procedures will
   define the level of assurance of the I2NSF environment.

Change section 6.1
from:
6.1.  Network Connecting I2NSF Users and the I2NSF Controller

   ...
   Upon successful authentication, a trusted connection between the
   user and the I2NSF Controller (or an endpoint designated by it) will
   be established.  All traffic to and from the NSF environment ...

to:
6.1. Network Connecting I2NSF Users and the I2NSF Controller

   ...
   Upon successful authentication, a trusted connection between the
   user and the I2NSF Controller (or an endpoint designated by it) will
   be established. This means that a direct, physical point-to-point
   connection, with physical access restricted according to access
   control, must be used. All traffic to and from the NSF environment...

Change 6.2:
from:
6.2.  Network Connecting the I2NSF Controller and NSFs
   ...

to:
6.2.  Network Connecting the I2NSF Controller and NSFs

   ...
   Therefore, the transport mechanism used to carry the control messages
   and monitoring information should provide reliable message delivery.
   TCP is the obvious current choice, but others such as Multipath TCP
   (MPTCP) and the Stream Control Transmission Protocol (SCTP) would
   be applicable as well.  Latency requirements for control message delivery
   must also be evaluated.
   ...
   I2NSF needs to rely on the use of standard I2NSF interfaces to
   properly verify peer identities (e.g., through an AAA framework).
   The implementations of identity management functions, as well as
   the AAA framework, are out of scope for I2NSF.

to:
   ...
   Therefore, the transport mechanism used to carry management data and
   information must be secure. It does not have to be a reliable
   transport; rather, a transport-independent reliable messaging
   mechanism is required, where communication can be performed reliably
   (e.g., by establishing end-to-end communication sessions and by
   introducing explicit acknowledgement of messages into the
   communication flow). Latency requirements for control message
   delivery must also be evaluated. Note that monitoring does not
   require reliable transport.
   ...
   The network connection between the I2NSF Controller and NSFs will
   use the trusted connection mechanisms described in section 6.1.
   Following these mechanisms, the connections need to rely on the use
   of properly verified peer identities (e.g., through an AAA
   framework). The implementations of identity management functions, as
   well as the AAA framework, are out of scope for I2NSF.

In addition, please see other changes to this thread (yesterday and this
morning, local time Singapore)

best regards,
John

On Tue, Oct 24, 2017 at 3:48 PM, Daniel Franke <dafranke@akamai.com> wrote:

> Reviewer: Daniel Franke
> Review result: Not 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.
>
> This document is too broad and too vague for any reasonable security
> review to
> be possible. It expresses a desire to define a framework which satisfies
> certain requirements and use cases, but does not actually define anything
> concrete. At its most specific, the document gives parametricity
> constraints
> that future definitions must satisfy, such as being agnostic to network
> topology. This doesn't give me much to go on.
>
> The security considerations section is brief, calling out the need for
> access
> control and for protecting the confidentiality and integrity of data.
> Again,
> with so few specifics, there's not much more to be said.
>
> I do not think it is useful to anyone to publish this document as an RFC,
> not
> even an informational one. It is perfectly fine, when specifying an
> intricate
> suite of protocols, to have a separate document that gives a broad
> architectural overview of them all without delving into the specifics
> necessary
> for implementation. RFC 4251, which outlines the SSH protocol, is a good
> example of this. But, crucially, RFC 4251 was published simultaneously with
> 4252-4256, which provided all those specifics. This document has nothing
> similar as a companion; everything it describes is simply aspirational. I
> do
> not see any value in publishing an RFC full of unfulfilled aspirations.
>
> _______________________________________________
> I2nsf mailing list
> I2nsf@ietf.org
> https://www.ietf.org/mailman/listinfo/i2nsf
>



-- 
regards,
John

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

<div dir=3D"ltr"><div>Dear Daniel,</div><div><br></div><div>thank you for p=
erforming this review. The following changes will be<br>implemented in vers=
ion 9 of this I-D, to be released on Monday 11/13.</div><div>In particular,=
<br></div><div><br></div><div><br></div><div>Change the last paragraph in s=
ection 4,</div><div>from:</div><div>=C2=A0=C2=A0 The above threats may be m=
itigated by requiring the use of an AAA<br>=C2=A0=C2=A0 framework for all u=
sers to access the I2NSF environment. This could<br>=C2=A0=C2=A0 be further=
 enhanced by requiring attestation to be used to detect<br>=C2=A0=C2=A0 cha=
nges to the I2NSF environment by authorized parties.<br></div><div><br></di=
v><div>to:</div><div>=C2=A0=C2=A0 The use of authentication, authorization,=
 accounting, and audit<br>=C2=A0=C2=A0 mechanisms is recommended for all us=
ers and applications to access<br>=C2=A0=C2=A0 the I2NSF environment. This =
can be further enhanced by requiring<br>=C2=A0=C2=A0 attestation to be used=
 to detect changes to the I2NSF environment<br>=C2=A0=C2=A0 by authorized p=
arties. The characteristics of these procedures will<br>=C2=A0=C2=A0 define=
 the level of assurance of the I2NSF environment.<br></div><div><br></div><=
div>Change section 6.1</div><div>from:</div><div>6.1.=C2=A0 Network Connect=
ing I2NSF Users and the I2NSF Controller</div><div><br></div><div>=C2=A0=C2=
=A0 ...</div><div>=C2=A0=C2=A0 Upon successful authentication, a trusted co=
nnection between the<br>=C2=A0=C2=A0 user and the I2NSF Controller (or an e=
ndpoint designated by it) will<br>=C2=A0=C2=A0 be established.=C2=A0 All tr=
affic to and from the NSF environment ...</div><div><br></div><div>to:</div=
><div>6.1. Network Connecting I2NSF Users and the I2NSF Controller<br>=C2=
=A0<br>=C2=A0=C2=A0 ...=C2=A0<br>=C2=A0=C2=A0 Upon successful authenticatio=
n, a trusted connection between the<br>=C2=A0=C2=A0 user and the I2NSF Cont=
roller (or an endpoint designated by it) will<br>=C2=A0=C2=A0 be establishe=
d. This means that a direct, physical point-to-point<br>=C2=A0=C2=A0 connec=
tion, with physical access restricted according to access<br>=C2=A0=C2=A0 c=
ontrol, must be used. All traffic to and from the NSF environment...<br></d=
iv><div><br></div><div>Change 6.2:</div><div>from:</div><div>6.2.=C2=A0 Net=
work Connecting the I2NSF Controller and NSFs</div><div>=C2=A0=C2=A0 ...</d=
iv><div><br></div><div>to:<br></div><div>6.2.=C2=A0 Network Connecting the =
I2NSF Controller and NSFs<br>=C2=A0<br>=C2=A0=C2=A0 ...<br></div><div>=C2=
=A0=C2=A0 Therefore, the transport mechanism used to carry the control mess=
ages<br>=C2=A0=C2=A0 and monitoring information should provide reliable mes=
sage delivery.<br>=C2=A0=C2=A0 TCP is the obvious current choice, but other=
s such as Multipath TCP <br>=C2=A0=C2=A0=C2=A0(MPTCP) and the Stream Contro=
l Transmission Protocol (SCTP) would <br>=C2=A0=C2=A0=C2=A0be applicable as=
 well.=C2=A0 Latency requirements for control message delivery<br>=C2=A0=C2=
=A0 must also be evaluated.</div><div>=C2=A0=C2=A0 ...</div><div>=C2=A0=C2=
=A0 I2NSF needs to rely on the use of standard I2NSF interfaces to<br>=C2=
=A0=C2=A0 properly verify peer identities (e.g., through an AAA framework).=
<br>=C2=A0=C2=A0 The implementations of identity management functions, as w=
ell as<br>=C2=A0=C2=A0 the AAA framework, are out of scope for I2NSF.<br>=
=C2=A0</div><div>to:</div><div>=C2=A0=C2=A0 ...</div><div><div>=C2=A0=C2=A0=
 Therefore, the transport mechanism used to carry management data and<br>=
=C2=A0=C2=A0 information must be secure. It does not have to be a reliable<=
br>=C2=A0=C2=A0 transport; rather, a transport-independent reliable messagi=
ng<br>=C2=A0=C2=A0 mechanism is required, where communication can be perfor=
med reliably<br>=C2=A0=C2=A0 (e.g., by establishing end-to-end communicatio=
n sessions and by<br>=C2=A0=C2=A0 introducing explicit acknowledgement of m=
essages into the<br>=C2=A0=C2=A0 communication flow). Latency requirements =
for control message<br>=C2=A0=C2=A0 delivery must also be evaluated. Note t=
hat monitoring does not<br>=C2=A0=C2=A0 require reliable transport.</div><d=
iv>=C2=A0=C2=A0 ...</div><div>=C2=A0=C2=A0 The network connection between t=
he I2NSF Controller and NSFs will<br>=C2=A0=C2=A0 use the trusted connectio=
n mechanisms described in section 6.1.<br>=C2=A0=C2=A0 Following these mech=
anisms, the connections need to rely on the use <br>=C2=A0=C2=A0 of properl=
y verified peer identities (e.g., through an AAA<br>=C2=A0=C2=A0 framework)=
.=C2=A0The implementations of identity management functions, as<br>=C2=A0=
=C2=A0 well as the AAA framework, are out of scope for I2NSF.<br></div><div=
><br></div></div><div>In addition, please see other changes to this thread =
(yesterday and this</div><div>morning, local time Singapore)<br></div><div>=
<br></div><div>best regards,</div><div>John</div></div><div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Tue, Oct 24, 2017 at 3:48 PM, Dani=
el Franke <span dir=3D"ltr">&lt;<a href=3D"mailto:dafranke@akamai.com" targ=
et=3D"_blank">dafranke@akamai.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">Reviewer: Daniel Franke<br>
Review result: Not Ready<br>
<br>
I have reviewed this document as part of the security directorate&#39;s ong=
oing<br>
effort to review all IETF documents being processed by the IESG. These comm=
ents<br>
were written primarily for the benefit of the security area directors. Docu=
ment<br>
editors and WG chairs should treat these comments just like any other last =
call<br>
comments.<br>
<br>
This document is too broad and too vague for any reasonable security review=
 to<br>
be possible. It expresses a desire to define a framework which satisfies<br=
>
certain requirements and use cases, but does not actually define anything<b=
r>
concrete. At its most specific, the document gives parametricity constraint=
s<br>
that future definitions must satisfy, such as being agnostic to network<br>
topology. This doesn&#39;t give me much to go on.<br>
<br>
The security considerations section is brief, calling out the need for acce=
ss<br>
control and for protecting the confidentiality and integrity of data. Again=
,<br>
with so few specifics, there&#39;s not much more to be said.<br>
<br>
I do not think it is useful to anyone to publish this document as an RFC, n=
ot<br>
even an informational one. It is perfectly fine, when specifying an intrica=
te<br>
suite of protocols, to have a separate document that gives a broad<br>
architectural overview of them all without delving into the specifics neces=
sary<br>
for implementation. RFC 4251, which outlines the SSH protocol, is a good<br=
>
example of this. But, crucially, RFC 4251 was published simultaneously with=
<br>
4252-4256, which provided all those specifics. This document has nothing<br=
>
similar as a companion; everything it describes is simply aspirational. I d=
o<br>
not see any value in publishing an RFC full of unfulfilled aspirations.<br>
<br>
______________________________<wbr>_________________<br>
I2nsf mailing list<br>
<a href=3D"mailto:I2nsf@ietf.org">I2nsf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i2nsf" target=3D"_blank" r=
el=3D"noreferrer">https://www.ietf.org/mailman/<wbr>listinfo/i2nsf</a><br>
</blockquote></div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_sig=
nature" data-smartmail=3D"gmail_signature"><div>regards,</div><div>John</di=
v></div>
</div>

--94eb2c1cb042a3f7ae055dd54b49--


From nobody Sun Nov 12 20:33:42 2017
Return-Path: <kaduk@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 BB215126DCA for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 20:33:40 -0800 (PST)
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 Qv6nEa_lc9Hm for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 20:33:39 -0800 (PST)
Received: from dmz-mailsec-scanner-6.mit.edu (dmz-mailsec-scanner-6.mit.edu [18.7.68.35]) (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 308FE124B0A for <ietf@ietf.org>; Sun, 12 Nov 2017 20:33:39 -0800 (PST)
X-AuditID: 12074423-0cbff70000007c25-b4-5a0920a0e3d7
Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-6.mit.edu (Symantec Messaging Gateway) with SMTP id E0.DF.31781.0A0290A5; Sun, 12 Nov 2017 23:33:37 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id vAD4XZLf027793; Sun, 12 Nov 2017 23:33:35 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id vAD4XUAc020062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 12 Nov 2017 23:33:33 -0500
Date: Sun, 12 Nov 2017 22:33:31 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: Paul Wouters <paul@nohats.ca>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, ietf@ietf.org
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
Message-ID: <20171113043330.GJ26425@kduck.kaduk.org>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprFKsWRmVeSWpSXmKPExsUixCmqrbtQgTPK4Pd8MYsJC18yWjzbOJ/F 4v2tS0wOzB5Llvxk8pj4bwOTx/d5TAHMUVw2Kak5mWWpRfp2CVwZj390shecEq44cvU5ewNj k0AXIyeHhICJROOxrcxdjFwcQgKLmSQ27d3JDuFsZJSYs/MsE4RzlUlib/9LVpAWFgFViScr W9hAbDYBFYmG7svMILaIgKLEpDOPWEBsZgEriduXN4JNEhZoYJR4tGYZWAMv0L6G//vZIKZu ZZQ4t/ojM0RCUOLkzCdQ3eoSf+ZdAopzANnSEsv/cUCE5SWat84GK+cUsJVYeu0h2ExRAWWJ vX2H2CcwCs5CMmkWkkmzECbNQjJpASPLKkbZlNwq3dzEzJzi1GTd4uTEvLzUIl0zvdzMEr3U lNJNjKBgZ3dR3sH4ss/7EKMAB6MSD++JKxxRQqyJZcWVuYcYJTmYlER5VT6zRwnxJeWnVGYk FmfEF5XmpBYfYpTgYFYS4T1yH6icNyWxsiq1KB8mJc3BoiTOuy1oV6SQQHpiSWp2ampBahFM VoaDQ0mCd5s8Z5SQYFFqempFWmZOCUKaiYMTZDgP0PATIDW8xQWJucWZ6RD5U4y6HM9mvm5g FmLJy89LlRLnrQQpEgApyijNg5sDSlIS2ftrXjGKA70lzLsHpIoHmODgJr0CWsIEtEQK5Dve 4pJEhJRUA6NZ3euDS+d/aP74X7LrBMvhisf8+9oNf3dME3mXaLVKlctulvmGuPv6am8Uw/0u 113YUb4m+/fMoN8Lwzdu71wtr8oX+8Xn+oGMzhMBNtWPFPjkjAzv/Zm49ti/Jz9s3+msNPf5 /KMndff7SVPnfuJcxN27SXn+ussnrJpeL1MSfxOn3bFsik+bEktxRqKhFnNRcSIAuqzj+y0D AAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rb_jbSOtduAc2GtUssnQKoRilk8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 04:33:41 -0000

On Sun, Nov 12, 2017 at 09:02:04PM +0800, Paul Wouters wrote:
> 
> 
> I concur with most of Stephane’s comments. And I find the use of the term “pervasive encryption” very problematic. Pervasive means:
> 
> “(especially of an unwelcome influence or physical effect) spreading widely throughout an area or a group of people.”
> 
> More encryption is never unwelcome to the enduser.

As the originator of the "pervasive encryption" term, I suppose I am obligated
to respond.  Though first I must note that absolute statements such as
"is never unwelcome" are risky positions to take, seeing as they are
undermined by even a single counterexample.

The idea for the "pervasive encryption" phrase stems from the use of
widespread encryption as a countermeasure against pervasive monitoring.
The somewhat negative ("unwelcome") connotation is not a primary motivator
for the use of the term, but does provide a secondary effect of making the
reader consider whether seeking ubiquitous encryption might have some downsides.
Alternatives such as "ubiquitous" or "widespread" encryption were not necessarily
appropriate, given that they could be seen as making claims about a current
state of affairs that would not be borne out by the facts.

I do not claim to have a solid, concrete, answer to the question of whether
there are downsides to seeking ever-increasing levels of encryption, but
am willing to admit the possibility of at least some localized downsides.

That said, please do not take my statements as an endorsement of the
current document overall.

> If this document listed these practises, along with valid methods for operators to switch to, i could be convinced the document is useful. But as Stephane pointed out, a lot of these problems are desired features. That the operator has less networking debugging tools is an unavoidable side effect, but should not be used as an argument against more encryption.
> 
> But in its current form, it seems this document would be prime candidate for operator misbehaviour justification “sanctioned” by the IETF. 
> 
> Note that I _do_ believe in the authors’ good intention of just documenting the new problems operators face. But the IETF will have taken these issues into consideration already before it published the RFCs.

I do sympathize with your concerns here.

-Ben

> This documents feels (unintentionally) that we need to go back to be drawing board to reconsider these operator issues.


From nobody Sun Nov 12 21:41:17 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 341F61287A5 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 21:41:15 -0800 (PST)
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 0qVaNf5I8IAX for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 21:41:12 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::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 26F49127337 for <ietf@ietf.org>; Sun, 12 Nov 2017 21:41:12 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id x7so11133781pfa.1 for <ietf@ietf.org>; Sun, 12 Nov 2017 21:41:12 -0800 (PST)
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=gc+c6Qa/AkDie8SoebnwBvefvzD/Ty+OgpRt4r8Htus=; b=EygnTKmScGXVQ8gIrzQAoHU48x811oIAx+qfTnxykdtr78Km34KmZ28pCUuRh7sbqG qTa2/sfGPxAxZWmADVWtPCValYpy9PXIu8uwqMSnJ5vWMgDU7yDMaRVHgrAtF00ROK/F //yR1cb+pRZaUeCFRrM1Yxm7TO5+7S7t3YCIourY4vWKgbDYCFGHE1v2EfeDH3nNQKwy gnUJjxsw2rthosAwBIQsrd7DreLd6WfXqv1DYD7rff7CxIYIdkuXFHZ28kw9/boW5qij 2BEqIO+i2HTBn2bM7+2Ng1NWcU0No0m4k72W5MFhvz59i4ycFjRH6RwNDOTjnpwpXmDL MTMA==
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=gc+c6Qa/AkDie8SoebnwBvefvzD/Ty+OgpRt4r8Htus=; b=brrWWYr37nUUJx9rXSiZlT50ubqA7SEkHDAHwUBel5P/oTxEcMVdP7vtWsFB1w3hEx ZHVx5hRo5xYdL8HDjy1GhXe90juKYvwa4i+tFQtnW9u2gWMJa/ws49tABh5+V7YrxqQ7 zI9koMzugee86epLwIkoF+xGaLct+reotMrmrZMKF8iXBtGVOqxeuFL+HRXGWds+XpFF ldlNkoAdgBkFwHurBI9eq6MxDpCptyrit1v8Sno0gtEq/6XEdQYBk7jUuwqxfNgN6+po feKA91ZL7Y/qCfLlD7arUBoo+c5Y7a2w5ufPOGfN11NEriiLsiAfKhhIihkgwSfYemcE N+sw==
X-Gm-Message-State: AJaThX5++V4UY2XQTp+XsoHPWh9etbesolLQisyoHZjG+TRqHiAA8YTW wBMeWR109KYrDXlPpaUnza6p7J5sdNIwNC/T6XY=
X-Google-Smtp-Source: AGs4zMbfmYN9QSBVW/ar6hQMjIrwIReTzAdXgWJ+t5Hf6DMbVxFRBr6+NLYH6LFw12kMmJHWi7lXhTyyAMPdzgREOIs=
X-Received: by 10.99.109.202 with SMTP id i193mr7595671pgc.443.1510551671482;  Sun, 12 Nov 2017 21:41:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.155.9 with HTTP; Sun, 12 Nov 2017 21:40:30 -0800 (PST)
In-Reply-To: <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 13 Nov 2017 00:40:30 -0500
Message-ID: <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Paul Wouters <paul@nohats.ca>
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, 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/gdsVrLnXOnl-yVKw8P3WbMYkFvg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 05:41:15 -0000

Hello,

Thanks for your comments on the draft.  We will respond to all
comments, but it may take time as it's a busy week and this message
seemed like one that I could respond to more quickly than the prior.

On Sun, Nov 12, 2017 at 8:02 AM, Paul Wouters <paul@nohats.ca> wrote:
>
>
> I concur with most of Stephane=E2=80=99s comments. And I find the use of =
the term =E2=80=9Cpervasive encryption=E2=80=9D very problematic. Pervasive=
 means:
>
> =E2=80=9C(especially of an unwelcome influence or physical effect) spread=
ing widely throughout an area or a group of people.=E2=80=9D
>
> More encryption is never unwelcome to the enduser.

Could you propose an alternate title?  We used the term ubiquitous
previously, and it was changed in a prior IETF list discussion to the
current title.

>
> If this document listed these practises, along with valid methods for ope=
rators to switch to, i could be convinced the document is useful. But as St=
ephane pointed out, a lot of these problems are desired features. That the =
operator has less networking debugging tools is an unavoidable side effect,=
 but should not be used as an argument against more encryption.

The purpose was to document the effects of increased encryption, not
to solve any of the problems. As the document states, there are cases
where the feature/function may just be eliminated with no way to
perform the desired feature (desired by some operators).  If you don't
look at the impacts as a first step, they will be an impediment to the
adoption of E2E protocols and the evolution that is happening with TLS
1.3 and QUIC for example.  By opening up the conversation, and having
both sides look at the problems, we are more likely to achieve E2E in
deployment scenarios.  Continuing an arms race is not effective -
rather stepping back to document impacts is a first step toward
removing obstacles to deployment for E2E.

I thought this point was fairly clear in the introduction, so if it is
not and you have wording suggestions, please provide them.

>
> But in its current form, it seems this document would be prime candidate =
for operator misbehaviour justification =E2=80=9Csanctioned=E2=80=9D by the=
 IETF.

The introduction makes it quite clear that it is not the case and
states the documented effects are not IETF sanctioned.

>
> Note that I _do_ believe in the authors=E2=80=99 good intention of just d=
ocumenting the new problems operators face. But the IETF will have taken th=
ese issues into consideration already before it published the RFCs.

Operators have responded very positively to this draft that has let
them open up the conversation, so I don't think the problems have been
looked at by the developers of protocols like TLS 1.3 and QUIC.
Operators were unaware of the changes.  Now it's time to have the
discussions and see how we can work together so that deployment of e2e
encryption happens.  Just because we release protocols does not ensure
their adoption.

>
> This documents feels (unintentionally) that we need to go back to be draw=
ing board to reconsider these operator issues.

Not necessarily.  The framing tries to make the intentions clear.  Can
you take a look at the introduction and let us know where that is not
clear?

Best regards,
Kathleen

>
> Paul
>
>> On Nov 12, 2017, at 19:55, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote=
:
>>
>> On Mon, Nov 06, 2017 at 06:06:50AM -0800,
>> The IESG <iesg-secretary@ietf.org> wrote
>> a message of 37 lines which said:
>>
>>> The IESG has received a request from an individual submitter to
>>> consider the following document: - 'Effect of Pervasive Encryption
>>> on Operators' <draft-mm-wg-effect-encrypt-13.txt> as Informational
>>> RFC
>>
>> I'm quite concerned by this document. Basically, it seems to me it
>> deviates a lot from a simple description of current practices, and
>> goes into promoting them. The overall effect seems to me very
>> dangerous. One can easily read this document as "encryption is a pain
>> for the operators, we should not promote it too agressively".
>>
>> My opinion is that its publication as it is would inflict real harm to
>> the efforts of IETF to promote privacy (which implies, among other
>> things, a lot of encryption).
>>
>> The document also completely ignores network neutrality, not to
>> mention the end-to-end principle.
>>
>> More precisely:
>>
>>> This document discusses practices currently used by network
>>> operators to manage, operate, and secure their networks
>>
>> Actually, it does not "discuss": it describes them, using only the
>> arguments of the operators that use these practices, rarely
>> questioning them.
>>
>>> the impact of pervasive encryption
>>
>> Note that we are far from "pervasive encryption". For instance, the
>> DNS traffic is almost entirely in clear (RFC 7858).
>>
>>> For example, the traffic patterns between server and browser are
>>> dependent on browser supplier and version
>>
>> That's a good example of why HTTP sessions must be encrypted: the
>> User-Agent: field is very revealing, among other infos sent by the
>> browser, as exemplified by the Panopticlick
>> <https://panopticlick.eff.org/>
>>
>>> Network operators use packet captures and protocol-dissecting
>>> analyzers when responding to customer problems,
>>
>> Not all network operators are so benevolent. I doubt that many 30 $ or
>> 25 =E2=82=AC / month ISP use tcpdump when the customer has a
>> problem :-) Seriously, this sentence is very dangerous because of:
>>
>>> The ability to identify the problem application's traffic is
>>> important and deep packet inspection (DPI) is often used for this
>>> purpose
>>
>> This really looks like an attempt to "sell" DPI by explaining that it
>> may benefit the users. Actually, I would like to see my ISP going into
>> such efforts to help me but I doubt it will be the case.
>>
>> Note that no ISP document the practices it actually use against user
>> flows. This is sufficient proof that they are not done in the interest
>> of the users.
>>
>>> For example, by investigating packet loss (from TCP sequence and
>>> acknowledgement numbers), round-trip-time (from TCP timestamp
>>> options or application-layer transactions, e.g., DNS or HTTP
>>> response time), TCP receive-window size, packet corruption,
>>> inefficient fragmentation, or application-layer problems, the
>>> operator can narrow the problem
>>
>> Almost all of these investigations can be performed even if TLS or SSH
>> is used. Again, it really seems an effort to make DPI acceptable.
>>
>>> Because of this, application server operators using increased
>>> encryption should expect to be called upon more frequently to assist
>>> with debugging and troubleshooting
>>
>> Hard to read this as something else than a threat "do not use
>> encryption or your business will suffer".
>>
>>> A common, early trigger for DDoS mitigation includes observing
>>> uncharacteristic traffic volumes or sources; congestion; or
>>> degradation of a given network or service.  One approach to mitigate
>>> such an attack involves distinguishing attacker traffic from
>>> legitimate user traffic.
>>
>> Are there really dDoS attacks using encryption? Hard data welcome.
>>
>>> Mobile networks especially rely on content/application based
>>> prioritization of Over-the-Top (OTT) services
>>
>> This is a very important point: if encryption really prevents
>> prioritization of some services over the others, then it means we need
>> more encryption, not less. If encryption can help preserve network
>> neutrality, this is a good reason to use it even more.
>>
>>> Due to the characteristics of the mobile link, performance-enhancing
>>> TCP proxies may perform local retransmission at the mobile edge.  In
>>> TCP, duplicated ACKs are detected and potentially concealed when the
>>> proxy retransmits a segment
>>
>> Again, TLS or SSH do not prevent this sort of hacks.
>>
>>> In addition to caching, various applications exist to provide data
>>> compression in order to conserve the life of the user's mobile data
>>> plan and optimize delivery over the mobile link
>>
>> I know that some mobile operators (see, in french,
>> <https://www.hteumeuleu.fr/la-compression-dimages-par-les-operateurs/>)
>> apply a LOSSY compression without the user consent or even
>> knowledge. Again, if end-to-end encryption prevents this, this is a
>> very good reason to deploy encryption.
>>
>>> These regulations include Lawful Intercept, adherence to Codes of
>>> Practice on content filtering, and application of court order
>>> filters.  Such regulations assume network access to provide content
>>> filtering and accounting, as discussed below.
>>
>> It seems to me that RFC 1984 already replies to this reasoning.
>>
>>> This type of granular filtering could occur at the endpoint.
>>> However, the lack of ability to efficiently manage endpoints as a
>>> service reduces providers' ability to offer parental control.
>>
>> I would be specially unhappy if IETF were to publish a RFC with such a
>> sentence without follow-up comments. Filtering MUST be done at the
>> endpoint, otherwise it is not a service, it is censorship.
>>
>> If we assume that the subscriber wants parental control, then we must
>> conclude that he/she will have no problem sending the traffic to a
>> filtering proxy. No need to break encryption for that.
>>
>>> Some mobile carriers use HTTP header insertion (see section 3.2.1 of
>>> [RFC7230]) to provide information about their customers to third
>>> parties or to their own internal systems [Enrich].
>>
>> Again, this technique, which has very serious privacy consequences
>> (see the mentioned reference [Enrich] with for example Vodafone which
>> added the phone number and the IMEI in HTTP headers) MUST NOT be done
>> and, if encryption stops it, great.
>>
>> Editorial issues:
>>
>>> Currently, some mobile network service providers redirect the
>>> customer using HTTP redirect to a page that explains to those
>>> customers the reason for the blockage and the steps to proceed
>>
>> A mention of RFC 6108 would be cool here.
>>
>>> monitor incoming mail to remove SPAM
>>
>> Why is spam uppercased?
>



--=20

Best regards,
Kathleen


From nobody Sun Nov 12 21:55:09 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 8575C1287A5 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 21:55:08 -0800 (PST)
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 5EPAh-v9AxH9 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 21:55:06 -0800 (PST)
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 6AE2A127977 for <ietf@ietf.org>; Sun, 12 Nov 2017 21:55:06 -0800 (PST)
Received: by mail-pg0-x22c.google.com with SMTP id j16so6428082pgn.9 for <ietf@ietf.org>; Sun, 12 Nov 2017 21:55:06 -0800 (PST)
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=j/Fcsdp00/m7v4a0VOsVI7CcNTpCxRZzILSOgo57v+k=; b=L0v63gH9G7RF7SduTaIgYnVmNJ08QElD0xF7H9PLtl7yc8+Qfye55KZdc4cIV2G0AZ Kth2j1w6I+r/vjbo0avzGYkc7Fa6qkIi2KlBDq9E5jF7clIzxBgWUfhUy9JelrAdMIc2 H+y0Zux/hooVV0g1Dr/RXncGBmGs01r5dERi++tjPRAZJzVy02QD9XY30DpVEz16lQLV QLGw7MBtM4FgmBr3MbCXerrYwY/rX+nSQus+Z1q5OySYzIpGP+W1iGzDiS23L5LwBVYx tUbF6Eh1YwrUaHD8MDnGDV2ekcmJwYTtNsi6sWkSu/1QCHO601eeatK9fFKyIN9tSSH6 gu2g==
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=j/Fcsdp00/m7v4a0VOsVI7CcNTpCxRZzILSOgo57v+k=; b=MTu0hq17HJwzZ+2fat84oqFMZwCfk5tfnjMXSLcejnnzpZ9Jg1DxPIM+dme2VlrLda 0zr1LoqLJMiycbagmMFcYwa+1OjlLon8D1/XKTernw5e8x2upPbvzyD7Wi4MtGAAXiN4 Giwyk0owGq5li33TVzH11Hy+7bRO8lpy/f3CdDoSqRQ9GsVenmliEIhsyhOiy/pwmgOl qUbQUankTPlHSjLJgJKYQaJeB388mV64cHuO2I7v1XCcSVrF5Q50NKnvizsoELnMPhLu +YPQE519sDgJxm0mPdp2dBA7QzLfu2La1Ab1RzphsnII5iZqqGiFNlqJtW5WskZLsdE3 4r1A==
X-Gm-Message-State: AJaThX7G2OuLIcay08aMfI00CMiFZrRtYpGTXB8Afa1xWmzViPlLHfpJ 46trxG4dVFrSPuyTov4oPlurmhhQN7ai3LyQi5w=
X-Google-Smtp-Source: AGs4zMavSohkPwzrxa67MoPgSV0wK/Nwy7dY7ywEqO9PyMUB3oiV2Lxizy1SR0iCrxZStFtTy4qnQiMLKJhdigNSF2Y=
X-Received: by 10.99.109.202 with SMTP id i193mr7619881pgc.443.1510552505868;  Sun, 12 Nov 2017 21:55:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.155.9 with HTTP; Sun, 12 Nov 2017 21:54:25 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20171112122108.10693078@elandnews.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <6.2.5.6.2.20171112122108.10693078@elandnews.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 13 Nov 2017 00:54:25 -0500
Message-ID: <CAHbuEH5a8Z=cOyksddxotg+XnAiGP0ZwG8J6fVFt3iBJqkgyGw@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SKYUXeNBlkE3Drrjw3R9tQmnJdw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 05:55:08 -0000

SM, thanks for your review of this draft.

On Sun, Nov 12, 2017 at 4:43 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Hello,
> At 06:06 AM 06-11-2017, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the
>> following document: - 'Effect of Pervasive Encryption on Operators'
>>   <draft-mm-wg-effect-encrypt-13.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-12-04. Exceptionally, comments may be
>
>
> On reading the draft, I wondered whether the authors of the draft have an
> opinion about "responsible encryption".

The authors are concerned with user privacy and obstacles to deploying
encryption.  If the obstacles are not documented and discussed,
adoption of encryption could suffer.
There is a statement in the introduction about operators being
interested to protect end user privacy and this has been repeated by a
number of contributing operators.  The desire to document the impacts
to their current operations is a positive one as they need help to
figure out if there are other ways to achieve the goal of the
described functions in new ways or if it just won't be possible.

>
> In Section 1.1:
>
>   "OS has been implemented as NULL Authentication with IPsec [RFC7619]
>    and there are a number of infrastructure use cases such as server
>    to server encryption, where this mode is deployed."
>
> It is possible to find use cases of deployment.  That does not mean that it
> is always a good idea.

I'd be hesitant to add text that says it doesn't mean it's a good idea
as that would feed into the assumptions being made in this thread that
this draft is trying to prevent the deployment of encryption, when it
is just the opposite.  Unless you mean that there should be a
statement that authenticated encryption is preferred?

>
> In Section 2:
>
>   "This and other increases in the use of encryption had the immediate
>    effect of helping protect the privacy of users' data, but created a
>    problem for some network management functions."
>
> Is this about privacy or is it about a security loophole?

That could depend on the content of data exposed.  Are you suggesting
a text change?

>
> In Section 2.1.2:
>
>   "The ability to identify the problem application's traffic is
>    important and deep packet inspection (DPI) is often used for
>    this purpose."
>
> Is debugging choppy video the main purpose of DPI?  Why should perversive
> surveillance software/hardware be used to debug application issues?

If you break this sentence apart, the "import" part is the ability to
identify problems in application traffic.  Many applications do a poor
job of logging, so DPI is sometimes used.  A solution would be to
improve logging and debugging in applications, which is suggested in
the draft as an answer to many of the documented effects.  I'm not
sure I follow your second question or what text led you to the
question?  I read this sentence as saying it is one way it is done
today, because it is not working to do this directly with debug
information from the application.  I read this as documenting what is
done and it leads me to think that applications need to improve their
debugging and logging capabilities.

>
> In Section 2.3:
>
>   "These regulations include Lawful Intercept, adherence to Codes of
>    Practice on content filtering, and application of court order filters."
>
> Are the "Codes of Practices" part of regulations?  Are there references to
> those Codes of Practices?
>
> In Section 3.2.2:
>
>   "STARTTLS ought have zero effect on anti-SPAM efforts for SMTP traffic."
>
> I doubt that STARTTLS cause any significant problem as the receiver has the
> ability to inspect emails.

So you agree with this statement?  Or are you asking a question?  If
you could clarify, I would appreciate it.

>
> In Section 4.1.1:
>
>   "detect and defend against Internet DDoS attacks, including both
>    volumetric and layer 7 attacks."
>
> Does the IETF use the OSI layer (re. layer 7)?
>
> As an overall comment, there are many uses of "many" in the document.  I
> read the entire document.  I understand that the authors may have put a lot
> of effort in this work.  However, I preferred to reduce the effort as it was
> a bit tedious to do a detailed review.  The title of the document is "Effect
> of Pervasive Encryption on Operators". Is this document about making the
> case against RFC 7258?

You may want to take another read of RFC7258.  This is a early step in
one of the stated goals of that document - to find a balance between
protections and the ability to perform network management by
documenting the impacts to serve as a start to that conversation.

>
> Regards,
> S. Moonesamy



-- 

Best regards,
Kathleen


From nobody Sun Nov 12 22:30:48 2017
Return-Path: <victor@jvknet.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2AF12948F for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 22:30:46 -0800 (PST)
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=jvknet-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 jxJdvxdZnZ_r for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 22:30:44 -0800 (PST)
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 78618129489 for <ietf@ietf.org>; Sun, 12 Nov 2017 22:30:44 -0800 (PST)
Received: by mail-oi0-x229.google.com with SMTP id r128so10571548oig.9 for <ietf@ietf.org>; Sun, 12 Nov 2017 22:30:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=KBwqOuzQUXPI4nyFFcpRRpWljDFOpaEHW6Y846fCoZ4=; b=hmuWJtqQO/DiKwoqxh8nR7rWfjMrizHf+uvFf1jHG8q4r3Do3S2KJxFYQx/QGBrof4 mf7/25oYTIU0hsnqxmqhzpnw70AfLp7diNBMKjzhxfz+aoOdtUqPqgZdSPbkEWCnHYjl Ugq4dZn71E4MSRC2s4KOVp05HVa8kMLbbe8MeJIArZMEtGtpF8vZttBaN1RWA/lJ2L88 PIxMJfEg4YnOsXKtj0tTqaf/D037RvS9E3Pdwnr4sSIUfgof7AZyFRnLkiOb/O9cSbvq jY31r46Z7x/w6p0WdkmzdPVHP1W8u+DASqv+cd3QtaTjIVKQbSB9SlZlpumDplyMm5f3 LASw==
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=KBwqOuzQUXPI4nyFFcpRRpWljDFOpaEHW6Y846fCoZ4=; b=ol3p0DpWAW14B+pAG7xHhP24IplP5sOdtkGl8vxXbxyWPvyu/IEvy5MvOQ65hd8IFE 0hCPrFqIo9qhz4IDTcEhMzNHHhHnNZkVuhe9+gqU+ctDDh3LeH+cHroUSb6qySyX8ZvN zYCz2GU1gjH8sFVdeF1Hi/mzqAEq24CtoKAaycKRHcd+8A535V/Jwcv+rxbZX76nU/Cb 7znrOZdqe7o2rj9FuEQ6iCH38wbTIqJ2BiRhG3v7vJeb7Bgg5l5U/f9KkZPcwTJ3eP5w 97yGopndkrWnHsRkfzEWYu8uIQ+sKOJEwIcqscpl3xsP1Wlo/c8D1Op0QALdi4/XcrC+ 33MQ==
X-Gm-Message-State: AJaThX7whAFAJMbq99l5VHfB0DVa6FTamP1lhODqh+b6oEa9cAw6gwcW Kc4nczJGAh3IflOJkjX2Nr7hz4J+T+U5pZekEV13vQ==
X-Google-Smtp-Source: AGs4zMafUMQCgLiqlJywSOX7lJ2xqw0+Cl8FAbaju+VUBRiaaM3AP7ckw8lm1F1aPhBLz0TG2ru+kaNrry89gDQMuoc=
X-Received: by 10.202.241.85 with SMTP id p82mr5020465oih.169.1510554643767; Sun, 12 Nov 2017 22:30:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.13.74 with HTTP; Sun, 12 Nov 2017 22:30:43 -0800 (PST)
In-Reply-To: <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Mon, 13 Nov 2017 01:30:43 -0500
Message-ID: <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: Paul Wouters <paul@nohats.ca>, 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/HioyFpN655sOoSvotqaEvKhvKNg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 06:30:46 -0000

Kathleen,

On Mon, Nov 13, 2017 at 12:40 AM, Kathleen Moriarty
<kathleen.moriarty.ietf@gmail.com> wrote:

> On Sun, Nov 12, 2017 at 8:02 AM, Paul Wouters <paul@nohats.ca> wrote:
>>
>>
>> I concur with most of Stephane=E2=80=99s comments. And I find the use of=
 the term =E2=80=9Cpervasive encryption=E2=80=9D very problematic. Pervasiv=
e means:
>>
>> =E2=80=9C(especially of an unwelcome influence or physical effect) sprea=
ding widely throughout an area or a group of people.=E2=80=9D
>>
>> More encryption is never unwelcome to the enduser.
>
> Could you propose an alternate title?  We used the term ubiquitous
> previously, and it was changed in a prior IETF list discussion to the
> current title.
>

The general definition when comparing various dictionaries seems to
associate the word "pervasive" with the common meaning of "spread
throughout".

Based on that, the title seems appropriate.

regards,

Victor K


>
> Best regards,
> Kathleen
>


From nobody Sun Nov 12 23:12:13 2017
Return-Path: <victor@jvknet.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1FE128D16 for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 23:12:11 -0800 (PST)
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=jvknet-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 cu_hDhbItHKh for <ietf@ietfa.amsl.com>; Sun, 12 Nov 2017 23:12:09 -0800 (PST)
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 3A711129483 for <ietf@ietf.org>; Sun, 12 Nov 2017 23:12:09 -0800 (PST)
Received: by mail-oi0-x232.google.com with SMTP id v123so484123oif.12 for <ietf@ietf.org>; Sun, 12 Nov 2017 23:12:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=FMe5gxqeMG949XOsaFWHhkjRvoW8bSm6A6w03/pbV0g=; b=abBbgEBxhWLRv5Phnzkvwd21ymTz9DFa9kvv8oYUEi3zkQbyEgkOpHu4OamTWNsfIH lHvPKoT0/I5NYnJ9n3MLlcbXDkA56qSKBXjNbkeC6eI1qTBHCF6kPdIeSuBFKYIfwJuT HEwu7m5qwcuF6/CDDzulHDU8tO0iestggDU+eA01KwaHK/u4xSDXiRgURqFFOs6I+S8d a3+THoZoifvTQGeqrCfaz/B1MMDpjTzZ/OTxOVrT7Tba2oOW/K9BMSYk1jjhy3gy/PK2 OOoIXhqiLNCXajMxcfV0nqlQ9MGKYRPQjjjp0K9m84DaX7EqE7YzZZd0x2K2wbWeLJkt mM8A==
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=FMe5gxqeMG949XOsaFWHhkjRvoW8bSm6A6w03/pbV0g=; b=XoDAgEwIQBkzUE43qoypJCtJkH2SFhkJ3/AkJryYg/V+ERz5WndsT7IUk2Fwspf4cD vtRer93LafdhmlV95ez+rFmuedIb8runnZJMZbDhCA9b8WiDY3Laf9kpzIFu4YH8mFwl th/eIpC+4iia2GlaBCI32zEwhigHIhjrRezy2Z3KprGH9tRP34JiTFX3sgncSgIEQRGS ZMpYVUMx5lv2CwAeWF7wnk7FIfMWdQdLXZwszSpJdgnzfinc0KPIQ5tFqToj7aDOaRdo H6YMYLs8P4JGuxgxthqme25rGQOCymVa899iy6f5cMISwBlGS0+czHe9W+ibqCOC1RtP 6NtA==
X-Gm-Message-State: AJaThX4Vw5GKwKxmxUqnhiRLGAFJ9cZJ6Pkc+qdY3xzG+gJQ3rYDiXjA nIQrpHwgvBDiVSqmnzFE55SshMjZVuxO7wCPnLNGow==
X-Google-Smtp-Source: AGs4zMYRLAXCujbR3XxM1sz8KjulDQ/DxTD5VMbS0GS+1U1NC+z8X4PzJnc+ITjAZvZel1v95ykBc4RLcfAHLEk4l50=
X-Received: by 10.202.217.6 with SMTP id q6mr5020650oig.37.1510557128366; Sun, 12 Nov 2017 23:12:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.13.74 with HTTP; Sun, 12 Nov 2017 23:12:07 -0800 (PST)
In-Reply-To: <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Mon, 13 Nov 2017 02:12:07 -0500
Message-ID: <CAJc3aaPR-xEJ4y7MU3b1AsaXfTKaNTCgxpyQYVNXtFMNW0K2HQ@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: Paul Wouters <paul@nohats.ca>, 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/ii0w0gGgp90ieHmqB02IKhBhdnU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 07:12:11 -0000

On Mon, Nov 13, 2017 at 12:40 AM, Kathleen Moriarty
<kathleen.moriarty.ietf@gmail.com> wrote:
> Hello,
>
> Thanks for your comments on the draft.  We will respond to all
> comments, but it may take time as it's a busy week and this message
> seemed like one that I could respond to more quickly than the prior.
>
> On Sun, Nov 12, 2017 at 8:02 AM, Paul Wouters <paul@nohats.ca> wrote:
>>
>>
>> I concur with most of Stephane=E2=80=99s comments. And I find the use of=
 the term =E2=80=9Cpervasive encryption=E2=80=9D very problematic. Pervasiv=
e means:
>>
>> =E2=80=9C(especially of an unwelcome influence or physical effect) sprea=
ding widely throughout an area or a group of people.=E2=80=9D
>>
>> More encryption is never unwelcome to the enduser.
>
> Could you propose an alternate title?  We used the term ubiquitous
> previously, and it was changed in a prior IETF list discussion to the
> current title.
>
>>
>> If this document listed these practises, along with valid methods for op=
erators to switch to, i could be convinced the document is useful. But as S=
tephane pointed out, a lot of these problems are desired features. That the=
 operator has less networking debugging tools is an unavoidable side effect=
, but should not be used as an argument against more encryption.
>
> The purpose was to document the effects of increased encryption, not
> to solve any of the problems. As the document states, there are cases
> where the feature/function may just be eliminated with no way to
> perform the desired feature (desired by some operators).  If you don't
> look at the impacts as a first step, they will be an impediment to the
> adoption of E2E protocols and the evolution that is happening with TLS
> 1.3 and QUIC for example.  By opening up the conversation, and having
> both sides look at the problems, we are more likely to achieve E2E in
> deployment scenarios.  Continuing an arms race is not effective -
> rather stepping back to document impacts is a first step toward
> removing obstacles to deployment for E2E.

This was my understanding as well and seems like a very rational and
healthy way of achieving the overall desires stated in RFC7258.
Documenting the realities of production networks is needed.


>
> I thought this point was fairly clear in the introduction, so if it is
> not and you have wording suggestions, please provide them.

It seems clear to me.

>
>>
>> But in its current form, it seems this document would be prime candidate=
 for operator misbehaviour justification =E2=80=9Csanctioned=E2=80=9D by th=
e IETF.
>
> The introduction makes it quite clear that it is not the case and
> states the documented effects are not IETF sanctioned.
>
>>
>> Note that I _do_ believe in the authors=E2=80=99 good intention of just =
documenting the new problems operators face. But the IETF will have taken t=
hese issues into consideration already before it published the RFCs.
>
> Operators have responded very positively to this draft that has let
> them open up the conversation, so I don't think the problems have been
> looked at by the developers of protocols like TLS 1.3 and QUIC.
> Operators were unaware of the changes.  Now it's time to have the
> discussions and see how we can work together so that deployment of e2e
> encryption happens.  Just because we release protocols does not ensure
> their adoption.

These are very important points.  If we want to to see our efforts on
E2E encryption realized, ensuring deployability is important. Ignoring
the operator side of the equation (which effectively connects the user
to the Internet) would seem like a problematic approach.  If we want
happy end users, then performance along with encryption (among other
things) are needed (not one in exclusion of the others).

The Internet is a complex place (with its massive collection of
distinctive networks, users, and applications).  Introducing changes
is not a simple task and oversimplifying what we need to do to affect
the right change will not equate to the end goals we want to achieve.

The draft is documenting challenges we should consider as we conduct
our work.  I don't see how this is a problem.

regards,

Victor K


From nobody Mon Nov 13 00:07:40 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 C758C12773A for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 00:07:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=JJ4Ryq4G; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=oUHbAq+G
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBf29Psrd9sd for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 00:07:33 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE975126C0F for <ietf@ietf.org>; Mon, 13 Nov 2017 00:07:33 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 161F6204F7; Mon, 13 Nov 2017 03:07:33 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 13 Nov 2017 03:07:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=UB6ATvq+bq1KPdVWn1MLLIlw1lxyk Od/LEgbymP0JTU=; b=JJ4Ryq4Gf7JAeaAH+YhfmPDQkQkGO0StO3GpgTn14XmkB oOukcCJ4MBRHTKsq/hILmOV7XsLifO+lTiqB4bjSej1ExTPzD4wZXlocVA4W1Jyf yhtP3o6kDDJIbglL2Za3W/MozAxFTyBSOMuPD9/TUx8jyTCvCU0eeEBhr4wIRNbj xgye/Sf5FV4myjOz8SlIqQEj/8206X6Egbqi80qslv7FIvJGLoooxknkvSD26tEA b58PUz/j64Bi69+U/jeA47GIxsGV+ewAQ7oarLMvUu90paJHerl+IEUfLdsKOFwq 9HGPkWbFCQUweC/QQk0F8nuh2HPtLJLMQ8L9GHyog==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=UB6ATv q+bq1KPdVWn1MLLIlw1lxykOd/LEgbymP0JTU=; b=oUHbAq+Gy8JnGpYSyk8Chm BpNaG28kCHY2d8AdR8tYIpcn8V+f+JnoCjuPbGuuF2KfgH/S6TauX7s3xgmMRIU/ ROtdzysmrPGVpZXv5mxhcwQqTm8Sd0+V+WuGbZF1gmeG/YDyg1rgMOfRZ8jG4QNr QuUuDElwR5z6d6ug8QximbkQN77iv94B7By1vHNHuNv7jZfTVZkmuLC6IJMCRgqZ yQnjMvHhGhQp2uQRL1TNFOdfYhnY5BrytH8JxyRYDHj1und00rwKO73zByfZa4HV NgmJllzZRgJE2lBjQfmANobddFfKOtZquUMdpRty/MIFzpTVLZOD0ElqRGO1GKag ==
X-ME-Sender: <xms:xVIJWnyDX-32-34Hbmsrtoh5FKc2sBssiDARoo8aveaClYXp_WZy6A>
Received: from dhcp-95ea.meeting.ietf.org (dhcp-95ea.meeting.ietf.org [31.133.149.234]) by mail.messagingengine.com (Postfix) with ESMTPA id 224B97F961; Mon, 13 Nov 2017 03:07:31 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com>
Date: Mon, 13 Nov 2017 16:08:08 +0800
Cc: IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ki_xLQkxTP9Q-3okmqmFgMmI8sQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 08:07:38 -0000

Since we're talking about the title, I had a different reaction to it; =
currently, it reads as if *all* operators are necessarily affected by =
pervasive encryption.=20

In the discussions I've had, the great majority of operators have said =
they are not affected by pervasive encryption (YMMV, of course), so I =
wonder if a title like "Reported Effects of Pervasive Encryption on =
Operators" or "Effects of Pervasive Encryption Purportedly Encountered =
by Some Operators" would be more appropriate.=20

Even then, many of the areas discussed lack important context about =
whether or not there are other options to achieve the same goal, and how =
prevalent their use by operators is. For example, the sections on =
Content Compression and Content Encryption beg these questions.=20

It might be useful to have a list of potential effects on network =
operators without that context, but some of the items still seem to be =
written in a way that assumes the intrinsic value and uniqueness of the =
technique being discussed (e.g., Performance Enhancing Proxies), which =
can be deeply misleading (despite the attempt at positioning in the =
Introduction). If this were Wikipedia, I'd say there were several NPOV =
issues remaining here.

A few more comments:

1. Introduction - "Ideally, new methods could be developed to accomplish =
the goals of current practices despite changes in the extent to which =
cleartext will be available to network operators." It's not at all clear =
that this would be ideal, since the goals of some of the documented =
practices are quite questionable, both technically and ethically.

2.2.5 Caching and Content Replication Near the Network Edge - "Web =
proxies are widely used [WebCache]" -- the reference covers four =
US-based mobile networks, only two of which deployed caching (table 1), =
so it's hardly supporting this claim, and the claim itself is about =
proxies, not caching. Forward proxy caching (which is the relevant thing =
here) has been steadily declining in deployment for years, partially =
because of the increased deployment of encryption, but also because =
content providers don't trust forward proxies; they have a reputation of =
too often taking liberties with serving stale responses.

2.2.5 Caching and Content Replication Near the Network Edge - "... and =
caching is supported by the recent update of "Hypertext Transfer =
Protocol (HTTP/1.1): Caching" in [RFC7234]."  Caching was first =
supported by RFC1945, HTTP/1.0.

2.3.4 HTTP Header Insertion - I'm deeply uncomfortable with having this =
text in an IETF document without a LOT more context.

4.1.3.3  HTTP Service Calls - This is confusing; it it talking about =
sniffing the back-end service calls, or the original request?=20
=20

Cheers,


> On 13 Nov 2017, at 2:30 pm, Victor Kuarsingh <victor@jvknet.com> =
wrote:
>=20
> Kathleen,
>=20
> On Mon, Nov 13, 2017 at 12:40 AM, Kathleen Moriarty
> <kathleen.moriarty.ietf@gmail.com> wrote:
>=20
>> On Sun, Nov 12, 2017 at 8:02 AM, Paul Wouters <paul@nohats.ca> wrote:
>>>=20
>>>=20
>>> I concur with most of Stephane=E2=80=99s comments. And I find the =
use of the term =E2=80=9Cpervasive encryption=E2=80=9D very problematic. =
Pervasive means:
>>>=20
>>> =E2=80=9C(especially of an unwelcome influence or physical effect) =
spreading widely throughout an area or a group of people.=E2=80=9D
>>>=20
>>> More encryption is never unwelcome to the enduser.
>>=20
>> Could you propose an alternate title?  We used the term ubiquitous
>> previously, and it was changed in a prior IETF list discussion to the
>> current title.
>>=20
>=20
> The general definition when comparing various dictionaries seems to
> associate the word "pervasive" with the common meaning of "spread
> throughout".
>=20
> Based on that, the title seems appropriate.
>=20
> regards,
>=20
> Victor K
>=20
>=20
>>=20
>> Best regards,
>> Kathleen
>>=20
>=20

--
Mark Nottingham   https://www.mnot.net/



From nobody Mon Nov 13 03:11:52 2017
Return-Path: <cpignata@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 73D5C128CF0; Mon, 13 Nov 2017 03:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level: 
X-Spam-Status: No, score=-14.519 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 QrCmQdHCjsvq; Mon, 13 Nov 2017 03:11:48 -0800 (PST)
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 6879812420B; Mon, 13 Nov 2017 03:11:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26234; q=dns/txt; s=iport; t=1510571508; x=1511781108; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=c0fBbBA54O09QEU8nw1OyPIv5unWvSjX7Qnd2D2yX/4=; b=M697t+d4Ma6w8ly5zbUiJNuaWvPSV8lf0mActqKPm4VIU69DrPmtVgcf uq11LzHEIepGHnpY6xh/ws+BLwJqZL9MKZip90OoKI+NDGVyrCfoc/qKT cpUAd06CJeGfDquNyUnMVGswBa5NhqdhMi5GPiTYGZwq/jd9y3rpWMvCU g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CwAAAWfQla/4oNJK1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM1ZG4nB4N3ih+PKZMFhUiCEQojhRgCGoQ+PxgBAQEBAQEBAQF?= =?us-ascii?q?rKIUfBg4VQgkLEAIBBgI7BAMCAgIwFBECBAoEBYk+ZBCNd51ogieLBgEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBARgFgzAEgWUBIYFVgWkpgwGEdwEBAoMxMYIyBaIqAod?= =?us-ascii?q?pgx5LiTCCFYYIiyWMaIkPAhEZAYE4AR84QoEwehV2AYImAQ+DEYFOdwGGK4Ekg?= =?us-ascii?q?REBAQE?=
X-IronPort-AV: E=Sophos;i="5.44,389,1505779200";  d="scan'208,217";a="323547682"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Nov 2017 11:11:47 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id vADBBkP3011782 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 13 Nov 2017 11:11:47 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 13 Nov 2017 06:11:46 -0500
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1320.000; Mon, 13 Nov 2017 06:11:46 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
CC: "paul.hoffman@vpnc.org" <paul.hoffman@vpnc.org>, "draft-mm-wg-effect-encrypt@ietf.org" <draft-mm-wg-effect-encrypt@ietf.org>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
Thread-Topic: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
Thread-Index: AQHTVwiQvnXAEwS2N0WytnUT58xVVqMShieA
Date: Mon, 13 Nov 2017 11:11:46 +0000
Message-ID: <87E699C3-418F-4B99-AC18-05B2B50E0700@cisco.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com>
In-Reply-To: <150997721010.25597.12135786015002954174.idtracker@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.68.210.101]
Content-Type: multipart/alternative; boundary="_000_87E699C3418F4B99AC1805B2B50E0700ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1X_vY5n1cTI9n_25C4JLJwgd3jQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 11:11:51 -0000

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

SGksDQoNClRoaXMgaXMgYSB2ZXJ5IGltcG9ydGFudCBkb2N1bWVudCBhbmQgYSBjbGVhciBzdGVw
IGZvcndhcmQgdG93YXJkcyBsb25nLXRlcm0gZGVwbG95YWJsZSBzZWN1cml0eSwgYnkgZG9jdW1l
bnRpbmcgdGhlIGVmZmVjdHMgb2YgcGVydmFzaXZlIGVuY3J5cHRpb24gb24gbmV0d29yayBvcGVy
YXRpb25zIGFuZCBtYW5hZ2VtZW50Lg0KDQpBcyBSRkMgNzI1OCB3cml0ZXM6DQoNCiAgIk1ha2lu
Zw0KICAgbmV0d29ya3MgdW5tYW5hZ2VhYmxlIHRvIG1pdGlnYXRlIFBNIGlzIG5vdCBhbiBhY2Nl
cHRhYmxlIG91dGNvbWUsDQogICBidXQgaWdub3JpbmcgUE0gd291bGQgZ28gYWdhaW5zdCB0aGUg
Y29uc2Vuc3VzIGRvY3VtZW50ZWQgaGVyZS4gIEFuDQogICBhcHByb3ByaWF0ZSBiYWxhbmNlIHdp
bGwgZW1lcmdlIG92ZXIgdGltZSBhcyByZWFsIGluc3RhbmNlcyBvZiB0aGlzDQogICB0ZW5zaW9u
IGFyZSBjb25zaWRlcmVkLuKAnQ0KDQpBbmQgZG9jdW1lbnQgZWZmZWN0cywgcG9zaXRpdmUgb3Ig
bmVnYXRpdmUsIG9uIGV4aXN0aW5nIG5ldHdvcmsgb3BlcmF0aW9uYWwgYW5kIG1hbmFnZW1lbnQg
cHJhY3RpY2VzIGlzIGluZGVlZCBzdGFydGluZyB0byBjb25zaWRlciB0aG9zZSByZWFsIGluc3Rh
bmNlcy4NCg0KUkZDIDcyNTggZnVydGhlciBzYXlzOg0KDQogICJXaGlsZSBQTSBpcyBhbiBhdHRh
Y2ssIG90aGVyIGZvcm1zIG9mIG1vbml0b3JpbmcgdGhhdCBtaWdodCBmaXQgdGhlDQogICBkZWZp
bml0aW9uIG9mIFBNIGNhbiBiZSBiZW5lZmljaWFsIGFuZCBub3QgcGFydCBvZiBhbnkgYXR0YWNr
LCBlLmcuLA0KICAgbmV0d29yayBtYW5hZ2VtZW50IGZ1bmN0aW9ucyBtb25pdG9yIHBhY2tldHMg
b3IgZmxvd3MgYW5kIGFudGktc3BhbQ0KICAgbWVjaGFuaXNtcyBuZWVkIHRvIHNlZSBtYWlsIG1l
c3NhZ2UgY29udGVudC4gIFvigKZdIg0KDQpDb25zZXF1ZW50bHksIGlmIGJlbmVmaWNpYWwgbWVj
aGFuaXNtcyBhcmUgYWR2ZXJzZWx5IGFmZmVjdGVkIChkZWdyYWRlZCBvciBmbGF0LW91dCBicm9r
ZW4pIGluIHByZXNlbmNlIG9mIHBlcnZhc2l2ZSBlbmNyeXB0aW9uLCBkb2N1bWVudGluZyBpcyB0
aGUgZmlyc3Qgc3RlcC4NCg0KRm9yIGV4YW1wbGUsIGlmIGEgcHJvdmlkZXIgdXNlcyBwYXNzaXZl
IHBlcmZvcm1hbmNlIG1lYXN1cmVtZW50IG1ldHJpY3MgYW5kIG1ldGhvZHMgdGVjaG5pcXVlcywg
ZGV2ZWxvcGVkIGJ5IHRoZSBJRVRGIChlLmcuLCBJUFBNKSwgaW4gb3JkZXIgdG8gcGVyZm9ybSBT
TEEgbWFuYWdlbWVudCBhbmQgdmVyaWZpY2F0aW9uLCBhbmQgdGhhdCBpcyBuZWdhdGl2ZWx5IGFm
ZmVjdGVkLCB0aGUgZmlyc3Qgc3RlcCBpcyB0byBkb2N1bWVudCB0aG9zZSBlZmZlY3RzLg0KDQoN
CkludGVyZXN0aW5nbHksIGFub3RoZXIgZHJhZnQgZXhwbG9yZXMgYSBzdWJzZXQgb2YgdGhpcyB0
b3BpYzogaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWZhaXJodXJzdC10c3Z3Zy10
cmFuc3BvcnQtZW5jcnlwdC0wMw0KDQpGb3IgZXhhbXBsZSwgU2VjdGlvbiAzIHNheXM6DQoNCiAg
IlRoaXMgc2VjdGlvbiBpZGVudGlmaWVzIHdheXMgdGhhdCBhY3RvcnMgY2FuIGJlbmVmaXQgYnkg
b2JzZXJ2aW5nDQogICAobm9uLWVuY3J5cHRlZCkgdHJhbnNwb3J0IGhlYWRlciBmaWVsZHMgYXQg
ZGV2aWNlcyBpbiB0aGUgbmV0d29yay7igJ0NCg0KQW5kIGFuYWx5c2lzIHdoYXQgd291bGQgaGFw
cGVuIGlmIGFjY2VzcyB0byBncmFudWxhciB0cmFuc3BvcnQgaGVhZGVyIGluZm9ybWF0aW9uIGlz
IG5vdCBhdmFpbGFibGUuIFRoZSBpbXBsaWNhdGlvbnMgYXJlIHRoZSBuZWVkIHRvIGJ1aWxkIG5l
dyB0b29scywgbmV3IG1ldGhvZHMsIHVzZSBhY3RpdmUgdnMuIHBhc3NpdmUgYXBwcm9hY2hlcywg
YWxsIG9mIHdoaWNoIHJlcXVpcmUgdGltZSBhbmQgbW9uZXkgKGFuZCBwb3RlbnRpYWxseSBuZXcg
cHJvdG9jb2wpLg0KDQpUaGlzIGRyYWZ0IGFsc28gaW5jbHVkZXMgdGhlIGZvbGxvd2luZyB0ZXh0
LCB3aGljaCBkZXNjcmliZXMgdGhlc2UgZWZmZWN0czoNCg0KICAiVGhlIGNvbW1vbiBsYW5ndWFn
ZSBiZXR3ZWVuIG5ldHdvcmsgb3BlcmF0b3JzIGFuZCBhcHBsaWNhdGlvbi9jb250ZW50DQogICBw
cm92aWRlcnMvdXNlcnMgaXMgcGFja2V0IHRyYW5zZmVyIHBlcmZvcm1hbmNlIGF0IGEgbGF5ZXIg
dGhhdCBhbGwNCiAgIGNhbiB2aWV3IGFuZCBhbmFseXplLiAgRm9yIG1vc3QgcGFja2V0cywgdGhp
cyBoYXMgYmVlbiB0cmFuc3BvcnQNCiAgIGxheWVyLCB1bnRpbCB0aGUgZW1lcmdlbmNlIG9mIFFV
SUMsIHdpdGggdGhlIG9idmlvdXMgZXhjZXB0aW9uIG9mDQogICBWUE5zIGFuZCBJUHNlYy4gIFdo
ZW4gZW5jcnlwdGlvbiBjb25jZWFscyBtb3JlIGxheWVycyBpbiBhIHBhY2tldCwNCiAgIHBlb3Bs
ZSBzZWVraW5nIHVuZGVyc3RhbmRpbmcgb2YgdGhlIG5ldHdvcmsgb3BlcmF0aW9uIG5lZWQgdG8g
cmVseQ0KICAgbW9yZSBvbiBwYXR0ZXJuIGluZmVyZW5jZXMgYW5kIG90aGVyIGhldXJpc3RpY3Mu
4oCdDQoNCkNvbnNlcXVlbnRseSwgdGhlIHJlYWwgKHNlY29uZCBvcmRlcikgZWZmZWN0IGlzIGxh
Y2sgb2YgY29tbW9uIHZvY2FidWxhcnkgYW5kIGxhbmd1YWdlIGJldHdlZW4gYXBwIHByb3ZpZGVy
cyBhbmQgbmV0d29yayBvcGVyYXRvcnMuDQoNCkl0IHNlZW1zIHNvbWUgdXNlLWNhc2VzIGxpc3Rl
ZCBpbiB0aGlzIGRyYWZ0IGNhbiBiZSBhZGRlZCB0byBkcmFmdC1tbS13Zy1lZmZlY3QtZW5jcnlw
dCBhcyB3ZWxsIChhbHRob3VnaCBJIGJlbGlldmUgYWxsIGJyb2FkIGNhdGVnb3JpZXMgYXJlIGNv
dmVyZWQpLg0KDQoNClRoZXJlIGlzIG9uZSBhZGRpdGlvbmFsIGFwcHJvYWNoIG5vdCBjb25zaWRl
cmVkIGluIGRyYWZ0LW1tLXdnLWVmZmVjdC1lbmNyeXB0OiBsZXZlcmFnZSBSRkMgNTcwNiBtb3Jl
LiBGb3IgZXhhbXBsZSwgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzU3MDYjc2VjdGlv
bi0yLjUNCg0KICAiVGhlIGludHJvZHVjdGlvbiBvZiBhIG5ldyBwcm90b2NvbCBvciBleHRlbnNp
b25zIHRvIGFuIGV4aXN0aW5nDQogICBwcm90b2NvbCBtYXkgaGF2ZSBhbiBpbXBhY3Qgb24gdGhl
IG9wZXJhdGlvbiBvZiBleGlzdGluZyBuZXR3b3Jrcy4NCiAgIFByb3RvY29sIGRlc2lnbmVycyBz
aG91bGQgb3V0bGluZSBzdWNoIGltcGFjdHMgKHdoaWNoIG1heSBiZQ0KICAgcG9zaXRpdmUpLCBp
bmNsdWRpbmcgc2NhbGluZyBjb25jZXJucyBhbmQgaW50ZXJhY3Rpb25zIHdpdGggb3RoZXINCiAg
IHByb3RvY29scy4iDQoNClBlcmhhcHMgb25lIHN0YXJ0IGlzIGEgdGlnaHRlciBsb29rIGF0IE1h
bmFnZWFiaWxpdHkgQ29uc2lkZXJhdGlvbnMuDQoNCkEgZmV3IGFkZGl0aW9uYWwgY29tbWVudHMg
b24gdGhlIGRyYWZ0IGl0c2VsZi4NCg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LW1tLXdnLWVmZmVjdC1lbmNyeXB0LTEzDQoNCkFic3RyYWN0Og0KDQogICJUaGlzIGRvY3VtZW50
IGRpc2N1c3NlcyBjdXJyZW50DQogICBzZWN1cml0eSBhbmQgbmV0d29yayBtYW5hZ2VtZW50IHBy
YWN0aWNlcyB0aGF0IG1heSBiZSBpbXBhY3RlZCBieSB0aGUNCiAgIHNoaWZ0IHRvIGluY3JlYXNl
ZCB1c2Ugb2YgZW5jcnlwdGlvbiB0byBoZWxwIGd1aWRlIHByb3RvY29sDQogICBkZXZlbG9wbWVu
dCBpbiBzdXBwb3J0IG9mIG1hbmFnZWFibGUsIHNlY3VyZSBuZXR3b3Jrcy4iDQoNCg0KVGhlIEFi
c3RyYWN0IGFuZCB2YXJpb3VzIG90aGVyIHBhcmFncmFwaHMgdGFsayBhYm91dCDigJxtYW5hZ2Vt
ZW50IHByYWN0aWNlc+KAnS4gSG93ZXZlciwgdGhhdCBvdWdodCB0byBiZSBicm9hZGVuZWQgdG8g
4oCcb3BlcmF0aW9ucyBhbmQgbWFuYWdlbWVudCBwcmFjdGljZXPigJ0gdGhyb3VnaG91dCwgYm90
aCBvZiB3aGljaCBtYWtlIHVwIG1hbmFnZWFiaWxpdHkuDQoNCkkgYmVsaWV2ZSB0aGlzIGlzIHRo
ZSByaWdodCB0ZXh0IChmcm9tIHRoZSBJbnRyb2R1Y3Rpb24pLCB3aGljaCBzaG91bGQgYmUgbWly
cm9yZWQgaW4gdGhlIEFic3RyYWN0IGFuZCBlbHNld2hlcmUg4oCUIOKAnG1hbmFnZSwgb3BlcmF0
ZSwgYW5kIHNlY3VyZSI6DQoNCiAgIlRoaXMgZG9jdW1lbnQgZGlzY3Vzc2VzIHByYWN0aWNlcyBj
dXJyZW50bHkgdXNlZCBieSBuZXR3b3JrIG9wZXJhdG9ycw0KICAgdG8gbWFuYWdlLCBvcGVyYXRl
LCBhbmQgc2VjdXJlIHRoZWlyIG5ldHdvcmtzIGFuZCBob3cgdGhvc2UgcHJhY3RpY2VzDQogICBt
YXkgYmUgaW1wYWN0ZWQgYnkgYSBzaGlmdCB0byBpbmNyZWFzZWQgdXNlIG9mIGVuY3J5cHRpb24u
Ig0KDQpTZWN0aW9uIDIuMi4gZGVzY3JpYmVzIGVmZmVjdHMgb24gdHJhZmZpYyBvcHRpbWl6YXRp
b24gYW5kIG1hbmFnZW1lbnQsIGluY2x1ZGluZyBzb21lIOKAnHNlcnZpY2UgZnVuY3Rpb25z4oCd
Lg0KDQpXaGF0IGl0IGRvZXNu4oCZdCBkZXNjcmliZSBpcyDigJxzZXJ2aWNlIGZ1bmN0aW9uIGNo
YWluaW5n4oCdIChpLmUuLCB0aGUgb3JkZXJlZCBzdGVlcmluZyBhbmQgYXBwbGljYXRpb24gb2Yg
dGhvc2Ugb3B0aW1pemF0aW9ucykuIElmIHRoZSBuZXR3b3JrIHZpc2liaWxpdHkgZ29lcyBmcm9t
IGEgNS10dXBsZSB0byBhIDItdHVwbGUsIG9yIGlmIGV2ZXJ5dGhpbmcgYWJvdmUgdGhlIHRyYW5z
cG9ydCBiZWNvbWVzIHVuYWNjZXNzaWJsZSwgdGhlbiBhIENsYXNzaWZpZXIgKFJGQyA3NjY1KSBp
biBhIHNlcnZpY2UgZnVuY3Rpb24gY2hhaW4gd2lsbCBub3QgYmUgYWJsZSB0byBwZXJmb3JtIGl0
cyBqb2IsIGFuZCB0aGUgc2VydmljZSBmdW5jdGlvbiBwYXRoIHdpbGwgYmUgYWR2ZXJzZWx5IGFm
ZmVjdGVkLg0KDQpBdCB0aGUgc2FtZSB0aW1lIGl0IGlzIGltcG9ydGFudCB0aGF0IHRoZXJlIGFy
ZSBtZWNoYW5pc21zIHByb3ZpZGVkIHRvIHByb3RlY3Qgc2VjdXJpdHkgYW5kIHByaXZhY3kg4oCU
IGluIHRoaXMgZXhhbXBsZSwgdGhlIGxheWVyIHVuZGVybmVhdGggYSBuZXR3b3JrIHNlcnZpY2Ug
aGVhZGVyIGNhbiBiZSBwcm90ZWN0ZWQgd2l0aCBzZXNzaW9uIGVuY3J5cHRpb24uIEEgZ29hbCBp
cyBwcm90ZWN0aW5nIGVuZC11c2VyIGRhdGEg4oCUIGJ1dCBhdCB0aGUgc2FtZSB0aW1lIG5vdCBt
YWtpbmcgdGhlIG5ldHdvcmsgaW5vcGVyYWJsZSBvciB1bm1hbmFnZWFibGUuDQoNCkFzIGEgY2xv
c2luZyBub3RlLCBhIHJlYWwgcG93ZXIgYW5kIGRpZmZlcmVudGlhdGlvbiBvZiB0aGUgSUVURiBp
cyBjcm9zcy1hcmVhIHN5bmVyZ2llcy4gVGhpcyB0b3BpYyBzaG91bGQgYmVjb21lIGEgYnJpZGdl
IGFuZCBub3QgYSBkaXZpc2lvbi4NCg0KVGhhbmtzLA0KDQrigJQNCkNhcmxvcyBQaWduYXRhcm8s
IGNhcmxvc0BjaXNjby5jb208bWFpbHRvOmNhcmxvc0BjaXNjby5jb20+DQoNCuKAnFNvbWV0aW1l
cyBJIHVzZSBiaWcgd29yZHMgdGhhdCBJIGRvIG5vdCBmdWxseSB1bmRlcnN0YW5kLCB0byBtYWtl
IG15c2VsZiBzb3VuZCBtb3JlIHBob3Rvc3ludGhlc2lzLiINCg0KT24gTm92IDYsIDIwMTcsIGF0
IDEwOjA2IFBNLCBUaGUgSUVTRyA8aWVzZy1zZWNyZXRhcnlAaWV0Zi5vcmc8bWFpbHRvOmllc2ct
c2VjcmV0YXJ5QGlldGYub3JnPj4gd3JvdGU6DQoNCg0KVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEg
cmVxdWVzdCBmcm9tIGFuIGluZGl2aWR1YWwgc3VibWl0dGVyIHRvIGNvbnNpZGVyIHRoZQ0KZm9s
bG93aW5nIGRvY3VtZW50OiAtICdFZmZlY3Qgb2YgUGVydmFzaXZlIEVuY3J5cHRpb24gb24gT3Bl
cmF0b3JzJw0KIDxkcmFmdC1tbS13Zy1lZmZlY3QtZW5jcnlwdC0xMy50eHQ+IGFzIEluZm9ybWF0
aW9uYWwgUkZDDQoNClRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4
dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0cyBmaW5hbA0KY29tbWVudHMgb24gdGhpcyBhY3Rpb24u
IFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRoZQ0KaWV0ZkBpZXRmLm9yZzxt
YWlsdG86aWV0ZkBpZXRmLm9yZz4gbWFpbGluZyBsaXN0cyBieSAyMDE3LTEyLTA0LiBFeGNlcHRp
b25hbGx5LCBjb21tZW50cyBtYXkgYmUNCnNlbnQgdG8gaWVzZ0BpZXRmLm9yZzxtYWlsdG86aWVz
Z0BpZXRmLm9yZz4gaW5zdGVhZC4gSW4gZWl0aGVyIGNhc2UsIHBsZWFzZSByZXRhaW4gdGhlIGJl
Z2lubmluZyBvZg0KdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4N
Cg0KQWJzdHJhY3QNCg0KDQogIFBlcnZhc2l2ZSBNb25pdG9yaW5nIChQTSkgYXR0YWNrcyBvbiB0
aGUgcHJpdmFjeSBvZiBJbnRlcm5ldCB1c2VycyBpcw0KICBvZiBzZXJpb3VzIGNvbmNlcm4gdG8g
Ym90aCB0aGUgdXNlciBhbmQgdGhlIG9wZXJhdG9yIGNvbW11bml0aWVzLg0KICBSRkM3MjU4IGRp
c2N1c3NlZCB0aGUgY3JpdGljYWwgbmVlZCB0byBwcm90ZWN0IHVzZXJzJyBwcml2YWN5IHdoZW4N
CiAgZGV2ZWxvcGluZyBJRVRGIHNwZWNpZmljYXRpb25zIGFuZCBhbHNvIHJlY29nbml6ZWQgbWFr
aW5nIG5ldHdvcmtzDQogIHVubWFuYWdlYWJsZSB0byBtaXRpZ2F0ZSBQTSBpcyBub3QgYW4gYWNj
ZXB0YWJsZSBvdXRjb21lLCBhbg0KICBhcHByb3ByaWF0ZSBiYWxhbmNlIGlzIG5lZWRlZC4gIFRo
aXMgZG9jdW1lbnQgZGlzY3Vzc2VzIGN1cnJlbnQNCiAgc2VjdXJpdHkgYW5kIG5ldHdvcmsgbWFu
YWdlbWVudCBwcmFjdGljZXMgdGhhdCBtYXkgYmUgaW1wYWN0ZWQgYnkgdGhlDQogIHNoaWZ0IHRv
IGluY3JlYXNlZCB1c2Ugb2YgZW5jcnlwdGlvbiB0byBoZWxwIGd1aWRlIHByb3RvY29sDQogIGRl
dmVsb3BtZW50IGluIHN1cHBvcnQgb2YgbWFuYWdlYWJsZSwgc2VjdXJlIG5ldHdvcmtzLg0KDQoN
Cg0KDQpUaGUgZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlhDQpodHRwczovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1tbS13Zy1lZmZlY3QtZW5jcnlwdC8NCg0KSUVTRyBkaXNjdXNzaW9u
IGNhbiBiZSB0cmFja2VkIHZpYQ0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQtbW0td2ctZWZmZWN0LWVuY3J5cHQvYmFsbG90Lw0KDQoNCk5vIElQUiBkZWNsYXJhdGlvbnMg
aGF2ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC4NCg0KDQoNCg0KDQo=

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+SGksPC9kaXY+DQo8ZGl2
IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5UaGlzIGlzIGEg
dmVyeSBpbXBvcnRhbnQgZG9jdW1lbnQgYW5kIGEgY2xlYXIgc3RlcCBmb3J3YXJkIHRvd2FyZHMg
bG9uZy10ZXJtIGRlcGxveWFibGUgc2VjdXJpdHksIGJ5IGRvY3VtZW50aW5nIHRoZSBlZmZlY3Rz
IG9mIHBlcnZhc2l2ZSBlbmNyeXB0aW9uIG9uIG5ldHdvcmsgb3BlcmF0aW9ucyBhbmQgbWFuYWdl
bWVudC48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNs
YXNzPSIiPkFzIFJGQyA3MjU4IHdyaXRlczo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNz
PSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4mbmJzcDsgJnF1b3Q7
TWFraW5nPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDtuZXR3b3JrcyB1bm1hbmFn
ZWFibGUgdG8gbWl0aWdhdGUgUE0gaXMgbm90IGFuIGFjY2VwdGFibGUgb3V0Y29tZSw8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwO2J1dCBpZ25vcmluZyBQTSB3b3VsZCBnbyBhZ2Fp
bnN0IHRoZSBjb25zZW5zdXMgZG9jdW1lbnRlZCBoZXJlLiAmbmJzcDtBbjwvZGl2Pg0KPGRpdiBj
bGFzcz0iIj4mbmJzcDsgJm5ic3A7YXBwcm9wcmlhdGUgYmFsYW5jZSB3aWxsIGVtZXJnZSBvdmVy
IHRpbWUgYXMgcmVhbCBpbnN0YW5jZXMgb2YgdGhpczwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4mbmJz
cDsgJm5ic3A7dGVuc2lvbiBhcmUgY29uc2lkZXJlZC7igJ08L2Rpdj4NCjwvZGl2Pg0KPGRpdiBj
bGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+QW5kIGRvY3VtZW50
IGVmZmVjdHMsIHBvc2l0aXZlIG9yIG5lZ2F0aXZlLCBvbiBleGlzdGluZyBuZXR3b3JrIG9wZXJh
dGlvbmFsIGFuZCBtYW5hZ2VtZW50IHByYWN0aWNlcyBpcyBpbmRlZWQgc3RhcnRpbmcgdG8gY29u
c2lkZXIgdGhvc2UgcmVhbCBpbnN0YW5jZXMuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFz
cz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5SRkMgNzI1OCBmdXJ0aGVyIHNheXM6PC9kaXY+
DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4NCjxk
aXYgY2xhc3M9IiI+Jm5ic3A7ICZxdW90O1doaWxlIFBNIGlzIGFuIGF0dGFjaywgb3RoZXIgZm9y
bXMgb2YgbW9uaXRvcmluZyB0aGF0IG1pZ2h0IGZpdCB0aGU8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+
Jm5ic3A7ICZuYnNwO2RlZmluaXRpb24gb2YgUE0gY2FuIGJlIGJlbmVmaWNpYWwgYW5kIG5vdCBw
YXJ0IG9mIGFueSBhdHRhY2ssIGUuZy4sPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJz
cDtuZXR3b3JrIG1hbmFnZW1lbnQgZnVuY3Rpb25zIG1vbml0b3IgcGFja2V0cyBvciBmbG93cyBh
bmQgYW50aS1zcGFtPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDttZWNoYW5pc21z
IG5lZWQgdG8gc2VlIG1haWwgbWVzc2FnZSBjb250ZW50LiAmbmJzcDtb4oCmXSZxdW90OzwvZGl2
Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFz
cz0iIj5Db25zZXF1ZW50bHksIGlmIGJlbmVmaWNpYWwgbWVjaGFuaXNtcyBhcmUgYWR2ZXJzZWx5
IGFmZmVjdGVkIChkZWdyYWRlZCBvciBmbGF0LW91dCBicm9rZW4pIGluIHByZXNlbmNlIG9mIHBl
cnZhc2l2ZSBlbmNyeXB0aW9uLCBkb2N1bWVudGluZyBpcyB0aGUgZmlyc3Qgc3RlcC48L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPkZvciBl
eGFtcGxlLCBpZiBhIHByb3ZpZGVyIHVzZXMgcGFzc2l2ZSBwZXJmb3JtYW5jZSBtZWFzdXJlbWVu
dCBtZXRyaWNzIGFuZCBtZXRob2RzIHRlY2huaXF1ZXMsIGRldmVsb3BlZCBieSB0aGUgSUVURiAo
ZS5nLiwgSVBQTSksIGluIG9yZGVyIHRvIHBlcmZvcm0gU0xBIG1hbmFnZW1lbnQgYW5kIHZlcmlm
aWNhdGlvbiwgYW5kIHRoYXQgaXMgbmVnYXRpdmVseSBhZmZlY3RlZCwgdGhlIGZpcnN0IHN0ZXAg
aXMgdG8gZG9jdW1lbnQNCiB0aG9zZSBlZmZlY3RzLjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIg
Y2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8
ZGl2IGNsYXNzPSIiPkludGVyZXN0aW5nbHksIGFub3RoZXIgZHJhZnQgZXhwbG9yZXMgYSBzdWJz
ZXQgb2YgdGhpcyB0b3BpYzombmJzcDs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtZmFpcmh1cnN0LXRzdndnLXRyYW5zcG9ydC1lbmNyeXB0LTAzIiBjbGFzcz0iIj5o
dHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtZmFpcmh1cnN0LXRzdndnLXRyYW5zcG9y
dC1lbmNyeXB0LTAzPC9hPjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rp
dj4NCjxkaXYgY2xhc3M9IiI+Rm9yIGV4YW1wbGUsIFNlY3Rpb24gMyBzYXlzOjwvZGl2Pg0KPGRp
diBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZx
dW90O1RoaXMgc2VjdGlvbiBpZGVudGlmaWVzIHdheXMgdGhhdCBhY3RvcnMgY2FuIGJlbmVmaXQg
Ynkgb2JzZXJ2aW5nPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDsobm9uLWVuY3J5
cHRlZCkgdHJhbnNwb3J0IGhlYWRlciBmaWVsZHMgYXQgZGV2aWNlcyBpbiB0aGUgbmV0d29yay7i
gJ08L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNz
PSIiPkFuZCBhbmFseXNpcyB3aGF0IHdvdWxkIGhhcHBlbiBpZiBhY2Nlc3MgdG8gZ3JhbnVsYXIg
dHJhbnNwb3J0IGhlYWRlciBpbmZvcm1hdGlvbiBpcyBub3QgYXZhaWxhYmxlLiBUaGUgaW1wbGlj
YXRpb25zIGFyZSB0aGUgbmVlZCB0byBidWlsZCBuZXcgdG9vbHMsIG5ldyBtZXRob2RzLCB1c2Ug
YWN0aXZlIHZzLiBwYXNzaXZlIGFwcHJvYWNoZXMsIGFsbCBvZiB3aGljaCByZXF1aXJlIHRpbWUg
YW5kIG1vbmV5IChhbmQgcG90ZW50aWFsbHkNCiBuZXcgcHJvdG9jb2wpLjwvZGl2Pg0KPGRpdiBj
bGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+VGhpcyBkcmFmdCBh
bHNvIGluY2x1ZGVzIHRoZSBmb2xsb3dpbmcgdGV4dCwgd2hpY2ggZGVzY3JpYmVzIHRoZXNlIGVm
ZmVjdHM6PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBj
bGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZxdW90O1RoZSBjb21tb24gbGFuZ3VhZ2Ug
YmV0d2VlbiBuZXR3b3JrIG9wZXJhdG9ycyBhbmQgYXBwbGljYXRpb24vY29udGVudDwvZGl2Pg0K
PGRpdiBjbGFzcz0iIj4mbmJzcDsgJm5ic3A7cHJvdmlkZXJzL3VzZXJzIGlzIHBhY2tldCB0cmFu
c2ZlciBwZXJmb3JtYW5jZSBhdCBhIGxheWVyIHRoYXQgYWxsPC9kaXY+DQo8ZGl2IGNsYXNzPSIi
PiZuYnNwOyAmbmJzcDtjYW4gdmlldyBhbmQgYW5hbHl6ZS4gJm5ic3A7Rm9yIG1vc3QgcGFja2V0
cywgdGhpcyBoYXMgYmVlbiB0cmFuc3BvcnQ8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZu
YnNwO2xheWVyLCB1bnRpbCB0aGUgZW1lcmdlbmNlIG9mIFFVSUMsIHdpdGggdGhlIG9idmlvdXMg
ZXhjZXB0aW9uIG9mPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDtWUE5zIGFuZCBJ
UHNlYy4gJm5ic3A7V2hlbiBlbmNyeXB0aW9uIGNvbmNlYWxzIG1vcmUgbGF5ZXJzIGluIGEgcGFj
a2V0LDwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4mbmJzcDsgJm5ic3A7cGVvcGxlIHNlZWtpbmcgdW5k
ZXJzdGFuZGluZyBvZiB0aGUgbmV0d29yayBvcGVyYXRpb24gbmVlZCB0byByZWx5PC9kaXY+DQo8
ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDttb3JlIG9uIHBhdHRlcm4gaW5mZXJlbmNlcyBhbmQg
b3RoZXIgaGV1cmlzdGljcy7igJ08L2Rpdj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xh
c3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Q29uc2VxdWVudGx5LCB0aGUgcmVhbCAoc2Vj
b25kIG9yZGVyKSBlZmZlY3QgaXMgbGFjayBvZiBjb21tb24gdm9jYWJ1bGFyeSBhbmQgbGFuZ3Vh
Z2UgYmV0d2VlbiBhcHAgcHJvdmlkZXJzIGFuZCBuZXR3b3JrIG9wZXJhdG9ycy48L2Rpdj4NCjxk
aXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPkl0IHNlZW1z
IHNvbWUgdXNlLWNhc2VzIGxpc3RlZCBpbiB0aGlzIGRyYWZ0IGNhbiBiZSBhZGRlZCB0byZuYnNw
O2RyYWZ0LW1tLXdnLWVmZmVjdC1lbmNyeXB0IGFzIHdlbGwgKGFsdGhvdWdoIEkgYmVsaWV2ZSBh
bGwgYnJvYWQgY2F0ZWdvcmllcyBhcmUgY292ZXJlZCkuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxi
ciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+VGhlcmUgaXMgb25lIGFkZGl0aW9uYWwgYXBwcm9hY2ggbm90IGNvbnNp
ZGVyZWQgaW4mbmJzcDtkcmFmdC1tbS13Zy1lZmZlY3QtZW5jcnlwdDogbGV2ZXJhZ2UgUkZDIDU3
MDYgbW9yZS4gRm9yIGV4YW1wbGUsJm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9odG1sL3JmYzU3MDYjc2VjdGlvbi0yLjUiIGNsYXNzPSIiPmh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9yZmM1NzA2I3NlY3Rpb24tMi41PC9hPjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIg
Y2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAm
cXVvdDtUaGUgaW50cm9kdWN0aW9uIG9mIGEgbmV3IHByb3RvY29sIG9yIGV4dGVuc2lvbnMgdG8g
YW4gZXhpc3Rpbmc8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwO3Byb3RvY29sIG1h
eSBoYXZlIGFuIGltcGFjdCBvbiB0aGUgb3BlcmF0aW9uIG9mIGV4aXN0aW5nIG5ldHdvcmtzLjwv
ZGl2Pg0KPGRpdiBjbGFzcz0iIj4mbmJzcDsgJm5ic3A7UHJvdG9jb2wgZGVzaWduZXJzIHNob3Vs
ZCBvdXRsaW5lIHN1Y2ggaW1wYWN0cyAod2hpY2ggbWF5IGJlPC9kaXY+DQo8ZGl2IGNsYXNzPSIi
PiZuYnNwOyAmbmJzcDtwb3NpdGl2ZSksIGluY2x1ZGluZyBzY2FsaW5nIGNvbmNlcm5zIGFuZCBp
bnRlcmFjdGlvbnMgd2l0aCBvdGhlcjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4mbmJzcDsgJm5ic3A7
cHJvdG9jb2xzLiZxdW90OzwvZGl2Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0i
Ij4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5QZXJoYXBzIG9uZSBzdGFydCBpcyBhIHRpZ2h0ZXIg
bG9vayBhdCZuYnNwO01hbmFnZWFiaWxpdHkgQ29uc2lkZXJhdGlvbnMuPC9kaXY+DQo8ZGl2IGNs
YXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5BIGZldyBhZGRpdGlv
bmFsIGNvbW1lbnRzIG9uIHRoZSBkcmFmdCBpdHNlbGYuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxi
ciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YSBocmVmPSJodHRwczovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtbW0td2ctZWZmZWN0LWVuY3J5cHQtMTMiIGNsYXNzPSIiPmh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1tbS13Zy1lZmZlY3QtZW5jcnlwdC0xMzwv
YT48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNz
PSIiPkFic3RyYWN0OjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmcXVvdDtUaGlzIGRvY3VtZW50
IGRpc2N1c3NlcyBjdXJyZW50PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDtzZWN1
cml0eSBhbmQgbmV0d29yayBtYW5hZ2VtZW50IHByYWN0aWNlcyB0aGF0IG1heSBiZSBpbXBhY3Rl
ZCBieSB0aGU8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZuYnNwO3NoaWZ0IHRvIGluY3Jl
YXNlZCB1c2Ugb2YgZW5jcnlwdGlvbiB0byBoZWxwIGd1aWRlIHByb3RvY29sPC9kaXY+DQo8ZGl2
IGNsYXNzPSIiPiZuYnNwOyAmbmJzcDtkZXZlbG9wbWVudCBpbiBzdXBwb3J0IG9mIG1hbmFnZWFi
bGUsIHNlY3VyZSBuZXR3b3Jrcy4mcXVvdDs8L2Rpdj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48
YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+
DQo8ZGl2IGNsYXNzPSIiPlRoZSBBYnN0cmFjdCBhbmQgdmFyaW91cyBvdGhlciBwYXJhZ3JhcGhz
IHRhbGsgYWJvdXQg4oCcbWFuYWdlbWVudCBwcmFjdGljZXPigJ0uIEhvd2V2ZXIsIHRoYXQgb3Vn
aHQgdG8gYmUgYnJvYWRlbmVkIHRvIOKAnG9wZXJhdGlvbnMgYW5kIG1hbmFnZW1lbnQgcHJhY3Rp
Y2Vz4oCdIHRocm91Z2hvdXQsIGJvdGggb2Ygd2hpY2ggbWFrZSB1cCBtYW5hZ2VhYmlsaXR5Ljwv
ZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+
SSBiZWxpZXZlIHRoaXMgaXMgdGhlIHJpZ2h0IHRleHQgKGZyb20gdGhlIEludHJvZHVjdGlvbiks
IHdoaWNoIHNob3VsZCBiZSBtaXJyb3JlZCBpbiB0aGUgQWJzdHJhY3QgYW5kIGVsc2V3aGVyZSDi
gJQg4oCcbWFuYWdlLCBvcGVyYXRlLCBhbmQgc2VjdXJlJnF1b3Q7OjwvZGl2Pg0KPGRpdiBjbGFz
cz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIi
PiZuYnNwOyAmcXVvdDtUaGlzIGRvY3VtZW50IGRpc2N1c3NlcyBwcmFjdGljZXMgY3VycmVudGx5
IHVzZWQgYnkgbmV0d29yayBvcGVyYXRvcnM8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+Jm5ic3A7ICZu
YnNwO3RvIG1hbmFnZSwgb3BlcmF0ZSwgYW5kIHNlY3VyZSB0aGVpciBuZXR3b3JrcyBhbmQgaG93
IHRob3NlIHByYWN0aWNlczwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4mbmJzcDsgJm5ic3A7bWF5IGJl
IGltcGFjdGVkIGJ5IGEgc2hpZnQgdG8gaW5jcmVhc2VkIHVzZSBvZiBlbmNyeXB0aW9uLiZxdW90
OzwvZGl2Pg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KU2Vj
dGlvbiAyLjIuIGRlc2NyaWJlcyBlZmZlY3RzIG9uIHRyYWZmaWMgb3B0aW1pemF0aW9uIGFuZCBt
YW5hZ2VtZW50LCBpbmNsdWRpbmcgc29tZSDigJxzZXJ2aWNlIGZ1bmN0aW9uc+KAnS4NCjxkaXYg
Y2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPldoYXQgaXQgZG9l
c27igJl0IGRlc2NyaWJlIGlzIOKAnHNlcnZpY2UgZnVuY3Rpb24gY2hhaW5pbmfigJ0gKGkuZS4s
IHRoZSBvcmRlcmVkIHN0ZWVyaW5nIGFuZCBhcHBsaWNhdGlvbiBvZiB0aG9zZSBvcHRpbWl6YXRp
b25zKS4gSWYgdGhlIG5ldHdvcmsgdmlzaWJpbGl0eSBnb2VzIGZyb20gYSA1LXR1cGxlIHRvIGEg
Mi10dXBsZSwgb3IgaWYgZXZlcnl0aGluZyBhYm92ZSB0aGUgdHJhbnNwb3J0IGJlY29tZXMgdW5h
Y2Nlc3NpYmxlLA0KIHRoZW4gYSBDbGFzc2lmaWVyIChSRkMgNzY2NSkgaW4gYSBzZXJ2aWNlIGZ1
bmN0aW9uIGNoYWluIHdpbGwgbm90IGJlIGFibGUgdG8gcGVyZm9ybSBpdHMgam9iLCBhbmQgdGhl
IHNlcnZpY2UgZnVuY3Rpb24gcGF0aCB3aWxsIGJlIGFkdmVyc2VseSBhZmZlY3RlZC48L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPkF0IHRo
ZSBzYW1lIHRpbWUgaXQgaXMgaW1wb3J0YW50IHRoYXQgdGhlcmUgYXJlIG1lY2hhbmlzbXMgcHJv
dmlkZWQgdG8gcHJvdGVjdCBzZWN1cml0eSBhbmQgcHJpdmFjeSDigJQgaW4gdGhpcyBleGFtcGxl
LCB0aGUgbGF5ZXIgdW5kZXJuZWF0aCBhIG5ldHdvcmsgc2VydmljZSBoZWFkZXIgY2FuIGJlIHBy
b3RlY3RlZCB3aXRoIHNlc3Npb24gZW5jcnlwdGlvbi4gQSBnb2FsIGlzIHByb3RlY3RpbmcgZW5k
LXVzZXIgZGF0YSDigJQNCiBidXQgYXQgdGhlIHNhbWUgdGltZSBub3QgbWFraW5nIHRoZSBuZXR3
b3JrIGlub3BlcmFibGUgb3IgdW5tYW5hZ2VhYmxlLjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIg
Y2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+QXMgYSBjbG9zaW5nIG5vdGUsIGEgcmVh
bCBwb3dlciBhbmQgZGlmZmVyZW50aWF0aW9uIG9mIHRoZSBJRVRGIGlzIGNyb3NzLWFyZWEgc3lu
ZXJnaWVzLiBUaGlzIHRvcGljIHNob3VsZCBiZWNvbWUgYSBicmlkZ2UgYW5kIG5vdCBhIGRpdmlz
aW9uLjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xh
c3M9IiI+VGhhbmtzLDxiciBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0K
PGRpdiBjbGFzcz0iIj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGxldHRlci1z
cGFjaW5nOiBub3JtYWw7IHRleHQtYWxpZ246IHN0YXJ0OyB0ZXh0LWluZGVudDogMHB4OyB0ZXh0
LXRyYW5zZm9ybTogbm9uZTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgd29yZC1zcGFjaW5nOiAwcHg7
IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDsgd29yZC13cmFwOiBicmVhay13b3JkOyAt
d2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUt
c3BhY2U7IiBjbGFzcz0iIj4NCuKAlDxiciBjbGFzcz0iIj4NCkNhcmxvcyBQaWduYXRhcm8sJm5i
c3A7PGEgaHJlZj0ibWFpbHRvOmNhcmxvc0BjaXNjby5jb20iIGNsYXNzPSIiPmNhcmxvc0BjaXNj
by5jb208L2E+PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGkgY2xhc3M9IiI+4oCcU29t
ZXRpbWVzIEkgdXNlIGJpZyB3b3JkcyB0aGF0IEkgZG8gbm90IGZ1bGx5IHVuZGVyc3RhbmQsIHRv
IG1ha2UgbXlzZWxmIHNvdW5kIG1vcmUgcGhvdG9zeW50aGVzaXMuJnF1b3Q7PC9pPjwvZGl2Pg0K
PC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNz
PSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBOb3YgNiwgMjAxNywgYXQgMTA6MDYgUE0sIFRoZSBJRVNH
ICZsdDs8YSBocmVmPSJtYWlsdG86aWVzZy1zZWNyZXRhcnlAaWV0Zi5vcmciIGNsYXNzPSIiPmll
c2ctc2VjcmV0YXJ5QGlldGYub3JnPC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIgY2xhc3M9IkFw
cGxlLWludGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+
PGJyIGNsYXNzPSIiPg0KVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIGFuIGlu
ZGl2aWR1YWwgc3VibWl0dGVyIHRvIGNvbnNpZGVyIHRoZTxiciBjbGFzcz0iIj4NCmZvbGxvd2lu
ZyBkb2N1bWVudDogLSAnRWZmZWN0IG9mIFBlcnZhc2l2ZSBFbmNyeXB0aW9uIG9uIE9wZXJhdG9y
cyc8YnIgY2xhc3M9IiI+DQombmJzcDsmbHQ7ZHJhZnQtbW0td2ctZWZmZWN0LWVuY3J5cHQtMTMu
dHh0Jmd0OyBhcyBJbmZvcm1hdGlvbmFsIFJGQzxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
ClRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3Ms
IGFuZCBzb2xpY2l0cyBmaW5hbDxiciBjbGFzcz0iIj4NCmNvbW1lbnRzIG9uIHRoaXMgYWN0aW9u
LiBQbGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21tZW50cyB0byB0aGU8YnIgY2xhc3M9IiI+DQo8
YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyIgY2xhc3M9IiI+aWV0ZkBpZXRmLm9yZzwvYT4g
bWFpbGluZyBsaXN0cyBieSAyMDE3LTEyLTA0LiBFeGNlcHRpb25hbGx5LCBjb21tZW50cyBtYXkg
YmU8YnIgY2xhc3M9IiI+DQpzZW50IHRvIDxhIGhyZWY9Im1haWx0bzppZXNnQGlldGYub3JnIiBj
bGFzcz0iIj5pZXNnQGlldGYub3JnPC9hPiBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNl
IHJldGFpbiB0aGUgYmVnaW5uaW5nIG9mPGJyIGNsYXNzPSIiPg0KdGhlIFN1YmplY3QgbGluZSB0
byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpB
YnN0cmFjdDxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNw
OyZuYnNwO1BlcnZhc2l2ZSBNb25pdG9yaW5nIChQTSkgYXR0YWNrcyBvbiB0aGUgcHJpdmFjeSBv
ZiBJbnRlcm5ldCB1c2VycyBpczxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO29mIHNlcmlvdXMg
Y29uY2VybiB0byBib3RoIHRoZSB1c2VyIGFuZCB0aGUgb3BlcmF0b3IgY29tbXVuaXRpZXMuPGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7UkZDNzI1OCBkaXNjdXNzZWQgdGhlIGNyaXRpY2FsIG5l
ZWQgdG8gcHJvdGVjdCB1c2VycycgcHJpdmFjeSB3aGVuPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7ZGV2ZWxvcGluZyBJRVRGIHNwZWNpZmljYXRpb25zIGFuZCBhbHNvIHJlY29nbml6ZWQgbWFr
aW5nIG5ldHdvcmtzPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7dW5tYW5hZ2VhYmxlIHRvIG1p
dGlnYXRlIFBNIGlzIG5vdCBhbiBhY2NlcHRhYmxlIG91dGNvbWUsIGFuPGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7YXBwcm9wcmlhdGUgYmFsYW5jZSBpcyBuZWVkZWQuICZuYnNwO1RoaXMgZG9j
dW1lbnQgZGlzY3Vzc2VzIGN1cnJlbnQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtzZWN1cml0
eSBhbmQgbmV0d29yayBtYW5hZ2VtZW50IHByYWN0aWNlcyB0aGF0IG1heSBiZSBpbXBhY3RlZCBi
eSB0aGU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtzaGlmdCB0byBpbmNyZWFzZWQgdXNlIG9m
IGVuY3J5cHRpb24gdG8gaGVscCBndWlkZSBwcm90b2NvbDxiciBjbGFzcz0iIj4NCiZuYnNwOyZu
YnNwO2RldmVsb3BtZW50IGluIHN1cHBvcnQgb2YgbWFuYWdlYWJsZSwgc2VjdXJlIG5ldHdvcmtz
LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0i
Ij4NCjxiciBjbGFzcz0iIj4NClRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWE8YnIgY2xhc3M9
IiI+DQo8YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1tbS13
Zy1lZmZlY3QtZW5jcnlwdC8iIGNsYXNzPSIiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LW1tLXdnLWVmZmVjdC1lbmNyeXB0LzwvYT48YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQpJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhPGJyIGNsYXNzPSIiPg0K
PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtbW0td2ctZWZm
ZWN0LWVuY3J5cHQvYmFsbG90LyIgY2xhc3M9IiI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtbW0td2ctZWZmZWN0LWVuY3J5cHQvYmFsbG90LzwvYT48YnIgY2xhc3M9IiI+
DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUg
YmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJyIGNsYXNzPSIiPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_87E699C3418F4B99AC1805B2B50E0700ciscocom_--


From nobody Mon Nov 13 04:47:29 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 C48FF12941C for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 04:47:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, 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 ECyYHH7zLkW0 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 04:47:26 -0800 (PST)
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 3D10C1292F4 for <ietf@ietf.org>; Mon, 13 Nov 2017 04:47:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2591; q=dns/txt; s=iport; t=1510577246; x=1511786846; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=K845La+huOlc7KvLqLDRIzhUBXVKCNj3c/y5Ie6gQCM=; b=bbXV/2gXy5GsZOvDZfFBUlJ4xB1a8iCkkU5BCChoxJmrpn7NtNicrZZ2 fv4kbWRlcb7J4EX3vlGZJydoOI4kHPfnzeMFfoZLpfJHODvYd33BRZOD9 XijB8OSdAcj9+95+ib6oEaYE5JRSKpJRTCn6vJs2K+iGcQDndkpU5kTse c=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CpAAA0kwla/4gNJK1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM1gVKEJYofjymBfZZQghEHA4U7AoRYPxgBAQEBAQEBAQFrKIU?= =?us-ascii?q?fAQUjVhALDgojBwICVwYBDAgBAYoeq3GCJ4sGAQEBAQEBAQEBAQEBAQEBAQEBE?= =?us-ascii?q?Q+DNIFlIoNngwGILIJjBZJ6jzCERoIkjhqCFYYIg2CHRZYkgTkfOIFyNCEIHRW?= =?us-ascii?q?DLoMQgVs0iRcBAQE?=
X-IronPort-AV: E=Sophos;i="5.44,389,1505779200";  d="asc'?scan'208";a="30703346"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Nov 2017 12:47:25 +0000
Received: from [10.70.233.6] ([10.70.233.6]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id vADClL0V015514; Mon, 13 Nov 2017 12:47:23 GMT
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Mark Nottingham <mnot@mnot.net>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com>
Date: Mon, 13 Nov 2017 20:47:08 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7Wd1LGPCM7XiwkAOMrDKv32JWkSuOIg53"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YOhqJJJubA42xa6_aB1o9guZ2uc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 12:47:28 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7Wd1LGPCM7XiwkAOMrDKv32JWkSuOIg53
Content-Type: multipart/mixed; boundary="E7LD9grgp5RfUoLDILqDN21P4M7dKe9wc";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Mark Nottingham <mnot@mnot.net>,
 Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>
Message-ID: <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of
 Pervasive Encryption on Operators) to Informational RFC
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com>
 <20171112115510.GA29392@laperouse.bortzmeyer.org>
 <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
 <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
 <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com>
 <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
In-Reply-To: <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>

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



On 11/13/17 4:08 PM, Mark Nottingham wrote:
> 1. Introduction - "Ideally, new methods could be developed to accomplis=
h the goals of current practices despite changes in the extent to which c=
leartext will be available to network operators." It's not at all clear t=
hat this would be ideal, since the goals of some of the documented practi=
ces are quite questionable, both technically and ethically.

Can you please explain what you mean by that last statement?=C2=A0 I ask
because the statement leads us to a dead end when it is not qualified,
rather than a way forward to address what you might think "legitimate"
problems to solve.=C2=A0

Eliot


--E7LD9grgp5RfUoLDILqDN21P4M7dKe9wc--

--7Wd1LGPCM7XiwkAOMrDKv32JWkSuOIg53
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

iQEcBAEBCAAGBQJaCZRNAAoJEIe2a0bZ0nozExAIALvH59+igKrQo1aRp8gN1g4j
iu/QbFA9gMPxVbqop+FZegXzuZLROPiQ24iGSCAMglptqqPoKMqZubbABLrRAd4H
AaYDugcPW4N3CG4LRAoXMc6yWGWZFYQFq2kKkoYZZQ+s4oHibnSlNY5D/fetiB6D
HhzSk8uwBnUygpOpnCK4PntxZhj2Lu63gEpOg5jUQndAgzLgEeECqZ13cRyr72C1
Ym78okhezzI4+WmJsPDgj37JMCdcoxdrcnu1kW7YE92NQUAG6DBBRbRh3mrA1ysN
toYc8bU1BNq4307Jl0vslg2rValADSiMIL54HpW0eFMblkUtO1HG+BmbeRY+eRY=
=mGuh
-----END PGP SIGNATURE-----

--7Wd1LGPCM7XiwkAOMrDKv32JWkSuOIg53--


From nobody Mon Nov 13 04:58:31 2017
Return-Path: <tjc@ecs.soton.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 1D909129418 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 04:58:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z4cg6NZGhfg7 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 04:58:26 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E48B12783A for <ietf@ietf.org>; Mon, 13 Nov 2017 04:58:25 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id vADCwJ3i018615; Mon, 13 Nov 2017 12:58:19 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk vADCwJ3i018615
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1510577899; bh=P6xayEp40UL9AcUg7lNUNv9U9iI=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=JufiTfQYyirnUUReBTK1xurbCPm4CVnQRR2dq0UeIJYH3KQ7MH0T5FN6NlCpR2NnR j25to9QtgaBxuHOGcJ3McqQdzbnZ5GpvFN3VQ/4HWop8g1gGOa7nASwI3ZYU5Y7uOr +7XpvdXT6pdPbxFTYKHLwBhKT4bIMU0jBIA+xBl8=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id yACCwJ1431308805Ha ret-id none; Mon, 13 Nov 2017 12:58:19 +0000
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:e565:a751:53f4:fd9a] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id vADCvPsI007143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Nov 2017 12:58:14 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: IETF Website Status Update
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <7930fd9b-3c06-7b5a-2a28-5198604af5de@gmail.com>
Date: Mon, 13 Nov 2017 12:58:14 +0000
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|4dee98c7626b21fb8f54f27492154f4fyACCwJ03tjc|ecs.soton.ac.uk|2FA836D7-81CF-4F4E-866B-5845C13AA4A1@ecs.soton.ac.uk>
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com> <7930fd9b-3c06-7b5a-2a28-5198604af5de@gmail.com> <2FA836D7-81CF-4F4E-866B-5845C13AA4A1@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ssss
X-smtpf-Report: sid=yACCwJ143130880500; tid=yACCwJ1431308805Ha; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: vADCwJ3i018615
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fZIgRzeEUD73e4kOKEvGGqpKss0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 12:58:29 -0000

> On 10 Nov 2017, at 23:01, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 01/11/2017 10:36, Russ Housley wrote:
>> I want to share an update on progress on the IETF website revamp =
project. In particular I=E2=80=99d like to highlight what has been done =
to respond to feedback from the IETF community received around IETF 99.
>>=20
>> A. Provide a landing page dedicated to current IETF participants
>>=20
>> A draft is currently posted at https://beta.ietf.org/links/
>>=20
>> That page includes links to:
>> - items on the left-side at www.ietf.org (or a subset thereof)
>> - information about the next IETF meeting=20
>> - links to functions at datatracker.ietf.org=20
>>=20
>> The goal is to make this page:
>> - viewable in a single screen on a desktop/laptop display
>=20
> In that, it fails, compared to https://www.ietf.org/content.html :
> a) at least 5cm vertical space is wasted with pointless blurb.
> b) because of the lack of columns and empty space, it is much
> harder to spot individual items.
>=20
> On the other hand, it's usable on a smartphone, which the old
> page hardly is.
>=20
> So there's the basic question: do we want to make the site
> harder to use on a laptop or desktop so that it's easier to use
> on a smartphone? That goes for pretty much every page on the beta
> site, I think, although it seems to be a rather noticeable issue
> for this particular page.

Do we have an example meeting page in the new =E2=80=9Cbeta=E2=80=9D =
format?

Tim

>=20
> Regards
>    Brian
>=20
>> - reachable via a short, memorable URL
>>=20
>> The current content includes changes implemented based on suggestions =
received via email after IETF 99. Of course, this page will be updated =
further based on input from the community.
>>=20
>> B. Ensure WCAG 2.0 compliance
>>=20
>> Since IETF 99, we have worked with the website developer to improve =
compliance. This is a requirement of the Statement of Work =
(https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf). =
We believe that has been accomplished. However, ensuring and improving =
accessibility must be part of ongoing editorial practices, so it will =
continue to be an area of focus for the website.
>>=20
>> C. Conduct review with other key audiences, especially potential =
participants and non-participants
>>=20
>> Additional interviews with members of the key audiences have been =
conducted to gather input. In general, response to the beta.ietf.org =
site was positive.  IETF newcomers say that the new site makes it easier =
to understand what the IETF is all about. Some specific suggestions have =
been incorporated into the project, and they are included at =
https://github.com/ietf/www.ietf.org/issues =20
>>=20
>> D. Improve data use and load times
>>=20
>> Since IETF 99, the beta.ietf.org site was placed behind the =
Cloudflare CDN. This has significantly improved load times. Of note, in =
interviews (see item C above), new or non-IETF participants located in =
Latin America and Africa did not report load time as a significant =
issue. However, as the new site moves to production, the editorial =
process will continue to fine tune how images and other elements are =
handled to further improve performance. =20
>>=20
>> Next steps:
>>=20
>> We are continuing to fine tune content and are aiming to move to =
production after IETF 100. One significant task remaining is to ensure =
continuity for important URLs, as specified in the Statement of Work. We =
expect to tackle that after IETF 100.
>>=20
>> We welcome input and suggestions. We held "office hours" at IETF 98 =
and IETF 99, and we will hold "office hours=E2=80=9D at IETF 100.  If =
you will be in Singapore, please take this opportunity to share feedback =
in person. Details will be posted on a sign around the IETF meeting =
registration desk. And, of course, questions or issues can always be =
raised at https://github.com/ietf/www.ietf.org/issues =20
>>=20
>> Sincerely,
>>  Russ Housley
>>  IETF Website Revamp Project Manager
>>=20
>=20


From nobody Mon Nov 13 06:06:36 2017
Return-Path: <victor@jvknet.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F200912943E for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 06:06:34 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jvknet-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 WNqcTpU4Z4CY for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 06:06:29 -0800 (PST)
Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::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 DD491129438 for <ietf@ietf.org>; Mon, 13 Nov 2017 06:06:28 -0800 (PST)
Received: by mail-ot0-x229.google.com with SMTP id s4so4469101ote.4 for <ietf@ietf.org>; Mon, 13 Nov 2017 06:06:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jvknet-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=6PpC+yn0mmhVCS+H8jCItssrutvj0rvi/4mpyUMHPPs=; b=ooLUWDe2A1AUxO0SwioEXK9hYW7dim6SMeQ8WAgso2G+KJhngAHZSzlQepbBD5RAVZ mRg9sEQpZlZ+adix5vhqUN4XTTXln2H+Ix4IbZIfnhZN9FFg7WjnyG44Wo8bsgQOYnc0 gVy3yRGGP/BEQe6SrCBaiLhKs3qbLWyILVerl5/Bb6Qx22d1uBOmX39BxpEAxuSuGYbb c4jArWhR6hhimOni4t3Fxt8ABKHZF/wjELF+upJ2eDNXBAexF5AOgGZ9Ar9DTCQ/OuXY 6wz1A0gCfFRFFFIznSUl4eJGJKZ5hEtimF6mt5w8UOJQvq9yjQ9WBZ1RJxBQOgDdOkQj OmqQ==
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=6PpC+yn0mmhVCS+H8jCItssrutvj0rvi/4mpyUMHPPs=; b=U4i3aIxqyR5cb+c6bexlvDWE46Kuc3RPzf/uRFZiMXCdG/p4NY+BMsTKfTjaNmkMU7 jFzsX1accVtpUBTWdQ2tmWaxtTLAxmZ5ATHCVVXx1b1ildS/BZKmNgQ+qLXdf2xuwqD7 8PYsQSZd6AbB3URp1HdEt7M0GTjm5scjfqHTe+hQWfiznLAMKLxEYnOhnwG7s5qG5WNQ y3ETPOeSsDhx0nJv0sHQgQSU7NS4WYbQ6apAjUFSplETr4yOwZ0ADohW5FLlA93fptPg QMJBcJzAaDxZJzO0rEFVhd4fQRttKnObj6CRfMAcsS+cpz5+3wAiNl3RRMVyDpgd1a9e j9Eg==
X-Gm-Message-State: AJaThX61cDbz8LyKPaqfHfaH9VprNkT3pcTHn3vcLV4AjjqdRJ1y4JLr +j5hkQOcHs5/4a84LzHCI/wBYLFnJge3XeExzHnXRg==
X-Google-Smtp-Source: AGs4zMYqxdwx21mYvy2kpGkY+vwatWcwseUcrhPE2B8YdQdfSe0tYw9Z6Jxyn7oR7JBuX0ofQ7RItqfTock/c2JYNFI=
X-Received: by 10.157.33.228 with SMTP id s91mr5750762otb.0.1510581987965; Mon, 13 Nov 2017 06:06:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.13.74 with HTTP; Mon, 13 Nov 2017 06:06:27 -0800 (PST)
In-Reply-To: <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
From: Victor Kuarsingh <victor@jvknet.com>
Date: Mon, 13 Nov 2017 09:06:27 -0500
Message-ID: <CAJc3aaOJz2C7kWzKOZa_SPoyi_VN76t7DzVv1KdnV4HvCPYaCw@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Mark Nottingham <mnot@mnot.net>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@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/xKsytMx_jf09KEbZNjjAUxjWzaE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 14:06:35 -0000

On Mon, Nov 13, 2017 at 3:08 AM, Mark Nottingham <mnot@mnot.net> wrote:
> Since we're talking about the title, I had a different reaction to it; cu=
rrently, it reads as if *all* operators are necessarily affected by pervasi=
ve encryption.
>
> In the discussions I've had, the great majority of operators have said th=
ey are not affected by pervasive encryption (YMMV, of course), so I wonder =
if a title like "Reported Effects of Pervasive Encryption on Operators" or =
"Effects of Pervasive Encryption Purportedly Encountered by Some Operators"=
 would be more appropriate.

I don't think we have enough data to put any quantitative value on
this.  What we have is a list of considerations / issues based on
input.  Suggesting "some" would be as erroneous as suggesting "many".
The current titles seems to be neutral in this regard.

I don't have any specific issues with adding work "Reported" in title,
but does that really add any intrinsic value to the reader? (assuming
one reads the draft and does not stop at the title).

>
> Even then, many of the areas discussed lack important context about wheth=
er or not there are other options to achieve the same goal, and how prevale=
nt their use by operators is. For example, the sections on Content Compress=
ion and Content Encryption beg these questions.

It's possible solutions deployed by operators may have other technical
options, however we lack the full set of data to make claims that
other options can be used, or if so, what obstacles need to be
overcome to change deployments.  There would likely be both technical
and business factors those entities need to address to change things.

Even if there is agreement and a desire to change things, it often
takes time to change production networks which means items listed are
factors for consideration.


>
> It might be useful to have a list of potential effects on network operato=
rs without that context, but some of the items still seem to be written in =
a way that assumes the intrinsic value and uniqueness of the technique bein=
g discussed (e.g., Performance Enhancing Proxies), which can be deeply misl=
eading  (despite the attempt at positioning in the Introduction). If this w=
ere Wikipedia, I'd say there were several NPOV issues remaining here.
>

Who do we think we are misleading?  The section seems to describe
proxies used in mobile networks to deal with real performance issues
related to that access network type.  As a former mobile network
architect and operator, I don't see an issue with what is described.
There are real latency issues to deal with there and this is one way
some have dealt with them.  Even within a single mobile provider's
network, there are often varying technical challenges to deal with
from market to market.

regards,

Victor K



>
>>
>
> --
> Mark Nottingham   https://www.mnot.net/
>
>


From nobody Mon Nov 13 06:40:55 2017
Return-Path: <roni.even@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 737AC129439 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 06:40:53 -0800 (PST)
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 pUHZRS6h9gCu for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 06:40:51 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3F9D5129AAA for <ietf@ietf.org>; Mon, 13 Nov 2017 06:40:51 -0800 (PST)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id C95204D1BBEE6 for <ietf@ietf.org>; Mon, 13 Nov 2017 14:40:47 +0000 (GMT)
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.361.1; Mon, 13 Nov 2017 14:40:49 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.14]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0361.001; Mon, 13 Nov 2017 22:40:42 +0800
From: Roni Even <roni.even@huawei.com>
To: Paul Wouters <paul@nohats.ca>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
Thread-Topic: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
Thread-Index: AQHTW7aHT2q0dvu93EGv5ZYM5mvl26MSYhIw
Date: Mon, 13 Nov 2017 14:40:42 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD836763@DGGEMM506-MBX.china.huawei.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
In-Reply-To: <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.52.40.56]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/12iiOcl6i7GSYE4tEBwzd2NS7rA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Nov 2017 14:40:53 -0000

SW5saW5lDQpSb25pDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0
ZiBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFBhdWwgV291dGVy
cw0KPiBTZW50OiDXmdeV153CoNeQIDEyINeg15XXkdee15HXqCAyMDE3IDE1OjAyDQo+IFRvOiBT
dGVwaGFuZSBCb3J0em1leWVyDQo+IENjOiBpZXRmQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBM
YXN0IENhbGw6IDxkcmFmdC1tbS13Zy1lZmZlY3QtZW5jcnlwdC0xMy50eHQ+IChFZmZlY3Qgb2YN
Cj4gUGVydmFzaXZlIEVuY3J5cHRpb24gb24gT3BlcmF0b3JzKSB0byBJbmZvcm1hdGlvbmFsIFJG
Qw0KPiANCj4gDQo+IA0KPiBJIGNvbmN1ciB3aXRoIG1vc3Qgb2YgU3RlcGhhbmXigJlzIGNvbW1l
bnRzLiBBbmQgSSBmaW5kIHRoZSB1c2Ugb2YgdGhlIHRlcm0NCj4g4oCccGVydmFzaXZlIGVuY3J5
cHRpb27igJ0gdmVyeSBwcm9ibGVtYXRpYy4gUGVydmFzaXZlIG1lYW5zOg0KPiANCj4g4oCcKGVz
cGVjaWFsbHkgb2YgYW4gdW53ZWxjb21lIGluZmx1ZW5jZSBvciBwaHlzaWNhbCBlZmZlY3QpIHNw
cmVhZGluZyB3aWRlbHkNCj4gdGhyb3VnaG91dCBhbiBhcmVhIG9yIGEgZ3JvdXAgb2YgcGVvcGxl
LuKAnQ0KPiANCj4gTW9yZSBlbmNyeXB0aW9uIGlzIG5ldmVyIHVud2VsY29tZSB0byB0aGUgZW5k
dXNlci4NCltSb25pIEV2ZW5dIEkgd2lsbCBhcmd1ZSB0aGlzIHN0YXRlbWVudC4gIE15IGV4cGVy
aWVuY2UgaXMgdGhhdCB0aGUgdXNlciBjYXJlIGFib3V0IHRoZSBlbmNyeXB0aW9uIG9mIGhpcyBj
b250ZW50LiBBcyBmb3IgcHJpdmFjeSAtIGRvIHlvdSBzZWUgdXNlcnMgc3RvcCB1c2luZyBzb2Np
YWwgbWVkaWE/IERvIHRoZXkgaW5zdGFsbCBhcHBsaWNhdGlvbnMgdGhhdCBhc2sgIGZvciBhY2Nl
c3MgdG8geW91IGNvbnRhY3QsIHBob3RvcywgbG9jYXRpb24gb3IgbGlrZSBtb3N0IHVzZXJzIHRo
ZXkganVzdCBhcHByb3ZlIHRoZW0uDQo+IA0KPiBJZiB0aGlzIGRvY3VtZW50IGxpc3RlZCB0aGVz
ZSBwcmFjdGlzZXMsIGFsb25nIHdpdGggdmFsaWQgbWV0aG9kcyBmb3INCj4gb3BlcmF0b3JzIHRv
IHN3aXRjaCB0bywgaSBjb3VsZCBiZSBjb252aW5jZWQgdGhlIGRvY3VtZW50IGlzIHVzZWZ1bC4g
QnV0IGFzDQo+IFN0ZXBoYW5lIHBvaW50ZWQgb3V0LCBhIGxvdCBvZiB0aGVzZSBwcm9ibGVtcyBh
cmUgZGVzaXJlZCBmZWF0dXJlcy4gVGhhdCB0aGUNCj4gb3BlcmF0b3IgaGFzIGxlc3MgbmV0d29y
a2luZyBkZWJ1Z2dpbmcgdG9vbHMgaXMgYW4gdW5hdm9pZGFibGUgc2lkZSBlZmZlY3QsDQo+IGJ1
dCBzaG91bGQgbm90IGJlIHVzZWQgYXMgYW4gYXJndW1lbnQgYWdhaW5zdCBtb3JlIGVuY3J5cHRp
b24uDQo+IA0KPiBCdXQgaW4gaXRzIGN1cnJlbnQgZm9ybSwgaXQgc2VlbXMgdGhpcyBkb2N1bWVu
dCB3b3VsZCBiZSBwcmltZSBjYW5kaWRhdGUgZm9yDQo+IG9wZXJhdG9yIG1pc2JlaGF2aW91ciBq
dXN0aWZpY2F0aW9uIOKAnHNhbmN0aW9uZWTigJ0gYnkgdGhlIElFVEYuDQo+IA0KPiBOb3RlIHRo
YXQgSSBfZG9fIGJlbGlldmUgaW4gdGhlIGF1dGhvcnPigJkgZ29vZCBpbnRlbnRpb24gb2YganVz
dCBkb2N1bWVudGluZw0KPiB0aGUgbmV3IHByb2JsZW1zIG9wZXJhdG9ycyBmYWNlLiBCdXQgdGhl
IElFVEYgd2lsbCBoYXZlIHRha2VuIHRoZXNlIGlzc3Vlcw0KPiBpbnRvIGNvbnNpZGVyYXRpb24g
YWxyZWFkeSBiZWZvcmUgaXQgcHVibGlzaGVkIHRoZSBSRkNzLg0KPiANCj4gVGhpcyBkb2N1bWVu
dHMgZmVlbHMgKHVuaW50ZW50aW9uYWxseSkgdGhhdCB3ZSBuZWVkIHRvIGdvIGJhY2sgdG8gYmUN
Cj4gZHJhd2luZyBib2FyZCB0byByZWNvbnNpZGVyIHRoZXNlIG9wZXJhdG9yIGlzc3Vlcy4NCj4g
DQo+IFBhdWwNCj4gDQo+ID4gT24gTm92IDEyLCAyMDE3LCBhdCAxOTo1NSwgU3RlcGhhbmUgQm9y
dHptZXllciA8Ym9ydHptZXllckBuaWMuZnI+DQo+IHdyb3RlOg0KPiA+DQo+ID4gT24gTW9uLCBO
b3YgMDYsIDIwMTcgYXQgMDY6MDY6NTBBTSAtMDgwMCwgVGhlIElFU0cNCj4gPiA8aWVzZy1zZWNy
ZXRhcnlAaWV0Zi5vcmc+IHdyb3RlIGEgbWVzc2FnZSBvZiAzNyBsaW5lcyB3aGljaCBzYWlkOg0K
PiA+DQo+ID4+IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSBhbiBpbmRpdmlk
dWFsIHN1Ym1pdHRlciB0bw0KPiA+PiBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50OiAt
ICdFZmZlY3Qgb2YgUGVydmFzaXZlIEVuY3J5cHRpb24gb24NCj4gPj4gT3BlcmF0b3JzJyA8ZHJh
ZnQtbW0td2ctZWZmZWN0LWVuY3J5cHQtMTMudHh0PiBhcyBJbmZvcm1hdGlvbmFsIFJGQw0KPiA+
DQo+ID4gSSdtIHF1aXRlIGNvbmNlcm5lZCBieSB0aGlzIGRvY3VtZW50LiBCYXNpY2FsbHksIGl0
IHNlZW1zIHRvIG1lIGl0DQo+ID4gZGV2aWF0ZXMgYSBsb3QgZnJvbSBhIHNpbXBsZSBkZXNjcmlw
dGlvbiBvZiBjdXJyZW50IHByYWN0aWNlcywgYW5kDQo+ID4gZ29lcyBpbnRvIHByb21vdGluZyB0
aGVtLiBUaGUgb3ZlcmFsbCBlZmZlY3Qgc2VlbXMgdG8gbWUgdmVyeQ0KPiA+IGRhbmdlcm91cy4g
T25lIGNhbiBlYXNpbHkgcmVhZCB0aGlzIGRvY3VtZW50IGFzICJlbmNyeXB0aW9uIGlzIGEgcGFp
bg0KPiA+IGZvciB0aGUgb3BlcmF0b3JzLCB3ZSBzaG91bGQgbm90IHByb21vdGUgaXQgdG9vIGFn
cmVzc2l2ZWx5Ii4NCj4gPg0KPiA+IE15IG9waW5pb24gaXMgdGhhdCBpdHMgcHVibGljYXRpb24g
YXMgaXQgaXMgd291bGQgaW5mbGljdCByZWFsIGhhcm0gdG8NCj4gPiB0aGUgZWZmb3J0cyBvZiBJ
RVRGIHRvIHByb21vdGUgcHJpdmFjeSAod2hpY2ggaW1wbGllcywgYW1vbmcgb3RoZXINCj4gPiB0
aGluZ3MsIGEgbG90IG9mIGVuY3J5cHRpb24pLg0KPiA+DQo+ID4gVGhlIGRvY3VtZW50IGFsc28g
Y29tcGxldGVseSBpZ25vcmVzIG5ldHdvcmsgbmV1dHJhbGl0eSwgbm90IHRvDQo+ID4gbWVudGlv
biB0aGUgZW5kLXRvLWVuZCBwcmluY2lwbGUuDQo+ID4NCj4gPiBNb3JlIHByZWNpc2VseToNCj4g
Pg0KPiA+PiBUaGlzIGRvY3VtZW50IGRpc2N1c3NlcyBwcmFjdGljZXMgY3VycmVudGx5IHVzZWQg
YnkgbmV0d29yayBvcGVyYXRvcnMNCj4gPj4gdG8gbWFuYWdlLCBvcGVyYXRlLCBhbmQgc2VjdXJl
IHRoZWlyIG5ldHdvcmtzDQo+ID4NCj4gPiBBY3R1YWxseSwgaXQgZG9lcyBub3QgImRpc2N1c3Mi
OiBpdCBkZXNjcmliZXMgdGhlbSwgdXNpbmcgb25seSB0aGUNCj4gPiBhcmd1bWVudHMgb2YgdGhl
IG9wZXJhdG9ycyB0aGF0IHVzZSB0aGVzZSBwcmFjdGljZXMsIHJhcmVseQ0KPiA+IHF1ZXN0aW9u
aW5nIHRoZW0uDQo+ID4NCj4gPj4gdGhlIGltcGFjdCBvZiBwZXJ2YXNpdmUgZW5jcnlwdGlvbg0K
PiA+DQo+ID4gTm90ZSB0aGF0IHdlIGFyZSBmYXIgZnJvbSAicGVydmFzaXZlIGVuY3J5cHRpb24i
LiBGb3IgaW5zdGFuY2UsIHRoZQ0KPiA+IEROUyB0cmFmZmljIGlzIGFsbW9zdCBlbnRpcmVseSBp
biBjbGVhciAoUkZDIDc4NTgpLg0KPiA+DQo+ID4+IEZvciBleGFtcGxlLCB0aGUgdHJhZmZpYyBw
YXR0ZXJucyBiZXR3ZWVuIHNlcnZlciBhbmQgYnJvd3NlciBhcmUNCj4gPj4gZGVwZW5kZW50IG9u
IGJyb3dzZXIgc3VwcGxpZXIgYW5kIHZlcnNpb24NCj4gPg0KPiA+IFRoYXQncyBhIGdvb2QgZXhh
bXBsZSBvZiB3aHkgSFRUUCBzZXNzaW9ucyBtdXN0IGJlIGVuY3J5cHRlZDogdGhlDQo+ID4gVXNl
ci1BZ2VudDogZmllbGQgaXMgdmVyeSByZXZlYWxpbmcsIGFtb25nIG90aGVyIGluZm9zIHNlbnQg
YnkgdGhlDQo+ID4gYnJvd3NlciwgYXMgZXhlbXBsaWZpZWQgYnkgdGhlIFBhbm9wdGljbGljaw0K
PiA+IDxodHRwczovL3Bhbm9wdGljbGljay5lZmYub3JnLz4NCj4gPg0KPiA+PiBOZXR3b3JrIG9w
ZXJhdG9ycyB1c2UgcGFja2V0IGNhcHR1cmVzIGFuZCBwcm90b2NvbC1kaXNzZWN0aW5nDQo+ID4+
IGFuYWx5emVycyB3aGVuIHJlc3BvbmRpbmcgdG8gY3VzdG9tZXIgcHJvYmxlbXMsDQo+ID4NCj4g
PiBOb3QgYWxsIG5ldHdvcmsgb3BlcmF0b3JzIGFyZSBzbyBiZW5ldm9sZW50LiBJIGRvdWJ0IHRo
YXQgbWFueSAzMCAkIG9yDQo+ID4gMjUg4oKsIC8gbW9udGggSVNQIHVzZSB0Y3BkdW1wIHdoZW4g
dGhlIGN1c3RvbWVyIGhhcyBhIHByb2JsZW0gOi0pDQo+ID4gU2VyaW91c2x5LCB0aGlzIHNlbnRl
bmNlIGlzIHZlcnkgZGFuZ2Vyb3VzIGJlY2F1c2Ugb2Y6DQo+ID4NCj4gPj4gVGhlIGFiaWxpdHkg
dG8gaWRlbnRpZnkgdGhlIHByb2JsZW0gYXBwbGljYXRpb24ncyB0cmFmZmljIGlzDQo+ID4+IGlt
cG9ydGFudCBhbmQgZGVlcCBwYWNrZXQgaW5zcGVjdGlvbiAoRFBJKSBpcyBvZnRlbiB1c2VkIGZv
ciB0aGlzDQo+ID4+IHB1cnBvc2UNCj4gPg0KPiA+IFRoaXMgcmVhbGx5IGxvb2tzIGxpa2UgYW4g
YXR0ZW1wdCB0byAic2VsbCIgRFBJIGJ5IGV4cGxhaW5pbmcgdGhhdCBpdA0KPiA+IG1heSBiZW5l
Zml0IHRoZSB1c2Vycy4gQWN0dWFsbHksIEkgd291bGQgbGlrZSB0byBzZWUgbXkgSVNQIGdvaW5n
IGludG8NCj4gPiBzdWNoIGVmZm9ydHMgdG8gaGVscCBtZSBidXQgSSBkb3VidCBpdCB3aWxsIGJl
IHRoZSBjYXNlLg0KPiA+DQo+ID4gTm90ZSB0aGF0IG5vIElTUCBkb2N1bWVudCB0aGUgcHJhY3Rp
Y2VzIGl0IGFjdHVhbGx5IHVzZSBhZ2FpbnN0IHVzZXINCj4gPiBmbG93cy4gVGhpcyBpcyBzdWZm
aWNpZW50IHByb29mIHRoYXQgdGhleSBhcmUgbm90IGRvbmUgaW4gdGhlIGludGVyZXN0DQo+ID4g
b2YgdGhlIHVzZXJzLg0KPiA+DQo+ID4+IEZvciBleGFtcGxlLCBieSBpbnZlc3RpZ2F0aW5nIHBh
Y2tldCBsb3NzIChmcm9tIFRDUCBzZXF1ZW5jZSBhbmQNCj4gPj4gYWNrbm93bGVkZ2VtZW50IG51
bWJlcnMpLCByb3VuZC10cmlwLXRpbWUgKGZyb20gVENQIHRpbWVzdGFtcA0KPiBvcHRpb25zDQo+
ID4+IG9yIGFwcGxpY2F0aW9uLWxheWVyIHRyYW5zYWN0aW9ucywgZS5nLiwgRE5TIG9yIEhUVFAg
cmVzcG9uc2UgdGltZSksDQo+ID4+IFRDUCByZWNlaXZlLXdpbmRvdyBzaXplLCBwYWNrZXQgY29y
cnVwdGlvbiwgaW5lZmZpY2llbnQNCj4gPj4gZnJhZ21lbnRhdGlvbiwgb3IgYXBwbGljYXRpb24t
bGF5ZXIgcHJvYmxlbXMsIHRoZSBvcGVyYXRvciBjYW4gbmFycm93DQo+ID4+IHRoZSBwcm9ibGVt
DQo+ID4NCj4gPiBBbG1vc3QgYWxsIG9mIHRoZXNlIGludmVzdGlnYXRpb25zIGNhbiBiZSBwZXJm
b3JtZWQgZXZlbiBpZiBUTFMgb3IgU1NIDQo+ID4gaXMgdXNlZC4gQWdhaW4sIGl0IHJlYWxseSBz
ZWVtcyBhbiBlZmZvcnQgdG8gbWFrZSBEUEkgYWNjZXB0YWJsZS4NCj4gPg0KPiA+PiBCZWNhdXNl
IG9mIHRoaXMsIGFwcGxpY2F0aW9uIHNlcnZlciBvcGVyYXRvcnMgdXNpbmcgaW5jcmVhc2VkDQo+
ID4+IGVuY3J5cHRpb24gc2hvdWxkIGV4cGVjdCB0byBiZSBjYWxsZWQgdXBvbiBtb3JlIGZyZXF1
ZW50bHkgdG8gYXNzaXN0DQo+ID4+IHdpdGggZGVidWdnaW5nIGFuZCB0cm91Ymxlc2hvb3RpbmcN
Cj4gPg0KPiA+IEhhcmQgdG8gcmVhZCB0aGlzIGFzIHNvbWV0aGluZyBlbHNlIHRoYW4gYSB0aHJl
YXQgImRvIG5vdCB1c2UNCj4gPiBlbmNyeXB0aW9uIG9yIHlvdXIgYnVzaW5lc3Mgd2lsbCBzdWZm
ZXIiLg0KPiA+DQo+ID4+IEEgY29tbW9uLCBlYXJseSB0cmlnZ2VyIGZvciBERG9TIG1pdGlnYXRp
b24gaW5jbHVkZXMgb2JzZXJ2aW5nDQo+ID4+IHVuY2hhcmFjdGVyaXN0aWMgdHJhZmZpYyB2b2x1
bWVzIG9yIHNvdXJjZXM7IGNvbmdlc3Rpb247IG9yDQo+ID4+IGRlZ3JhZGF0aW9uIG9mIGEgZ2l2
ZW4gbmV0d29yayBvciBzZXJ2aWNlLiAgT25lIGFwcHJvYWNoIHRvIG1pdGlnYXRlDQo+ID4+IHN1
Y2ggYW4gYXR0YWNrIGludm9sdmVzIGRpc3Rpbmd1aXNoaW5nIGF0dGFja2VyIHRyYWZmaWMgZnJv
bQ0KPiA+PiBsZWdpdGltYXRlIHVzZXIgdHJhZmZpYy4NCj4gPg0KPiA+IEFyZSB0aGVyZSByZWFs
bHkgZERvUyBhdHRhY2tzIHVzaW5nIGVuY3J5cHRpb24/IEhhcmQgZGF0YSB3ZWxjb21lLg0KPiA+
DQo+ID4+IE1vYmlsZSBuZXR3b3JrcyBlc3BlY2lhbGx5IHJlbHkgb24gY29udGVudC9hcHBsaWNh
dGlvbiBiYXNlZA0KPiA+PiBwcmlvcml0aXphdGlvbiBvZiBPdmVyLXRoZS1Ub3AgKE9UVCkgc2Vy
dmljZXMNCj4gPg0KPiA+IFRoaXMgaXMgYSB2ZXJ5IGltcG9ydGFudCBwb2ludDogaWYgZW5jcnlw
dGlvbiByZWFsbHkgcHJldmVudHMNCj4gPiBwcmlvcml0aXphdGlvbiBvZiBzb21lIHNlcnZpY2Vz
IG92ZXIgdGhlIG90aGVycywgdGhlbiBpdCBtZWFucyB3ZSBuZWVkDQo+ID4gbW9yZSBlbmNyeXB0
aW9uLCBub3QgbGVzcy4gSWYgZW5jcnlwdGlvbiBjYW4gaGVscCBwcmVzZXJ2ZSBuZXR3b3JrDQo+
ID4gbmV1dHJhbGl0eSwgdGhpcyBpcyBhIGdvb2QgcmVhc29uIHRvIHVzZSBpdCBldmVuIG1vcmUu
DQo+ID4NCj4gPj4gRHVlIHRvIHRoZSBjaGFyYWN0ZXJpc3RpY3Mgb2YgdGhlIG1vYmlsZSBsaW5r
LCBwZXJmb3JtYW5jZS1lbmhhbmNpbmcNCj4gPj4gVENQIHByb3hpZXMgbWF5IHBlcmZvcm0gbG9j
YWwgcmV0cmFuc21pc3Npb24gYXQgdGhlIG1vYmlsZSBlZGdlLiAgSW4NCj4gPj4gVENQLCBkdXBs
aWNhdGVkIEFDS3MgYXJlIGRldGVjdGVkIGFuZCBwb3RlbnRpYWxseSBjb25jZWFsZWQgd2hlbiB0
aGUNCj4gPj4gcHJveHkgcmV0cmFuc21pdHMgYSBzZWdtZW50DQo+ID4NCj4gPiBBZ2FpbiwgVExT
IG9yIFNTSCBkbyBub3QgcHJldmVudCB0aGlzIHNvcnQgb2YgaGFja3MuDQo+ID4NCj4gPj4gSW4g
YWRkaXRpb24gdG8gY2FjaGluZywgdmFyaW91cyBhcHBsaWNhdGlvbnMgZXhpc3QgdG8gcHJvdmlk
ZSBkYXRhDQo+ID4+IGNvbXByZXNzaW9uIGluIG9yZGVyIHRvIGNvbnNlcnZlIHRoZSBsaWZlIG9m
IHRoZSB1c2VyJ3MgbW9iaWxlIGRhdGENCj4gPj4gcGxhbiBhbmQgb3B0aW1pemUgZGVsaXZlcnkg
b3ZlciB0aGUgbW9iaWxlIGxpbmsNCj4gPg0KPiA+IEkga25vdyB0aGF0IHNvbWUgbW9iaWxlIG9w
ZXJhdG9ycyAoc2VlLCBpbiBmcmVuY2gsDQo+ID4gPGh0dHBzOi8vd3d3Lmh0ZXVtZXVsZXUuZnIv
bGEtY29tcHJlc3Npb24tZGltYWdlcy1wYXItbGVzLQ0KPiBvcGVyYXRldXJzLz4NCj4gPiApIGFw
cGx5IGEgTE9TU1kgY29tcHJlc3Npb24gd2l0aG91dCB0aGUgdXNlciBjb25zZW50IG9yIGV2ZW4N
Cj4gPiBrbm93bGVkZ2UuIEFnYWluLCBpZiBlbmQtdG8tZW5kIGVuY3J5cHRpb24gcHJldmVudHMg
dGhpcywgdGhpcyBpcyBhDQo+ID4gdmVyeSBnb29kIHJlYXNvbiB0byBkZXBsb3kgZW5jcnlwdGlv
bi4NCj4gPg0KPiA+PiBUaGVzZSByZWd1bGF0aW9ucyBpbmNsdWRlIExhd2Z1bCBJbnRlcmNlcHQs
IGFkaGVyZW5jZSB0byBDb2RlcyBvZg0KPiA+PiBQcmFjdGljZSBvbiBjb250ZW50IGZpbHRlcmlu
ZywgYW5kIGFwcGxpY2F0aW9uIG9mIGNvdXJ0IG9yZGVyDQo+ID4+IGZpbHRlcnMuICBTdWNoIHJl
Z3VsYXRpb25zIGFzc3VtZSBuZXR3b3JrIGFjY2VzcyB0byBwcm92aWRlIGNvbnRlbnQNCj4gPj4g
ZmlsdGVyaW5nIGFuZCBhY2NvdW50aW5nLCBhcyBkaXNjdXNzZWQgYmVsb3cuDQo+ID4NCj4gPiBJ
dCBzZWVtcyB0byBtZSB0aGF0IFJGQyAxOTg0IGFscmVhZHkgcmVwbGllcyB0byB0aGlzIHJlYXNv
bmluZy4NCj4gPg0KPiA+PiBUaGlzIHR5cGUgb2YgZ3JhbnVsYXIgZmlsdGVyaW5nIGNvdWxkIG9j
Y3VyIGF0IHRoZSBlbmRwb2ludC4NCj4gPj4gSG93ZXZlciwgdGhlIGxhY2sgb2YgYWJpbGl0eSB0
byBlZmZpY2llbnRseSBtYW5hZ2UgZW5kcG9pbnRzIGFzIGENCj4gPj4gc2VydmljZSByZWR1Y2Vz
IHByb3ZpZGVycycgYWJpbGl0eSB0byBvZmZlciBwYXJlbnRhbCBjb250cm9sLg0KPiA+DQo+ID4g
SSB3b3VsZCBiZSBzcGVjaWFsbHkgdW5oYXBweSBpZiBJRVRGIHdlcmUgdG8gcHVibGlzaCBhIFJG
QyB3aXRoIHN1Y2ggYQ0KPiA+IHNlbnRlbmNlIHdpdGhvdXQgZm9sbG93LXVwIGNvbW1lbnRzLiBG
aWx0ZXJpbmcgTVVTVCBiZSBkb25lIGF0IHRoZQ0KPiA+IGVuZHBvaW50LCBvdGhlcndpc2UgaXQg
aXMgbm90IGEgc2VydmljZSwgaXQgaXMgY2Vuc29yc2hpcC4NCj4gPg0KPiA+IElmIHdlIGFzc3Vt
ZSB0aGF0IHRoZSBzdWJzY3JpYmVyIHdhbnRzIHBhcmVudGFsIGNvbnRyb2wsIHRoZW4gd2UgbXVz
dA0KPiA+IGNvbmNsdWRlIHRoYXQgaGUvc2hlIHdpbGwgaGF2ZSBubyBwcm9ibGVtIHNlbmRpbmcg
dGhlIHRyYWZmaWMgdG8gYQ0KPiA+IGZpbHRlcmluZyBwcm94eS4gTm8gbmVlZCB0byBicmVhayBl
bmNyeXB0aW9uIGZvciB0aGF0Lg0KPiA+DQo+ID4+IFNvbWUgbW9iaWxlIGNhcnJpZXJzIHVzZSBI
VFRQIGhlYWRlciBpbnNlcnRpb24gKHNlZSBzZWN0aW9uIDMuMi4xIG9mDQo+ID4+IFtSRkM3MjMw
XSkgdG8gcHJvdmlkZSBpbmZvcm1hdGlvbiBhYm91dCB0aGVpciBjdXN0b21lcnMgdG8gdGhpcmQN
Cj4gPj4gcGFydGllcyBvciB0byB0aGVpciBvd24gaW50ZXJuYWwgc3lzdGVtcyBbRW5yaWNoXS4N
Cj4gPg0KPiA+IEFnYWluLCB0aGlzIHRlY2huaXF1ZSwgd2hpY2ggaGFzIHZlcnkgc2VyaW91cyBw
cml2YWN5IGNvbnNlcXVlbmNlcw0KPiA+IChzZWUgdGhlIG1lbnRpb25lZCByZWZlcmVuY2UgW0Vu
cmljaF0gd2l0aCBmb3IgZXhhbXBsZSBWb2RhZm9uZSB3aGljaA0KPiA+IGFkZGVkIHRoZSBwaG9u
ZSBudW1iZXIgYW5kIHRoZSBJTUVJIGluIEhUVFAgaGVhZGVycykgTVVTVCBOT1QgYmUNCj4gZG9u
ZQ0KPiA+IGFuZCwgaWYgZW5jcnlwdGlvbiBzdG9wcyBpdCwgZ3JlYXQuDQo+ID4NCj4gPiBFZGl0
b3JpYWwgaXNzdWVzOg0KPiA+DQo+ID4+IEN1cnJlbnRseSwgc29tZSBtb2JpbGUgbmV0d29yayBz
ZXJ2aWNlIHByb3ZpZGVycyByZWRpcmVjdCB0aGUNCj4gPj4gY3VzdG9tZXIgdXNpbmcgSFRUUCBy
ZWRpcmVjdCB0byBhIHBhZ2UgdGhhdCBleHBsYWlucyB0byB0aG9zZQ0KPiA+PiBjdXN0b21lcnMg
dGhlIHJlYXNvbiBmb3IgdGhlIGJsb2NrYWdlIGFuZCB0aGUgc3RlcHMgdG8gcHJvY2VlZA0KPiA+
DQo+ID4gQSBtZW50aW9uIG9mIFJGQyA2MTA4IHdvdWxkIGJlIGNvb2wgaGVyZS4NCj4gPg0KPiA+
PiBtb25pdG9yIGluY29taW5nIG1haWwgdG8gcmVtb3ZlIFNQQU0NCj4gPg0KPiA+IFdoeSBpcyBz
cGFtIHVwcGVyY2FzZWQ/DQoNCg==


From nobody Mon Nov 13 18:56:23 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 4FC701292FD; Mon, 13 Nov 2017 18:56:10 -0800 (PST)
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_PASS=-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 pufDvwyYGBIG; Mon, 13 Nov 2017 18:56:08 -0800 (PST)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0079.outbound.protection.outlook.com [104.47.32.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFA7512878D; Mon, 13 Nov 2017 18:56:07 -0800 (PST)
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=jHqaQQGqYI7vEqIAye8psJhIO6rTXhqABMHNRL7ZOVI=; b=Ogj5V/600fWbB0m9RF48I37L8vq7+A4kCQDQpznuMvuvQRhXp+8KBOM01rwpU1+xn7e5w2CKqiKcVsomSzm2wQ/F/FHceSZfHrN55diP4IkkWQuoWG7cyG7lFbIiVR+PolmHhSZ7iSUtFlDDQ9HiNfy9/4vZXuwIX9WA9E3aN9c=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=ford@isoc.org; 
Received: from [IPv6:2001:67c:370:128:bc5c:3d65:bb4e:bd9b] (2001:67c:370:128:bc5c:3d65:bb4e:bd9b) by BY2PR06MB2213.namprd06.prod.outlook.com (10.166.113.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.218.12; Tue, 14 Nov 2017 02:56:04 +0000
From: Matthew Ford <ford@isoc.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Date: Tue, 14 Nov 2017 10:56:00 +0800
Subject: IETF Journal: Latest issue now available
Message-Id: <24667AD9-44E6-4995-9F15-2B98B93D0020@isoc.org>
To: ietf@ietf.org, 100attendees@ietf.org, isoc-trustees Elist <isoc-trustees@elists.isoc.org>
X-Mailer: Apple Mail (2.3445.4.7)
X-Originating-IP: [2001:67c:370:128:bc5c:3d65:bb4e:bd9b]
X-ClientProxiedBy: SG2PR0601CA0010.apcprd06.prod.outlook.com (10.170.128.20) To BY2PR06MB2213.namprd06.prod.outlook.com (10.166.113.151)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 382da7e1-cf83-456e-d9af-08d52b0b3faf
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603258); SRVR:BY2PR06MB2213; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2213; 3:jonlFd6WFZVwaQTh4tA5Mw0+47HvVWPE+iBaKz0GeUyoZqZPEEM/rqYCMsxYLwTZMX3Lm6BJtv/jrhA6eBc6Ol58eioRW3DcoPxjtyRYSz/gxMkSB14a+HBd4nidQhACh5KdBpVumq1UessJhcJWmmN0vV0LiYzS77tIWTaO1slZsRLHU4kOSNMRddznV8+v7FIZ6z5lGjiY9YFiwSLqaUBJ0WnXshbRSYNgFR/Orn8Z3Iq5fyL4mkyVQDsbtgZ9; 25:KJdYVZNFFn2KcLhTzotHjSpCY8+aNG/thbybhfsife2YS/SkcFQ+7qgzS3Zg5PvcTBrHGtzOeRozazmm50TaiG1KawEysvTU5+IyMlkGerKod1XYeVchcJ/N4DNQ+RBVcjaPuXe9ls4B9DjtyqSEbOljEbMqguaL42BSYZq/tyb+B+/2qsXa8Kv/XcJ846tAQEgD+7MQN+I4oeQUH4DlL5dhqzfLTnuFgGVfmmTlboR1PzrbNqPdVFpHgyUuAACXp1c6pzPRVqzOU5mF0Mca8w7XN3FzA5P6E1VOg04l78QtJy+NJihGBg4+UnWIZtwFfDTgy1YB4TjB53n7fF46Sw==; 31:AMhEbJL5PInCC2eXyvL3XEwBjHLPnEIeMWLLKRTTdFpMs5D/bzwGjzzrQiy5T85qco/1TDjGdNmQUdqQlNGajUlUHvBK0YRCCAG5j11m7oxmqVkcffowkC13uGSUynQRkQN1pqhmBGltbg/iyaElol6hCRYi4RyGEM+kGdZWAYvSztam9mbBuWl2i5TUYiVQmtwuvvHucvs4MZuDuvQ/rGubIlHDu/cJMRPjX8PSm9Y=
X-MS-TrafficTypeDiagnostic: BY2PR06MB2213:
X-LD-Processed: 89f84dfb-7285-4810-bc4d-8b9b5794554f,ExtAddr
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2213; 20:i8RyI63T+lhQNXJy9X4dh+kczetCYd6VXFW0GdXhMbo7fFk/j2Lrh+ng06/UBTXrYSZ29MWysGIiDzBePFSpneOOypqUv7NothfLrZr3rqom9B4nj59jrN7rAd0/B0QEUx8g1pPftaJUKQiCVxQW5bwjeMO43AryR0NDLzKDRiaCeF2Gd9E0uus1JxmXOimWiYJTb6JK/FXsdou972XS2ez+L9DciDR1W2Ushj+48+o3rS5Xw7tyEzuSwdsocE6aXUJ7iTnWJQEIKOHFcBXIEFTeA5R99pzYdLaiosKOrQDzpclfx6leHH7Mk6+ZammmP/ZjLKKxJGwSgV+Xh84o1xSW6zU2QFK+yKCyhOi1dRF4WHDIeDORfNZxtXIV1LmJF5l5S4Pn0rkFsx+r3yhrS4RrA84ydFTbRhS2owICIs7KBnt7pGMovfgJ5qyRfUEaM7xEitX4A+uWCdsqbARK+s15PYC8SpIN2/eSn7pj5pXgLhjp3AqTIxTPwTjB0Bgi; 4:D24ccVwy6vOxwTLtKBTw9egZADeYaT4gOMwHRaNyX1eCY8F49uEPYjRvsVoN8m+4HTdyst0sotYLG+7C5kNOJy/xGOn4RrsuxId6ZpNELZhPNrBbXzjZAqAhJZKDdIfM8n8GfaAtPm5Q5BaF6KQLBtR82hxlmuPhGoP7Rw85TS9w2o5mfEY9r35+1pA4Y70/4Gp38Yd2EZdjvIG1ub/3ZrllRtR94wTK5XNQ47cWi1kUZjwnT4ZMyfF2qlB34PahWSrQ78kfCUIpfTH7tv4wvRBblnUQGpIAnsSMpw67lTxDfqZgZO6T6eDE4L+2bgZBYD0Vt8tomgNTbiKuu7qGQg1eqwKhnK7qyliOX0IN6LAHQTR3O7Lb5/z7UFoQNxhkaJTGjUBoKXKH0gsYDgLQK4HukVikiUq/jwc5WTAEbWE=
X-Microsoft-Antispam-PRVS: <BY2PR06MB2213DB07AA3E3C8FBDB5C6B3A7280@BY2PR06MB2213.namprd06.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(148322886591682)(209352067349851)(192374486261705)(81227570615382); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(3231022)(3002001)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(6041248)(20161123560025)(20161123558100)(20161123564025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR06MB2213; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR06MB2213; 
X-Forefront-PRVS: 04916EA04C
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(39830400002)(376002)(346002)(199003)(54164003)(189002)(31014005)(53936002)(6666003)(478600001)(556974002)(50466002)(316002)(5660300001)(86362001)(6116002)(6916009)(1706002)(6306002)(82746002)(7736002)(83716003)(305945005)(57306001)(33656002)(97736004)(47776003)(23676003)(25786009)(8676002)(8746002)(81156014)(68736007)(36756003)(189998001)(101416001)(50226002)(106356001)(81166006)(2906002)(105586002)(50986999)(8936002)(6486002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR06MB2213; H:[IPv6:2001:67c:370:128:bc5c:3d65:bb4e:bd9b]; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: isoc.org does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA2TUIyMjEzOzIzOklPb3FnM0p5aDFyNzAvcEpSa0ZqdkhjUUJl?= =?utf-8?B?djQydDlZZ1ZtT3JrTUVJSk1yWEdtTjZhcmNNUnFodmpuaHdRWkhrT3VkSnRv?= =?utf-8?B?b2VJcVpET1dEc1pxQmdtSXpleXJHbm1LUFpRbTBaSnhRdkFGMmlPWUpLUWUy?= =?utf-8?B?U21jemxNQlhYSFZmM2tONCtWWVN1QnF0dHpOWWVobFF4d0pDVDdIQjNKRFFM?= =?utf-8?B?ajVYQmdlbWJhN1NQSjBGd3JWQ3JGT3M1Y0l1TGZzdU8yQ3pubmYvbTFrdy9W?= =?utf-8?B?LyswWHY5dmltZUpENUFWMEE3UzRzRThDWXlFRTJvR241T3Z4YXZOUk05dVNI?= =?utf-8?B?ZEQ0QStGVDUvb1FHeVljbkk5N3loK2JLUFp4UktQL3cyMVJTMnRjRGl6YkFY?= =?utf-8?B?eU1MTEVYaEI1VnhLVzM5OVU2c3ZOeS9DT3l0aWh3K3NuaUlhd1h6a3FLRTRq?= =?utf-8?B?QW1tcWMxMWdxQ1lCMzNadmhIWHFZamVYVStJRjl4b042dGoxSE0wTVNoSXNB?= =?utf-8?B?ZVRDME1neFFLNTRXRkZvYUJTcSs2MlpLYTBrblRjejdidGZXWXpTZHhvMmNB?= =?utf-8?B?MHJKcTNnWmdJSWY5VEI1WjIzY2EreWtFR0RsU3NFSWxBMlJOU0VsZ3RnNkN1?= =?utf-8?B?Z2I1MnU4bWJCdzZueitJNnJUWmFmVE80WUY3QTdSUkp5SVc0cERXREF5am10?= =?utf-8?B?TkF1UHdIVmxITkNGeUZkMjhnanNYNG8zUGRZa21BWmhiVk8veFFxNmxJZWF3?= =?utf-8?B?dG5aamlBYmpEcG9mbmVWREZiREk5ZW5XY3lXTzNZbktYdXh2T01mT1AycENl?= =?utf-8?B?SlJDcDZxTlRmZzRWaFRrdFo5RkVwcXIxb0NqaUs3cFJxMkN0WUp3MUdnWHFm?= =?utf-8?B?WU1xVVdYeFpKVW9vWGg5Uzk3bHpyMUZIdExBQTNrZFpRWTJ4U0g5NzVFbnBa?= =?utf-8?B?NG9oWHh6UVJJaXRneWdzWDBmS2NWeU9RRW1MK2YwMzFsaHVLZngrY25ZTTdD?= =?utf-8?B?d3ArVE5EZ2lQWWh1blI5bmlWY0ZLdVpDRmhuOUdYVjdhZk1RY3Q0UXFKR3Y2?= =?utf-8?B?MFM4WmJLN0ZHSW5BVE56RjNsTkxDTGl2NGFRc1kycVRzckIxQjRLS1I1bVkz?= =?utf-8?B?Ri9ZTjhsMldqUUNwcEVVaEViN2JIREdmM0RQNll1SXN5KzhUTm1QWlRITHh5?= =?utf-8?B?QlRGUFA5RGI1SVFvam80VGlOcFpTU2ZScGc3NlJqVkFMbHZWR0RMWWh5WDgr?= =?utf-8?B?UDZFWTE0TkNNaHBTWHpvNEpIdkpGVy9GN2ZkNW84SFFiWVFIak9jYkZRR1Ey?= =?utf-8?B?L05oNzVCVW1pVU5GZDZ1MkhnSmhsOWRpbkQ4d1ZBRjBFUWpDYjJET0NCemRI?= =?utf-8?B?OTlFWmw4NkM5ekMwMXB1Q0M3R0IwUHJFekxQZDkrYlpUdHk0REhWSnJQMnhG?= =?utf-8?Q?ZI6m1d0WlcmOgYzgtS/1Ikwg5M+?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR06MB2213; 6:aXsKSWhXrB991qiH9NZJ/VSVembT5qsQGdYEV4LtNWB+6pxlstd8ePRwBBf2mJvMud/FKbX4Sf8hyXzdNeL/PmpbBRDTMoLJKK7ptp3IHpMD0BpQlOropHbYGDvI/zxrHRLL0lnsSe1IH8c4I4CA7qviHcJI0KME2Asa1Od8q/jJj8xKmC+7EqEwYXUtToNHZZ/y0iYTQGIy8445FQf+JYNjzyOzNFWggF9TKmZsmzRoX9jp2YUzC4uA6VSLGOlRjdk5VSt1x/qVvTp2BW9k8vwXvSHRnQVIhT5oNnNRa27oBsFJY30tRTPCG6WnKz7pAuyKYku/0djy6r6NDYZYD0X7B3Tnp1W2hKodYameBHc=; 5:I4RWs9e/G1kMDHKxvJE09vmTK1H4NOehf3DzO34/TniDMYToSxB0J/FnOwewAMQ3ijNpa3vujqYuPWWAok4dg+fYpNrzqJ08w2twB/DiW8pQGRUmSTU++hvt1u3y1ibWNAC5ktnQvUIE3+o5kI54acFSoUQBTQKCygTQnt/z96I=; 24:9/QKHrPgQJ4aPSLo7C8b+SCKbXZdVx4H+lnywjd0YLHEIPzVcAIJ9L7XKFi4yZz8jWaTEcOzkGxR9TCld+6znEl1NWO5m4j2K7KtAWomyhA=; 7:EOd4N15LAQihejnDVuUC7iAlIoDfhL2lTEU+EJWbiWLc147M8yXRbvNtxJXAHB8UP1Xy7x/h6oCh1OeG4ejmDCk/yPZKn66Zw7IzpJhDOPY3QWPCS0U4v0mZElVU7mu8R9o/X2sVi2Ic2H6lKZnOQv2xxKBx8NwNXatYF69VpbiLLW/8dSdnf7ltRH4DN5iLEbikKkYkZVh4bxIkAHhBvr0JI4qx9kQz/3hR0GaH+oq5J6UyQDqt7GoXG8FEs8BL
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Nov 2017 02:56:04.5135 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 382da7e1-cf83-456e-d9af-08d52b0b3faf
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR06MB2213
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NxeCSGABrORygdzBocAaGtJTb1s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 02:56:10 -0000

Hello! [and =C2=A1Hola! to our Spanish-readers - see below]

I=E2=80=99d like to draw your attention to the latest issue of the IETF =
Journal (Volume 13, Issue 2) which is now available in hardcopy at the =
IETF 100 meeting taking place in Singapore, and online:

	<https://www.ietfjournal.org/journal-issues/november-2017/>

This issue marks the final hardcopy version of the IETF Journal. Since =
2005, the Journal has been printed three times a year, and distributed =
at IETF meetings and by postal mail. As we explain in =E2=80=9CWe=E2=80=99=
re Going Digital!=E2=80=9D, starting in 2018 we=E2=80=99ll be shifting =
our focus to our website, ietfjournal.org. Be sure to follow us on =
Twitter (@ietfjournal) and Facebook (facebook.com/IETFJournal) to stay =
current with future IETF Journal content.

In this issue, you can learn about implementation work taking place in =
the Human Rights Protocol Considerations Research Group, the latest =
security updates to Network Time Protocol, new email-related Working =
Groups JMAP and EXTRA, as well as the important coding work that took =
place as part of the IETF Hackathon.

Our regular columns from the IETF, IAB, and IRTF chairs and coverage of =
the Birds-of-a-Feather meetings and presentations from the Applied =
Networking Research Prize winners wrap up the issue.

Spanish speakers, please note the entire *June* issue (the last one) is =
translated and online at =
<https://www.ietfjournal.org/journal-issues/julio-2017/>

Many thanks to all our contributors. Please send any comments or =
suggestions for future articles to ietfjournal@isoc.org.


Thanks, and happy reading!=20

=E2=80=94 Mat


Mat Ford
Managing Editor
IETF Journal
<https://www.ietfjournal.org/>=


From nobody Mon Nov 13 18:57:37 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 1CE9312944C for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 18:57:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=j1hOtOWK; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=OS5TfsYc
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hLBIUtVHReJW for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 18:57:32 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0E54127076 for <ietf@ietf.org>; Mon, 13 Nov 2017 18:57:27 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 14D1E20DE5; Mon, 13 Nov 2017 21:57:27 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 13 Nov 2017 21:57:27 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=gyt7yXdkVMMHbzr1dEz4+93QngzUd oQzQE0Vu4krIgg=; b=j1hOtOWKbrkT9e3Xu/rwh49TEXHHPlLF2e49WYRK4IcVz HnNKleKn0ljW2f0Zhzg4ZwjphE8pFAbTpj4XPVnFfy5lGoXlFG/XvYcafqdyEP67 shfdg7Eo50M0HSCUnLrHATiHN5r8ToTlYJKpPA/f7SIHdDgg/tuOjOVvfSZy8INU /RHcC1yOBAN+4G53C8tfyFrF/Jq2UIhIHZmOFMaJQfUqCKxcPd1Eoq8YSFiFrrmz 8e3IMiKglmd9GPtxzSPBsbXBBQgJTxMrRe3U6PFb9bSzIpy6OAEkadZNEImb/yAK vLzHTcROc0jBubZWsA4ZyaIbgi0cNypTKgmJ+Ej0g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=gyt7yX dkVMMHbzr1dEz4+93QngzUdoQzQE0Vu4krIgg=; b=OS5TfsYcgPbDGrSd8wukU8 QZWAxyVdD8D4cL+6mD6o7TTKUS7YCs7w2LTVMW693B3Sqbsp/veGsxrl0+6MdbQr tCcv3uGLlPQfzxZOCtH2WsCiIXLL0avrsURFGGnhzgdlwRyJbWGeC7ZPTxzR0ZTC yjp0al05vNRg0iIJdnixYJPQE9//3fKMZC7xY5orwpq9thKeRVGbJNxRVWearl+r tof55cKcDkkZc5N25wMjlSGn/uGimXN12BoVPnJtVI/9malVYrCuBYBFmVn0Vxfm cjcAHhZpY0ajqPzlvN4gwfw3i1IqG+AY52Fhzr2VUwP1mgelwL7jppgH4g1nJLEw ==
X-ME-Sender: <xms:l1sKWimY36Hb8Nimjb6_QgSXQCyI6nkptw7qbArMKWOIMbCydfH__A>
Received: from dhcp-80a4.meeting.ietf.org (dhcp-80a4.meeting.ietf.org [31.133.128.164]) by mail.messagingengine.com (Postfix) with ESMTPA id CC0E67EECF; Mon, 13 Nov 2017 21:57:25 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com>
Date: Tue, 14 Nov 2017 10:58:03 +0800
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net> <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZKEgReGPlNSa7HRFLLmINCTKC5o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 02:57:34 -0000

> On 13 Nov 2017, at 8:47 pm, Eliot Lear <lear@cisco.com> wrote:
>=20
>=20
>=20
> On 11/13/17 4:08 PM, Mark Nottingham wrote:
>> 1. Introduction - "Ideally, new methods could be developed to =
accomplish the goals of current practices despite changes in the extent =
to which cleartext will be available to network operators." It's not at =
all clear that this would be ideal, since the goals of some of the =
documented practices are quite questionable, both technically and =
ethically.
>=20
> Can you please explain what you mean by that last statement?  I ask
> because the statement leads us to a dead end when it is not qualified,
> rather than a way forward to address what you might think "legitimate"
> problems to solve.=20

I mean that the word "ideally" is not really appropriate here. This =
sentence should be dropped, or modified to remove that implication.=20


--
Mark Nottingham   https://www.mnot.net/



From nobody Mon Nov 13 19:01:33 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 8B42A129B39 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:01:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.11
X-Spam-Level: ***
X-Spam-Status: No, score=3.11 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no 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 JB-OXCiMhrry for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:01:30 -0800 (PST)
Received: from sonic302-26.consmr.mail.gq1.yahoo.com (sonic302-26.consmr.mail.gq1.yahoo.com [98.137.68.152]) (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 813E2129B8C for <ietf@ietf.org>; Mon, 13 Nov 2017 19:01:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1510628487; bh=1UXHXwdA+iR+MypG01d565lEW9Ez08JRNGA018RwZZc=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=oT+44L9jn360iyA+OlGIKiV3XH7UPPXNDJAxar5EjizGdKxxQO/ddYr5FjdhKgvpbjXcj+AZJcuytRY/IjkLJwdIAQMCpUxykRopyoyPNB9tbPHLWmmj9T8MxI+a1iGrqFiX75u2+S5z6sJgpNufr1i9O5HFym4y7ddlQx3vYCT0meRF5YSXOScdD5uIOQixDjDpkIy9wmfvQZ/CWdIyt/yIVbzznJQhs+YxiFBM+s/BgPIu64sWF8nmQ3cDv+4fnFB9+K4j2xDKbic/6mB7GIDPfp/7qua7InxKpNg35VfuiUYo7mPL9Qy1uL5ulEDR5sxhuC+oY2hg4dNx49dCkA==
X-YMail-OSG: iTAj53cVM1nqtZbkJ51BDdNBjX9_QmZSBoGEOGS4OzODNoOwjL6p85tgiBHaXHa GVYeiE6TtejUL.V._IkXDceNSFRPAAcVOWWM.E9fb4Nq4XyJ9nmUuYMzN1Nuek6oZNQr6Yj2b4QX U64XTmmvlgOMHMPrSqvouqAKHI6WbIhKst.ciIBDK5nrXzNEFLFjedH04PP9gy1bZh_WiBN_SoRq NHg_cLhVY7nmbjepz7Nanbsd9AuUlH2xqqSs_MYrkLRrIbi6AgkfSlobMz.4MD7C2BlMv5CFukFc 80UC4k3qpPKFbzv3eGxrwPMeLBa8n12x0SxM4rP6BLqzewp4mZKH7LZOzQ3oc0IzvAAsj2pZG9xg hujxEf17LdSOZN1umYyIAKUbsje4UC1H3OSVvToHqEIpeA5tC4vamoMBExyACRBElRbCBm1TlJXE 13KSIYBhY72OOE_sq338m_twnXVWHlF3h4T2lmhmyPjmKX.IwiWER9Y1z1HyhsqYEE15ziZbZCPJ ZMRjHqYAV8zI8Ffj66fxu2x_vwWwETElu2gJq4INtYxiIK3lLlffzu87p
Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.gq1.yahoo.com with HTTP; Tue, 14 Nov 2017 03:01:27 +0000
Date: Tue, 14 Nov 2017 03:01:22 +0000 (UTC)
From: Nalini J Elkins <nalini.elkins@insidethestack.com>
Reply-To: Nalini J Elkins <nalini.elkins@insidethestack.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <250219985.1486417.1510628482189@mail.yahoo.com>
In-Reply-To: <51005421-DA91-41C4-8E28-13F8833E1A9C@tik.ee.ethz.ch>
References: <51005421-DA91-41C4-8E28-13F8833E1A9C@tik.ee.ethz.ch>
Subject: Fw: [ippm] Adoption call for draft-amf-ippm-route to end 5 Dec 2017
MIME-Version: 1.0
Content-Type: multipart/mixed;  boundary="----=_Part_1486416_857460918.1510628482188"
X-Mailer: WebService/1.1.10940 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.89 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q9BLuZ7dPI2d0lwIICPe3jcoiLo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 03:01:31 -0000

------=_Part_1486416_857460918.1510628482188
Content-Type: multipart/alternative; 
	boundary="----=_Part_1486413_1057845679.1510628482137"

------=_Part_1486413_1057845679.1510628482137
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I support adoption of this draft.=C2=A0Thanks,

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

    =20
----- Forwarded Message -----
 From: Brian Trammell <trammell@tik.ee.ethz.ch>
 To: IETF IPPM WG <ippm@ietf.org>=20
 Sent: Sunday, November 12, 2017 11:02 PM
 Subject: [ippm] Adoption call for draft-amf-ippm-route to end 5 Dec 2017
  =20
Greetings, all,

Following clear consensus in the room at our meeting in Singapore this morn=
ing, this message begins a call for adoption for draft-amf-ippm-route-02 as=
 a working group draft to meet the following new milestone:

Jul 2019: Submit a Standards Track draft defining a metric for unidirection=
al route assessment to the IESG

Please send messages in support or non-support of this adoption to ietf@iet=
f.org by 5 December 2017.

Thanks, cheers,

Brian, as IPPM co-chair_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm


  =20
------=_Part_1486413_1057845679.1510628482137
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 id=3D"yui_3_16_0_ym19_1_1510627868969_10934"><span>I suppo=
rt adoption of this draft.</span></div><div></div><div id=3D"yui_3_16_0_ym1=
9_1_1510627868969_10963">&nbsp;</div><div class=3D"signature" id=3D"yui_3_1=
6_0_ym19_1_1510627868969_10967">Thanks,<br><br>Nalini Elkins<br>CEO and Fou=
nder<br>Inside Products, Inc.<br>www.insidethestack.com<br>(831) 659-8360</=
div><div class=3D"qtdSeparateBR"><br><br></div><div class=3D"yahoo_quoted" =
id=3D"yui_3_16_0_ym19_1_1510627868969_11102" style=3D"display: block;">  <d=
iv style=3D"font-family: Helvetica Neue, Helvetica, Arial, Lucida Grande, s=
ans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_1510627868969_11101"> =
<div style=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_15106=
27868969_11100"> <div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1510627868969_110=
99"> <font size=3D"2" face=3D"Arial" id=3D"yui_3_16_0_ym19_1_1510627868969_=
11105"> <br>----- Forwarded Message -----<br> <b><span style=3D"font-weight=
:bold;">From:</span></b> Brian Trammell &lt;trammell@tik.ee.ethz.ch&gt;<br>=
 <b><span style=3D"font-weight: bold;">To:</span></b> IETF IPPM WG &lt;ippm=
@ietf.org&gt; <br> <b><span style=3D"font-weight: bold;">Sent:</span></b> S=
unday, November 12, 2017 11:02 PM<br> <b><span style=3D"font-weight: bold;"=
>Subject:</span></b> [ippm] Adoption call for draft-amf-ippm-route to end 5=
 Dec 2017<br> </font> </div> <div class=3D"y_msg_container" id=3D"yui_3_16_=
0_ym19_1_1510627868969_11106"><br><div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_=
1510627868969_11107">Greetings, all,<br></div><div dir=3D"ltr"><br></div><d=
iv dir=3D"ltr">Following clear consensus in the room at our meeting in Sing=
apore this morning, this message begins a call for adoption for draft-amf-i=
ppm-route-02 as a working group draft to meet the following new milestone:<=
br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Jul 2019: Submit a Sta=
ndards Track draft defining a metric for unidirectional route assessment to=
 the IESG<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Please send =
messages in support or non-support of this adoption to <a ymailto=3D"mailto=
:ietf@ietf.org" href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> by 5 Decemb=
er 2017.<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Thanks, cheer=
s,<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Brian, as IPPM co-c=
hair</div>_______________________________________________<br>ippm mailing l=
ist<br><a ymailto=3D"mailto:ippm@ietf.org" href=3D"mailto:ippm@ietf.org">ip=
pm@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/ippm" t=
arget=3D"_blank">https://www.ietf.org/mailman/listinfo/ippm</a><br><br><br>=
</div> </div> </div>  </div></div></body></html>
------=_Part_1486413_1057845679.1510628482137--

------=_Part_1486416_857460918.1510628482188
Content-Type: application/pgp-signature
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="signature.asc"
Content-ID: <3b334271-53fe-e39d-08b4-939776be1c85@yahoo.com>

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KCmlRSXpCQUVCQ2dBZEZpRUVrQ1RTVHAyYklC
NmZCUkhJaWhLM3Z3dnFScU1GQWxvSlE0VUFDZ2tRaWhLM3Z3dnEKUnFOMUNCQUFnRVI0UlVyRzd1
aVpWcFJPRWxWTDNmeFNmSUwxbTZENTBsQlJ2SDRjcUZZL3VuMmEvY2J6ZXRJWgpTL0VOVjJaVXRG
UENzTEx6RDlVdVBkaXlnS2p3SlcwQW9JSkVaZnVBZXBpRUdkcmpZaTBPOXMxemFDZHJhRXdpClBs
b3IwV0FBSlJwZVNVbTRxcjh3QnFkK21jNnBBZEQrc1RESy8zTW1vR1lGWDljMHZIbUJaU0dhWjRr
Yy8rMEwKMGp3b2hMalZVVk9BVVNJMkxRTy82Sk5kL1FHb25uVHlGR2VsQ2JxRUxjZ2dybnY0VitZ
dEpyTStERVhreCtxSwp5VVJUa0dYVkN6SU5LZGVpWUdxRVpBb1o4bGRJQWR0VWNISVAwL3NRYXBF
cmNmcjhWUFRPWFphOVZrdVUvb3dDCll5SlFpS2pucXJ1Z0ltRnZQWGVZdmpBMzdTckZWUXhVbW53
T3V0Q0VadE5PdGJ2Ymh5OHZGaXFQSFA3QS9kNnoKSWJrL0gvSjBlZ1NYTzJXMW1hV1kzMmFxY3Fv
Nm10L3RibThOK1V1eHZ1Z3BGSFZsemZwUlR2NmdSbGFMejNIaApYUlFWMWVhSVcwam9rZEVRRWtY
ZEZ4SW5mbTJQQWhmTHFIVXlxZ2hQWC9wTFFGVTZrMUljME91ZUUzMFZ4L296ClpjbXBwV2ExYlRV
R3FEcDJkTUVtNEZSVFhqRUx3Tm04SXFsUDA1dUJiVUM4QjRRZENuVHd6TFAvSTFOeFBXemwKWkVh
MlVON2YwKzM4cmY1a0xwUWJQSk9EaHY1YVBhVWN6SEhReitJemxPbUxPbEZJYWdkT2NGM09ydGFU
ekZ5OApianV6c3lsMXVWU0lQVGZaRWxycDJsQ2RxZjNtNXB0WWsyTlc3bTlmTXlIR1pNOE5pQXM9
Cj10eXArCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQo=

------=_Part_1486416_857460918.1510628482188--


From nobody Mon Nov 13 19:36:41 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 0E1C11241F5 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, 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 aa1gkU-YKv_I for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:36:35 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A1BD1242EA for <ietf@ietf.org>; Mon, 13 Nov 2017 19:36:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3071; q=dns/txt; s=iport; t=1510630595; x=1511840195; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=lnhKdqvyOAj4Dop9+w0eV0jqu9XB9rj/RCzesIFakOE=; b=B0Xez6CaAgJZtTXparTDdG/718OvcS8V6TkZyeY9IEAbSsb677VYNkQN ve7ay+HAT42PwIPF7E+QO7glGvQEoaH5DMOeLXvEjrdOGjIXbzaKmIUg9 8/a6tw7DBj/OJGByvNe3A+e0DkVkcQBCrHnBphbv+GU8zLCI67bAU57X5 g=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CTAQByYwpa/5RdJa1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM1gVIng36ZToF9llCCEQcDhTsChGVAFwEBAQEBAQEBAWsohR8?= =?us-ascii?q?BBSNWEAsOCiMHAgJXBg0GAgEBih6rOoInixABAQEBAQEBAQEBAQEBAQEBARIPg?= =?us-ascii?q?zSBZSKDZ4MBiCyCYwWSeo8whEaCJI4aghWGCINgh0WWJIE5IAE2gXI0IQgdFYM?= =?us-ascii?q?tgxGBWzQ2iEkBAQE?=
X-IronPort-AV: E=Sophos;i="5.44,392,1505779200";  d="asc'?scan'208";a="320276917"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Nov 2017 03:36:34 +0000
Received: from [10.70.234.7] ([10.70.234.7]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id vAE3aWWD008803; Tue, 14 Nov 2017 03:36:33 GMT
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Mark Nottingham <mnot@mnot.net>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, IETF <ietf@ietf.org>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net> <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com> <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com>
Date: Tue, 14 Nov 2017 11:35:59 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7nwW8qgtNLMFpitT7WSFF7sVWqRlXPeoK"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/22Tncdx28LfqflTCCXGSgCasV0E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 03:36:37 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7nwW8qgtNLMFpitT7WSFF7sVWqRlXPeoK
Content-Type: multipart/mixed; boundary="gNfB2dR6dFLMfnagsBiEtunWKU5bfUncF";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, IETF <ietf@ietf.org>
Message-ID: <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of
 Pervasive Encryption on Operators) to Informational RFC
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com>
 <20171112115510.GA29392@laperouse.bortzmeyer.org>
 <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
 <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
 <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com>
 <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
 <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com>
 <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net>
In-Reply-To: <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net>

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



On 11/14/17 10:58 AM, Mark Nottingham wrote:
>
>> On 13 Nov 2017, at 8:47 pm, Eliot Lear <lear@cisco.com> wrote:
>>
>>
>>
>> On 11/13/17 4:08 PM, Mark Nottingham wrote:
>>> 1. Introduction - "Ideally, new methods could be developed to accompl=
ish the goals of current practices despite changes in the extent to which=
 cleartext will be available to network operators." It's not at all clear=
 that this would be ideal, since the goals of some of the documented prac=
tices are quite questionable, both technically and ethically.
>> Can you please explain what you mean by that last statement?  I ask
>> because the statement leads us to a dead end when it is not qualified,=

>> rather than a way forward to address what you might think "legitimate"=

>> problems to solve.=20
> I mean that the word "ideally" is not really appropriate here. This sen=
tence should be dropped, or modified to remove that implication.=20
>
>

What I am asking is this: what is technically or ethically quesitonable?

Thanks,

Eliot



--gNfB2dR6dFLMfnagsBiEtunWKU5bfUncF--

--7nwW8qgtNLMFpitT7WSFF7sVWqRlXPeoK
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

iQEcBAEBCAAGBQJaCmSfAAoJEIe2a0bZ0nozX9EIALadO1Fx3EOUX0/jn6uP5QyX
3ibQZG+WP7/Siqm/U52jPt+09AZmHnlc4BDjj0Kttr8kqn8ivGKXj68pFfGZhvXx
ZG6/cNKEdDd7j3rU7d+f9woxOXAynBn9wAyZn4XzhEGs8Zvgk0F5C2PtP9N63ccT
+GW7wMeaFrggFtu0y8aedFAvXGXzDKoS0eaCiCzBMizWJ5lyJN2Rrji6zlrXX6RK
R/xA5ZkdbF4fKNNGNktgm0JDZw5GBYKV8I560lw3pMdqQb9+FAYy7ZRvTzXGTbGc
Oyr84QURsMRzPQ9lrG5L7Q6gZFvH6G4Cb6/velhX6ZNFBqs9E4iPWYhOBSVo8Sw=
=C/RT
-----END PGP SIGNATURE-----

--7nwW8qgtNLMFpitT7WSFF7sVWqRlXPeoK--


From nobody Mon Nov 13 19:36:59 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 EF6B7128DF3 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=moGdFj/C; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nxD8wCxD
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwIuw0Df-Tls for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:36:55 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 653FE127342 for <ietf@ietf.org>; Mon, 13 Nov 2017 19:36:55 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id B983621175; Mon, 13 Nov 2017 22:36:54 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 13 Nov 2017 22:36:54 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=kWkNdm+RbFW6SOq5//v3B0N4TM+cG jgqyfEqkPLco58=; b=moGdFj/C1stI4FSiXAkdkMgBqBTytXwzSnwjuzMisN6wm ilcBKnKAJAXzrXHKNc62bVeqQ/areBpvZ2t9PV39VfA3Dr7Lnt9UuKiky/s4FcFx 9n6L+MF8WeyJ7/AWL7v0afyzi1DPbyI8xDBGorO+OcfcMb1KqMiVh5nR9/PMcgXt /q1Q+XH8msstHJCA7X+whlxeltJu8PywzFekt8e0buAKP+BTToU4Gpq0m5hXFah2 +/E9+Soez4wJ/jEiEy5hlWdPw32cZFUJwo9V2UOb6tDygcEIDnyKVTuLobq37nnB 6zDho8Ott/rOCKjxpX3a/0So/gWiSzexMnt8z8Q2Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=kWkNdm +RbFW6SOq5//v3B0N4TM+cGjgqyfEqkPLco58=; b=nxD8wCxD0czvq9pgYLGw60 tZ1Zo0yO4cBZAJH0QwzrInxbKg+jcpusMlUiAqj8boa7fnixD02YFRASuD7/xS6S wpvCF69Ifjdt7i0ZIAvLURPPRYrNTSOfiO5+Tiq2LnxcpJHGGxKxGyAy52UwBfWm waKPqqfIv9gHKwnF2E1LtF+HgDzJXQNuzIb6Aci0hzYzEUlImycGUCMyM6JViSBk MVaZ19tbni9TQvFq2A1J4PB0xW2BWMqzo9ZANBExolTp0VBpv5E9YCvVbcbYfi8R JFV0e8fHDugiqhVVe6o/Guw+bsrkvCrFZg3XhEl3ESTd9oKUCeABIdEEeUnf82UQ ==
X-ME-Sender: <xms:1mQKWg3zdQl5qFKqvy3S92MbikVg8VIFNH3wHM03VqHgiQxq3KVvsA>
Received: from dhcp-80a4.meeting.ietf.org (dhcp-80a4.meeting.ietf.org [31.133.128.164]) by mail.messagingengine.com (Postfix) with ESMTPA id 294E224A12; Mon, 13 Nov 2017 22:36:52 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAJc3aaOJz2C7kWzKOZa_SPoyi_VN76t7DzVv1KdnV4HvCPYaCw@mail.gmail.com>
Date: Tue, 14 Nov 2017 11:37:33 +0800
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F424E136-18BF-41A2-A061-F9837DBD4C7D@mnot.net>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net> <CAJc3aaOJz2C7kWzKOZa_SPoyi_VN76t7DzVv1KdnV4HvCPYaCw@mail.gmail.com>
To: Victor Kuarsingh <victor@jvknet.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hs4GYJYK0trX9_LevepE9a9oqgc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 03:36:58 -0000

On 13 Nov 2017, at 10:06 pm, Victor Kuarsingh <victor@jvknet.com> wrote:

> On Mon, Nov 13, 2017 at 3:08 AM, Mark Nottingham <mnot@mnot.net> =
wrote:
>> Since we're talking about the title, I had a different reaction to =
it; currently, it reads as if *all* operators are necessarily affected =
by pervasive encryption.
>>=20
>> In the discussions I've had, the great majority of operators have =
said they are not affected by pervasive encryption (YMMV, of course), so =
I wonder if a title like "Reported Effects of Pervasive Encryption on =
Operators" or "Effects of Pervasive Encryption Purportedly Encountered =
by Some Operators" would be more appropriate.
>=20
> I don't think we have enough data to put any quantitative value on
> this.  What we have is a list of considerations / issues based on
> input.  Suggesting "some" would be as erroneous as suggesting "many".
> The current titles seems to be neutral in this regard.

I disagree; "effect" implies it's complete and always encountered; it =
reads as "*The* effect".


> I don't have any specific issues with adding work "Reported" in title,
> but does that really add any intrinsic value to the reader? (assuming
> one reads the draft and does not stop at the title).

To be explicit -- part of my problem with this draft as written is that =
it's pretty obviously had significant edits to the Introduction to try =
to re-cast it and address the concerns raised, but the body of the text =
(as well as the title) have not been changed to align with that. As =
such, someone reading isolated parts of the RFC (yes, that happens) =
could be mislead about the IETF's position on these things.

The title goes a long way to setting the stage for how someone reads a =
document; it's what shows up in citations.



>> Even then, many of the areas discussed lack important context about =
whether or not there are other options to achieve the same goal, and how =
prevalent their use by operators is. For example, the sections on =
Content Compression and Content Encryption beg these questions.
>=20
> It's possible solutions deployed by operators may have other technical
> options, however we lack the full set of data to make claims that
> other options can be used, or if so, what obstacles need to be
> overcome to change deployments.  There would likely be both technical
> and business factors those entities need to address to change things.
>=20
> Even if there is agreement and a desire to change things, it often
> takes time to change production networks which means items listed are
> factors for consideration.

My point is that in some cases, the goals listed may be met by parties =
other than operators, and that's worth mentioning.


>> It might be useful to have a list of potential effects on network =
operators without that context, but some of the items still seem to be =
written in a way that assumes the intrinsic value and uniqueness of the =
technique being discussed (e.g., Performance Enhancing Proxies), which =
can be deeply misleading  (despite the attempt at positioning in the =
Introduction). If this were Wikipedia, I'd say there were several NPOV =
issues remaining here.
>=20
> Who do we think we are misleading?  The section seems to describe
> proxies used in mobile networks to deal with real performance issues
> related to that access network type.  As a former mobile network
> architect and operator, I don't see an issue with what is described.
> There are real latency issues to deal with there and this is one way
> some have dealt with them.  Even within a single mobile provider's
> network, there are often varying technical challenges to deal with
> from market to market.

The term "Performance-Enhancing Proxy" generally refers to a number of =
different techniques (as RFC3135 explains). Amongst people who run =
services, PEPs are widely known to cause problems with performance, =
rather than enhance it, because many operators deploy and forget them. =
Having an appliance that's optimising the 2017 Internet for conditions =
in 2005 isn't helping. Saying that the technique "measurably improves" =
it (the draft's words) isn't the whole story.


--
Mark Nottingham   https://www.mnot.net/



From nobody Mon Nov 13 19:41:54 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 5162B126C2F for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=m1WYJKQf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dZ5PkGjv
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAWUbCNUmqiH for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 19:41:51 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C470126DFE for <ietf@ietf.org>; Mon, 13 Nov 2017 19:41:51 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 8D56920C81; Mon, 13 Nov 2017 22:41:50 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Mon, 13 Nov 2017 22:41:50 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=wWUwn0Yfoci1uXEPK+bU3bT4HJ0eX G3xAa2mNCGCj4s=; b=m1WYJKQf3dcNvVALW2WIx9meTAv2u+2NJR4O6S485Xndt 3P8HQEiOtOe8DMWL7DekeggB+kEat11yTQjQqIVfRhHTsjwIARRODunT9AND2nlr rAkvsKkC50NN0gxU5IBNKULj6ZYHVJ57sfurbgkzLkj7uihs/VYnA1uoaFweTlLL ERbUrUnzX9U4TgaOiFN+wK5ruqxiV7+MuydL5jLdGCuo91OcSeXIp3O6FYMdxfrG gSK74+21Js1O/TFM9jIQX9B9OkrttdQhoDg8PTStrp3R/v6NDj0X+jQcmjoiJ292 GLjVzrm+3q3esOIMquc8vb2n9BMNA69fp3Z9whpfQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=wWUwn0 Yfoci1uXEPK+bU3bT4HJ0eXG3xAa2mNCGCj4s=; b=dZ5PkGjvS9sRF7e2pF3Hgf gZltg8CO51Qmcqy5BmpXsA2r5Ybti0Fiic9PYFdN7eZqLtBnnJrFya6zcJ9ykEvJ ygG1zjmbgp7o0Le2ETW8ZgjhV8Ur0TBT3ZTdh1keuRYeIDkXWagDgP6b1hAGzXQ9 iQ1GxdkZ0cMkt7f4gaHs2zRER2pYwkdd/OB9ObnvDjd4I6rufpL5+yoaXEjNK6E0 NDZDTGUhB7kTGK5vojhyVi4rDKd3jZbspnsjUbro81dsWu58Y1OGjvw++MnDRLI7 1/B4H5L5JL0i6DgkjUKqprFHEWhi2a+T5zmlefw/ueVz/gl2Thi2D5VLU5//9kLA ==
X-ME-Sender: <xms:_mUKWoT449OtX4SfJ4Z_lKgvn5PnxSGiBqsyywLognQOSueN6cAjDw>
Received: from dhcp-80a4.meeting.ietf.org (dhcp-80a4.meeting.ietf.org [31.133.128.164]) by mail.messagingengine.com (Postfix) with ESMTPA id 4969F240B2; Mon, 13 Nov 2017 22:41:49 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com>
Date: Tue, 14 Nov 2017 11:42:29 +0800
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7E619AE-9D45-41C3-BFA0-B8B0BE453918@mnot.net>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net> <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com> <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net> <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UUOaQPFdVJ0KQjivXtSnhk8s5xg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 03:41:53 -0000

> On 14 Nov 2017, at 11:35 am, Eliot Lear <lear@cisco.com> wrote:
>=20
>=20
>=20
> On 11/14/17 10:58 AM, Mark Nottingham wrote:
>>=20
>>> On 13 Nov 2017, at 8:47 pm, Eliot Lear <lear@cisco.com> wrote:
>>>=20
>>>=20
>>>=20
>>> On 11/13/17 4:08 PM, Mark Nottingham wrote:
>>>> 1. Introduction - "Ideally, new methods could be developed to =
accomplish the goals of current practices despite changes in the extent =
to which cleartext will be available to network operators." It's not at =
all clear that this would be ideal, since the goals of some of the =
documented practices are quite questionable, both technically and =
ethically.
>>> Can you please explain what you mean by that last statement?  I ask
>>> because the statement leads us to a dead end when it is not =
qualified,
>>> rather than a way forward to address what you might think =
"legitimate"
>>> problems to solve.=20
>> I mean that the word "ideally" is not really appropriate here. This =
sentence should be dropped, or modified to remove that implication.=20
>>=20
>>=20
>=20
> What I am asking is this: what is technically or ethically =
quesitonable?

- HTTP header insertion / "enrichment" (in many scenarios)
- Content filtering (to some people, in some situations)
- Performance-enhancing proxies (in some deployments, as they add to =
ossification)
- Customer access monitoring (to some people, in some situations)
- Content compression (depending on how it's interposed)


--
Mark Nottingham   https://www.mnot.net/



From nobody Mon Nov 13 20:00:20 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 AC31A1286B1 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 20:00:17 -0800 (PST)
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 1GKDKB88qG79 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 20:00:14 -0800 (PST)
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 73E501242EA for <ietf@ietf.org>; Mon, 13 Nov 2017 20:00:14 -0800 (PST)
Received: by mail-pg0-x229.google.com with SMTP id c123so6341791pga.11 for <ietf@ietf.org>; Mon, 13 Nov 2017 20:00:14 -0800 (PST)
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=PAAWn0hCqMJR5NA7YTH1QBxo0vR+QQyzJZt5up4VIlo=; b=IchhTnbAoEoW4BTPJelxpjBa2fuUFdtoGR1rRp6yyqo53MxH47NoXl9gYtMifA0Ela WqvzWAxw6e3kGLiZNbbRB3x6Is0xYIde8DvOmoEgrRlYHLgA2A2Hz2zsDFxW3RllU8yv PwgcSECeflcm0+l23BRkmc6qE7vCF6asAdyxyQlsxicRQex+QbzYOgJi21tbvbv90QWR B1lL2srywcCAoVWaj9ARiRhBdqCG7hhWIN86JYV7vFN7mZ4BXHoRYVc+z+5hzB6m3+At 0JhQIVwtBaow1+66P/B+7pm6W8lqkFAjqTlH6QrUWmWLRofn1p7qjIa0JZjyrnRjmYfl rD3A==
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=PAAWn0hCqMJR5NA7YTH1QBxo0vR+QQyzJZt5up4VIlo=; b=bXEfIORkD25aXufE4nyuKbC2bTg+5UKHzn0lamf88Uc0ybEpRvMM4Hs9nnJNfMduax 21qy1wmxxVZkd8G5NwSmsJcpuiXdTT1EzGPBMadcKhHMxZ7GYp8E2Bikoyg4MtpD6P1L FSvRCBm4aw0ElcOWyUJKgdmTQGSoumlUWghimUCKpsa8OxE4Q5UkrIr/BUzhJ7PCxehG H+mp4Rp1W/Led0187XNcwF+pQbwbsWMyAkcBM7x1RgtuIbB+hsqDneCyagkZyljq5Pmk blJ3ynf5E89od+JOqwvxdG7Dx4r0WIoLolur3n869wQRdsJTAmQefKn0Z6z7V8Apl/Wi dLrg==
X-Gm-Message-State: AJaThX5n9HlWnMVaOfbJSbdVbtT3IrDvKVxWFWNMByX4SM0Oho/LKH9w Rmg57D2vBAhQQrVf4r/JLMQlgzM4TzxXmjyqSpXASA==
X-Google-Smtp-Source: AGs4zMZxKrafVL2jfqQGEYSV1xTZyFUG7pcqxgOQR1conwvIp3m/u2hv5Ssy/3b8RtY0fHPThUjD0Gia8Ul5Gux8KTU=
X-Received: by 10.159.197.1 with SMTP id bj1mr11176942plb.219.1510632013570; Mon, 13 Nov 2017 20:00:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.155.9 with HTTP; Mon, 13 Nov 2017 19:59:32 -0800 (PST)
In-Reply-To: <20171112115510.GA29392@laperouse.bortzmeyer.org>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 13 Nov 2017 22:59:32 -0500
Message-ID: <CAHbuEH4qXVeGYEeTgbtnbc7jq6S0PGbrV0XfgJzUM03BqHZzsA@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: 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/PF91rr0sQiN6csNP4EuLf6AWfro>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 04:00:17 -0000

Dear Stephane,

Thank you for your review and comments.  Let's see if we can work
through your questions, discuss updates and perspectives to see where
we get.  I appreciate your engagement in advance.

Inline

On Sun, Nov 12, 2017 at 6:55 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wr=
ote:
> On Mon, Nov 06, 2017 at 06:06:50AM -0800,
>  The IESG <iesg-secretary@ietf.org> wrote
>  a message of 37 lines which said:
>
>> The IESG has received a request from an individual submitter to
>> consider the following document: - 'Effect of Pervasive Encryption
>> on Operators' <draft-mm-wg-effect-encrypt-13.txt> as Informational
>> RFC
>
> I'm quite concerned by this document. Basically, it seems to me it
> deviates a lot from a simple description of current practices, and
> goes into promoting them. The overall effect seems to me very
> dangerous. One can easily read this document as "encryption is a pain
> for the operators, we should not promote it too agressively".

We worked hard on the framing in the introduction, so I'd like to see
if your concerns are captured there in this discussion or if wording
tweaks to make sure the statements are read as explanations of what is
in use as opposed to endorsements as they are not.  This is meant as a
starting point for discussion to find balance between network
management and prevention of pervasive monitoring, which is called for
in RFC7258.  We as a community have to work through these discussions
to determine where the balance lies.  This type of conversation and
ones that would follow based on this and other work is helpful toward
that goal.

>
> My opinion is that its publication as it is would inflict real harm to
> the efforts of IETF to promote privacy (which implies, among other
> things, a lot of encryption).

I think wording tweaks may help, so let's see where we get as this is
an important conversation to have.  As one of the SecADs, I am
constantly reviewing drafts and identifying security and privacy
issues with new and evolving protocols.  Acknowledging what practices
are in place is very important to determine next steps and to work
toward a common goal of privacy.  Note that many of the techniques are
aimed at network management and not with the intent of exploiting end
user privacy. Operators are also concerned with end user privacy and
in many cases, the end point application is actually the biggest risk
to that user's privacy.  Many of the use cases described are working
towards use of a 5-tuple or 2-tuple or limited data that has been
exposed at the transport layer.  Yes, identifiers and flow information
can be be used to expose information on end users.

It is also clear that at least several of the described use cases
could be solved with improved logging and debugging at the
application.  This is a known gap that if we worked together to
address could help with a shift towards increased deployment of e2e
encryption.

>
> The document also completely ignores network neutrality, not to
> mention the end-to-end principle.
>

Perhaps a text change to highlight this better might help.  The E2E
principle is referenced with 3 RFCs in the second paragraph of the
Introduction.  When this was added, I had suggested that it might be a
stronger statement to separate out the e2e references into a separate
subsequent sentence since the documents don't quite fit with the
preceding references. The IESG (in their review) did not think that
was necessary, so we have the current text.  I think it might be
helpful to pull this out separately as you missed it's presence and
others will likely too.  It's also important to note, that like this
document, the three on the e2e are informational and thus do not
represent IETF consensus. So, they probably don't fit with the
sentence they were in anyway since they are BCPs or policy documents
(2804). RFC1958 is informational, but does offer guidance that is not
immutable, so I think it's fine to leave where it is, but could see
how that might be debatable.  E2E is a guiding principle, the existing
documents encourage it's use, document use cases, but explicitly do
not make recommendations.

Here's a proposal, edit suggestions are welcome, of course:

OLD:

   The document does not endorse the use
   of the practices described herein.  Nor does it aim to provide a
   comprehensive treatment of the effects of current practices, some of
   which have been considered controversial from a technical or business
   perspective or contradictory to previous IETF statements (e.g., [RFC
   1958], [RFC 1984], [RFC 2804], [RFC 2775], [RFC 3724], [RFC 7754]).

NEW:

   The document does not endorse the use
   of the practices described herein.  Nor does it aim to provide a
   comprehensive treatment of the effects of current practices, some of
   which have been considered controversial from a technical or business
   perspective or contradictory to previous IETF statements (e.g., [RFC
   1958], [RFC 1984], [RFC 2804]).
   The following informational documents consider the end to end (e2e)
architectural principle, a guiding principle for the development of
Internet protocols [RFC 2775], [RFC 3724], [RFC 7754]).


> More precisely:
>
>> This document discusses practices currently used by network
>> operators to manage, operate, and secure their networks
>
> Actually, it does not "discuss": it describes them, using only the
> arguments of the operators that use these practices, rarely
> questioning them.

Good catch, thanks. How about:
s/discuss/documents/

>
>> the impact of pervasive encryption
>
> Note that we are far from "pervasive encryption". For instance, the
> DNS traffic is almost entirely in clear (RFC 7858).

This discussion has continued in the larger thread, so I'll follow
along there to see if the end result is to change to a new term or if
this term has agreement.  If you have proposals for alternate terms,
please do add them to that discussion.  Thank you.

>
>> For example, the traffic patterns between server and browser are
>> dependent on browser supplier and version
>
> That's a good example of why HTTP sessions must be encrypted: the
> User-Agent: field is very revealing, among other infos sent by the
> browser, as exemplified by the Panopticlick
> <https://panopticlick.eff.org/>
>

Sure, that's not being argued.  If you think a text change would help
to make it clear that this is just being documented, please suggest
text.  The statement above reads as documentation of use to me, not an
argument in either direction, but if you read it in another way, a
clarification might be helpful.  We're happy to consider proposals and
discuss on list.

>> Network operators use packet captures and protocol-dissecting
>> analyzers when responding to customer problems,
>
> Not all network operators are so benevolent. I doubt that many 30 $ or
> 25 =E2=82=AC / month ISP use tcpdump when the customer has a
> problem :-) Seriously, this sentence is very dangerous because of:

I think the rest of your thought was omitted, but I believe this was
discussed further in the thread.  I will wait to see if text
adjustments are needed.  As far as I recall of the list discussion,
"some" being added didn't seem to help as that is already implied with
the existing sentence. Other text modification suggestions are welcome
to help resolve a concern, if one exists still.

>
>> The ability to identify the problem application's traffic is
>> important and deep packet inspection (DPI) is often used for this
>> purpose
>
> This really looks like an attempt to "sell" DPI by explaining that it
> may benefit the users. Actually, I would like to see my ISP going into
> such efforts to help me but I doubt it will be the case.

I believe I responded to this point later in the thread, so I won't
respond here too.  I suggest this gets snipped in a response.

>
> Note that no ISP document the practices it actually use against user
> flows. This is sufficient proof that they are not done in the interest
> of the users.

Hmm, or this is because it's part of their secret sauce to provide
enhanced performance over a competitor to meet or exceed SLAs for
which contract services are based on and that allows them to continue
to sell bandwidth and operate networks for which applications rely
upon.

>
>> For example, by investigating packet loss (from TCP sequence and
>> acknowledgement numbers), round-trip-time (from TCP timestamp
>> options or application-layer transactions, e.g., DNS or HTTP
>> response time), TCP receive-window size, packet corruption,
>> inefficient fragmentation, or application-layer problems, the
>> operator can narrow the problem
>
> Almost all of these investigations can be performed even if TLS or SSH
> is used. Again, it really seems an effort to make DPI acceptable.

The draft acks that some of the practices rely on the use of a 2-tuple
or 5-tuple.  You're arguing that a 5-tuple is enough for this
particular type of monitoring that is documented. Is the expanded text
around this statement contradictory to that point?  If so, do you have
a text suggestion to clarify?  I think the description of what
metadata is used in the quoted text makes your point clear already,
but if you are reading it otherwise, others may too.

>
>> Because of this, application server operators using increased
>> encryption should expect to be called upon more frequently to assist
>> with debugging and troubleshooting
>
> Hard to read this as something else than a threat "do not use
> encryption or your business will suffer".

Hmm, what text would you suggest?  This points to a problem that we
have currently in that applications are not providing adequate logging
and debugging information.  To be successful in expanding the use of
e2e, it is necessary to address this gap.  Is there a way to rephrase
this text, but still convey this point so you don;t feel like it's a
threat?  It's meant to be a possible way forward.

>
>> A common, early trigger for DDoS mitigation includes observing
>> uncharacteristic traffic volumes or sources; congestion; or
>> degradation of a given network or service.  One approach to mitigate
>> such an attack involves distinguishing attacker traffic from
>> legitimate user traffic.
>
> Are there really dDoS attacks using encryption? Hard data welcome.

This text was provided by 3 contributors (in ack section) with hands
on experience on DDoS attacks.  I can understand why you might
question why encryption would be used as it would seem unnecessary,
but it could be targeting services that are encrypted to deplete
resources.  the important point here is the ack that a fingerprint of
encrypted traffic is adequate to identifying DDoS traffic to assist
with mitigation.  If you are arguing the e2e principle, I'm not sure
why you'd be concerned with this statement where a type of monitoring
has been able to proceed in an encrypted world and serves as a good
example.

>
>> Mobile networks especially rely on content/application based
>> prioritization of Over-the-Top (OTT) services
>
> This is a very important point: if encryption really prevents
> prioritization of some services over the others, then it means we need
> more encryption, not less. If encryption can help preserve network
> neutrality, this is a good reason to use it even more.

This is a technical summary, nit a policy one.  So if we were to dive
into net neutrality, we'd have to understand how they were
prioritizing services.  Is this based on paid SLAs with large
customers, which would mean that it doesn't enter the net neutrality
space.  Is it to prefer their services over competitors?  For this
case, it is a problem.  If it is to prefer services that do not have a
tolerance for latency, like weighting phone calls over email, is this
just normal traffic management to ensure things like emergency calls
are given a preference?

I'd have to go back and look at the surrounding text.  If you have a
text proposal here, please let us know.  We're interested to document
uses of monitoring, not to make policy statements or recommendations
as this is intended to be an informational document.  If there are
references to other statements that already provide such guidance, I
think it would be better to include a link rather than trying to work
toward consensus on any such statement in this draft.  This one
clearly states the practices documented are not endorsed and I think
that should address your concern.  Having said that, if you do have a
wording suggestion, please provide it.

>
>> Due to the characteristics of the mobile link, performance-enhancing
>> TCP proxies may perform local retransmission at the mobile edge.  In
>> TCP, duplicated ACKs are detected and potentially concealed when the
>> proxy retransmits a segment
>
> Again, TLS or SSH do not prevent this sort of hacks.

Similar to the above statement, is there text around this that states
more than the 5-tuple is needed?  I would think the documentation of
what is used makes that clear already.  A 2-tuple would prevent this
type of monitoring, which is also a possibility and good to document
so application developers are aware of this usage and might discuss it
further with operators when considering a move to encrypted protection
that moves this from having the 5-tuple exposed to only having the
2-tuple exposed.  the prevalence and importance could be discussed at
that time, it's just important to have an understanding of use for the
purpose of this document.

>
>> In addition to caching, various applications exist to provide data
>> compression in order to conserve the life of the user's mobile data
>> plan and optimize delivery over the mobile link
>
> I know that some mobile operators (see, in french,
> <https://www.hteumeuleu.fr/la-compression-dimages-par-les-operateurs/>)
> apply a LOSSY compression without the user consent or even
> knowledge. Again, if end-to-end encryption prevents this, this is a
> very good reason to deploy encryption.

Interesting.  Could you propose text written neutrally that documents
this application of compression?  I don't speak French.  This document
does not endorse the documented practices.  We had some statements
sprinkled throughout the document, but through reviews, it was
deciding framing text in the introduction was sufficient.

>
>> These regulations include Lawful Intercept, adherence to Codes of
>> Practice on content filtering, and application of court order
>> filters.  Such regulations assume network access to provide content
>> filtering and accounting, as discussed below.
>
> It seems to me that RFC 1984 already replies to this reasoning.

The full text of that section is as follows:

   Mobile Networks and many ISPs operate under the regulations of their
   licensing government authority.  These regulations include Lawful
   Intercept, adherence to Codes of Practice on content filtering, and
   application of court order filters.  Such regulations assume network
   access to provide content filtering and accounting, as discussed
   below.

RFC1984 is already mentioned in the introduction in the same paragraph
that explicitly states the documented practices are not endorsed.  I
see why you might be concerned and we've tried to avoid repeating
these points throughout the document, but I'll propose text to see if
it is agreed upon (or a tweaked version):

NEW:

   Mobile Networks and many ISPs operate under the regulations of their
   licensing government authority.  These regulations include Lawful
   Intercept, adherence to Codes of Practice on content filtering, and
   application of court order filters.  Such regulations assume network
   access to provide content filtering and accounting, as discussed
   below.  As previously stated, the intent of this document is to document
   existing practices, the development of IETF protocols follows the
   guiding principles of [RFC1984] and [RFC2804].

It feels unnecessary and duplicative to me, but understanding if
others find this or a variant of this text useful would be helpful.

>
>> This type of granular filtering could occur at the endpoint.
>> However, the lack of ability to efficiently manage endpoints as a
>> service reduces providers' ability to offer parental control.
>
> I would be specially unhappy if IETF were to publish a RFC with such a
> sentence without follow-up comments. Filtering MUST be done at the
> endpoint, otherwise it is not a service, it is censorship.

I think that point is subjective and debatable.  While important, it
would be a rat hole.  In the interest of being productive, do you have
a text suggestion that keeps us out of that discussion and just
documents use of monitoring without endorsement?  Considering the
introductory text that already exists?  TIA.

>
> If we assume that the subscriber wants parental control, then we must
> conclude that he/she will have no problem sending the traffic to a
> filtering proxy. No need to break encryption for that.

Hmm, I think we are reading the text differently as I read it as
describing this use usage that you seem to be okay with (this document
merely documents it, does not endorse it).  This still breaks e2e, but
in a way that is permitted by the end user who decides to trust this
service.  We were trying not to split hairs on methods used to view
traffic - it is already sent in the clear, some type of interception
is performed (enterprise use cases where the server is already managed
by that entity), or proxy services that serve as an endpoint for the
encrypted session.  Do you have text tweaks to suggest if you look at
this again and find a place where it is not written as intended?  I
don't seen an issue with the quoted text, but that could just be me.
TIA.

>
>> Some mobile carriers use HTTP header insertion (see section 3.2.1 of
>> [RFC7230]) to provide information about their customers to third
>> parties or to their own internal systems [Enrich].
>
> Again, this technique, which has very serious privacy consequences
> (see the mentioned reference [Enrich] with for example Vodafone which
> added the phone number and the IMEI in HTTP headers) MUST NOT be done
> and, if encryption stops it, great.

Omitting this text would be ignoring the practice.  Isn't it better to
document all uses of monitoring to understand motivations and to open
discussions between protocol developers and operators?  This may
result in wide-scale use of encryption to protect this data, but it
could also highlight to developers the need to communicate with end
users and find alternate methods to offer information to users.

I think MNOT may have commented on this same section, so perhaps he
has suggestions.  If not, text suggestions are welcome.

>
> Editorial issues:
>
>> Currently, some mobile network service providers redirect the
>> customer using HTTP redirect to a page that explains to those
>> customers the reason for the blockage and the steps to proceed
>
> A mention of RFC 6108 would be cool here.

That's a good addition.  I only skimmed, but it states a requirement
on port 80, so this relies on a clear text stream, is that right?
Do you have text to propose for this addition?

>
>> monitor incoming mail to remove SPAM
>
> Why is spam uppercased?

Thanks for catching that.

>



--=20

Best regards,
Kathleen


From nobody Mon Nov 13 22:17: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 A53B6129405 for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 22:17:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, 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 HXbTJjl0q03T for <ietf@ietfa.amsl.com>; Mon, 13 Nov 2017 22:17:50 -0800 (PST)
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 6F96C124D6C for <ietf@ietf.org>; Mon, 13 Nov 2017 22:17:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3226; q=dns/txt; s=iport; t=1510640270; x=1511849870; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=UuM/wSIc1Bn6xryY6NlDFPCLygnqp5qp9ZnTyBT/rtk=; b=XOjlIna3p07r5mCdTuVv2qQkgMOWgHoICTNTT3YnQF4M0q34uGntQJv2 Gs6trItpG3/9W+mJ5xuFBLFD1o6bqadU77jGbw5sh9ZtUA1hXudBfU9iQ 5wGpGFcUCyRbww2ZXXxt01aj2aqB1/j70Bx/18j0I3ZUxmWu4sVpJ1Axm 0=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CWAQDHiQpa/5hdJa1bGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM2ZG6EJZlOgX2WUIIRBwOFOwKEZkAXAQEBAQEBAQEBayiFHwE?= =?us-ascii?q?FI08HEAsOCiMHAgJXBg0IAQGKHqs4gieLEQEBAQEBAQEBAQEBAQEBAQEBEg+DN?= =?us-ascii?q?IFlIoNngwGILIJjBZJ8jzGER4IkjhqLfYdFliiBOSEDM0KBMDQhCB0Vgy6DEIF?= =?us-ascii?q?bNIkQAQEB?=
X-IronPort-AV: E=Sophos;i="5.44,393,1505779200";  d="asc'?scan'208";a="323915765"
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; 14 Nov 2017 06:17:49 +0000
Received: from [10.70.233.66] ([10.70.233.66]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id vAE6Hlat021871; Tue, 14 Nov 2017 06:17:48 GMT
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Mark Nottingham <mnot@mnot.net>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, IETF <ietf@ietf.org>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net> <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com> <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net> <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com> <F7E619AE-9D45-41C3-BFA0-B8B0BE453918@mnot.net>
From: Eliot Lear <lear@cisco.com>
Message-ID: <3461ac75-2cb8-5a17-b6ea-64c90f10ea7e@cisco.com>
Date: Tue, 14 Nov 2017 14:17:15 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <F7E619AE-9D45-41C3-BFA0-B8B0BE453918@mnot.net>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="onUTnTIDnhRDTG2ABvm5TUFdpQ7JhKgr9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wnWiM9EsUP08EhhoZ4gTj3WHYrI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 06:17:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--onUTnTIDnhRDTG2ABvm5TUFdpQ7JhKgr9
Content-Type: multipart/mixed; boundary="e95MDfA4LjHaON2o5JUv9neaGpHI8rFlR";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, IETF <ietf@ietf.org>
Message-ID: <3461ac75-2cb8-5a17-b6ea-64c90f10ea7e@cisco.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of
 Pervasive Encryption on Operators) to Informational RFC
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com>
 <20171112115510.GA29392@laperouse.bortzmeyer.org>
 <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca>
 <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com>
 <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com>
 <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net>
 <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com>
 <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net>
 <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com>
 <F7E619AE-9D45-41C3-BFA0-B8B0BE453918@mnot.net>
In-Reply-To: <F7E619AE-9D45-41C3-BFA0-B8B0BE453918@mnot.net>

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

Hi,


On 11/14/17 11:42 AM, Mark Nottingham wrote:
>
> - HTTP header insertion / "enrichment" (in many scenarios)
> - Content filtering (to some people, in some situations)
> - Performance-enhancing proxies (in some deployments, as they add to os=
sification)
> - Customer access monitoring (to some people, in some situations)
> - Content compression (depending on how it's interposed)
>

Perhaps the devil is in the detail in each of these cases, but in
sorting through them there are probably authorized ways to accomplish
certain goals, while others might need to be left behind.=C2=A0 It seems =
like
in most of these cases it comes down to a matter of authorization, and
the relationship between parties.=C2=A0 I don't think that's for this
document to delve too deeply into, but as one decides which problems to
work on later, at that point, teasing out those aspects may be
worthwhile.=C2=A0 Starting with a statement of what the issues they are
facing are is pretty much factual.=C2=A0=C2=A0 Whether we choose to addre=
ss those
issues over time is separate.

Eliot



--e95MDfA4LjHaON2o5JUv9neaGpHI8rFlR--

--onUTnTIDnhRDTG2ABvm5TUFdpQ7JhKgr9
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

iQEcBAEBCAAGBQJaCoprAAoJEIe2a0bZ0nozEYkIAKKYORby3qBWLk8IXVZHKdtZ
H+Yiq1uz98JRdJ205T3y8HAzdP36QeHSX47IhAH22KLdM0TWJjMfry8Zu6qWLiNY
8N6X2/PafeVjLKJzhoWRTXyiE7zELIqc5XZkXSwMyzd5kp3c0RmQMQy+qD18HqTP
DEDfHsGnwPizkWCrG3OTf5lr5khHOgpha47NPIJFv2zY/oadBPRjEOjQgC8yw1Kl
RXOytznYnQ05VG5mwv0aCvCbxd7b4m2cACYljzZgQfUij8PCfa/+cy9tXgT5zN0k
LgxvvL+3qqhcp/P9u8aZwhdc/j9U0ggwsFNKJ4woAz3P1j6b/Rm0/zMCe7E4+EA=
=xs9J
-----END PGP SIGNATURE-----

--onUTnTIDnhRDTG2ABvm5TUFdpQ7JhKgr9--


From nobody Tue Nov 14 00:34:05 2017
Return-Path: <tjc@ecs.soton.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 31769127077 for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 00:34:04 -0800 (PST)
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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WhAyaQ6giArj for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 00:34:01 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D870124D6C for <ietf@ietf.org>; Tue, 14 Nov 2017 00:34:00 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id vAE8XwnR016932; Tue, 14 Nov 2017 08:33:58 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk vAE8XwnR016932
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1510648438; bh=ewZhiXbcCpEMMdG+jB5UazLvrz4=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=sIDKPE7M9aXOH4g222UzTuHEXpRQoYpF9sHph9JtM53iZ6aYqZvNeIgc/ejLI/ipt fTe+o4t9K0kh8ZjH6vbNO79qXBJ8t6ZxK8iR/CVQlyMxQwSo9NTFBIfsXUrWna9Rqy EGCtuBC/zV/f2PS89+zwrS3U3OxL5IChC3dywLdI=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id yAD8Xv0776002732fS ret-id none; Tue, 14 Nov 2017 08:33:58 +0000
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:e5b3:72ef:b0f5:10e2] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id vAE8XpdO008129 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Nov 2017 08:33:51 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: IETF Website Status Update (meeting page)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <C1D60040-615E-42B2-9B8B-6C766083923A@isoc.org>
Date: Tue, 14 Nov 2017 08:33:50 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|187ee73b610fa88e018581a66d2757beyAD8Xv03tjc|ecs.soton.ac.uk|5569E985-A6FA-46F2-A306-03475856F36E@ecs.soton.ac.uk>
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com> <7930fd9b-3c06-7b5a-2a28-5198604af5de@gmail.com> <2FA836D7-81CF-4F4E-866B-5845C13AA4A1@ecs.soton.ac.uk> <EMEW3|4dee98c7626b21fb8f54f27492154f4fyACCwJ03tjc|ecs.soton.ac.uk|2FA836D7-81CF-4F4E-866B-5845C13AA4A1@ecs.soton.ac.uk> <C1D60040-615E-42B2-9B8B-6C766083923A@isoc.org> <5569E985-A6FA-46F2-A306-03475856F36E@ecs.soton.ac.uk>
To: Greg Wood <wood@isoc.org>, IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3445.4.7)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ssss
X-smtpf-Report: sid=yAD8Xv077600273200; tid=yAD8Xv0776002732fS; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: vAE8XwnR016932
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pD6AOh0QUwfVonIftUB6Rd10drg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 08:34:04 -0000

Hi,

> On 13 Nov 2017, at 21:41, Greg Wood <wood@isoc.org> wrote:
>=20
> Hi Tim,
>=20
>> On Nov 13, 2017, at 8:58 PM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>>=20
>>> On 10 Nov 2017, at 23:01, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>>=20
>>> On 01/11/2017 10:36, Russ Housley wrote:
>>>> I want to share an update on progress on the IETF website revamp =
project. In particular I=E2=80=99d like to highlight what has been done =
to respond to feedback from the IETF community received around IETF 99.
>>>>=20
>>>> A. Provide a landing page dedicated to current IETF participants
>>>>=20
>>>> A draft is currently posted at https://beta.ietf.org/links/
>>>>=20
>>>> That page includes links to:
>>>> - items on the left-side at www.ietf.org (or a subset thereof)
>>>> - information about the next IETF meeting=20
>>>> - links to functions at datatracker.ietf.org=20
>>>>=20
>>>> The goal is to make this page:
>>>> - viewable in a single screen on a desktop/laptop display
>>>=20
>>> In that, it fails, compared to https://www.ietf.org/content.html :
>>> a) at least 5cm vertical space is wasted with pointless blurb.
>>> b) because of the lack of columns and empty space, it is much
>>> harder to spot individual items.
>>>=20
>>> On the other hand, it's usable on a smartphone, which the old
>>> page hardly is.
>>>=20
>>> So there's the basic question: do we want to make the site
>>> harder to use on a laptop or desktop so that it's easier to use
>>> on a smartphone? That goes for pretty much every page on the beta
>>> site, I think, although it seems to be a rather noticeable issue
>>> for this particular page.
>>=20
>> Do we have an example meeting page in the new =E2=80=9Cbeta=E2=80=9D =
format?
>=20
> I believe the best example is:
>=20
> https://beta.ietf.org/how/meetings/past/99/

This appears to be a significant drop in usability compared to=20

https://www.ietf.org/meeting/99/index.html

Not least having to click to see the details under each heading.

The beauty of the current meeting page is that everything is easy to see =
and easily reached in one click.

> The IETF 100 meeting hasn=E2=80=99t yet been fully synced, but it is =
available at:
>=20
> https://beta.ietf.org/how/meetings/100/

The same applies here, sadly.

Tim

>=20
> -Greg
>=20
>=20
>>=20
>> Tim
>>=20
>>>=20
>>> Regards
>>>  Brian
>>>=20
>>>> - reachable via a short, memorable URL
>>>>=20
>>>> The current content includes changes implemented based on =
suggestions received via email after IETF 99. Of course, this page will =
be updated further based on input from the community.
>>>>=20
>>>> B. Ensure WCAG 2.0 compliance
>>>>=20
>>>> Since IETF 99, we have worked with the website developer to improve =
compliance. This is a requirement of the Statement of Work =
(https://iaoc.ietf.org/documents/IETF-Website-SOW-20140604-Final.pdf). =
We believe that has been accomplished. However, ensuring and improving =
accessibility must be part of ongoing editorial practices, so it will =
continue to be an area of focus for the website.
>>>>=20
>>>> C. Conduct review with other key audiences, especially potential =
participants and non-participants
>>>>=20
>>>> Additional interviews with members of the key audiences have been =
conducted to gather input. In general, response to the beta.ietf.org =
site was positive.  IETF newcomers say that the new site makes it easier =
to understand what the IETF is all about. Some specific suggestions have =
been incorporated into the project, and they are included at =
https://github.com/ietf/www.ietf.org/issues =20
>>>>=20
>>>> D. Improve data use and load times
>>>>=20
>>>> Since IETF 99, the beta.ietf.org site was placed behind the =
Cloudflare CDN. This has significantly improved load times. Of note, in =
interviews (see item C above), new or non-IETF participants located in =
Latin America and Africa did not report load time as a significant =
issue. However, as the new site moves to production, the editorial =
process will continue to fine tune how images and other elements are =
handled to further improve performance. =20
>>>>=20
>>>> Next steps:
>>>>=20
>>>> We are continuing to fine tune content and are aiming to move to =
production after IETF 100. One significant task remaining is to ensure =
continuity for important URLs, as specified in the Statement of Work. We =
expect to tackle that after IETF 100.
>>>>=20
>>>> We welcome input and suggestions. We held "office hours" at IETF 98 =
and IETF 99, and we will hold "office hours=E2=80=9D at IETF 100.  If =
you will be in Singapore, please take this opportunity to share feedback =
in person. Details will be posted on a sign around the IETF meeting =
registration desk. And, of course, questions or issues can always be =
raised at https://github.com/ietf/www.ietf.org/issues =20
>>>>=20
>>>> Sincerely,
>>>> Russ Housley
>>>> IETF Website Revamp Project Manager
>=20


From nobody Tue Nov 14 01:40:32 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 6E533124205 for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 01:40:31 -0800 (PST)
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 nuKMur1wsZnQ for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 01:40:29 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::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 252A1124B09 for <ietf@ietf.org>; Tue, 14 Nov 2017 01:40:29 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id b6so13769345pff.10 for <ietf@ietf.org>; Tue, 14 Nov 2017 01:40:29 -0800 (PST)
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-language:content-transfer-encoding; bh=f+RtyUJc7uBcIMHGc56CsBGz4cPgr9J5sHDrlk0wcDI=; b=KWuUCqdsmiy4MSE/sfN2pGSbZNJzJzD5V8DuHLpyUXg4aJh4h0BCJSbQUFYyyKIsDX 3ShOw14lq7aymu0XKu3KoC7uYGkeXa+9FrIOPuIi0Y5dewT5wRcY2gnybdqNS0cWk634 wk1gyoApSyb/fhuoj4Pn///9jCSPSx6/VUyIkP+O0umEizjXUVun43zWPrXbKJWZWSrm qyWxRlB8fFjXJ39ardKnvwvGgeLBmzbnwf8seHD5ILixG0x4IeU6v9LO+5eO5r7nkpIv 9YZx/KLMLS0lLDxqgkI5dpnppQL25N8kWZPaL7YqPmN3Ky03FpO3xG5ofaP1LZEtPyiz Nrvg==
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-language:content-transfer-encoding; bh=f+RtyUJc7uBcIMHGc56CsBGz4cPgr9J5sHDrlk0wcDI=; b=EWNREbNwCqiccxdsxHLXk/UXh6F3z6pgI9W+EFG0KGl1BB5PMQ0r6eliJJEE1+No1a sHdzu8rFpP4cfba+flAzLf2084tMUbYCHeDwSrnB8dkT0xnblcmQ7Wn6pK4qTUHmM4x0 QcAocjA0zMFYr0qQ1lv1NfKBntqvysHcyTvn7rYomLjYx7RTVtJjRsM/FVeZG5iT92Fs kttmmpxXRckbXtZzpBHqG3GmUh6cBXPZHDJfyDxFv3UulR83BjhURoZj/2I/ep7Bu5UF rY+PlF0es5pyx9jKOdHIWGSFxz8KOkWRnMWMnpz+8eMidrgw4wjU4oZv3cBQU8jxLE0F cotg==
X-Gm-Message-State: AJaThX59ngtKbONzceLQYJbRcYis0NpfNfQ668Iz3Lur13h5OIB+6M5L cRc1F126wkNy2z5Z30Fpa1LSig==
X-Google-Smtp-Source: AGs4zMaXQn+OCdgW4khPlWpPsQC8YOoCv/MecPQJYoY3sWKBJxnDF4pGcddF2TQ0LgmkwPp4BhDFdw==
X-Received: by 10.99.191.10 with SMTP id v10mr11171861pgf.291.1510652428164; Tue, 14 Nov 2017 01:40:28 -0800 (PST)
Received: from [172.16.132.82] ([101.100.166.3]) by smtp.gmail.com with ESMTPSA id n10sm39125917pfk.174.2017.11.14.01.40.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Nov 2017 01:40:27 -0800 (PST)
Subject: Re: IETF Website Status Update (meeting page)
To: Tim Chown <tjc@ecs.soton.ac.uk>, Greg Wood <wood@isoc.org>, IETF <ietf@ietf.org>
References: <C4C26BCB-1A37-4CA6-99A2-BE4581C4C645@vigilsec.com> <3C9DA6A0-82E7-4FAD-8113-13079E2EC903@vigilsec.com> <7930fd9b-3c06-7b5a-2a28-5198604af5de@gmail.com> <2FA836D7-81CF-4F4E-866B-5845C13AA4A1@ecs.soton.ac.uk> <EMEW3|4dee98c7626b21fb8f54f27492154f4fyACCwJ03tjc|ecs.soton.ac.uk|2FA836D7-81CF-4F4E-866B-5845C13AA4A1@ecs.soton.ac.uk> <C1D60040-615E-42B2-9B8B-6C766083923A@isoc.org> <5569E985-A6FA-46F2-A306-03475856F36E@ecs.soton.ac.uk> <EMEW3|187ee73b610fa88e018581a66d2757beyAD8Xv03tjc|ecs.soton.ac.uk|5569E985-A6FA-46F2-A306-03475856F36E@ecs.soton.ac.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <88b958d4-31ca-4ab6-d9f8-7f877ad20ecc@gmail.com>
Date: Tue, 14 Nov 2017 22:40:25 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <EMEW3|187ee73b610fa88e018581a66d2757beyAD8Xv03tjc|ecs.soton.ac.uk|5569E985-A6FA-46F2-A306-03475856F36E@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e-IZQ98gi0Z8iWrA1AbxCjVKuPE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 09:40:31 -0000

On 14/11/2017 21:33, Tim Chown wrote:
=2E..
>>> Do we have an example meeting page in the new =E2=80=9Cbeta=E2=80=9D =
format?
>>
>> I believe the best example is:
>>
>> https://beta.ietf.org/how/meetings/past/99/
>=20
> This appears to be a significant drop in usability compared to=20
>=20
> https://www.ietf.org/meeting/99/index.html
>=20
> Not least having to click to see the details under each heading.

Plus wasted vertical space in the top and bottom banners, larger
font than is useful for some text, and general signs of having
been designed to meet some aesthetic criteria rather than
just laying out the material in the simplest practical way.

And why is there that annoying bouncy thing at the right hand
side for "sharing" the link with social media?  I can't imagine
ever wanting to do that, and I would really want an option to
get rid of this, for ever, on all IETF pages.

The tourist photo of Prague is sadly lacking, too. That is a
nice touch of vanity in the old format.

> The beauty of the current meeting page is that everything is easy to se=
e and easily reached in one click.
>=20
>> The IETF 100 meeting hasn=E2=80=99t yet been fully synced, but it is a=
vailable at:
>>
>> https://beta.ietf.org/how/meetings/100/
>=20
> The same applies here, sadly.

Yes.
   Brian


From nobody Tue Nov 14 10:14:25 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A04A0127342 for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 10:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=opendkim.org header.b=KE8jIhI1; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=XP6AbhpL
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6CnBVXB8Ssa for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 10:14:18 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0DAC127005 for <ietf@ietf.org>; Tue, 14 Nov 2017 10:14:17 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([197.227.80.130]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vAEIDxFw015572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Nov 2017 10:14:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510683249; x=1510769649; bh=U79SRwvrbb9glKI5VWXnBxmp7JoIcJo8NFvRxO+eAgw=; h=Date:To:From:Subject:In-Reply-To:References; b=KE8jIhI1UJ7V1vBr5XLfcsA4fdIK1OvDV69QpjzDgwg62Wbde7qxuPmwLmGuJ+3S0 3JWpoHS1OptMDZNKjTt+6yBdqhe++NXYusist4RDEeI59sZz0Q8q+PEVSfzWoX5juu uozJwDSXDOX2fb1SDr6VjqVGi4rQh0Adc91eigJk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510683249; x=1510769649; i=@elandsys.com; bh=U79SRwvrbb9glKI5VWXnBxmp7JoIcJo8NFvRxO+eAgw=; h=Date:To:From:Subject:In-Reply-To:References; b=XP6AbhpL7hsdfucoIarjzY/K5TDzT2Bu2aIE2DxGyEu2ssVWckJZ2vBc2LoN594Nz RRaltXkUJivgejwXtUxHsXfSdgHk+I9iC1R0PbDPXV0T6Rlet8AwbpfjmEZiXzy7Q6 RZ/rnt6DMESR4gFCGcTC4VO+xX9dQvm5v9Dk0IoY=
Message-Id: <6.2.5.6.2.20171113214536.106f0a00@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 14 Nov 2017 10:12:45 -0800
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
In-Reply-To: <CAHbuEH5a8Z=cOyksddxotg+XnAiGP0ZwG8J6fVFt3iBJqkgyGw@mail.g mail.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <6.2.5.6.2.20171112122108.10693078@elandnews.com> <CAHbuEH5a8Z=cOyksddxotg+XnAiGP0ZwG8J6fVFt3iBJqkgyGw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/leJFgm1TItNtg2WhwXVYbE6nM8o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Nov 2017 18:14:23 -0000

Hi Kathleen,
At 09:54 PM 12-11-2017, Kathleen Moriarty wrote:
>The authors are concerned with user privacy and obstacles to deploying
>encryption.  If the obstacles are not documented and discussed,
>adoption of encryption could suffer.

Thanks for that comment.

>I'd be hesitant to add text that says it doesn't mean it's a good idea
>as that would feed into the assumptions being made in this thread that
>this draft is trying to prevent the deployment of encryption, when it
>is just the opposite.  Unless you mean that there should be a
>statement that authenticated encryption is preferred?

Sorry for not being clear.  The draft states that "NULL 
Authentication with IPsec" has been implemented and deployed.  Given 
that it is a practice, is it a good idea?  That was my point.  The 
document is length as it is.  I don't think that adding more text 
would make it better.

Stepping back, I'd say that the authors should decide what the 
document is about.  Is it about documenting what is in use by 
operators?  Is it a discussion of the practices?  Is it about telling 
the reader what the IETF recommends?

> > In Section 2:
> >
> >   "This and other increases in the use of encryption had the immediate
> >    effect of helping protect the privacy of users' data, but created a
> >    problem for some network management functions."
> >
> > Is this about privacy or is it about a security loophole?
>
>That could depend on the content of data exposed.  Are you suggesting
>a text change?

There was a news article in the Washington Post about such an 
issue.  From what I recall, it was considered as a security issue.  I 
suggest looking at this from a security perspective.

>If you break this sentence apart, the "import" part is the ability to
>identify problems in application traffic.  Many applications do a poor
>job of logging, so DPI is sometimes used.  A solution would be to
>improve logging and debugging in applications, which is suggested in
>the draft as an answer to many of the documented effects.  I'm not
>sure I follow your second question or what text led you to the
>question?  I read this sentence as saying it is one way it is done
>today, because it is not working to do this directly with debug
>information from the application.  I read this as documenting what is
>done and it leads me to think that applications need to improve their
>debugging and logging capabilities.

The text which led me to the question is the second paragraph in 
Section 2.1.2.  The DPI specification (Y.2770) references RFC 3871; 
it's related to logging capabilities (please see the paragraph quoted 
above).  DPI is about inspecting the traffic (including content) 
passing through the network.  The primary function of the DPI device 
is not troubleshooting.  Nowadays, the function is supposed to be DLP.

Why does an encrypted stream prevent the the network from being 
excluded as "the problem"?  If I understood the arguments in that 
section, the IETF might as well recommend "cleartext" to make "the 
internet work better".

> > In Section 3.2.2:
> >
> >   "STARTTLS ought have zero effect on anti-SPAM efforts for SMTP traffic."
> >
> > I doubt that STARTTLS cause any significant problem as the receiver has the
> > ability to inspect emails.
>
>So you agree with this statement?  Or are you asking a question?  If
>you could clarify, I would appreciate it.

I don't understand why the document is discussing about 
spam.  Anyway, STARTTLS does not have any effect on spam 
filtering.  The sentence, as written, sounds like: in theory, 
STARTTLS has zero effect ...

The last paragraph in Section 3.2.2 gets into "user-to-user 
encryption" and provides a reference to a vendor.  What does that 
have to do with the heading for that section?

>You may want to take another read of RFC7258.  This is a early step in
>one of the stated goals of that document - to find a balance between
>protections and the ability to perform network management by
>documenting the impacts to serve as a start to that conversation.

I read RFC 7258 and the draft once again.

Regards,
S. Moonesamy 


From nobody Tue Nov 14 20:00:15 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 DB8F11270FC for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 20:00:14 -0800 (PST)
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, 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 6GVpfGU3sg4Q for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 20:00:13 -0800 (PST)
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 7A0A0126CBF for <ietf@ietf.org>; Tue, 14 Nov 2017 20:00:13 -0800 (PST)
Received: from dhcp-8100.meeting.ietf.org (dhcp-8100.meeting.ietf.org [31.133.129.0]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id vAF408O2028787 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 14 Nov 2017 22:00:10 -0600 (CST) (envelope-from adam@nostrum.com)
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Eliot Lear <lear@cisco.com>, Mark Nottingham <mnot@mnot.net>
Cc: IETF <ietf@ietf.org>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net> <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com> <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net> <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com> <F7E619AE-9D45-41C3-BFA0-B8B0BE453918@mnot.net> <3461ac75-2cb8-5a17-b6ea-64c90f10ea7e@cisco.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <8659283f-e71c-c863-1d49-b0f3ee4c4162@nostrum.com>
Date: Wed, 15 Nov 2017 12:00:07 +0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <3461ac75-2cb8-5a17-b6ea-64c90f10ea7e@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p1LqIaAfCF2hx4FqgidhN8FH5fA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Nov 2017 04:00:15 -0000

On 11/14/17 14:17, Eliot Lear wrote:
> Hi,
>
>
> On 11/14/17 11:42 AM, Mark Nottingham wrote:
>> - HTTP header insertion / "enrichment" (in many scenarios)
>> - Content filtering (to some people, in some situations)
>> - Performance-enhancing proxies (in some deployments, as they add to ossification)
>> - Customer access monitoring (to some people, in some situations)
>> - Content compression (depending on how it's interposed)
>>
> Perhaps the devil is in the detail in each of these cases, but in
> sorting through them there are probably authorized ways to accomplish
> certain goals, while others might need to be left behind.  It seems like
> in most of these cases it comes down to a matter of authorization, and
> the relationship between parties.  I don't think that's for this
> document to delve too deeply into, but as one decides which problems to
> work on later, at that point, teasing out those aspects may be
> worthwhile.  Starting with a statement of what the issues they are
> facing are is pretty much factual.   Whether we choose to address those
> issues over time is separate.

And the goalposts go shooting off into the distance.

Mark is right. The questionability of some of these practices in some of 
the ways they have been deployed argues against the use of the word 
"ideally".

/a


From nobody Tue Nov 14 21:06:36 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 9BFA9127873 for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 21:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GAyao8s2HT89 for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 21:06:34 -0800 (PST)
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 73A141242EA for <ietf@ietf.org>; Tue, 14 Nov 2017 21:06:34 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3ycC5f5m1tz38P; Wed, 15 Nov 2017 06:06:30 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1510722390; bh=flTOKH2XyAubqE6dnLbq7dTOnNWvU4lVMfzQeSfrmDE=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=MaC4ZvtxP/dLDdjYfg5W9Qu2gdw73ZiUi1prIxbY1SiFLzc18FZUbsJaZyr6K/W6N Qur4QMBkP30H5b766H4kytH+3VyQxE2yHJhp10PcDfNUKfNCPumRhFLICl88plD9zf 0G3qwvV7WZlmd0Z/LIXGzJarK764ldPMk1tiUh1k=
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 FUZNXiHA-pNE; Wed, 15 Nov 2017 06:06:28 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 15 Nov 2017 06:06:27 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 0592B62D29; Wed, 15 Nov 2017 00:06:26 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 0592B62D29
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id E184340D35AF; Wed, 15 Nov 2017 00:06:26 -0500 (EST)
Date: Wed, 15 Nov 2017 00:06:26 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: S Moonesamy <sm+ietf@elandsys.com>
cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
In-Reply-To: <6.2.5.6.2.20171113214536.106f0a00@elandnews.com>
Message-ID: <alpine.LRH.2.21.1711142359390.30054@bofh.nohats.ca>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <6.2.5.6.2.20171112122108.10693078@elandnews.com> <CAHbuEH5a8Z=cOyksddxotg+XnAiGP0ZwG8J6fVFt3iBJqkgyGw@mail.gmail.com> <6.2.5.6.2.20171113214536.106f0a00@elandnews.com>
User-Agent: Alpine 2.21 (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/nK9SasAPOtmfFAg20sbPAn-Sjc8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Nov 2017 05:06:36 -0000

On Tue, 14 Nov 2017, S Moonesamy wrote:

> Sorry for not being clear.  The draft states that "NULL Authentication with 
> IPsec" has been implemented and deployed.  Given that it is a practice, is it 
> a good idea?

The deployments I'm aware of with mesh encryption using IPsec did try
to keep some kind of network based monitoring/filtering in place, but
in the end concluded enterprise wide mesh encryption is more important,
and the rules of the network monitoring/firewalls can be pushed to the
endnodes using the usual sync methods (puppet, ansible, new gold image
container, etc).

I dont think the IETF should try to answer whether it is a good idea or
not. There was a need for this, and we enabled the protocol to perform
this optional function.

Paul


From nobody Tue Nov 14 22:16:17 2017
Return-Path: <warren@kumari.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 7B9C31243F6 for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 22:16:15 -0800 (PST)
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=kumari-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 KfbkDS6MV3qo for <ietf@ietfa.amsl.com>; Tue, 14 Nov 2017 22:16:14 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 2686812954B for <ietf@ietf.org>; Tue, 14 Nov 2017 22:15:26 -0800 (PST)
Received: by mail-wm0-x231.google.com with SMTP id r68so651058wmr.1 for <ietf@ietf.org>; Tue, 14 Nov 2017 22:15:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=x4K1DQrRBKORpN43G6Vqy3v4NkuUox6+u0i8TUxCfwI=; b=DUunfoWsnnMQXV2acogginokR4iGhzf8zSUBYwEAXTOlWwdW9hFGO2jBtYemeECYnX drpP3vRqMpTmiLYHKIyU2/7UEw40Neo9kiOdwQqj2GcVX2BtaJpQf5bPMnd/ysFH3VKT 0qMYiXgS84UzQPt5r0W25T1rq/LwAWicZjUOTuuwEbC28z6D9XM0t4VMlYsuu4DTf5pT 7n4zY03KoHZaAEbeUx4FDAz0qOhcZJjupLgLiEi4rjtsFeH/x9VInMmgdcSDLFfzS9Za 5GwVnpD5GWvTSooiSL+chfqBuGyRBAWNpkrk61fRauAXa6iC91pgc2YrnS+vSA0/iyxV qApw==
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=x4K1DQrRBKORpN43G6Vqy3v4NkuUox6+u0i8TUxCfwI=; b=aoCr3kpYefL+PQ30nEpkixKmH2hEeI5skGsTRBlN7Ivwd194ApMrTVUNPBt980dLHA ZD6VEA4kD9rHhGUeEDI1lOwVMBq6f2359Rg/UBjhZnS9k+tJuhiMOGXOvF334t9r2/2z aCzfNz/zsH3fjzhGdg4OJ0ltk9Ln/zPOgHYsiT8be7tZBHh8EqXJE1BtZxF2yFoiaIU/ W7Mf51b3JwIqnNffUmAyQCeTVV6y4vbR909rPbfvmqNZklfNCReD+uhc6qo1XjARbF82 r9AfHYwXKE4vPJRrZtOJ7NvWm8AZAwuEY0IJpC/ZAfKV7kr74fi8fA8yGtaSbid6ou3d xGJw==
X-Gm-Message-State: AJaThX4LQ5rID73zcrfljt4609xqmcdV/286Ve0xHkT48kFoNgWoq8o7 9sxTREGKoKfjGvhUJ3m9nj5SHRNmrISJLTCm3+uTN8AH
X-Google-Smtp-Source: AGs4zMbtr7Q+GXx0eqazvVJMvhAygkRyvtYuj+ckK6c+jkykcsi+FoAhjQKWDeBnkBAJR8ok5X7lAD8TBmqr6chWj3A=
X-Received: by 10.28.191.80 with SMTP id p77mr11792427wmf.85.1510726524467; Tue, 14 Nov 2017 22:15:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.160.149 with HTTP; Tue, 14 Nov 2017 22:14:43 -0800 (PST)
In-Reply-To: <alpine.LRH.2.21.1711142359390.30054@bofh.nohats.ca>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <6.2.5.6.2.20171112122108.10693078@elandnews.com> <CAHbuEH5a8Z=cOyksddxotg+XnAiGP0ZwG8J6fVFt3iBJqkgyGw@mail.gmail.com> <6.2.5.6.2.20171113214536.106f0a00@elandnews.com> <alpine.LRH.2.21.1711142359390.30054@bofh.nohats.ca>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 15 Nov 2017 14:14:43 +0800
Message-ID: <CAHw9_iJVaiK7N_ZsAMFGXdj42YWWtOJ_mWjnDfHddpTp8qNbPA@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Paul Wouters <paul@nohats.ca>
Cc: S Moonesamy <sm+ietf@elandsys.com>, IETF Discuss <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Vge16EmW3hrwgTu7YVU67KC4BBA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Nov 2017 06:16:15 -0000

On Wed, Nov 15, 2017 at 1:06 PM, Paul Wouters <paul@nohats.ca> wrote:
> On Tue, 14 Nov 2017, S Moonesamy wrote:
>
>> Sorry for not being clear.  The draft states that "NULL Authentication
>> with IPsec" has been implemented and deployed.  Given that it is a practice,
>> is it a good idea?
>
>
> The deployments I'm aware of with mesh encryption using IPsec did try
> to keep some kind of network based monitoring/filtering in place, but
> in the end concluded enterprise wide mesh encryption is more important,
> and the rules of the network monitoring/firewalls can be pushed to the
> endnodes using the usual sync methods (puppet, ansible, new gold image
> container, etc).
>
> I dont think the IETF should try to answer whether it is a good idea or
> not. There was a need for this, and we enabled the protocol to perform
> this optional function.
>

... and the document isn't trying to make those sorts of judgement
calls. I've heard some mumblings that people thought that this
document was somehow recommending against encryption or that
encryption is "bad" in some way. This really isn't the intent; rather
documenting places where encryption impacts operators network
management practices informs the operator so they can design new ways
to manage the network, and also informs protocol designers so they are
aware that removing certain information may negatively impact how well
the network works (and so negatively impact their performance).

An example of this is that some enterprises prioritize VoIP / video
conference traffic (esp from remote offices) to provide better user
experience. Having this data encrypted (e.g from a browser) is (note:
personal judgement call here!) a good thing, but it does mean that the
enterprise cannot use their existing methods to prioritize the
traffic, and having them know this is useful - otherwise a: the
quality gets sucky, and b: the enterprise may try block this.
So, documenting the effects of encryption is NOT to discourage it, but
rather try make it better deployed -- the authors are not
anti-encryption, quite the opposite.  One of the authors is a Security
AD, the original sponsoring AD was another Security AD (Stephen).

Much of the document came from contributions - earlier versions of the
document hadn't fully scrubbed the tone to remove judgements - please
note that it has had significant rewrites to scrub this; places where
there may be implications that encryption is bad are not intentional
and should be point out so they can be addressed (e.g the "ideally")

W

> Paul
>



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Wed Nov 15 00:23:21 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 43E2D128B44 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 00:23:20 -0800 (PST)
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 3hj8Tzh1JqAy for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 00:23:18 -0800 (PST)
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 53BA0126C25 for <ietf@ietf.org>; Wed, 15 Nov 2017 00:23:18 -0800 (PST)
Received: by mail-pf0-x22d.google.com with SMTP id n89so16495160pfk.11 for <ietf@ietf.org>; Wed, 15 Nov 2017 00:23:18 -0800 (PST)
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=OIm6ehoMplURpOnCooIC+owR1zC4MJOqDE9BvPq0ImQ=; b=G5TWDCzUmYU5v1kGxn2o2xqnwCoNyhA5e+lhRlzvZr/veXSB0/lpzNv3vG2ea4PUam 71YiCfwF7QGR66xJXe9sEzrTos0BjVdaQ2ayyt+T6h3f+ARjVmCaaFriSl5sxKzI/skH oE80QN6EQwwL1yjJFfK2diyGe8qByisdoUhkYxREBpE6RHsalGAWlTraE5Nn6337VbQQ jRZ02fa4+7sBtxXtjS11HWHRFnHYb+Na52/dBcUlKlYFpDICClUhlb1qc7yojL7UgE42 kAwjV2YBOd/vxLKVCfMh7REZImQs120DqLBU4xz9JfX+tb/inSMzBSPOcqV6bb6THli2 NXMw==
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=OIm6ehoMplURpOnCooIC+owR1zC4MJOqDE9BvPq0ImQ=; b=SLeWd+/LarBDCkRyXjioXpw7XFlCscRp9oO6NtJcnHDUqHVCNUSx1B9PfR2cTox9En 7bVONjANx76X9WYcdf155l3m4Ph6HN2O3yavDhL87CTncYO42y4qWuGGbqwwCfqoFrPG C0OmchBUPCwD1I+NizL0VLviawWo2WjyuZDM/cACmByZfIBpGS9VC5yp2HFw/2Q6e+aM Bqcu/3lEG/YeczN0mjGL08ndGW0c307KDy3D92/C7H4do8daGt6F3L2toadqP0QEYQPk uQSxwXcxfEp8EPpK7FVSZTQ+S3O7UmckuK7S/pZBu/st+b8OxPOvuCx22mkDU45Zi3X0 lvwA==
X-Gm-Message-State: AJaThX4FmPyKi3nGpaDpeooxMNLMXiZVn/KNeyTScziEHdEcY8CmofH6 yoB8azGysCkliVkZ32JIxOMrQKe2FpTraR67aTE9pA==
X-Google-Smtp-Source: AGs4zMZE4ITR7ZcoHaiNhWIOkl5oRGyftRUdKCfFwHImDoZWs1i7VBepeWMVEJnhgroaCyen0zwgyye7lGrnJF18Kuc=
X-Received: by 10.99.169.25 with SMTP id u25mr14523554pge.77.1510734197838; Wed, 15 Nov 2017 00:23:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.155.9 with HTTP; Wed, 15 Nov 2017 00:22:37 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20171113214536.106f0a00@elandnews.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <6.2.5.6.2.20171112122108.10693078@elandnews.com> <CAHbuEH5a8Z=cOyksddxotg+XnAiGP0ZwG8J6fVFt3iBJqkgyGw@mail.gmail.com> <6.2.5.6.2.20171113214536.106f0a00@elandnews.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 15 Nov 2017 03:22:37 -0500
Message-ID: <CAHbuEH7Xttvk1h40=qWpbH+Kn1v-mS99A954qQZkTnDyk50KWg@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sR43ITPK72_kQ5XLVRz6dpbXP_E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Nov 2017 08:23:20 -0000

Hi SM,

Thanks for your additional comments, inline.

On Tue, Nov 14, 2017 at 1:12 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> Hi Kathleen,
> At 09:54 PM 12-11-2017, Kathleen Moriarty wrote:
>>
>> The authors are concerned with user privacy and obstacles to deploying
>> encryption.  If the obstacles are not documented and discussed,
>> adoption of encryption could suffer.
>
>
> Thanks for that comment.
>
>> I'd be hesitant to add text that says it doesn't mean it's a good idea
>> as that would feed into the assumptions being made in this thread that
>> this draft is trying to prevent the deployment of encryption, when it
>> is just the opposite.  Unless you mean that there should be a
>> statement that authenticated encryption is preferred?
>
>
> Sorry for not being clear.  The draft states that "NULL Authentication with
> IPsec" has been implemented and deployed.  Given that it is a practice, is
> it a good idea?  That was my point.  The document is length as it is.  I
> don't think that adding more text would make it better.

We have tried not to comment on what's a good idea or not in the
document, so I'd rather not start. If you have read something that
sounds like we have, please let us know and we'll make sure to edit to
just document the practice.  Text is always welcome with such
suggestions.

>
> Stepping back, I'd say that the authors should decide what the document is
> about.  Is it about documenting what is in use by operators?  Is it a
> discussion of the practices?  Is it about telling the reader what the IETF
> recommends?

Just the first and that's stated in the document introduction and abstract.

>
>> > In Section 2:
>> >
>> >   "This and other increases in the use of encryption had the immediate
>> >    effect of helping protect the privacy of users' data, but created a
>> >    problem for some network management functions."
>> >
>> > Is this about privacy or is it about a security loophole?
>>
>> That could depend on the content of data exposed.  Are you suggesting
>> a text change?
>
>
> There was a news article in the Washington Post about such an issue.  From
> what I recall, it was considered as a security issue.  I suggest looking at
> this from a security perspective.

Fair point, deploying encryption assists with confidentiality and
integrity and isn't necessarily in regard to privacy.  Thanks for
highlighting this text.


NEW:
 "This and other increases in the use of encryption had the immediate
  effect of providing confidentiality and intergity for protected
data, but created a
  problem for some network management functions."


>
>> If you break this sentence apart, the "import" part is the ability to
>> identify problems in application traffic.  Many applications do a poor
>> job of logging, so DPI is sometimes used.  A solution would be to
>> improve logging and debugging in applications, which is suggested in
>> the draft as an answer to many of the documented effects.  I'm not
>> sure I follow your second question or what text led you to the
>> question?  I read this sentence as saying it is one way it is done
>> today, because it is not working to do this directly with debug
>> information from the application.  I read this as documenting what is
>> done and it leads me to think that applications need to improve their
>> debugging and logging capabilities.
>
>
> The text which led me to the question is the second paragraph in Section
> 2.1.2.  The DPI specification (Y.2770) references RFC 3871; it's related to
> logging capabilities (please see the paragraph quoted above).  DPI is about
> inspecting the traffic (including content) passing through the network.  The
> primary function of the DPI device is not troubleshooting.  Nowadays, the
> function is supposed to be DLP.
>
> Why does an encrypted stream prevent the the network from being excluded as
> "the problem"?  If I understood the arguments in that section, the IETF
> might as well recommend "cleartext" to make "the internet work better".

We'll have to look at this a bit closer, thank you for pointing out
the section that led you to that conclusion.  We'll work on it.

>
>> > In Section 3.2.2:
>> >
>> >   "STARTTLS ought have zero effect on anti-SPAM efforts for SMTP
>> > traffic."
>> >
>> > I doubt that STARTTLS cause any significant problem as the receiver has
>> > the
>> > ability to inspect emails.
>>
>> So you agree with this statement?  Or are you asking a question?  If
>> you could clarify, I would appreciate it.
>
>
> I don't understand why the document is discussing about spam.  Anyway,
> STARTTLS does not have any effect on spam filtering.  The sentence, as
> written, sounds like: in theory, STARTTLS has zero effect ...

This was requested by the sponsoring AD at the time in his review.  It
seemed like a reasonable addition to state that there is no impact in
this instance, so we added it.

>
> The last paragraph in Section 3.2.2 gets into "user-to-user encryption" and
> provides a reference to a vendor.  What does that have to do with the
> heading for that section?

Are you referring to DarkMail as a vendor?  It seems they are a
technical alliance and had presented at SAAG a few years back.
user-to-user encryption will impact any mail service and could make
them irrelevant depending on the parts of the message encrypted.
There have been discussions about encrypting the header of mail in
addition to the body.  This was in earlier versions of the draft, but
I think got cut.  Do you think additional text is needed here?

>
>> You may want to take another read of RFC7258.  This is a early step in
>> one of the stated goals of that document - to find a balance between
>> protections and the ability to perform network management by
>> documenting the impacts to serve as a start to that conversation.
>
>
> I read RFC 7258 and the draft once again.

Thanks for taking the time to do that and for your review and comments.

>
> Regards,
> S. Moonesamy



-- 

Best regards,
Kathleen


From nobody Wed Nov 15 00:28:52 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 BAC7E1279EB for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 00:28:49 -0800 (PST)
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 SXssFvMNO6eM for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 00:28:48 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::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 8401A126C25 for <ietf@ietf.org>; Wed, 15 Nov 2017 00:28:48 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id b6so16259564pff.10 for <ietf@ietf.org>; Wed, 15 Nov 2017 00:28:48 -0800 (PST)
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=BOTNc6/oGiLiqK1r3WRTk4QZCB1kMKxuGKDuOWX+Ef8=; b=WBOQgdJx5FiehlK5nKEDUlz9xpcPLfxfM+mkegIEi5Vq/e5cCRon2hrGv3QXI20PfE 85T9RDZJX5/kz0TRjcL+GjWuEeXpGCfxWEsvLaAd6jdbXkRN8o6Nk76Ipi0Ukn2ZTbfs 5kjIihYME3qSv5qma0hKv2yt1t0ZaWVCEbwPitIsEd8DlYIJMpypZgipBXVQz3/mgUsE 9ttDYS194+Ad91IppYsg2TqXhyQlhk1J8i3vZ0YGlN76oN2ihAx4Q7QlS6zeeXExtG0U b8ugh/OGRO39mrM4cx+MTvb5GB2Q2BkVHJK5nz/n1NWWGIi2wQ7hBv9POax3ImdBnqnK uMhQ==
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=BOTNc6/oGiLiqK1r3WRTk4QZCB1kMKxuGKDuOWX+Ef8=; b=bo7pN+8KntSId45Nai38BtApyFsVdCWoJ2RIIAJWzEEhDbinS+Khd7Zc82YQSZYhTA ah8gIjqm2RGXcqQti+tzKLLk/TzO+HQ8sXf1CjDlWxJ5S3mC39siSdQU+SZigUvgKvUa Xlu/kdk9ztjGhD5LjEor+Ed7fvf+KyNlpT11zFakJRn2nnAlApaeyNWT0Ic+yM1y1p47 DTP69xvJF69X1MTxy2d+3x2nI4AAfl6pC7Dp+9WJMJK01xlpslMuDK24qUgXn60gK/H+ ImQjBK31q4sMbjV5OX8Wy96/abEnCdaMe9mirD60g04NE/E/HjiiMJiOfmsfxaeg+Wk2 RinQ==
X-Gm-Message-State: AJaThX44nxaDZ3MXaDrfbImke3mMaqSiFtSa2qzvd8GvNBLhCtuU6yrT Hoh6KKA8qRtwUcUsuFFydlEZdVXdZ3YTwbZAjRE=
X-Google-Smtp-Source: AGs4zMbuiSjW6xIhPOaT9mcqvzjrfG7/d2G1S818TPrIv3/f/M0V3abVvC1bvy+8rgj0TA3XwB2vwoYOKHdRw/y4dPk=
X-Received: by 10.99.109.202 with SMTP id i193mr14820732pgc.443.1510734528082;  Wed, 15 Nov 2017 00:28:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.155.9 with HTTP; Wed, 15 Nov 2017 00:28:07 -0800 (PST)
In-Reply-To: <8659283f-e71c-c863-1d49-b0f3ee4c4162@nostrum.com>
References: <150997721010.25597.12135786015002954174.idtracker@ietfa.amsl.com> <20171112115510.GA29392@laperouse.bortzmeyer.org> <8973D093-36B4-4FFD-BB83-89F42A272902@nohats.ca> <CAHbuEH5AkX3mCLASJ98JXQg=JdssiqFu30rm5Dm5agSq4Pvt9g@mail.gmail.com> <CAJc3aaMgTYgnNhckK31AuU1FVCSFL93y5NwZVo3EodeRQuVR9A@mail.gmail.com> <B57253F4-A418-4EF1-9B25-B45FC469317D@mnot.net> <a57ac866-d646-b58c-94d4-22f220cb0e61@cisco.com> <C66C8829-F1A1-49A7-961F-25453795D34C@mnot.net> <59bf7131-050c-e219-3f45-33bf0b90a5e3@cisco.com> <F7E619AE-9D45-41C3-BFA0-B8B0BE453918@mnot.net> <3461ac75-2cb8-5a17-b6ea-64c90f10ea7e@cisco.com> <8659283f-e71c-c863-1d49-b0f3ee4c4162@nostrum.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 15 Nov 2017 03:28:07 -0500
Message-ID: <CAHbuEH54cSd9GTcPoUhy9YQ01RjMsiZ-1nv+enk_1MMYjBjipg@mail.gmail.com>
Subject: Re: Last Call: <draft-mm-wg-effect-encrypt-13.txt> (Effect of Pervasive Encryption on Operators) to Informational RFC
To: Adam Roach <adam@nostrum.com>
Cc: Eliot Lear <lear@cisco.com>, Mark Nottingham <mnot@mnot.net>, IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9YXVeNOEg47D0_NtWRE8_JgyRPw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Nov 2017 08:28:50 -0000

On Tue, Nov 14, 2017 at 11:00 PM, Adam Roach <adam@nostrum.com> wrote:
> On 11/14/17 14:17, Eliot Lear wrote:
>>
>> Hi,
>>
>>
>> On 11/14/17 11:42 AM, Mark Nottingham wrote:
>>>
>>> - HTTP header insertion / "enrichment" (in many scenarios)
>>> - Content filtering (to some people, in some situations)
>>> - Performance-enhancing proxies (in some deployments, as they add to
>>> ossification)
>>> - Customer access monitoring (to some people, in some situations)
>>> - Content compression (depending on how it's interposed)
>>>
>> Perhaps the devil is in the detail in each of these cases, but in
>> sorting through them there are probably authorized ways to accomplish
>> certain goals, while others might need to be left behind.  It seems like
>> in most of these cases it comes down to a matter of authorization, and
>> the relationship between parties.  I don't think that's for this
>> document to delve too deeply into, but as one decides which problems to
>> work on later, at that point, teasing out those aspects may be
>> worthwhile.  Starting with a statement of what the issues they are
>> facing are is pretty much factual.   Whether we choose to address those
>> issues over time is separate.
>
>
> And the goalposts go shooting off into the distance.
>
> Mark is right. The questionability of some of these practices in some of the
> ways they have been deployed argues against the use of the word "ideally".

Thanks Mark for spotting this, we'll address it in the update.


>
> /a
>



-- 

Best regards,
Kathleen


From nobody Wed Nov 15 08:43:08 2017
Return-Path: <hsantos@isdg.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 7A958126579 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 08:43:06 -0800 (PST)
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, 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=isdg.net header.b=Pf65sRNg; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=L0pnC+Ly
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8RD_O9kC0ai for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 08:43:04 -0800 (PST)
Received: from ntbbs.winserver.com (secure.winserver.com [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id D6360124C27 for <ietf@ietf.org>; Wed, 15 Nov 2017 08:43:03 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1344; t=1510764174; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=0mzeH8TqU5pkDFqEO2s+witt/p0=; b=Pf65sRNgaCQC2QbBCHlxiPXObTH0Ni44D/2KO3G90zlHTbTrfxQdAiITXmXXgN AU6I96fcbDpT/3DyIDsuOyDwcmVMeji8+7z1bjfzho00jGOVKuUUQsOxCTIQzwC2 MtAi4n8Jr1Vuu6X3Ivu3Go1PbUdVzM2//AOY+RTN8DfUA=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6) for ietf@ietf.org; Wed, 15 Nov 2017 11:42:54 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 632912172.1.3392; Wed, 15 Nov 2017 11:42:53 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1344; t=1510764038; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=nGg+TPI BG9XQOqn21/BRsSxka52nwQE8yZ/TrU1lFSM=; b=L0pnC+Lyjpcr8JYpcWh17Y2 TbOjpvCDuon5M77NdAOtpWfJkvvS+lAOyLcFcT/1X4+NUD8ScQSPGqMLZ1X3CxkE oheYyer05fvJvTz0lOZhQuD8fNf9p3xqS0gO6k80RNuH1ekez6Aq13cKXHiFIDvL 6wUnW/KxUZl37kXteF5E=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.6) for ietf@ietf.org; Wed, 15 Nov 2017 11:40:38 -0500
Received: from [192.168.1.68] ([99.121.5.8]) by beta.winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 632878985.9.216332; Wed, 15 Nov 2017 11:40:37 -0500
Message-ID: <5A0C6E8F.4060105@isdg.net>
Date: Wed, 15 Nov 2017 11:42:55 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: Benjamin Kaduk <kaduk@mit.edu>
CC: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org>
In-Reply-To: <20171113015919.GG26425@kduck.kaduk.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ga_5DDRuIQ35HmWz4BYfRa2x7fA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Nov 2017 16:43:06 -0000

On 11/12/2017 8:59 PM, Benjamin Kaduk wrote:
> On Sun, Nov 12, 2017 at 08:36:59PM -0500, Hector Santos wrote:
>> Hi, I was perusing the IETF 100 agenda and proceeded to click a
>> meeting video.
>>
>> First, with javascript off (my security default), it thinks I need a
>> new browser. It should just say "This site requires javascript to
>> function."
>>
>> Second, with javascript now enabled and the website white listed, it
>> took me to a series of clicks where I think I am required to register
>> even under "Read Only" mode.   I didn't click the Read/Write
>> (participant mode) option.
>>
>> Is this read-only registration necessary?
>
> It was conscious choice, yes.
>
> There was previous discussion on (IIRC) this list.
>   In particular, the thread starting at
>   https://www.ietf.org/mail-archive/web/ietf/current/msg102867.html
>
> Note that the audio-only stream does not require this registration.
>


Thanks for the link.

I've always been an advocate for a "Basic Remote Member ietf.org" 
registration system, it would resolve all sorts of things and maybe 
good for recruiting.

But in this case, at that moment, it killed the interest I had to 
continue.

The videos (archive?) 
https://ietf100.conf.meetecho.com/index.php/Recordings
here doesn't required log in.  Good material.


-- 
HLS



From nobody Wed Nov 15 15:21:37 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 55221126CF9 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 15:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 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, 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 NT2sIGU42KKP for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 15:21:34 -0800 (PST)
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 89A06120727 for <ietf@ietf.org>; Wed, 15 Nov 2017 15:21:34 -0800 (PST)
Received: by mail-pg0-x235.google.com with SMTP id 4so10235377pge.1 for <ietf@ietf.org>; Wed, 15 Nov 2017 15:21:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:cc:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=xnVgX6YTv9X79VQcXuV/dQU+ZJFwrVfC7hZg1UVx0us=; b=CZLEJoIHrYVavdEeJI4a2IYVLjlcobxtkRKxGwrt0/QzyR+TscExB+rrhCLXRWl3Ss Psf5APEMx+gLQ3iniJc+3M1izmQ17MvSgHzYMOFdxDMA8QgCG1HWEZglqoq7i0tvCfLo IBMNKW68GstSargZdQ0VZlPIu0+I6Fp0RLh+i9EHC1vRs5EII3+DmNeRL75hrFeZnuSe +Xm4N2bhsblVswlF+hCqdtG6/uRu7CDBqrK4vJA1ylobUrrGsMN+Sks2T6PBMpOHf1s/ 8jZgsiAUkZct8rTG9F4cPZc3HhCdXDjPOB/dMdRmaX+Qa9J6mgE6tjjbfMDl4+BdMiMx VuzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=xnVgX6YTv9X79VQcXuV/dQU+ZJFwrVfC7hZg1UVx0us=; b=l0jPFmoicVAdBs5it4ZPNijFXjiLh8bXCgeqWWU4ZTrWboG8Zuq+3LvIjR6vUYUZVJ hJiZEpBQGADyP7mqfv8cCwjgxMSPbvNsZBsbtW7of0bTarikb56exQv0KA6mfexqmtDM jz4JTmmgCslX2ERJfaNvOG+061/pxcwbFPDwyZPHbcqjsWQ1x3EbzC0xiyaKAahT4xDq qpwXejENAeTKLDxjlfoRwxPokamExAtIj+wYpGr8TrpfeLwV8cs8k82yST56yPTzW4ri RvWmC96+ldpf018cl3OWAaImAsgjq6VtQM6sdCZ4zYid2XyHDdv25Y/Trk48wmmSN7Rk +AIQ==
X-Gm-Message-State: AJaThX60P91I8bmScVUsRsnXKdfWJ9aUe3OR19n+hXqkw0yv5a6H8Lwz oYacZpYlnCvUwAmJYFJiUBELrw==
X-Google-Smtp-Source: AGs4zMZ6rsATltckpV5PezSt6PoVqOMLHvEPAYhAkhvL4ttPnJ1QpBgs3Dww3+tFMCfQ5vlGY3IdFg==
X-Received: by 10.99.181.6 with SMTP id y6mr17002480pge.270.1510788093712; Wed, 15 Nov 2017 15:21:33 -0800 (PST)
Received: from [172.16.132.82] ([101.100.166.3]) by smtp.gmail.com with ESMTPSA id c1sm41137774pfa.12.2017.11.15.15.21.31 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2017 15:21:32 -0800 (PST)
Subject: Re: IETF 100 MeetEcho connectivity
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com>
Date: Thu, 16 Nov 2017 12:21:35 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <5A0C6E8F.4060105@isdg.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GQ290K4o7eFwIYDzwNr5xuy-6b4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Nov 2017 23:21:36 -0000

Here's a modest suggestion. At https://www.ietf.org/meeting/100/index.html,
even though there is a "Registration" link under "Remote Participation",
it isn't apparent that this is a required step. This is made clear behind
the "Info" link. So if the "Registration" link was removed, and "Info" link
renamed as "Start Here", people would not miss the registration step.

(The same applies to https://beta.ietf.org/how/meetings/100/ of course.)

Regards
   Brian

On 16/11/2017 05:42, Hector Santos wrote:
> 
> On 11/12/2017 8:59 PM, Benjamin Kaduk wrote:
>> On Sun, Nov 12, 2017 at 08:36:59PM -0500, Hector Santos wrote:
>>> Hi, I was perusing the IETF 100 agenda and proceeded to click a
>>> meeting video.
>>>
>>> First, with javascript off (my security default), it thinks I need a
>>> new browser. It should just say "This site requires javascript to
>>> function."
>>>
>>> Second, with javascript now enabled and the website white listed, it
>>> took me to a series of clicks where I think I am required to register
>>> even under "Read Only" mode.   I didn't click the Read/Write
>>> (participant mode) option.
>>>
>>> Is this read-only registration necessary?
>>
>> It was conscious choice, yes.
>>
>> There was previous discussion on (IIRC) this list.
>>   In particular, the thread starting at
>>   https://www.ietf.org/mail-archive/web/ietf/current/msg102867.html
>>
>> Note that the audio-only stream does not require this registration.
>>
> 
> 
> Thanks for the link.
> 
> I've always been an advocate for a "Basic Remote Member ietf.org" 
> registration system, it would resolve all sorts of things and maybe 
> good for recruiting.
> 
> But in this case, at that moment, it killed the interest I had to 
> continue.
> 
> The videos (archive?) 
> https://ietf100.conf.meetecho.com/index.php/Recordings
> here doesn't required log in.  Good material.
> 
> 


From nobody Wed Nov 15 16:26:30 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 51B12120721 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 16:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fmKgJD4RysKu for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 16:26:27 -0800 (PST)
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 494E51292FD for <ietf@ietf.org>; Wed, 15 Nov 2017 16:26:16 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eF80V-000MGd-6D; Wed, 15 Nov 2017 19:26:15 -0500
Date: Wed, 15 Nov 2017 19:26:08 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
Message-ID: <D1A229DF8EE0895C3747F15F@PSB>
In-Reply-To: <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@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.10
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/qsgr3gd9sXyPY_NQvCeRNu9rJfM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 00:26:29 -0000

--On Thursday, November 16, 2017 12:21 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> Here's a modest suggestion. At
> https://www.ietf.org/meeting/100/index.html, even though there
> is a "Registration" link under "Remote Participation", it
> isn't apparent that this is a required step. This is made
> clear behind the "Info" link. So if the "Registration" link
> was removed, and "Info" link renamed as "Start Here", people
> would not miss the registration step.
> 
> (The same applies to https://beta.ietf.org/how/meetings/100/
> of course.)

If we are going to design this by committee, a useful
alternative of addition would be to make the link text for the
main "Register" link under "General" read "Register (On-site and
remote)" and then be sure the registration form layout was
remote participant friendly.    

The problem with removing the "Register" link under "Remote
Participation" is that those of us who have participated
remotely many times are fairly unlikely to click on an "Info"
link unless we think something is different.   To demonstration
this, if the "Register" link under "General" were replaced with
"Info", how often do you think you would click on it, at least
before you got frustrated looking in all the other obvious and
non-obvious places.

Another way to deal with the problem would be to move the
"Remote Participation" category up so it immediately followed
"General" and maybe create a new title in that column for "On
Site Participation" and make "Additional Events", "Social
Event", "Venue and...", and "On the Ground..." subsidiary to it.

It actually took me a while to find the remote participation
registration link because the location of that category at the
lower right, under the rather specialized "New Attendees" and
"Session Chair Tools" categories was counterintuitive.

   john
   (remotely)





From nobody Wed Nov 15 18:16:33 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 E7DAE127775 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 18:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DqZDC0WUobl5 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 18:16:29 -0800 (PST)
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 909471241F3 for <ietf@ietf.org>; Wed, 15 Nov 2017 18:16:29 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eF9j9-00086y-LL; Thu, 16 Nov 2017 02:16:28 +0000
Date: Thu, 16 Nov 2017 10:16:26 +0800
Message-ID: <m2shdf55ol.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
In-Reply-To: <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 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/p2y2i2NZ2pkhmU9E8Mvz9sS576g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 02:16:31 -0000

what is the threat model which makes any sort of registration needed?

randy


From nobody Wed Nov 15 18:48: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 14EC912943B for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 18:48:11 -0800 (PST)
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 RS5CPx_LzeP9 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 18:48:09 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::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 A9956129421 for <ietf@ietf.org>; Wed, 15 Nov 2017 18:47:43 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id c123so11483240pga.11 for <ietf@ietf.org>; Wed, 15 Nov 2017 18:47:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=o+LJQltsSVgMg7qbc365RhaOnqP9DSwe/xYIbzSRpms=; b=D6rkySv+wVwI1dR91JcXiUbdxYijejoazASNWm7gYlFyJqhNm01NyPDUG3Q/4HgtuM GOcthV4NgsjAZs3s4SWMNOQxBNUtRAsmZ5+RVu2ORKjIxJmiAK5zR8Q42iJeRE5qRUUI WsulrnmN/ljLpMwSfQnLndi3jeTbhPSs5atJr48F0cFnAVXpRDj53bExDtao156XlPa9 7CS7aIr3a3oWNA8o+0lQcZxCUvr6DuPT9llVYtD3dLwXXnI+cNvaxCH58Tzq4uRHOKB5 sfAW+qAlb9dOlYuayQlxbEUCQoFxDgBFZiEz6Ye5UnfTd3zbgttiaE502/41dbEcZXSw N0RA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=o+LJQltsSVgMg7qbc365RhaOnqP9DSwe/xYIbzSRpms=; b=i4IwdYq/V80jrRkqJ+7wkvjSOGXloZ7JxnKM2BCbMHLZGorIvTwkzDKGU7+Kufu2uf FtL/h26C65HN0ea8huNt63Rm96mkvT4atDpUXJCVZWQCLoXWbIN9kX3AZM/CXJBnqrmu kGN6dwQmwRx/f+7hGIzNnLVaXoGclHNHGhkO0IerRqXi9sQaY/T7Ifz4r45uER+KIeB7 zovffrSyI5OgaPTZ8yALOSYnyCDt5p/0lSVSoA1Xv8f3BtW2w69ox628GviYIDJkEU7n UREwTlvykQApYILgy1qrKliCcLm3nnQC1AbGyddrgRAMXHIrIzSsXHXQ+W12EOX5PeOU /XJQ==
X-Gm-Message-State: AJaThX68Q7vU9Smk5Y5qpMfbIbCgxQhZtoNRRO7xPAyz36Y6dyvkq+aW lCKD8RBZ20HgM6LIJg6y0XXikg==
X-Google-Smtp-Source: AGs4zMZcmmiowgcng8KKYGzw0BPCJSm0HFUzW9Rn6TOWHh5UR/JgV+xvw9N8hscbhV1daM1RmO5HbQ==
X-Received: by 10.99.130.74 with SMTP id w71mr181141pgd.31.1510800462871; Wed, 15 Nov 2017 18:47:42 -0800 (PST)
Received: from ?IPv6:2001:67c:370:1998:28cc:dc4c:9703:6781? ([2001:67c:370:1998:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id s25sm95715pge.44.2017.11.15.18.47.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2017 18:47:41 -0800 (PST)
Subject: Re: IETF 100 MeetEcho connectivity
To: Randy Bush <randy@psg.com>
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com>
Date: Thu, 16 Nov 2017 15:47:44 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <m2shdf55ol.wl-randy@psg.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7uJgyS18R1Yon8YHwl_PmW7rpEw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 02:48:11 -0000

On 16/11/2017 15:16, Randy Bush wrote:
> what is the threat model which makes any sort of registration needed?

Dunno. Ask meetecho? I do understand that they need a registration
in order for a remote attendee to speak, and that may be a last-minute
decision.

  Brian


From nobody Wed Nov 15 19:02:06 2017
Return-Path: <akatlas@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 EDE52128954 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:02:04 -0800 (PST)
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 YsTxzg2zkM_r for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:02:03 -0800 (PST)
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 09E9B124BE8 for <ietf@ietf.org>; Wed, 15 Nov 2017 19:02:03 -0800 (PST)
Received: by mail-oi0-x232.google.com with SMTP id l138so7407060oib.7 for <ietf@ietf.org>; Wed, 15 Nov 2017 19:02:03 -0800 (PST)
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=xW/o/HCodO54FF+rHPIv4+HGxfwVbXxbFkkIOA72TKs=; b=ExxV6fWcxw0xq9bCDtoSWz6IztS+1KpdrhzlWlFH3EKr4qtajS1vu5wGtfGwe9W42J X7YZnaAMlSgfONQN1a8gwnMlNV/SLKl1tlMFRu5IllXHqUkkM49jFUFbNsdLAVYGRf6w N3yv+zK7shb1pDdwvYVd47p+AP88l4ZxfEHvafdHcWAAvckzDcWkDKCU1IFYTBAZVqGO owp6C7ppjFzHQY7HFr5tL9mkQXjIHDcGqLczBSW29I5N7e7MTPtDuQtUUBnZ8hp2HhNI 6yrSCOBViFA1kKlXx8FsEpvmArD8flPVlnBIoB6s7x6W60/tj7P5ZwsC78DuFlW6o2JN 10dQ==
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=xW/o/HCodO54FF+rHPIv4+HGxfwVbXxbFkkIOA72TKs=; b=LYXWCGacIge9wZNIBSswwA7wOnD1yXZujshTXC/xIU0DhD0XOyb2NfbBzkDCWn7vea tXlbLAKfW+C2AtWQWVMFJxWv93lArYWRp6Cu+FuoyikIY5m0gSf6c76/NBsp85mupCmp Dhu+ObFYsgOwKab1EzqlxnTAXKcAYex8AOZOF8IJZhIZ46M9Ax5V0qyBtKx7lhv986Fk OIlXUAfO/J6HjXzmypKc4CMwynD4PQbwldyeQAye7K/soi2wWlAGxNGrvsxNxS4J93bt iZCln+SxXmFKSMeQ/P93pnwzLU9b+LWwDmm5AmMRl5JD1TNCr03l9ddJ0XnTr6eF7BpQ 6MAg==
X-Gm-Message-State: AJaThX46ZOOBktHCODgEvSW5QjHPvZJv36qyZRLZz94oGLy1pZc8rooZ 3lws6PEFFoAGdCHADaLGP6wjqkO/db9aHIuvqWI=
X-Google-Smtp-Source: AGs4zMb+FndAZs3Z5UNWcWeU8QlSMVkRixZibwoqEP8vCiEBy6uYkVNH6gfwk68cKaGIUPMi7XA35qK2PzYrqM0xTb4=
X-Received: by 10.202.244.10 with SMTP id s10mr128186oih.352.1510801322124; Wed, 15 Nov 2017 19:02:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.0.143 with HTTP; Wed, 15 Nov 2017 19:02:01 -0800 (PST)
In-Reply-To: <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, 15 Nov 2017 22:02:01 -0500
Message-ID: <CAG4d1rfrP=rVvWMtn--wPTTKzJydrkmEXN2CJBDwt0=yzsjV3A@mail.gmail.com>
Subject: Re: IETF 100 MeetEcho connectivity
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Randy Bush <randy@psg.com>, IETF General Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1134e0ba21ac0e055e10d8eb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P67BSj1LGWQdxSrsM2zGviKSQXw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 03:02:05 -0000

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

Understanding our participation and having those remote participants clearly
acknowledge the Note-Well is useful for the IETF.

I do not believe that a threat model is necessary for justification.

Regards,
Alila

On Wed, Nov 15, 2017 at 9:47 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 16/11/2017 15:16, Randy Bush wrote:
> > what is the threat model which makes any sort of registration needed?
>
> Dunno. Ask meetecho? I do understand that they need a registration
> in order for a remote attendee to speak, and that may be a last-minute
> decision.
>
>   Brian
>
>

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

<div dir=3D"ltr">Understanding our participation and having those remote pa=
rticipants clearly<div>acknowledge the Note-Well is useful for the IETF.</d=
iv><div><br></div><div>I do not believe that a threat model is necessary fo=
r justification.</div><div><br></div><div>Regards,</div><div>Alila</div></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Nov 15=
, 2017 at 9:47 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.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"><span class=3D"">=
On 16/11/2017 15:16, Randy Bush wrote:<br>
&gt; what is the threat model which makes any sort of registration needed?<=
br>
<br>
</span>Dunno. Ask meetecho? I do understand that they need a registration<b=
r>
in order for a remote attendee to speak, and that may be a last-minute<br>
decision.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 Brian<br>
<br>
</font></span></blockquote></div><br></div>

--001a1134e0ba21ac0e055e10d8eb--


From nobody Wed Nov 15 19:02: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 66044124BE8 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:02:05 -0800 (PST)
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 ZIBcxv7E0s6b for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:02:03 -0800 (PST)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e: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 ADCCF126DEE for <ietf@ietf.org>; Wed, 15 Nov 2017 19:02:03 -0800 (PST)
Received: by mail-pg0-x236.google.com with SMTP id 207so16727775pgc.12 for <ietf@ietf.org>; Wed, 15 Nov 2017 19:02:03 -0800 (PST)
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=5NVrZvsajh4j0GwNSJ7lli35vZ808Ande36xiRc+674=; b=p5ZTXJkhNJNeXBVRVFh1P5ILy0VU/5C1lShFX9kfVd6WI5JcuPoCHUdZrK3k25R+qu /a8ig9kBI4GrOOHiNCboKzfr/qxUBmbraOSmozVFZuGNjogN06lzC/ZIgc0ofp9T24MJ 3AJmKd0Li08qpsIz7bVUVXAdu6PNtU2BXAbb6wL6X2noCBDtIR0W1dtjr+eiA5s+GT0k WBwBEBPK5mwfF6QuYqdD+m/Jjgyxq3/Y22UrAS42wrXrMAYe1sej4C8+2go1+w4UzyvV 3ticb3CeS7nqn8bMvYCKTwQAi0tTfDQuUT+jTnEPzuZGr2baZXmQAOgMl+fe/ikqy3rw 5Zcg==
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=5NVrZvsajh4j0GwNSJ7lli35vZ808Ande36xiRc+674=; b=nDyFXzmXWw1ibJHT7CXYHMEoi0/4uFc2gnI1ZqCFU9/z1lTOmULks2FnGecPqhOK5m JSAHnoNVjwf/MJkaq7siUfYpwlgUkrzyp7NhiKlg9RCen9PVEBkqxr5ui8zxdvcM2yAL E/glAgdQ3pIow4epvyzNjW1Ugj1sJa0bRf7miE1E2dSDAC58Vn18GPGXJ5d0XcmoG/Fz wzbqITAU9v7HQ0+nJcBOF5swHhPmV9G6WG9GqPCYwJKAnAWm4pbscIoy7xtHKZEoBUdc W9sDj3u+7PABXCZdBxGBVVyMUJV3vSpcBBtJc9m5ebPYXMGO+d82gZ91Np3+wlcw51yb PTyA==
X-Gm-Message-State: AJaThX7zzdqrS+uH5nJUOAimEoJlBT5WjVbKGTOrd8FEJNp079eDdqBp JAvoBLtoDbiRtyJ2BvZpS/M=
X-Google-Smtp-Source: AGs4zMZDzQhMxFk3zfXx8K5FM6mUaEafOaCb7B31PctQc4D97IQYua9GYI3m20ZsUMVal+/BKzp4ww==
X-Received: by 10.98.157.67 with SMTP id i64mr263670pfd.40.1510801323380; Wed, 15 Nov 2017 19:02:03 -0800 (PST)
Received: from ?IPv6:2001:67c:370:128:706e:6e54:a9ca:335c? ([2001:67c:370:128:706e:6e54:a9ca:335c]) by smtp.gmail.com with ESMTPSA id b10sm148119pfj.20.2017.11.15.19.02.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Nov 2017 19:02:02 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <DAFB79E7-EF52-4C64-9AB7-C593C0B70567@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F84E72E7-F4AC-456E-9BC7-465A07C8AA26"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: IETF 100 MeetEcho connectivity
Date: Thu, 16 Nov 2017 11:02:19 +0800
In-Reply-To: <m2shdf55ol.wl-randy@psg.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF General Discussion Mailing List <ietf@ietf.org>
To: Randy Bush <randy@psg.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dC2HYRAB1z_s6M1MWnn-l6B1WkY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 03:02:05 -0000

--Apple-Mail=_F84E72E7-F4AC-456E-9BC7-465A07C8AA26
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I think this was done mostly to be able to count how many remote =
attendees we have (as opposed to someone who just listens in on one or =
two sessions)

> On 16 Nov 2017, at 10:16, Randy Bush <randy@psg.com> wrote:
>=20
> what is the threat model which makes any sort of registration needed?
>=20
> randy
>=20


--Apple-Mail=_F84E72E7-F4AC-456E-9BC7-465A07C8AA26
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-----

iQEzBAEBCgAdFiEE9OWnAqT2UIzvSbaAuEkLFQpYzJkFAloM/7sACgkQuEkLFQpY
zJmExQf/c8GxvAShvTq1+HsVq6WEJv1i/NsefDvgbWk7Kh0eD9BquodBRpiHMh8i
WF5zqAaeTERCxdMS8c0kF5OJIi72BHGtX2Z7v1u4SXg/o1b/zjAD1NE5RmxT1+Nr
AXA3s9Sz1Ljc1FerhwJGhnEf8glVEsrvoi8V2cWFqhaZY34s/s4ubvKBoS2rwj2V
hmJB1FbIgy5Mi20Ra0Gb+z+kLcf4xOudPndEozIDOdPPR3N/TrklbaJ8e6QRMxep
tvUdo8uRKIc5S0JrwpPnIDOrXf1bMgnPJxuR1+e/qJPV3QADkegvrpno7xPLo3cj
zq7/h2iyuVvVd0nEtTm7OVRaPx4vUA==
=JmPa
-----END PGP SIGNATURE-----

--Apple-Mail=_F84E72E7-F4AC-456E-9BC7-465A07C8AA26--


From nobody Wed Nov 15 19:05: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 841BD129434 for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:05:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j1_sjjaibpXd for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:05:00 -0800 (PST)
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 3506B129407 for <ietf@ietf.org>; Wed, 15 Nov 2017 19:05:00 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eFAU6-00007M-Cv; Thu, 16 Nov 2017 03:04:58 +0000
Date: Thu, 16 Nov 2017 11:04:56 +0800
Message-ID: <m2o9o26i07.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
In-Reply-To: <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 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/ownXSGxYqAcpMBYfZJacaa8gpPw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 03:05:01 -0000

>> what is the threat model which makes any sort of registration needed?
> 
> Dunno. Ask meetecho? I do understand that they need a registration
> in order for a remote attendee to speak, and that may be a last-minute
> decision.

i happen to be sitting next to the meetecho folk in the noc.  they say
it is what they were told to do; just following orders.  reminding them
of nurenberg did not seem appropriate.

randy


From nobody Wed Nov 15 19:11:17 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 193D6126E7A for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LWS6O0CsQEgs for <ietf@ietfa.amsl.com>; Wed, 15 Nov 2017 19:11:13 -0800 (PST)
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 C49F8124BE8 for <ietf@ietf.org>; Wed, 15 Nov 2017 19:11:13 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eFAa8-00008B-Id; Thu, 16 Nov 2017 03:11:12 +0000
Date: Thu, 16 Nov 2017 11:11:11 +0800
Message-ID: <m2mv3m6hps.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Alia Atlas <akatlas@gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
In-Reply-To: <CAG4d1rfrP=rVvWMtn--wPTTKzJydrkmEXN2CJBDwt0=yzsjV3A@mail.gmail.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com> <CAG4d1rfrP=rVvWMtn--wPTTKzJydrkmEXN2CJBDwt0=yzsjV3A@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 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/9NYaNCobejEcvFvTH2mlEP9HMa8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 03:11:15 -0000

> Understanding our participation

sorry, i do not understand what you intend here

> having those remote participants clearly acknowledge the Note-Well is
> useful for the IETF.

this i understand.  and we are all used to the Ts&Cs checkboxes none of
us read.

we talk about open blah blah.  this makes merely listening daunting.  i
almost gave up on trying to watch last night's plenary (felt i should be
in noc).

randy


From nobody Thu Nov 16 03:02:47 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 CE7A21293FD for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 03:02:45 -0800 (PST)
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 lIKQYBkl_dhq for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 03:02:39 -0800 (PST)
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 AE270127873 for <ietf@ietf.org>; Thu, 16 Nov 2017 03:02:39 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eFHwL-000Nlt-HS; Thu, 16 Nov 2017 06:02:37 -0500
Date: Thu, 16 Nov 2017 06:02:30 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Randy Bush <randy@psg.com>
cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
Message-ID: <4B1B3C4884E0809C0B360928@PSB>
In-Reply-To: <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@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.10
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/lCpg-L-ObaM0Q18FNxIPtMFa5EA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 11:02:46 -0000

--On Thursday, November 16, 2017 15:47 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 16/11/2017 15:16, Randy Bush wrote:
>> what is the threat model which makes any sort of registration
>> needed?
> 
> Dunno. Ask meetecho? I do understand that they need a
> registration in order for a remote attendee to speak, and that
> may be a last-minute decision.

AFAIK, there are two issues, at least if one accepts that anyone
was is going to speak or otherwise attempt to influence
decisions needs to be registered and, insofar as is possible and
reasonable, registered with an identity that is understandable
by others.  Note that should apply to entering anything into a
Jabber room (with a "MIC" request or not) as well as using the
Meetecho queue request mechanism.

One is the rapid switching Brian mentions above. If one
concludes, midway in a WG session, that one needs to speak up or
say something on Jabber, the odds are high that the conversation
will have passed the topic by if one has to pause and go through
a registration procedure rather than just switching modes.  That
is, IMO, the important issue on a short-term basis.

THe other is the cost of doing this remote participation stuff,
costs that are going to rise if things some of us have discussed
to make things work better or more smoothly are implemented.
ISOC's generosity notwithstanding, even some of us who are
happily taking advantage of the free ride are uncomfortable
about doing so.   If, as a community, we are going to understand
the costs and plan for the future, we need to have some
understanding of who is using the real time facilities and how.
Passive listening or video-watching hours or days later is
another matter -- we want to have the recordings for historical
and documentation purposes and the marginal cost of an extra
person downloading or streaming them is rather small.   But
real-time remote participant, and even remote observer, costs
are another matter.   

IIR, the registration form does have an "I prefer to not
register" box.  That presumable locks one into Observer mode
with no possibility of a real-time switch to Participant.  IMO,
that is reasonable, important to have as an option, and should
accommodate anyone whose privacy concerns outweigh any desire
they might have to switch over to active participation.

   john



From nobody Thu Nov 16 12:53:56 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 6194A129431 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 12:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G_7k2N_aNkfw for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 12:53:53 -0800 (PST)
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 C5C66129407 for <ietf@ietf.org>; Thu, 16 Nov 2017 12:53:53 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 2148320091; Thu, 16 Nov 2017 15:55:39 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 0079382639; Thu, 16 Nov 2017 15:53:52 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Randy Bush <randy@psg.com>
cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: IETF 100 MeetEcho connectivity
In-Reply-To: <m2shdf55ol.wl-randy@psg.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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: Thu, 16 Nov 2017 15:53:52 -0500
Message-ID: <21579.1510865632@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mf5s1C03itjvRbBG5fGswtwA5bk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 20:53:55 -0000

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


Randy Bush <randy@psg.com> wrote:
    > what is the threat model which makes any sort of registration needed?

Bluesheet/IPR concerns.
You have to read the Note Well if you want to contribute/speak.

--
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+93Q3WUFAloN+uAACgkQgItw+93Q
3WXcQwf/X7GpkCGpqhbr5Y8okr4ZFLpXfaFmZG01VOoJ6tsdVGE2Yx6b7OBshddN
/Uh4Tv1KZxi0IrvjyFhtaHhQ7f0F/p3FVr/02ISlxdQb8l2GEeysDo1Zbuvtaj0d
9BlI9zsX/msJZooU/HMgZc/+5Er/IhCuXfvrKgZhy5X7yQRPdbiOzMwRLuJf0HMG
so4rPvVMliFCQaNWsnD03RijQZoTvS77DMRkGcfsGpNYBUOoz0/LM49CO1UswfhW
zHSGNraq/JKbk+eaYBQ4Ls7AcK7OL6qBKA9GVddPB8PY/+8kGzkjzk8IYJY97935
fnnmT8cAwI/v5g9+6rEXHJG/7iBPvA==
=Kba7
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Nov 16 14:02:36 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CBB3127517 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 14:02:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=opendkim.org header.b=sEgxmGUp; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=OslCPH3N
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfNquosssY7q for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 14:02:34 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3003C127342 for <ietf@ietf.org>; Thu, 16 Nov 2017 14:02:34 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com (ADSL-TPLUS-80-17.telecomplus.net [196.27.80.17]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vAGM2Msh000188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Nov 2017 14:02:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510869753; x=1510956153; bh=BUZzc9PNjUOfbYP9x0gM8xllqwjpBldTaTluyDCL5ew=; h=Date:To:From:Subject:In-Reply-To:References; b=sEgxmGUpO+6/5PMrfOtwsS+p1J+k7ls2qzZqMRwwSUsNZ6PgkqmpB61TKwE/qGehK KHdGfBRStXyFuWJw2yOt/t5Y0p5QpD/4/758Hhlb4t/5EDMX6p1SfBwAGQUXqeiQHY h6dxxc4ITqnk+johYapIP4qUF2QucXrAfdKruDJE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510869753; x=1510956153; i=@elandsys.com; bh=BUZzc9PNjUOfbYP9x0gM8xllqwjpBldTaTluyDCL5ew=; h=Date:To:From:Subject:In-Reply-To:References; b=OslCPH3NPyRUbmmal3zSJkb1b6CTQF44lC6f8jvJMRUBu4tfaH1zkXLxHkGpehhbM Lf+la7LRb7VmOHDhgT5bLVUZG8lG3+/iVAjvqCqHz0J5zahewsOaPU/Y+9hyYu/yqD JpB7NSVARfGj3tdpUn3ZcpCXgZXRTOG72z0RkAp8=
Message-Id: <6.2.5.6.2.20171116131140.114da858@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 16 Nov 2017 13:59:55 -0800
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF 100 MeetEcho connectivity
In-Reply-To: <4B1B3C4884E0809C0B360928@PSB>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com> <4B1B3C4884E0809C0B360928@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gG3aybJl18LygAeH4gCmVqE8heY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 22:02:35 -0000

Hi John,
At 03:02 AM 16-11-2017, John C Klensin wrote:
>AFAIK, there are two issues, at least if one accepts that anyone
>was is going to speak or otherwise attempt to influence
>decisions needs to be registered and, insofar as is possible and
>reasonable, registered with an identity that is understandable
>by others.  Note that should apply to entering anything into a
>Jabber room (with a "MIC" request or not) as well as using the
>Meetecho queue request mechanism.
>
>One is the rapid switching Brian mentions above. If one
>concludes, midway in a WG session, that one needs to speak up or
>say something on Jabber, the odds are high that the conversation
>will have passed the topic by if one has to pause and go through
>a registration procedure rather than just switching modes.  That
>is, IMO, the important issue on a short-term basis.

Over the years it was possible to comment in a Jabber room without 
having to click through a "Note Well" and it is still like that 
today.  Meetecho Observer mode is audio only; it used to be audio and 
video after Meetecho was introduced.

>THe other is the cost of doing this remote participation stuff,
>costs that are going to rise if things some of us have discussed
>to make things work better or more smoothly are implemented

The expenses for remote participation is 4.7% of meeting expenses.

Regards,
S. Moonesamy  


From nobody Thu Nov 16 15:02:42 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 8088E126C0F for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 15:02:38 -0800 (PST)
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 t0yzQo3TV97Z for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 15:02:36 -0800 (PST)
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 C9AF81250B8 for <ietf@ietf.org>; Thu, 16 Nov 2017 15:02:36 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eFTB4-000Ozn-TU; Thu, 16 Nov 2017 18:02:34 -0500
Date: Thu, 16 Nov 2017 18:02:27 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
Subject: Re: IETF 100 MeetEcho connectivity
Message-ID: <E46F5E2121CB0D6474779767@PSB>
In-Reply-To: <6.2.5.6.2.20171116131140.114da858@elandnews.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com> <4B1B3C4884E0809C0B360928@PSB> <6.2.5.6.2.20171116131140.114da858@elandnews.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.10
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/kOMROwrZJHJ4pktubrkZeBiqIBY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Nov 2017 23:02:38 -0000

--On Thursday, November 16, 2017 13:59 -0800 S Moonesamy
<sm+ietf@elandsys.com> wrote:

> Hi John,
>...
>> One is the rapid switching Brian mentions above. If one
>> concludes, midway in a WG session, that one needs to speak up
>> or say something on Jabber, the odds are high that the
>> conversation will have passed the topic by if one has to
>> pause and go through a registration procedure rather than
>> just switching modes.  That is, IMO, the important issue on a
>> short-term basis.
 
> Over the years it was possible to comment in a Jabber room
> without having to click through a "Note Well" and it is still
> like that today.

Yes.  And from the standpoint of the IETF being able to document
who is influencing decisions about standards is a bad idea.
How bad is a question for lawyers and may depend on one's
assessment of the likelihood of someone getting upset about, or
feeling that they have been hurt by, IETF decisions to challenge
the fairness and openness of the process.   What situation we
would be in if someone mounted that sort of challenge and we
couldn't document participants, balance, etc., is also a
question for lawyers, preferably ones with a crystal ball
supply, but other SDOs who have found themselves with that sort
of problem have not found it to be pleasant experience.

>  Meetecho Observer mode is audio only; it
> used to be audio and video after Meetecho was introduced.

If that has actually changed, I think it is very problematic.  I
don't recall any discussions or decisions that should have
changed it.
 
>> THe other is the cost of doing this remote participation
>> stuff, costs that are going to rise if things some of us have
>> discussed to make things work better or more smoothly are
>> implemented
> 
> The expenses for remote participation is 4.7% of meeting
> expenses.

That depends on how and what one counts.  And that isn't a topic
I want to get drawn into especially outside IASA 2.0 discussions
about how transparent the IAOC has been and whether the
community cares.

best,
   john



From nobody Thu Nov 16 18:30:39 2017
Return-Path: <prvs=1494ff0e50=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 1F50512008A for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:30:38 -0800 (PST)
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 JKUQqU1H-41V for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:30:36 -0800 (PST)
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 1E6FB126DFE for <ietf@ietf.org>; Thu, 16 Nov 2017 18:30:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510885834; x=1511490634; 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=l6vCJB5jAJG8zGjziUcz6TlFeeYCo/UkjMQ0Ah64f9k=; b=YDE11ElcG7lfA Um0uqghmjBj/Ptj5gmzEBLwdYLh+OHLNRZL0+yGqNnHjiwH84OlVjxS2V/CV/DGe sqrdzvhDblx8UPNdG6N0sxSl+IXzD4ptkbQQX8hAyZfWBzbHM7DYlmc8CieMHZr4 Rt5H29VWDlx31mKOsTwLuRRtSb98OY=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=l/XlnTMlaaFhXcwBKpW1P+/mOgUfqvXFkI4sa8AktLbPgY6r7NU04Uw3QU+P cPUFOI7v++4jI8bndYCR1R+evNTHhq/qQzIi5CPdF7DspOdIyYO9VDhNy Zktlcxv1HOp79dI4gZK+kPgucJ66mz3zYAmH/Y5QBrbhLd5cNa7gr0=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:30:34 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:30:33 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005626194.msg for <ietf@ietf.org>; Fri, 17 Nov 2017 03:30:32 +0100
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:171117:md50005626194::MIOCbVQmAOIh4j+8:00000th0
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Fri, 17 Nov 2017 10:30:20 +0800
Subject: delayed emails
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Message-ID: <25DB30C9-5289-4F4E-8308-1AB71E8A4477@consulintel.es>
Thread-Topic: delayed emails
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/2q3QbCBSuF5ERuBBKCDey9S8tJ0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 02:30:38 -0000

I=E2=80=99ve noticed during this week that all the IETF mail exploders are =
getting big delays (several hours).

I=E2=80=99ve investigated my email server, and don=E2=80=99t looks as any i=
nternal problem in my side.

Just wondering if somebody else noticed this, or even if the secretariat ca=
n check it, or if something has changed recently that can cause that.

Regards,
Jordi
=20



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

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Thu Nov 16 18:31:31 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 501FE127522 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:31:19 -0800 (PST)
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] 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 KaRmKRgAcdDx for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:31:17 -0800 (PST)
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 1A95D1274D2 for <ietf@ietf.org>; Thu, 16 Nov 2017 18:31:16 -0800 (PST)
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 7872F58C4AF for <ietf@ietf.org>; Fri, 17 Nov 2017 03:31:13 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 57E64B0D1C9; Fri, 17 Nov 2017 03:31:13 +0100 (CET)
Date: Fri, 17 Nov 2017 03:31:13 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: ietf@ietf.org
Subject: Spare IETF1100100 sticker ?
Message-ID: <20171117023112.GA6181@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cLhTiG-SdUtdqA0FCNsAqqcgBs0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 02:31:19 -0000

I lost out on noticing the availability of this real nice IETF sticker.
If anyone has a spare one i could have, i would really appreciate!

Cheers
    Toerless


From nobody Thu Nov 16 18:39:53 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 D267F126D73 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.205
X-Spam-Level: 
X-Spam-Status: No, score=-3.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, PLING_QUERY=0.994, 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 CHTbLdCbTsp4 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:39:51 -0800 (PST)
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 A63D71267BB for <ietf@ietf.org>; Thu, 16 Nov 2017 18:39:51 -0800 (PST)
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 41A4758C4AF for <ietf@ietf.org>; Fri, 17 Nov 2017 03:39:48 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 2F108B0D1C9; Fri, 17 Nov 2017 03:39:48 +0100 (CET)
Date: Fri, 17 Nov 2017 03:39:48 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: ietf@ietf.org
Subject: Done! Re: Spare IETF1100100 sticker ?
Message-ID: <20171117023948.GB6181@faui40p.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/neWO06v-yxyEiWlZhKr9DP_jY7Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 02:39:53 -0000

Thanks, Greg!

and sorry for postting to ietf instead of the ietf100-attendees list, ENOCOFFEE


From nobody Thu Nov 16 18:43:21 2017
Return-Path: <prvs=1494ff0e50=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 1640E126C0F for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:43:19 -0800 (PST)
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 VA_uNE3GpOpK for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:43:17 -0800 (PST)
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 80CB2124F57 for <ietf@ietf.org>; Thu, 16 Nov 2017 18:43:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510886593; x=1511491393; 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=kwRphoj22p50197+6YRo3i+16 1fT2p9XQn9Z5OXNy5E=; b=kMWl3QdkasUxw8icDMuCq7KarCKJw97amf1Ek6VFJ PjM4/CTN4N46BG4/5weSZL2fTOkgUx9Wa/4I0phuBe1R7sq/p7Q9s3+5KolJhCzR D4eV6aVKWZwJPpJZRzENcxw2v4Xz6+BeaZIprTO8hcMXTR5aN3Lq1MBxP5qNa+lu NM=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=bpR7yWlbCJGiA+Pe88yjb47X1SiuO0aCAPI8MepiVAKaMUBvoYAOyiPmSCk6 Msl801kgixt5eGNRhcomYpYRxMGO/Bauju3tseNR08j5mtT2Cj0SvgeCR LjVZ7f2hoJYMC6s2vMMvG6iWIH59hv67rhktGi2vFLsOD+Zr6FoGeM=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:43:12 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:43:11 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005626208.msg for <ietf@ietf.org>; Fri, 17 Nov 2017 03:43:11 +0100
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:171117:md50005626208::O+J0hlpeyD+U0CUS:00006BJN
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Fri, 17 Nov 2017 10:42:49 +0800
Subject: Re: On audio quality requirements for IETF meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "<ietf@ietf.org>" <ietf@ietf.org>
CC: <ingemar.s.johansson@ericsson.com>
Message-ID: <CA878EBF-4EF9-4E17-9AB1-1A868D0A58E9@consulintel.es>
Thread-Topic: On audio quality requirements for IETF meetings
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com>
In-Reply-To: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.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/PICJvjg7GIvVmJHDJmZNNnCtxJ8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 02:43:19 -0000

Hi all,

I=E2=80=99ve got the below question from Ingemar (confirmed with him that i=
s ok to respond in the list).

This document:

https://datatracker.ietf.org/doc/draft-palet-ietf-meeting-network-requireme=
nts/

is mainly about the network, but also =E2=80=9Cother=E2=80=9D technical req=
uirements, so I think it will be fine to include audio specs.

I=E2=80=99m sure we have some audio experts in the list that can figure out=
 what will be the correct wording for our criteria on this?

I want to take the opportunity to ask the list for:
1) Please review the document, specially the NOC team and secretariat, but =
in general in case there are other technical requirements that aren=E2=80=
=99t being considered.
2) IETF chair/IESG, as the mtgvenue WG believes there is not good expertise=
 there to evaluate this document, what is the path forward?

I don=E2=80=99t want to have the same experience as I had in 2006 with this=
 document and the original draft-palet-ietf-meeting-venue-selection-criteri=
a, which after hard work were silently ignored and we started the work from=
 scratch in mtgvenue without even mentioning them.

This is another topic, but I want to mention it as it is a perfect example:=
 I think this is a global IETF problem and we should somehow correct it. Pe=
ople do some work =E2=80=A6 is not considered by IETF, fine, but then after=
 some time, somebody else take on that work and the original authors aren=
=E2=80=99t referenced. I think is a matter of basic politeness and acknowle=
dgment.

Regards,
Jordi
=20

-----Mensaje original-----
De: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Responder a: <ingemar.s.johansson@ericsson.com>
Fecha: viernes, 17 de noviembre de 2017, 10:17
Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Asunto: On audio quality requirements for IETF meetings

    Hi
    Tried to find the RFC that describes the requirements for the IETF meet=
ing rooms, still not lucky in my search. I would be interested to see if th=
ere are any stated requirements on the audio quality.
   =20
    I personally suffer from degraded hearing since childhood and quite oft=
en have problems to hear what people say. The reasons are :
    + High noise from AC and ventilation
    + Low  audio level (sometimes close to 0dB S/N)
    + Long reverberation times (boomy acoustics)
    =20
    Some of these issues are relatively easy to fix (requirements on audio =
levels), others can be involve more work. I don=E2=80=99t have all the answ=
ers right now but for instance.
    + Line array loudspeakers are generally better than point sources and b=
uilt in ceiling speakers, as the line arrays control the audio dispersion b=
etter, a great benefit in venues with boomy acoustics.
   =20
    + Requirements on e.g RT60 and noise levels.=20
    + Audio monitors should face the WG/AD/* chairs and the presenter
    =20
    I believe that improved acoustics would non only benefit people with ba=
d hearing, it would also reduce fatigue for people with good hearing
    =20
    Is there any document that can be updated with recommendations, unless =
there are any requirements/recommendations available already ?
   =20
    =20
    Regards
    Ingemar
    =20
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    Ingemar Johansson  M.Sc.
   =20
    Master Researcher
    =20
    Ericsson Research
    Network Protocols & E2E Performance
    Labratoriegr=C3=A4nd 11
    971 28, Lule=C3=A5, Sweden
    Phone +46-1071 43042
    SMS/MMS +46-73 078 3289
    ingemar.s.johansson@ericsson.com
    www.ericsson.com
    =20
    The world is full of magical things patiently
   =20
        waiting for our wits to grow sharper
                   Bertrand Russell
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Thu Nov 16 18:47:20 2017
Return-Path: <prvs=1494ff0e50=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 4D339126CB6 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:47:14 -0800 (PST)
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 YYJHHYIMngQQ for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:47:11 -0800 (PST)
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 CFAF9126C0F for <ietf@ietf.org>; Thu, 16 Nov 2017 18:46:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510886795; x=1511491595; 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=7lJPZJwIlFJZM2laBsbEmJqZk trBC2rGN4RO41xnkpA=; b=KPKMfUB4xGr/i8vXzOhZrz7ZN+TAJ+KeY7NO0PMG5 oe9htyd8qB+nZ1a8t66pXuzprLtNqOWrrELMdmudSb5WeBZTdHEHWGxd+6g6yPnB RwCiAY4CZXlH4yR2+D7AjJSZ3jmuLorUIYmEUQDC3ceSjUfM2TjoHDe3ZmbMNOBD Wg=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=ONF41GVEl50M/H4XOMSfyNZKB9e7TM6zSZTGWSQA6uxmErBJyi7ES8aLFROq uECpda/H21Qn+h1N1kYW49gT5rCdkgqaf0PHMx2pTeRh0YfQ0MpkxXTqx oT4FXNgIsKZhz5UD8AD/yLY7C+Rbi+Kd+Lglu6hQsBT7h4bkMdSRjU=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:46:35 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:46:33 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005626214.msg for <ietf@ietf.org>; Fri, 17 Nov 2017 03:46:33 +0100
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:171117:md50005626214::N8ySO8oJt/WOJuIT:00007APk
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Fri, 17 Nov 2017 10:46:19 +0800
Subject: Re: On audio quality requirements for IETF meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Message-ID: <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es>
Thread-Topic: On audio quality requirements for IETF meetings
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es>
In-Reply-To: <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@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/xkvqMDL9bQFS93lnO_QKXLWvNHE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 02:47:14 -0000

By the way =E2=80=A6 maybe I=E2=80=99m starting to suffer hearing problems,=
 don=E2=80=99t noticed before, but in this meeting, I=E2=80=99ve real diffi=
culties to heard and consequently understand people at the mike when I was =
presenting.

I think it will be interesting to know if Ingemar and I, are alone on this =
=E2=80=A6

Regards,
Jordi
=20

-----Mensaje original-----
De: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Fecha: viernes, 17 de noviembre de 2017, 10:42
Para: "<ietf@ietf.org>" <ietf@ietf.org>
CC: <ingemar.s.johansson@ericsson.com>
Asunto: Re: On audio quality requirements for IETF meetings

    Hi all,
   =20
    I=E2=80=99ve got the below question from Ingemar (confirmed with him th=
at is ok to respond in the list).
   =20
    This document:
   =20
    https://datatracker.ietf.org/doc/draft-palet-ietf-meeting-network-requi=
rements/
   =20
    is mainly about the network, but also =E2=80=9Cother=E2=80=9D technical=
 requirements, so I think it will be fine to include audio specs.
   =20
    I=E2=80=99m sure we have some audio experts in the list that can figure=
 out what will be the correct wording for our criteria on this?
   =20
    I want to take the opportunity to ask the list for:
    1) Please review the document, specially the NOC team and secretariat, =
but in general in case there are other technical requirements that aren=E2=
=80=99t being considered.
    2) IETF chair/IESG, as the mtgvenue WG believes there is not good exper=
tise there to evaluate this document, what is the path forward?
   =20
    I don=E2=80=99t want to have the same experience as I had in 2006 with =
this document and the original draft-palet-ietf-meeting-venue-selection-cri=
teria, which after hard work were silently ignored and we started the work =
from scratch in mtgvenue without even mentioning them.
   =20
    This is another topic, but I want to mention it as it is a perfect exam=
ple: I think this is a global IETF problem and we should somehow correct it=
. People do some work =E2=80=A6 is not considered by IETF, fine, but then a=
fter some time, somebody else take on that work and the original authors ar=
en=E2=80=99t referenced. I think is a matter of basic politeness and acknow=
ledgment.
   =20
    Regards,
    Jordi
    =20
   =20
    -----Mensaje original-----
    De: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
    Responder a: <ingemar.s.johansson@ericsson.com>
    Fecha: viernes, 17 de noviembre de 2017, 10:17
    Para: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
    Asunto: On audio quality requirements for IETF meetings
   =20
        Hi
        Tried to find the RFC that describes the requirements for the IETF =
meeting rooms, still not lucky in my search. I would be interested to see i=
f there are any stated requirements on the audio quality.
       =20
        I personally suffer from degraded hearing since childhood and quite=
 often have problems to hear what people say. The reasons are :
        + High noise from AC and ventilation
        + Low  audio level (sometimes close to 0dB S/N)
        + Long reverberation times (boomy acoustics)
        =20
        Some of these issues are relatively easy to fix (requirements on au=
dio levels), others can be involve more work. I don=E2=80=99t have all the =
answers right now but for instance.
        + Line array loudspeakers are generally better than point sources a=
nd built in ceiling speakers, as the line arrays control the audio dispersi=
on better, a great benefit in venues with boomy acoustics.
       =20
        + Requirements on e.g RT60 and noise levels.=20
        + Audio monitors should face the WG/AD/* chairs and the presenter
        =20
        I believe that improved acoustics would non only benefit people wit=
h bad hearing, it would also reduce fatigue for people with good hearing
        =20
        Is there any document that can be updated with recommendations, unl=
ess there are any requirements/recommendations available already ?
       =20
        =20
        Regards
        Ingemar
        =20
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
        Ingemar Johansson  M.Sc.
       =20
        Master Researcher
        =20
        Ericsson Research
        Network Protocols & E2E Performance
        Labratoriegr=C3=A4nd 11
        971 28, Lule=C3=A5, Sweden
        Phone +46-1071 43042
        SMS/MMS +46-73 078 3289
        ingemar.s.johansson@ericsson.com
        www.ericsson.com
        =20
        The world is full of magical things patiently
       =20
            waiting for our wits to grow sharper
                       Bertrand Russell
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
        =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Thu Nov 16 18:47:28 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DDA124D68 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xM7kjTXf7cnx for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:47:14 -0800 (PST)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (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 68B66124F57 for <ietf@ietf.org>; Thu, 16 Nov 2017 18:46:59 -0800 (PST)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp003.me.com by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0OZJ00200JJAML00@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Fri, 17 Nov 2017 02:46:44 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1510886804; bh=6JJCDDY0vUAg+MeDM00HcSWyArN20OkRqFjM3l76NJQ=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=TY7ih9UjUl+aWrbwtZXDH1hOLtzCGXuNgvck9ghe0swRSqaDUVQO8xKGQYV0XJmEj Y35rnWrRc5WMt4lijBd0bq++XH3OL745nTgLo9niY2hB+2vA1bl6OjS4CYXXISlbOs DaB1DkWqWrM+3v5HVKYFeNFwP+2C01W3ndwn0JxOKGP8JbD+UNXsHU6aCFElWaI6iR wxARiInq/4sLEmVagF7hPzIoNjHJlDNrMRxasIHuXGuMiTRU+KHlR75OKG8J9cw8e6 FyhqNMfozxJCRyGiDuZmmokGNjHEJz7zYS/9tSfSGiSTjfEI2JwCPQdLtAQpu2QkX6 6e+yGhBNIS+4Q==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0OZJ00B2CJPVG920@mr11p00im-asmtp003.me.com>; Fri, 17 Nov 2017 02:46:44 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-17_01:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711170034
Date: Thu, 16 Nov 2017 18:46:43 -0800 (PST)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: delayed emails
In-reply-to: <25DB30C9-5289-4F4E-8308-1AB71E8A4477@consulintel.es>
Message-id: <alpine.OSX.2.01.1711161845180.69466@ole-pro.local>
References: <25DB30C9-5289-4F4E-8308-1AB71E8A4477@consulintel.es>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="0-1616135354-1510886803=:69466"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NuCXT4d7jCioChDVFsSINoAKIvM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 02:47:19 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1616135354-1510886803=:69466
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: 8BIT


Hi Jordi,

On the IETF100 list I just received a warning about excessive bounces 
and that my membership would be cancelled :-(

But I have received lots of mail on the list, so perhaps the problem
is a busy server.

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office: +1 415-550-9433
Cell:   +1 415-370-4628
Docomo: +81 090 3337-9311
E-mail: olejacobsen@me.com
Skype: organdemo


On Fri, 17 Nov 2017, JORDI PALET MARTINEZ wrote:

> I’ve noticed during this week that all the IETF mail exploders are 
> getting big delays (several hours).
> 
> I’ve investigated my email server, and don’t looks as any internal 
> problem in my side.
> 
> Just wondering if somebody else noticed this, or even if the 
> secretariat can check it, or if something has changed recently that 
> can cause that.
> 
> 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 exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> 
> 
> 
--0-1616135354-1510886803=:69466--


From nobody Thu Nov 16 18:57:05 2017
Return-Path: <prvs=1494ff0e50=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 36EAF126C0F for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:57:04 -0800 (PST)
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 7aMI5vODOKVQ for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 18:57:02 -0800 (PST)
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 17F661267BB for <ietf@ietf.org>; Thu, 16 Nov 2017 18:57:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510887419; x=1511492219; 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=HtXmGo5SA2z89/I14mB0GH0VD esJMgZFPSYJx7Nkgp4=; b=AZpQOi4XKjrcNkZp3drI6IwbmyOCkVwDzUR5Z0CNh e5K4L8dLlqNgWy0Y/DMlDTJXP6G4n0nUGy7QROAi/BUOHR7fnNbJUG5Uk7Ao+Fix IaHUax41ksaUYW8XKKJLrozHgfP0Ot23BVpm58S4rXzJ8n/WXn/W6HKy36usMX5n iQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=aZphsLR3xFvX1umqnJSBlMYkpJhNVabcBpfCc65ExU3aOzijTQ9OWMu5WcjT OGTS0/ZazYRMJ0+mwuIqpoiU9TQFtGwPvvwx9k/9sznaJlKyAil6Vzqhe Z+uhhjVEC3myCtkG75avSO7d+PdwdMov7tQjYq3zwQ18/lasQFmDQs=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:56:59 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 03:56:58 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005626224.msg for <ietf@ietf.org>; Fri, 17 Nov 2017 03:56:57 +0100
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:171117:md50005626224::aKKAN0heWqeVz6L2:00001d6w
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Fri, 17 Nov 2017 10:51:33 +0800
Subject: Re: delayed emails
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Message-ID: <F2DD1981-CC9C-41FE-9E3A-204BE67CB080@consulintel.es>
Thread-Topic: delayed emails
References: <25DB30C9-5289-4F4E-8308-1AB71E8A4477@consulintel.es> <alpine.OSX.2.01.1711161845180.69466@ole-pro.local>
In-Reply-To: <alpine.OSX.2.01.1711161845180.69466@ole-pro.local>
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/UqqAMVVZLARgtuFYFlaMylJ5Cns>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 02:57:04 -0000

I really think is surprising it is because a busy server =E2=80=A6 didn=E2=
=80=99t noticed =E2=80=9Cmore=E2=80=9D email traffic that in any other IETF=
 meeting, but secretariat can tell, and if that=E2=80=99s the issue, some a=
ction taken. I guess an email server can handle much more traffic than what=
 we generate (ask the so-called =E2=80=9Cemail marketing companies=E2=80=9D=
, actually I call them =E2=80=9Ccriminals of spam=E2=80=9D).

Some meetings notifications/changes arrived after it already happened (even=
 day after) =E2=80=A6 so not nice.

Saludos,
Jordi
=20

-----Mensaje original-----
De: Ole Jacobsen <olejacobsen@me.com>
Responder a: Ole Jacobsen <olejacobsen@me.com>
Fecha: viernes, 17 de noviembre de 2017, 10:47
Para: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
CC: "<ietf@ietf.org>" <ietf@ietf.org>
Asunto: Re: delayed emails

   =20
    Hi Jordi,
   =20
    On the IETF100 list I just received a warning about excessive bounces=
=20
    and that my membership would be cancelled :-(
   =20
    But I have received lots of mail on the list, so perhaps the problem
    is a busy server.
   =20
    Ole
   =20
   =20
    Ole J. Jacobsen
    Editor and Publisher
    The Internet Protocol Journal
    Office: +1 415-550-9433
    Cell:   +1 415-370-4628
    Docomo: +81 090 3337-9311
    E-mail: olejacobsen@me.com
    Skype: organdemo
   =20
   =20
    On Fri, 17 Nov 2017, JORDI PALET MARTINEZ wrote:
   =20
    > I=E2=80=99ve noticed during this week that all the IETF mail exploder=
s are=20
    > getting big delays (several hours).
    >=20
    > I=E2=80=99ve investigated my email server, and don=E2=80=99t looks as=
 any internal=20
    > problem in my side.
    >=20
    > Just wondering if somebody else noticed this, or even if the=20
    > secretariat can check it, or if something has changed recently that=
=20
    > can cause that.
    >=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 exclusive use of=
 the individual(s) named above and further non-explicilty authorized disclo=
sure, copying, distribution or use of the contents of this information, eve=
n if partially, including attached files, is strictly prohibited and will b=
e considered a criminal offense. If you are not the intended recipient be a=
ware that any disclosure, copying, distribution or use of the contents of t=
his information, even if partially, including attached files, is strictly p=
rohibited, will be considered a criminal offense, so you must reply to the =
original sender to inform about this communication and delete it.
    >=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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Thu Nov 16 19:03:09 2017
Return-Path: <ietf@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD241241F3 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 19:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 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_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=aruba.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tL96a33aws3L for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 19:03:06 -0800 (PST)
Received: from smtpcmd01240.aruba.it (smtpcmd14170.aruba.it [62.149.156.170]) by ietfa.amsl.com (Postfix) with ESMTP id D1D6C124D68 for <ietf@ietf.org>; Thu, 16 Nov 2017 19:03:05 -0800 (PST)
Received: from [31.130.230.90] ([31.130.230.90]) by smtpcmd14.ad.aruba.it with bizsmtp id ar2y1w0121xgSgX01r306s; Fri, 17 Nov 2017 04:03:04 +0100
Subject: Re: IETF 100 MeetEcho connectivity
To: John C Klensin <john-ietf@jck.com>, S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com> <4B1B3C4884E0809C0B360928@PSB> <6.2.5.6.2.20171116131140.114da858@elandnews.com> <E46F5E2121CB0D6474779767@PSB>
From: Meetecho IETF support <ietf@meetecho.com>
Message-ID: <76ea9dff-441e-c262-00fa-a9b934b25538@meetecho.com>
Date: Fri, 17 Nov 2017 04:02:58 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <E46F5E2121CB0D6474779767@PSB>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aruba.it; s=a1; t=1510887784; bh=2rd3bvgsRB6jr1tnQ/v5MLGk2tt50SyxY83wR2FuKNk=; h=Subject:To:From:Date:MIME-Version:Content-Type; b=GLVopo2nlunF60KMI63pVdD7g8iIrQSDzJeLRNvOdOa3ayrXLWckmMPjd9zYrn8Jt Jn/AggF9Cx0ZkoKIOR0MNuqIYkcWQ11qoqa4RYYEwH2+ucTnEYqriGzkgndZe4hWQh LgApR4Ty1KArPTpNaRLDD4bcuOGe+xFQ/6L3N+INKRsdqfA9R5VTC7fXU008emdYQx pJt+Y51Vv3uQ1QQAGU0jhrpnQJlrlDuJuDHnlFJ+icUqLmJMeYP1hiOZMYC1Ssg8zo mLR/fAJFpH5TIDmwNHdUn1GYRkbpSg2UyFiTZdundFJnuZ7gIrvEox0nSy8DhJuwR8 N67jb5nYU7zdQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sxq4xJdU62N8Z3rrG5c1_8Bs8Jc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 03:03:08 -0000

>>   Meetecho Observer mode is audio only; it
>> used to be audio and video after Meetecho was introduced.
> 
> If that has actually changed, I think it is very problematic.  I
> don't recall any discussions or decisions that should have
> changed it.
>   

It hasn't. Meetecho "Observer" mode still has audio + video + slides + 
jabber + etherpad. The only thing that is missing is the possibility to 
raise your hand to make comments through the virtual queue.

More info here:

	https://ietf100.conf.meetecho.com/index.php/Remote_Participation

Cheers,
the Meetecho team


From nobody Thu Nov 16 19:15:12 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 D31001276AF for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 19:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.08
X-Spam-Level: 
X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-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 YG19XxRRnF9S for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 19:15:00 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B36F4127517 for <ietf@ietf.org>; Thu, 16 Nov 2017 19:14:59 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id vAH3Es39031074; Fri, 17 Nov 2017 03:14:54 GMT
Received: from 950129200 (dhcp-8924.meeting.ietf.org [31.133.137.36]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id vAH3EpHr031037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Nov 2017 03:14:53 GMT
Reply-To: <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <jordi.palet@consulintel.es>, <ietf@ietf.org>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es>
In-Reply-To: <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es>
Subject: RE: On audio quality requirements for IETF meetings
Date: Fri, 17 Nov 2017 03:14:49 -0000
Message-ID: <170901d35f52$3c4a0fc0$b4de2f40$@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: AQIr7wyJqva7jVfCICsGZYvRNJRBjwHt85rAAcVVpwWiSSukkA==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-23470.004
X-TM-AS-Result: No--4.622-10.0-31-10
X-imss-scan-details: No--4.622-10.0-31-10
X-TMASE-MatchedRID: e/tT8EyIjJSyXgYYhqRDwpV8hSZp5ynXWEPEl3ozFuMsX4dJC/gI/ou3 renu5Y0wubuHEcFPbyYkOZlozX424GlwnxmUMV/FngIgpj8eDcByZ8zcONpAsdmzcdRxL+xwKra uXd3MZDX2qNUR5NGQMbqGDzW+mVDnpNd5IOEn6USyb8UwAmsmXxlyJMh36YUtNhaOBHxzal2OTC SnRTeg+iPVIUGLlI4nRt01ZrBZr355ekLjAaeHxA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/koKexrYGLLV6cWE0rUEo-67e2a8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 03:15:02 -0000

You are not alone!
Conference centre PA not good.
Mics very distance-sensitive.
Not so bad that unusable, but hard work.
Adrian

> By the way =E2=80=A6 maybe I=E2=80=99m starting to suffer hearing =
problems, don=E2=80=99t noticed
> before, but in this meeting, I=E2=80=99ve real difficulties to heard =
and consequently
> understand people at the mike when I was presenting.
>=20
> I think it will be interesting to know if Ingemar and I, are alone on =
this =E2=80=A6


From nobody Thu Nov 16 19:21:27 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 A955D126CD8 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 19:21:13 -0800 (PST)
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 vn5JDQzGflAK for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 19:21:12 -0800 (PST)
Received: from mail-pg0-x232.google.com (mail-pg0-x232.google.com [IPv6:2607:f8b0:400e:c05::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 8F2E91275F4 for <ietf@ietf.org>; Thu, 16 Nov 2017 19:21:10 -0800 (PST)
Received: by mail-pg0-x232.google.com with SMTP id z184so905908pgd.13 for <ietf@ietf.org>; Thu, 16 Nov 2017 19:21:10 -0800 (PST)
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=VGkq9Q08/vlNTjO5pgo6xCH5wLC8avxRm5mKVWJUjak=; b=A21JNj4a28XInzCHR6N9YoRzzKzhmbsPLulP9vUnjwmtBGl2XWHRlKSBa5kWzwj13Z rCbYyRPc+hxW+03y8qX5oqR/OKV3eM5wQCwxXfZeL/o8afUTByQkE+10udNBCl0q07QQ N9JYBYXFijqvpDnLod86DqF11QHfYg9jc7PiY5gN7dJas+Bml4VYB7IPc1HtkIHmPu1p UpN36vSH2xxbubBJgx4kNzHzl5LRlF4k3Qx5YsIJts0UGujuGGv9U2cwksobpwLBjhXF imyMOGmoGpxV35u4hi4x+lUlJpRvRAjvlgSRxtSq8hypFsOn+/Qlb8UfjHTh3IOBGBpW ZKFA==
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=VGkq9Q08/vlNTjO5pgo6xCH5wLC8avxRm5mKVWJUjak=; b=TZ5CYLp0+TnDMachrvQviaN1X6KM4XZZSPgEirQxaGHJbfS6q7qWHQLTt1O3wzwx+o X/IKDFhig7FgRdkEL9cOGnupPlluxr/Cdghi1H+IuN+koWuOqsl7VFcRneSPa5O9Te6r O0LE6bnlPbKwMLrhV6ujhA1RwZfbWPl82Y22z0CNzvNSwnzsJxUu4vtx9ZDJ9u+EIlq5 bOGUIZZLBGlqG3Ha/S4EyRS1RkVsncP73G2uAuGVUUupQB0k3TTBnEa71ekSbtmNebz5 QWazR27MWGJ1uHgOpbHCpYnGS5dj1WFz3NrnwRm5D7Xc9oK/wD4FmDCw/Jpccf9PEgSA UhmA==
X-Gm-Message-State: AJaThX6iqP36oBQZULf21LDUdqZh4wZA/FMyrVsQOrbpfVpMhMWsf5GJ gDo9xYXkDgpf4rgnU9jbdiQJfZaNA88=
X-Google-Smtp-Source: AGs4zMautF8OEt3V9Z1wdteM0dVFAQnBF2pnAbgT0q3Ne0UCs9POi8ET9DHlqSgpxjY//sLoDrQmXA==
X-Received: by 10.101.96.35 with SMTP id p3mr3687539pgu.230.1510888870141; Thu, 16 Nov 2017 19:21:10 -0800 (PST)
Received: from ?IPv6:2001:67c:370:1998:64db:3d1e:6d2f:8b68? ([2001:67c:370:1998:64db:3d1e:6d2f:8b68]) by smtp.gmail.com with ESMTPSA id d8sm5433394pfh.178.2017.11.16.19.21.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Nov 2017 19:21:09 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5BF0CC78-CAD4-4C3F-919D-87446D611B28"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: On audio quality requirements for IETF meetings
Date: Fri, 17 Nov 2017 11:21:07 +0800
In-Reply-To: <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk>
Cc: jordi.palet@consulintel.es, ietf@ietf.org
To: adrian@olddog.co.uk
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/InrfCH5k1_mm6cL_K1U4ynPPv0g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 03:21:14 -0000

--Apple-Mail=_5BF0CC78-CAD4-4C3F-919D-87446D611B28
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 17, 2017, at 11:14 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Conference centre PA not good.
> Mics very distance-sensitive.
> Not so bad that unusable, but hard work.

Another issue is that the microphones kept running out of power, and =
there's no way to charge them.   Either we need someone other than the =
participants doing this, or else there needs to be resources in each =
room that chairs or others can use to get microphones working when they =
fail.


--Apple-Mail=_5BF0CC78-CAD4-4C3F-919D-87446D611B28
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; line-break: after-white-space;" class=3D"">On =
Nov 17, 2017, at 11:14 AM, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk" class=3D"">adrian@olddog.co.uk</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"">Conference centre =
PA not good.</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""><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"">Mics very distance-sensitive.</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""><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"">Not so bad that unusable, but hard =
work.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Another issue is that the microphones kept running out of =
power, and there's no way to charge them. &nbsp; Either we need someone =
other than the participants doing this, or else there needs to be =
resources in each room that chairs or others can use to get microphones =
working when they fail.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_5BF0CC78-CAD4-4C3F-919D-87446D611B28--


From nobody Thu Nov 16 20:04:02 2017
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3D9127843 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 20:04:00 -0800 (PST)
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 OGN2jOQ9fi1l for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 20:03:58 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0A011275F4 for <ietf@ietf.org>; Thu, 16 Nov 2017 20:03:53 -0800 (PST)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id BF1E11CAC42 for <ietf@ietf.org>; Thu, 16 Nov 2017 20:03:13 -0800 (PST)
Received: from mail-io0-f174.google.com (mail-io0-f174.google.com [209.85.223.174]) by c8a.amsl.com (Postfix) with ESMTPSA id 9B32C1CAC30 for <ietf@ietf.org>; Thu, 16 Nov 2017 20:03:13 -0800 (PST)
Received: by mail-io0-f174.google.com with SMTP id 189so7462185iow.10 for <ietf@ietf.org>; Thu, 16 Nov 2017 20:03:53 -0800 (PST)
X-Gm-Message-State: AJaThX5NRETvn2TiXikT9YCOJMU4feMJZiWkxLxfJnnrHZQXnZ7RflJa DcuPGYMEZHu0b2Dez7usK287ceCUbXJh1Yw+5js=
X-Google-Smtp-Source: AGs4zMZy/kd+JFvO7xtf3xqOjMTcLBhXV4NS6GSHt2XwcL1ceb72GzTAXmXS6kOMCKLU375ZL3nWLvYnDbX07wks35Y=
X-Received: by 10.107.25.18 with SMTP id 18mr1343021ioz.11.1510891432945; Thu, 16 Nov 2017 20:03:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.67.10 with HTTP; Thu, 16 Nov 2017 20:03:32 -0800 (PST)
In-Reply-To: <F2DD1981-CC9C-41FE-9E3A-204BE67CB080@consulintel.es>
References: <25DB30C9-5289-4F4E-8308-1AB71E8A4477@consulintel.es> <alpine.OSX.2.01.1711161845180.69466@ole-pro.local> <F2DD1981-CC9C-41FE-9E3A-204BE67CB080@consulintel.es>
From: Glen <glen@amsl.com>
Date: Thu, 16 Nov 2017 20:03:32 -0800
X-Gmail-Original-Message-ID: <CABL0ig7VGMy8XDDC0VrM1GcUxYt-5Yb12wsB2gzW+yU2+LjWqA@mail.gmail.com>
Message-ID: <CABL0ig7VGMy8XDDC0VrM1GcUxYt-5Yb12wsB2gzW+yU2+LjWqA@mail.gmail.com>
Subject: Re: delayed emails
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a113ff1e827ae64055e25d390"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4bKn6Ic9P2zBMDLcl3bIyOno4yE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 04:04:00 -0000

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

Jordi wrote:
> I=E2=80=99ve noticed during this week that all the IETF mail exploders ar=
e
getting big delays (several hours).    I=E2=80=99ve investigated my email s=
erver,
and don=E2=80=99t looks as any internal problem in my side.  Just wondering=
 if
somebody else noticed this, or even if the secretariat can check it, or if
something has changed recently that can cause that.

Hi Jordi -

The secretariat can indeed check it, but the IT team does not generally
monitor the IETF discussion list, since that's intended as general chat for
IETF participants, and is rather busy.

Instead, we have a trouble ticket queue that staff monitors, which can be
reached at:  ietf-action@ietf.org .

I have checked, and the server is not running slow at the moment, and our
monitoring systems have not reported any delays in Mailman or email
processing.

Of course, mail can be delayed for lots of reasons; but, generally, an
examination of the mail headers "Received" lines can tell you where the
delay occurred, and, often, what the cause was.

If you have received an email that you feel has been delayed, and are
unable to determine where the delay occurred, please do forward the message
- with all headers intact (which may require that you paste the headers
into the message body) - to ietf-action@ietf.org, and I or one of my team
will be happy to analyze it for you.

But just wanted to make clear and remind everyone that we are *there* to
help - but we are not *here* to help (on this particular mailing list) :-)
- so please do reach out to ietf-action@ietf.org if you need anything from
us.

(And of course, if any of you feel that you're not getting a response
there, please do escalate to me directly at glen@amsl.com and I will handle
things personally for you.  This is never a problem, it is why I am here.)

Ole wrote:
> On the IETF100 list I just received a warning about excessive bounces and
that my membership would be cancelled :-(  But I have received lots of mail
on the list, so perhaps the problem is a busy server.

I do see bounces from me.com for you Ole, and I will reply to you off-list
right now with details.

Glen

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

<div dir=3D"ltr"><div><div><div><div><div><div>Jordi wrote:<br> &gt; I=E2=
=80=99ve noticed during this week that all the IETF mail exploders are gett=
ing big delays (several hours).=C2=A0 =C2=A0 I=E2=80=99ve investigated my e=
mail server, and don=E2=80=99t looks as any internal problem in my side.=C2=
=A0 Just wondering if somebody else noticed this, or even if the secretaria=
t can check it, or if something has changed recently that can cause that.<b=
r><br></div>Hi Jordi -<br><br></div>The secretariat can indeed check it, bu=
t the IT team does not generally monitor the IETF discussion list, since th=
at&#39;s intended as general chat for IETF participants, and is rather busy=
.=C2=A0 <br><br></div>Instead, we have a trouble ticket queue that staff mo=
nitors, which can be reached at:=C2=A0 <a href=3D"mailto:ietf-action@ietf.o=
rg">ietf-action@ietf.org</a> .<br><br></div>I have checked, and the server =
is not running slow at the moment, and our monitoring systems have not repo=
rted any delays in Mailman or email processing.<br><br></div>Of course, mai=
l can be delayed for lots of reasons; but, generally, an examination of the=
 mail headers &quot;Received&quot; lines can tell you where the delay occur=
red, and, often, what the cause was.<br><br></div>If you have received an e=
mail that you feel has been delayed, and are unable to determine where the =
delay occurred, please do forward the message - with all headers intact (wh=
ich may require that you paste the headers into the message body) - to <a h=
ref=3D"mailto:ietf-action@ietf.org">ietf-action@ietf.org</a>, and I or one =
of my team will be happy to analyze it for you.<br><br><div>But just wanted=
 to make clear and remind everyone that we are *there* to help - but we are=
 not *here* to help (on this particular mailing list) :-) - so please do re=
ach out to <a href=3D"mailto:ietf-action@ietf.org">ietf-action@ietf.org</a>=
 if you need anything from us.<br></div><div><br></div><div>(And of course,=
 if any of you feel that you&#39;re not getting a response there, please do=
 escalate to me directly at <a href=3D"mailto:glen@amsl.com">glen@amsl.com<=
/a> and I will handle things personally for you.=C2=A0 This is never a prob=
lem, it is why I am here.)<br></div><div><br><div><div><div>Ole wrote:<br><=
/div><div><div><div><div><div><div>&gt; On the IETF100 list I just received=
 a warning about excessive bounces and that my membership would be cancelle=
d :-(=C2=A0 But I have received lots of mail on the list, so perhaps the pr=
oblem is a busy server.</div><div><br></div>I do see bounces from <a href=
=3D"http://me.com">me.com</a> for you Ole, and I will reply to you off-list=
 right now with details.</div><div><br></div><div>Glen<br></div></div></div=
></div></div></div></div></div></div>

--001a113ff1e827ae64055e25d390--


From nobody Thu Nov 16 20:25:37 2017
Return-Path: <dmiloshevic@afilias.info>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C387B126C26 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 20:25:35 -0800 (PST)
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 QijEIDUgXMUF for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 20:25:34 -0800 (PST)
Received: from outbound.afilias.info (outbound.afilias.info [66.199.183.4]) (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 3C5721200CF for <ietf@ietf.org>; Thu, 16 Nov 2017 20:25:34 -0800 (PST)
Received: from maia.afilias-int.info ([10.109.8.9] helo=smtp.afilias.info) by outbound.afilias.info with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.88) (envelope-from <dmiloshevic@afilias.info>) id 1eFYDd-000BsX-4a for ietf@ietf.org; Fri, 17 Nov 2017 04:25:33 +0000
Received: from mail-pg0-f69.google.com ([74.125.83.69]) by smtp.afilias.info with esmtps (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <dmiloshevic@afilias.info>) id 1eFYDd-0004BQ-49 for ietf@ietf.org; Fri, 17 Nov 2017 04:25:33 +0000
Received: by mail-pg0-f69.google.com with SMTP id u3so1384890pgn.11 for <ietf@ietf.org>; Thu, 16 Nov 2017 20:25:33 -0800 (PST)
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=kP+CD0y1vy4uUcz9YQ3txUmm7mJe/La4V8TEfBFOWag=; b=c8jGiC563sPXpu2NE28Hf1F+7E0cAoX0gSVgZMKrahMwQ1GMXbAg8nYQY9SMbunQN0 17AyZ4L5eQjaCAO2+m8DAmBQE8fPtpkqjiCta+2nrU/iolZoZT1juPYGT+3P5tKu1cAJ cHslIVbj63AcGhG23PuobyrZ7HzSZQ2b5rJMyMgcaJwjF8AEoc69XW7emVXkPhb0d8Si t0qrXl4qOX2wH2QPPKU5ChYUOar66tRItVs5E0C+9unUVkF57RAR+DPBzJ0OHjOpzY+B j4OKmNTmBXT3jWB5f/bmjvO0U1M+kB/mzNglybcyfDLO6hu8SA3gm9dZrod81k9exJMn gMhQ==
X-Gm-Message-State: AJaThX6YbvqGniJbXpZa2LA2IPddB7c7Wa87kR/7MD0zgI2MIjKAVrxv p4UMU+e2ApWIZbSek1o8dA1hQnMAx0gFzpx6qRGArwxvJulo1N8xXKIWG+7rBfiOTKucZREyToI yXtP0TYw=
X-Received: by 10.84.210.109 with SMTP id z100mr4002079plh.364.1510892727477;  Thu, 16 Nov 2017 20:25:27 -0800 (PST)
X-Google-Smtp-Source: AGs4zMY3XqT+HVgQrKWe3aDwrROryGZt+Z5//LcV5sBNUzWbcoDQ0hLgq7jO64vCTB+BqI+NScGm3Q==
X-Received: by 10.84.210.109 with SMTP id z100mr4002067plh.364.1510892727112;  Thu, 16 Nov 2017 20:25:27 -0800 (PST)
Received: from ?IPv6:2001:67c:1232:144:ad8a:4c0f:1eed:e4c5? ([2001:67c:1232:144:ad8a:4c0f:1eed:e4c5]) by smtp.gmail.com with ESMTPSA id c9sm5520550pfj.76.2017.11.16.20.25.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Nov 2017 20:25:26 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Spare IETF1100100 sticker ?
From: Desiree Miloshevic <dmiloshevic@afilias.info>
In-Reply-To: <20171117023112.GA6181@faui40p.informatik.uni-erlangen.de>
Date: Fri, 17 Nov 2017 04:25:23 +0000
Cc: ietf@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <882E3738-188A-40BB-8BCB-5EC6AC291F47@afilias.info>
References: <20171117023112.GA6181@faui40p.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/383dSQYneDKrF5R22ceGemy16kI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 04:25:36 -0000

+1
I misplaced my registration badge and the sticker that was in it.

Cheers

Desiree
--
> On 17 Nov 2017, at 02:31, Toerless Eckert <tte@cs.fau.de> wrote:
> 
> I lost out on noticing the availability of this real nice IETF sticker.
> If anyone has a spare one i could have, i would really appreciate!
> 
> Cheers
>    Toerless
> 


From nobody Thu Nov 16 21:00:57 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7EA128796 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 21:00:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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=opendkim.org header.b=N05/njxl; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=uyrnhsfj
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3vYmz0Z6tmZ for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 21:00:54 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B635C127136 for <ietf@ietf.org>; Thu, 16 Nov 2017 21:00:54 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com (ADSL-TPLUS-80-17.telecomplus.net [196.27.80.17]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id vAH50fPp015029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Nov 2017 21:00:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1510894853; x=1510981253; bh=RZCzItGOMjUE4oMUwMuIWIrz/4WZFZkZfJWDiGT3IuQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=N05/njxlFe2OJEsS3n6dJC5RCTBWgeFwVc/bJGh57Du2dJChdLDhpduUeZ/guc+vN 09G1+EXnfwh/1eMlWEvD/PbWBIK8o9ZvDSWsikKkGloNgESJ6iH1ox4Dg8EAWKoABI 46E1CfQXoR2LV0cfcFl43yauW+ZyZmpwiShHzEFw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1510894853; x=1510981253; i=@elandsys.com; bh=RZCzItGOMjUE4oMUwMuIWIrz/4WZFZkZfJWDiGT3IuQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uyrnhsfj1dx/Z1PdwXnhv9mniAREUfKryeNEn7nq/fak8sfI+NDjQsVZdzoLKUm+3 9oMzWvm250pP3HVUwwQKs0koR7eqK3UTMl3PzvhSrNx3qNm+CJz+Z5WaTdM7ZA0Zen afukJqpNSV8ZgnOD9YGQJxCVA2VfNreDCR5g302Q=
Message-Id: <6.2.5.6.2.20171116204548.1076f1a0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 16 Nov 2017 20:53:07 -0800
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF 100 MeetEcho connectivity
In-Reply-To: <76ea9dff-441e-c262-00fa-a9b934b25538@meetecho.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com> <4B1B3C4884E0809C0B360928@PSB> <6.2.5.6.2.20171116131140.114da858@elandnews.com> <E46F5E2121CB0D6474779767@PSB> <76ea9dff-441e-c262-00fa-a9b934b25538@meetecho.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WbEFSDJMrNGUiVG3MVWXAfQeFUA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 05:00:55 -0000

Hi John,
At 07:02 PM 16-11-2017, Meetecho IETF support wrote:
>It hasn't. Meetecho "Observer" mode still has audio + video + slides 
>+ jabber + etherpad. The only thing that is missing is the 
>possibility to raise your hand to make comments through the virtual queue.

The change where registration is required for Observer mode occurred 
as from IETF99.  Prior to that, registration was optional.

Regards,
S. Moonesamy  


From nobody Thu Nov 16 21:23:26 2017
Return-Path: <marka@isc.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 1056C126B72 for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 21:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKL4gw5PTS9x for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 21:23:23 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67BE7124D6C for <ietf@ietf.org>; Thu, 16 Nov 2017 21:23:23 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id D0B263B0F94; Fri, 17 Nov 2017 05:23:21 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id A7B5B160041; Fri, 17 Nov 2017 05:23:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 7EC39160069; Fri, 17 Nov 2017 05:23:21 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id BginY92_HIJr; Fri, 17 Nov 2017 05:23:21 +0000 (UTC)
Received: from [172.30.42.89] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 9BC0D160041; Fri, 17 Nov 2017 05:23:20 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IETF 100 MeetEcho connectivity
From: Mark Andrews <marka@isc.org>
In-Reply-To: <6.2.5.6.2.20171116204548.1076f1a0@elandnews.com>
Date: Fri, 17 Nov 2017 16:23:18 +1100
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC7B7DC4-3CAD-41E5-BD86-D41DF6C3D3F6@isc.org>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com> <4B1B3C4884E0809C0B360928@PSB> <6.2.5.6.2.20171116131140.114da858@elandnews.com> <E46F5E2121CB0D6474779767@PSB> <76ea9dff-441e-c262-00fa-a9b934b25538@meetecho.com> <6.2.5.6.2.20171116204548.1076f1a0@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jrhnek2Aw8_nsgTEl_1S929kP1U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 05:23:25 -0000

> On 17 Nov 2017, at 3:53 pm, S Moonesamy <sm+ietf@elandsys.com> wrote:
>=20
> Hi John,
> At 07:02 PM 16-11-2017, Meetecho IETF support wrote:
>> It hasn't. Meetecho "Observer" mode still has audio + video + slides =
+ jabber + etherpad. The only thing that is missing is the possibility =
to raise your hand to make comments through the virtual queue.
>=20
> The change where registration is required for Observer mode occurred =
as from IETF99.  Prior to that, registration was optional.
>=20
> Regards,
> S. Moonesamy =20

I suspect that is more a terminology clash than anything else.

Meetecho as a observer mode vs being a observer rather than a =
registrant.

(echoes of what IPv6-only means)

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


From nobody Thu Nov 16 21:53:15 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 31C7012778E for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 21:53:13 -0800 (PST)
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 7FGR3t6fF3Ub for <ietf@ietfa.amsl.com>; Thu, 16 Nov 2017 21:53:09 -0800 (PST)
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 608B8126B6D for <ietf@ietf.org>; Thu, 16 Nov 2017 21:53:09 -0800 (PST)
Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vAH5r6W1142674 for <ietf@ietf.org>; Fri, 17 Nov 2017 00:53:09 -0500
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by mx0a-001b2d01.pphosted.com with ESMTP id 2e9q2up4df-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 17 Nov 2017 00:53:08 -0500
Received: from localhost by e35.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, 16 Nov 2017 22:53:08 -0700
Received: from b03cxnp08027.gho.boulder.ibm.com (9.17.130.19) by e35.co.us.ibm.com (192.168.1.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 16 Nov 2017 22:53:06 -0700
Received: from b03ledav004.gho.boulder.ibm.com (b03ledav004.gho.boulder.ibm.com [9.17.130.235]) by b03cxnp08027.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id vAH5r5lJ63045664 for <ietf@ietf.org>; Thu, 16 Nov 2017 22:53:05 -0700
Received: from b03ledav004.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BA5AB78038 for <ietf@ietf.org>; Thu, 16 Nov 2017 22:53:05 -0700 (MST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav004.gho.boulder.ibm.com (Postfix) with ESMTPS id 9FE4378041 for <ietf@ietf.org>; Thu, 16 Nov 2017 22:53:05 -0700 (MST)
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 vAH5r4of004746 for <ietf@ietf.org>; Fri, 17 Nov 2017 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id vAH5r4t7004684 for ietf@ietf.org; Fri, 17 Nov 2017 00:53:04 -0500
From: narten@us.ibm.com
Date: Fri, 17 Nov 2017 00:53:04 -0500
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: 17111705-0012-0000-0000-0000154F485B
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00008079; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000240; SDB=6.00947033; UDB=6.00478094; IPR=6.00727325;  BA=6.00005696; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00018057; XFM=3.00000015; UTC=2017-11-17 05:53:07
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17111705-0013-0000-0000-0000504CEA9D
Message-Id: <201711170553.vAH5r4t7004684@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-11-17_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=52 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-1709140000 definitions=main-1711170079
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nXDDmMhXI7GORFo9lf1sah8baus>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 05:53:13 -0000

Total of 74 messages in the last 7 days.
 
script run at: Fri Nov 17 00:53:02 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.11% |    6 |  9.65% |    97242 | kathleen.moriarty.ietf@gmail.com
  1.35% |    1 | 10.17% |   102562 | gregimirsky@gmail.com
  6.76% |    5 |  4.73% |    47725 | sm+ietf@elandsys.com
  5.41% |    4 |  4.88% |    49181 | jordi.palet@consulintel.es
  5.41% |    4 |  4.71% |    47514 | mnot@mnot.net
  5.41% |    4 |  4.59% |    46284 | brian.e.carpenter@gmail.com
  4.05% |    3 |  5.55% |    55956 | strazpdj@gmail.com
  4.05% |    3 |  3.40% |    34225 | victor@jvknet.com
  4.05% |    3 |  3.39% |    34131 | lear@cisco.com
  4.05% |    3 |  2.73% |    27547 | john-ietf@jck.com
  4.05% |    3 |  2.08% |    21018 | randy@psg.com
  2.70% |    2 |  2.91% |    29329 | tjc@ecs.soton.ac.uk
  2.70% |    2 |  2.51% |    25302 | paul@nohats.ca
  2.70% |    2 |  2.30% |    23214 | allison.mankin@gmail.com
  2.70% |    2 |  1.96% |    19781 | kaduk@mit.edu
  2.70% |    2 |  1.94% |    19554 | akatlas@gmail.com
  1.35% |    1 |  3.27% |    32927 | vishnupavan@gmail.com
  1.35% |    1 |  3.24% |    32693 | cpignata@cisco.com
  2.70% |    2 |  1.84% |    18507 | hsantos@isdg.net
  2.70% |    2 |  1.31% |    13256 | tte@cs.fau.de
  1.35% |    1 |  1.83% |    18432 | aaron.falk@gmail.com
  1.35% |    1 |  1.80% |    18145 | gonzalo.camarillo@ericsson.com
  1.35% |    1 |  1.71% |    17286 | roni.even@huawei.com
  1.35% |    1 |  1.70% |    17143 | ford@isoc.org
  1.35% |    1 |  1.40% |    14098 | nalini.elkins@insidethestack.com
  1.35% |    1 |  1.38% |    13880 | bortzmeyer@nic.fr
  1.35% |    1 |  1.29% |    12994 | glen@amsl.com
  1.35% |    1 |  1.24% |    12475 | phill@hallambaker.com
  1.35% |    1 |  1.21% |    12219 | narten@us.ibm.com
  1.35% |    1 |  1.20% |    12120 | mellon@fugue.com
  1.35% |    1 |  1.12% |    11322 | warren@kumari.net
  1.35% |    1 |  1.05% |    10597 | olejacobsen@me.com
  1.35% |    1 |  0.99% |     9934 | ynir.ietf@gmail.com
  1.35% |    1 |  0.88% |     8826 | dmiloshevic@afilias.info
  1.35% |    1 |  0.87% |     8801 | adam@nostrum.com
  1.35% |    1 |  0.84% |     8443 | ietf@meetecho.com
  1.35% |    1 |  0.79% |     8009 | adrian@olddog.co.uk
  1.35% |    1 |  0.78% |     7878 | mcr+ietf@sandelman.ca
  1.35% |    1 |  0.75% |     7537 | barryleiba@computer.org
--------+------+--------+----------+------------------------
100.00% |   74 |100.00% |  1008087 | Total


From nobody Thu Nov 16 22:56:16 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 AFFBC128DE5; Thu, 16 Nov 2017 22:56:14 -0800 (PST)
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-stir-certificates.all@ietf.org, stir@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-stir-certificates-15
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151090177468.22136.5281729043778955691@ietfa.amsl.com>
Date: Thu, 16 Nov 2017 22:56:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lcbc8Cmvj5dROn9iHr_env2ZiyI>
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, 17 Nov 2017 06:56:15 -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 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-stir-certificates-15
Reviewer: Joel Halpern
Review Date: 2017-11-16
IETF LC End Date: 2017-11-30
IESG Telechat date: 2017-12-14

Summary:

Major issues:

Minor issues:
    Section 4 bullet 4 in naming the crypto algorithms refers quite clearly to
    2 algorithms.  It then references one of them as RS256.  I assume those
    versed in the field will know which one is meant.  But it would be better
    if the abbreviation RS256 appeared next to the first reference to whichever
    algorithm it means.

    The security considerations section points to RFC 5280 security
    considerations for most issues.  I presume that the intention is to use
    that section regarding trusting CAs.  However, it seems that there is an
    issue here much like that of classic web CAs.  The number of CAs that must
    be trusted seems to be on the order of the number of countries in the
    world.  That seems to leave a large window for false or misleading
    certifications, as I can see nothing which restricts what numbers for which
    those top level CAs can provide attestation.  I presume we do not want to
    go down the path of requiring an uber-CA for all national authorities.  I
    would expect some explicit recognition of this issue in this document.

Nits/editorial comments:



From nobody Fri Nov 17 00:13:59 2017
Return-Path: <dbg@scs.stanford.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 3F5E8128C84; Fri, 17 Nov 2017 00:13:57 -0800 (PST)
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 fr7pyPV49Q12; Fri, 17 Nov 2017 00:13:56 -0800 (PST)
Received: from market.scs.stanford.edu (www.scs.stanford.edu [IPv6:2001:470:806d:1::9]) (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 EFF96124319; Fri, 17 Nov 2017 00:13:55 -0800 (PST)
Received: from market.scs.stanford.edu (localhost [127.0.0.1]) by market.scs.stanford.edu (8.15.2/8.15.2) with ESMTP id vAH8DtWH089661; Fri, 17 Nov 2017 00:13:55 -0800 (PST)
Received: (from dbg@localhost) by market.scs.stanford.edu (8.15.2/8.15.2/Submit) id vAH8DslG052450; Fri, 17 Nov 2017 00:13:54 -0800 (PST)
Date: Fri, 17 Nov 2017 00:13:54 -0800
From: Daniel B Giffin <dbg@scs.stanford.edu>
To: Barry Leiba <barryleiba@computer.org>
Cc: secdir@ietf.org, draft-ietf-tcpinc-tcpcrypt.all@ietf.org, tcpinc@ietf.org,  ietf@ietf.org
Subject: Re: Secdir telechat review of draft-ietf-tcpinc-tcpcrypt-09
Message-ID: <20171117081354.GC57159@scs.stanford.edu>
References: <151046377334.30804.5873766900092971520@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <151046377334.30804.5873766900092971520@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I0nXgf2Ip--sR9ucoa1cPNFtWiA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 08:13:57 -0000

Thanks for the review!

Barry Leiba wrote:
> Reviewer: Barry Leiba
> Review result: Has Issues
> 
> I’ve looked at Stephen Kent’s review and the discussion thereof, and have
> little to add to that.  A couple of small things:
> 
> 1. Section 3 says that the subsections “describes the tcpcrypt protocol at an
> abstract level.”  There is no sense in which this description is abstract, and
> I’d prefer that we not try to say it is, because that gives a reader an
> expectation that it will be high-level, and perhaps even non-normative.  Maybe
> this?:
> 
> NEW
>    This section provides details of the operation of the tcpcrypt protocol.
>    The wire format of all messages is specified in Section 4.
> END

Good point, thanks -- for the next draft I've gone with
something very similar:

   This section describes the operation of the tcpcrypt protocol.  The
   wire format of all messages is specified in Section 4.

> 2. In Section 7 (IANA), you say:
> 
>    Tcpcrypt's TEP identifiers will need to be incorporated in IANA's
>    "TCP encryption protocol identifiers" registry under the
>    "Transmission Control Protocol (TCP) Parameters" registry
> 
> I can find no such registry.  Can you help me here, maybe give me a URL?

Right, that registry is defined in TCP-ENO, which I
understand would be published in tandem with this draft.
Does that solve the problem, or ought we provide a reference
to TCP-ENO here?

For now, I've provided at least a hint by mentioning TCP-ENO
at the beginning of that sentence:

   For use with TCP-ENO's negotiation mechanism, tcpcrypt's TEP
   identifiers will need to be incorporated in IANA's "TCP encryption
   protocol identifiers" registry under the "Transmission Control
   Protocol (TCP) Parameters" registry, as in Table 4 below.  The
	 [...]

> Also, with respect to the new “tcpcrypt AEAD Algorithm" registry:
> 
>    Future assignments are to be made under the "RFC Required" policy
> 
> Note that that policy allows for assignments to be made in any RFC stream,
> which includes the IRTF, the IAB, and the Independent Stream.  Do you really
> want people to be able to send documents to the Independent Stream Editor, and
> to have them published and make assignments with minimal review?
> 
> You might consider whether “IETF Review” is more appropriate.  That allows RFCs
> of any type (Standards Track, Informational, Experimental, BCP), but requires
> that they be in the IETF stream and have a formal IETF last call.

Following the discussion about assignment policy in another
thread, I've updated this to use the same policy as TCP-ENO.
The paragraph on the "tcpcrypt AEAD Algorithm" registry now
reads:

   In Section 4.1, this document defines "sym_cipher" specifiers in the
   range 0x0001 to 0xFFFF inclusive, for which IANA is to maintain a new
   "tcpcrypt AEAD Algorithm" registry under the "Transmission Control
   Protocol (TCP) Parameters" registry.  The initial values for this
   registry are given in Table 5 below.  The AEAD algorithms named there
   are defined in Section 6.  Future assignments are to be made upon
   satisfying either of two policies defined in [RFC8126]: "IETF Review"
   or (for non-IETF stream specifications) "Expert Review with RFC
   Required."  IANA will furthermore provide early allocation [RFC7120]
   to facilitate testing before RFCs are finalized.


> It will also help IANA if you make it clear what the valid range of values is
> for the “Value” column.  Is 0x0000 valid?  Is 0xFFFF the maximum?  Explicitly
> saying that values must be in the range 0x0001 to 0xFFFF inclusive will be
> helpful.  (I say this with particular note that you changed how the Value field
> is specified between -07 and -09, so this clearly has not even been clear to
> the spec developers.)

Thanks, I've added that as you can see above.

daniel


From nobody Fri Nov 17 00:49:36 2017
Return-Path: <shahanajabc@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 DAA0B12943F for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 00:49:34 -0800 (PST)
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 ghdKkgYQ45TY for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 00:49:33 -0800 (PST)
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 DC1021293F9 for <ietf@ietf.org>; Fri, 17 Nov 2017 00:49:21 -0800 (PST)
Received: by mail-wr0-x232.google.com with SMTP id o88so1442110wrb.6 for <ietf@ietf.org>; Fri, 17 Nov 2017 00:49:21 -0800 (PST)
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=Bphr3uV0bRVm5XEeOOjVmQe4OLZzBY4DOzyZ0YvMyk8=; b=TJp6VUqtxTxRJnq4eGgCP4e9RNAcixpGZpOpcpR/vdVfXWPbLKxx5EswDF/12KWR0L /yTm+7lXbKTLtkjBCAn4t6EZu09fW3OcA/QB6v3h3QsIXLeUgzjdPnDK0+kNEzx3/iY1 hBfkGGxzb8ik7UFJKT6ps38QcCHmy1DRhIsfWwyVAj25vHG9LifwuD2wJHV6KVbXYlbB Sb9bEYKRDdcdPytwzp+uFghzEFa4aX7HaCWduztLpRKLuZ9vYnZaKaNsk6JzkCryrfsq PgJXcEu/djY/K7YYgqUPZO4JpUawBOtD0Lo4m8JqWOvBN6HMo/Bh21c4n6gIu2aHdrbt nDhg==
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=Bphr3uV0bRVm5XEeOOjVmQe4OLZzBY4DOzyZ0YvMyk8=; b=HW87louLSBk6EwhF93ebjchg0a7YqrjTbRlo9nY/0sBZNv30eDNNrr/GkwwTaY4tX3 5o1KWPUIGtvZ8ikuCLiB5rfZRKBL6I7IXxZzheVqfSKlezk80dIuAB/YznH9eCWsWeI7 9BuobBRQ6uIvFPAss+r34O6WIguzVGVfkZogyDBo3AYvdbfowggVH3xHxCv6VRxP5pr1 h+QVLdwYfuUBVNNMp3/SFrVw6jGMEgi81v1l9Z3B0cigcPuCf099ejcyTruYJd2IX7jC dFRR3IDKpkHPNDfVxVxD9XUTzkVWeU9aihs/mon22wL2pLlbPDzRphDV7S2/+rYnGTli KzTQ==
X-Gm-Message-State: AJaThX45pnkikaDymROfkkxiYRlcSTYkDgIuAa5xpu5iUqA6OEgEclp8 eSbu9OAravD64JU/Yo5YyJ0VmhOKRxR++QzXe3Y=
X-Google-Smtp-Source: AGs4zMausd4vZ1HCz/7waQeYrOzB49TbDogCPvFPQxyyWMeDYoQwAhR7hysO3Momlim416qm+exQ+cS+k+fpATUmHec=
X-Received: by 10.223.160.217 with SMTP id n25mr3639370wrn.27.1510908560249; Fri, 17 Nov 2017 00:49:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.54.228 with HTTP; Fri, 17 Nov 2017 00:49:19 -0800 (PST)
In-Reply-To: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com>
References: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com>
From: Shahanaj RBT <shahanajabc@gmail.com>
Date: Fri, 17 Nov 2017 14:49:19 +0600
Message-ID: <CALcGQd5HuapBeNVnAghKn+ca6v_bADhXy5k8hsPJaa-pyv7BuA@mail.gmail.com>
Subject: Re: [100all] Very Few T-shirts Left
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c0676f40597e3055e29d05c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LKFQpp7Nu9BoSrI-N2pL9okY2l0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 08:49:35 -0000

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

I  am  attending  remotely, May  I have one please.=F0=9F=98=8E

On Fri, Nov 17, 2017 at 9:02 AM, IESG Secretary <iesg-secretary@ietf.org>
wrote:

> But if you want one there are a very few 3XL size t-shirts available.
> First come first served.
>
> Again, 3XL only.
>
> _______________________________________________
> 100all mailing list
> 100all@ietf.org
> https://www.ietf.org/mailman/listinfo/100all
>

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

<div dir=3D"ltr">I=C2=A0 am=C2=A0 attending=C2=A0 remotely, May=C2=A0 I hav=
e one please.=F0=9F=98=8E</div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Fri, Nov 17, 2017 at 9:02 AM, IESG Secretary <span dir=3D"=
ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-=
secretary@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
But if you want one there are a very few 3XL size t-shirts available. First=
 come first served.<br>
<br>
Again, 3XL only.<br>
<br>
______________________________<wbr>_________________<br>
100all mailing list<br>
<a href=3D"mailto:100all@ietf.org">100all@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/100all" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/100all</a><br=
>
</blockquote></div><br></div>

--94eb2c0676f40597e3055e29d05c--


From nobody Fri Nov 17 01:01:18 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FEC31293E4 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 01:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8vnSbkZrNQC for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 01:01:09 -0800 (PST)
Received: from mr11p00im-asmtp004.me.com (mr11p00im-asmtp004.me.com [17.110.69.135]) (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 EA4121286D6 for <ietf@ietf.org>; Fri, 17 Nov 2017 01:01:09 -0800 (PST)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp004.me.com by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0OZJ00700ZTB6200@mr11p00im-asmtp004.me.com> for ietf@ietf.org; Fri, 17 Nov 2017 09:01:09 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1510909269; bh=E5qbiMcJOqFJIDwxIDi1IVF45WrGQGUCkuZ3GkmgNj4=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=GS5fTgflVSGUbgYtk5PrWUIQIRHoK/fXLKmgWdG3oyz8xB69MUL8YDXK1SHUMuHJr 4J+hH/Rp7v96+z1DjCtsVZ8/uJ5jmxNTQHJyZeIMkgQhNcEACF7qsEJ7dwmVvZXUdV z1+QjQmVaogx2zrypWihI0lYpgGLlTy6hK53r5fAptPOuj3mPLn6Y1OgVxLCKHevX9 38nSbOutEhEYradRuYgjYZwKHUGsGjVAtY0L4tYvSSgDxgcswdRLkP+sCg0EBBleQr vF7I90VfT9rKnc7Zd0+AQq9ENvej61BnZKmJFN3B7kYOp/XKY7hqFnMyGsP6obxxia fZzT5bTyHlw8A==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0OZK004W511Q4U20@mr11p00im-asmtp004.me.com>; Fri, 17 Nov 2017 09:01:07 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-17_03:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711170123
Date: Fri, 17 Nov 2017 01:01:01 -0800 (PST)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: Shahanaj RBT <shahanajabc@gmail.com>
Cc: ietf@ietf.org
Subject: Re: [100all] Very Few T-shirts Left
In-reply-to: <CALcGQd5HuapBeNVnAghKn+ca6v_bADhXy5k8hsPJaa-pyv7BuA@mail.gmail.com>
Message-id: <alpine.OSX.2.01.1711170059290.94555@ole-pro.local>
References: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com> <CALcGQd5HuapBeNVnAghKn+ca6v_bADhXy5k8hsPJaa-pyv7BuA@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="0-1556036501-1510909267=:94555"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ppcn-b90rIxS2VqKLPu6LYUdQVk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 09:01:16 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1556036501-1510909267=:94555
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: 8BIT


Serious suggestion: Could we do a crowsource funding and reprint
this historic shirt for distribution by mail or in London? We
used to have a Cafe Press page too, is that still alive?
\

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office: +1 415-550-9433
Cell:   +1 415-370-4628
Docomo: +81 090 3337-9311
E-mail: olejacobsen@me.com
Skype: organdemo


On Fri, 17 Nov 2017, Shahanaj RBT wrote:

> I  am  attending  remotely, May  I have one please.😎
> 
> On Fri, Nov 17, 2017 at 9:02 AM, IESG Secretary <iesg-secretary@ietf.org>
> wrote:
> 
> > But if you want one there are a very few 3XL size t-shirts available.
> > First come first served.
> >
> > Again, 3XL only.
> >
> > _______________________________________________
> > 100all mailing list
> > 100all@ietf.org
> > https://www.ietf.org/mailman/listinfo/100all
> >
> 
--0-1556036501-1510909267=:94555--


From nobody Fri Nov 17 01:41:45 2017
Return-Path: <prvs=1494ff0e50=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 2C47F126CE8 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 01:41:43 -0800 (PST)
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 FEyl1QRTAQio for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 01:41:40 -0800 (PST)
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 86471124D6C for <ietf@ietf.org>; Fri, 17 Nov 2017 01:41:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510911697; x=1511516497; 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=cF+yhBlAElQjbjwDulrTGPi0L cpIc8o/oDA1u/W76U4=; b=NMS7fHu1ViySai9aYkWBvJaeTLqhTKmTKzZwPtpMx Ru0NJpG4D+2/h5xM6O1IjsSXXW8kex2KNmdsvCqA7Q8b1ZLvNLQstHISjBJ4bP4Y uY9wTE0IGNG+erUH180D67QPMBWGo3IBox6Etm6/MdYCaRYdj5UMC3OkbHJv4qLe ws=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=m0eXAYL45yxlpUMNsA9s1FGcpUreYk+XqHDAUKqOEoPbm9sXjhGBoxVY47cv ptIKX32Wztyke+fkej3yaraSFQ8gzb7GgUfbJ4SqRZkJ51HE1yhvRj1vX 9q/mFkuZcCreHW8dCk786h66qYa+XSEu4ZAsDaYLs99obV72Rjs6z0=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 10:41:37 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 10:41:35 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005626689.msg for <ietf@ietf.org>; Fri, 17 Nov 2017 10:41:35 +0100
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:171117:md50005626689::p/N5J0yzlnc2hJ4E:00000tD/
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Fri, 17 Nov 2017 17:41:24 +0800
Subject: Re: delayed emails
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <6D2F43DA-B02B-42F9-8D00-68689E718E98@consulintel.es>
Thread-Topic: delayed emails
References: <25DB30C9-5289-4F4E-8308-1AB71E8A4477@consulintel.es> <alpine.OSX.2.01.1711161845180.69466@ole-pro.local> <F2DD1981-CC9C-41FE-9E3A-204BE67CB080@consulintel.es> <CABL0ig7VGMy8XDDC0VrM1GcUxYt-5Yb12wsB2gzW+yU2+LjWqA@mail.gmail.com>
In-Reply-To: <CABL0ig7VGMy8XDDC0VrM1GcUxYt-5Yb12wsB2gzW+yU2+LjWqA@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/NoLK38AJTrIFdGm5byuxJ_wuKjY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 09:41:43 -0000

Hi Glen,

I noticed the problem not just for the ietf@ietf.org list, but for 100atten=
dees, 6man, v6ops, homenet, etc.

I will try to find a couple of those emails =E2=80=A6 but because they are =
archived, I delete them when I respond or read them =E2=80=A6

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Glen <glen@amsl.com>
Responder a: <glen@amsl.com>
Fecha: viernes, 17 de noviembre de 2017, 17:21
Para: <ietf@ietf.org>
Asunto: Re: delayed emails

    Jordi wrote:
     > I=E2=80=99ve noticed during this week that all the IETF mail explode=
rs are getting big delays (several hours).    I=E2=80=99ve investigated my =
email server, and don=E2=80=99t looks as any internal problem in my side.  =
Just wondering if somebody else noticed this, or even if the secretariat ca=
n check it, or if something has changed recently that can cause that.
   =20
   =20
    Hi Jordi -
   =20
   =20
    The secretariat can indeed check it, but the IT team does not generally=
 monitor the IETF discussion list, since that's intended as general chat fo=
r IETF participants, and is rather busy. =20
   =20
   =20
    Instead, we have a trouble ticket queue that staff monitors, which can =
be reached at:  ietf-action@ietf.org .
   =20
   =20
    I have checked, and the server is not running slow at the moment, and o=
ur monitoring systems have not reported any delays in Mailman or email proc=
essing.
   =20
   =20
    Of course, mail can be delayed for lots of reasons; but, generally, an =
examination of the mail headers "Received" lines can tell you where the del=
ay occurred, and, often, what the cause was.
   =20
   =20
    If you have received an email that you feel has been delayed, and are u=
nable to determine where the delay occurred, please do forward the message =
- with all headers intact (which may require that you paste the headers int=
o the message body) - to ietf-action@ietf.org, and I or one of my team will=
 be happy to analyze it for you.
   =20
    But just wanted to make clear and remind everyone that we are *there* t=
o help - but we are not *here* to help (on this particular mailing list) :-=
) - so please do reach out to ietf-action@ietf.org if you need anything fro=
m us.
   =20
   =20
    (And of course, if any of you feel that you're not getting a response t=
here, please do escalate to me directly at glen@amsl.com and I will handle =
things personally for you.  This is never a problem, it is why I am here.)
   =20
   =20
    Ole wrote:
   =20
    > On the IETF100 list I just received a warning about excessive bounces=
 and that my membership would be cancelled :-(  But I have received lots of=
 mail on the list, so perhaps the problem is a busy server.
   =20
    I do see bounces from me.com <http://me.com> for you Ole, and I will re=
ply to you off-list right now with details.
   =20
    Glen
   =20
   =20
   =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

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Fri Nov 17 02:03:41 2017
Return-Path: <ajs@crankycanuck.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 671C1124217 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 02:03:39 -0800 (PST)
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, 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=yitter.info header.b=OCIndfDY; dkim=pass (1024-bit key) header.d=yitter.info header.b=e+F9Ukv7
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qu183hp68vNm for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 02:03:38 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C296120724 for <ietf@ietf.org>; Fri, 17 Nov 2017 02:03:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 694BABF56B; Fri, 17 Nov 2017 10:03:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1510913017; bh=VaXWLbmeNqoVwVRtdC/vme1ETLvp4inGW0kCJDA2hzY=; h=From:To:Date:In-Reply-To:References:Subject:From; b=OCIndfDYDGtQZCdv9+YtkJuVaEvNoftCeUAiYDGaXo9NktKNOONtmagNQGVK88O6e T7cUIvF4I/HCIF6FtZc5n0g5Wv2boTYLrsNdEEVTo4n7tugRz9Z1oDlX34mUvrtnlF ZnwaWXeaVuKT75CNj4al2Mj7CTo/fiHakBkRGXwo=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CdzJwrQ0raV6; Fri, 17 Nov 2017 10:03:36 +0000 (UTC)
From: Andrew Sullivan <ajs@crankycanuck.ca>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1510913016; bh=VaXWLbmeNqoVwVRtdC/vme1ETLvp4inGW0kCJDA2hzY=; h=From:To:Date:In-Reply-To:References:Subject:From; b=e+F9Ukv7bhcCWfQB+PlAVwk7kTP376aFXwWThA2jgtEAEg5Ipc5bjLiKuShcsm11D zm8QVE79P1Pbniisl+dKsXX9rgn+aDS306wWHWCcuoqok3YY+IxYodltXnNvuQR2ug LcghMgohHh2vFLE5bVp70elsI9hokeoBtesFFpHI=
To: <adrian@olddog.co.uk>, <jordi.palet@consulintel.es>, <ietf@ietf.org>
Date: Fri, 17 Nov 2017 18:03:29 +0800
Message-ID: <15fc96eaeb8.2772.9bc7627f4bf0daf95da66808f3dcb332@crankycanuck.ca>
In-Reply-To: <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk>
Subject: RE: On audio quality requirements for IETF meetings
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xFoF7eE0M3a-D_XLIVuCDs5Qs_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: Fri, 17 Nov 2017 10:03:39 -0000

I also find my aging and decreasingly capable ears had a hard time in this 
venue.  I wonder whether this might better be discussed on the meeting 
list, however.

A

Please excuse my clumbsy thums



----------
On November 17, 2017 11:15:19 "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> You are not alone!
> Conference centre PA not good.
> Mics very distance-sensitive.
> Not so bad that unusable, but hard work.
> Adrian
>
>> By the way … maybe I’m starting to suffer hearing problems, don’t noticed
>> before, but in this meeting, I’ve real difficulties to heard and consequently
>> understand people at the mike when I was presenting.
>>
>> I think it will be interesting to know if Ingemar and I, are alone on this …
>



From nobody Fri Nov 17 02:38:47 2017
Return-Path: <mersue@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 CE1BA1267BB for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 02:38:45 -0800 (PST)
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 J63fDydQipI3 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 02:38:43 -0800 (PST)
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 A84A51242EA for <ietf@ietf.org>; Fri, 17 Nov 2017 02:38:43 -0800 (PST)
Received: by mail-pg0-x229.google.com with SMTP id u3so1681070pgn.7 for <ietf@ietf.org>; Fri, 17 Nov 2017 02:38:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=OAUHBteBgnuyS0sszTup4Kno5QflyHHqdDEXuTZ8Ae8=; b=GLuGyic3IR/5a7oyZrdjDrZPUVPtf7UoViRZrehjb7yATDYJDk1Ask0kxv/BpK6vnB 5uMVgqY9D++KFAU1i7WEjTkRO/DqqtrvCpBiL3jF5Sy47QCOX0wzppeC4fERWe6KIM24 Lf3QzogXwEnD5zmY5Deni3pPIpGFlizF9b5LACyHfHb8JW1kUgh0ez5ArR4GRDAmTbYX yGd6OJir/1K+9oLDLvF8gAQK5ft9bayEcMPjzkzKZSj4A47shKFd1J7RMuj+d+bjAG4o cPlJ9tXEezhONn0I6WPoH9uEm/7LQdDHMhH4ecVDWY8TLnPGyUGXia+HB6sOyXiR1XDy Xdzw==
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:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:content-language :thread-index; bh=OAUHBteBgnuyS0sszTup4Kno5QflyHHqdDEXuTZ8Ae8=; b=B9HJV0uSDssvkAqpiDzLaXyaWXEU3nmiZHC5qm0cqeciTdy7tH4HLlW42/EEAK5cbZ g3AIE6G/64wFfp5tjL0xjB65B1u52jBi996MBlzw4SpM80C62E5nYHZj+FCjVhoKeHRE 6WsInl6tWb3qYEXz8J7Lkzu+quQosKGinbLC7mL4CNElwFFusKCTIVaeifzksZ7zK59H vcXuKDMsga51edOtd1zTpdHp8C77Fdg5dhRgiM8mU6S/I3j7R64eiktyZ6aw//OeQUkj EMCBKAJBLMNdkspb80YZ+Gj0nw/fJMjANS7fKavxj73MQuzOFLem2Q4eZkWtiAIxIF9y hblw==
X-Gm-Message-State: AJaThX6gzKT7MGyVCAFOjOuuC9ab8bikJx90SdUFCnHoxD76KfANF66M A9p+a+TV6GQguG3qcoAFrcnn3w==
X-Google-Smtp-Source: AGs4zMb2XE2VLvnubr1PxYKy94DRZRB/nnetEdyId+Auv38cmY1TTSsK3UH/xlkuYBrXTnQBdnQ0Ow==
X-Received: by 10.101.100.216 with SMTP id t24mr4580721pgv.439.1510915123079;  Fri, 17 Nov 2017 02:38:43 -0800 (PST)
Received: from DESKTOPFLHJVQJ ([2001:67c:1232:144:4ca7:95a6:24ad:549c]) by smtp.gmail.com with ESMTPSA id u7sm6533857pfh.142.2017.11.17.02.38.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 02:38:42 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'Ole Jacobsen'" <olejacobsen@me.com>, "'Shahanaj RBT'" <shahanajabc@gmail.com>
Cc: <ietf@ietf.org>
References: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com> <CALcGQd5HuapBeNVnAghKn+ca6v_bADhXy5k8hsPJaa-pyv7BuA@mail.gmail.com> <alpine.OSX.2.01.1711170059290.94555@ole-pro.local>
In-Reply-To: <alpine.OSX.2.01.1711170059290.94555@ole-pro.local>
Subject: RE: [100all] Very Few T-shirts Left
Date: Fri, 17 Nov 2017 18:38:42 +0800
Message-ID: <01ec01d35f90$3e4f2560$baed7020$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: de
Thread-Index: AQNkPKI62+Lq9YgD2Ou3Ojz7i/QxtAGvcYgYAY7fWPSf3LRTIA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AQWJRO_OHjZ7wCHAztgbokg0lwg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 10:38:46 -0000

Yes. It is: http://www.cafepress.com/ietf/7211616

Agree. IETF 100 shirt should be added.

Cheers,
Mehmet

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ole Jacobsen
> Sent: Friday, November 17, 2017 5:01 PM
> To: Shahanaj RBT <shahanajabc@gmail.com>
> Cc: ietf@ietf.org
> Subject: Re: [100all] Very Few T-shirts Left
>=20
>=20
> Serious suggestion: Could we do a crowsource funding and reprint this
> historic shirt for distribution by mail or in London? We used to have =
a Cafe
> Press page too, is that still alive?
> \
>=20
> Ole
>=20
>=20
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office: +1 415-550-9433
> Cell:   +1 415-370-4628
> Docomo: +81 090 3337-9311
> E-mail: olejacobsen@me.com
> Skype: organdemo
>=20
>=20
> On Fri, 17 Nov 2017, Shahanaj RBT wrote:
>=20
> > I  am  attending  remotely, May  I have one please.=F0=9F=98=8E
> >
> > On Fri, Nov 17, 2017 at 9:02 AM, IESG Secretary
> > <iesg-secretary@ietf.org>
> > wrote:
> >
> > > But if you want one there are a very few 3XL size t-shirts =
available.
> > > First come first served.
> > >
> > > Again, 3XL only.
> > >
> > > _______________________________________________
> > > 100all mailing list
> > > 100all@ietf.org
> > > https://www.ietf.org/mailman/listinfo/100all
> > >
> >


From nobody Fri Nov 17 03:15:28 2017
Return-Path: <prvs=1494ff0e50=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 B87E21205F0 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 03:15:26 -0800 (PST)
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 bqX7g-3SANGv for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 03:15:25 -0800 (PST)
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 EAA3312008A for <ietf@ietf.org>; Fri, 17 Nov 2017 03:15:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510917323; x=1511522123; 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=ENO2/y+0UCFlLToqFCij1ZKpv 9xn6Ago9CmN4mYO6Ws=; b=PHS43L8dwoNg+weOXBc8T1QJbdvT5BIf6E1AvESQm XlbApGDDKBBGD4JCPUtztu44MdrTENMHHDQBh5en9NBcNl7xEM8UrBD03ofaDgag b3cfmIXU+B5xg3d09LnJD9bohFkH9ei4p66zyHwr64x8Iy/TcWrFWgYASfvYTVLD R4=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=i6bpTNNM7Z2+pp7vda90BakGqA04kFyL9Wt00S29lB54Q18qSlV6SFvTN2xg mpDPlRpJEf9hOcLNp2LdFUnUlCB2PDY6qeXrdS2DZ/6j5DFvEJTmOHxAI 8AGyYLtiX6+EbzaRWILUFmkk6EeE2W9OuzWwxZl+qfB6wHpJzk6V+s=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 12:15:23 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 12:15:22 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005626772.msg for <ietf@ietf.org>; Fri, 17 Nov 2017 12:15:21 +0100
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:171117:md50005626772::wY5UIL6lX5d5LAAu:00005nAo
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Fri, 17 Nov 2017 19:15:03 +0800
Subject: Re: On audio quality requirements for IETF meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <CD1D0A64-9A08-4D67-BB5E-8BF71BD13E5F@consulintel.es>
Thread-Topic: On audio quality requirements for IETF meetings
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <15fc96eaeb8.2772.9bc7627f4bf0daf95da66808f3dcb332@crankycanuck.ca>
In-Reply-To: <15fc96eaeb8.2772.9bc7627f4bf0daf95da66808f3dcb332@crankycanuck.ca>
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/h6_jA2_c6fmHe4_xwB_nglYcDTA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 11:15:27 -0000

Because I=E2=80=99m trying to find the right text to put in the document, f=
rom audio experts, and having a bigger audience list will make it easier?

Just forgot to say to contact me unicast, if we want to avoid noise, to pro=
vide inputs on that.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Andrew Sullivan <ajs@crankyca=
nuck.ca>
Responder a: <ajs@crankycanuck.ca>
Fecha: viernes, 17 de noviembre de 2017, 18:21
Para: <adrian@olddog.co.uk>, <jordi.palet@consulintel.es>, <ietf@ietf.org>
Asunto: RE: On audio quality requirements for IETF meetings

    I also find my aging and decreasingly capable ears had a hard time in t=
his=20
    venue.  I wonder whether this might better be discussed on the meeting=
=20
    list, however.
   =20
    A
   =20
    Please excuse my clumbsy thums
   =20
   =20
   =20
    ----------
    On November 17, 2017 11:15:19 "Adrian Farrel" <adrian@olddog.co.uk> wro=
te:
   =20
    > You are not alone!
    > Conference centre PA not good.
    > Mics very distance-sensitive.
    > Not so bad that unusable, but hard work.
    > Adrian
    >
    >> By the way =E2=80=A6 maybe I=E2=80=99m starting to suffer hearing pr=
oblems, don=E2=80=99t noticed
    >> before, but in this meeting, I=E2=80=99ve real difficulties to heard=
 and consequently
    >> understand people at the mike when I was presenting.
    >>
    >> I think it will be interesting to know if Ingemar and I, are alone o=
n this =E2=80=A6
    >
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Fri Nov 17 03:23: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 A7036127201 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 03:23:54 -0800 (PST)
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 e9hvlySKSkKQ for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 03:23:53 -0800 (PST)
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 E306912008A for <ietf@ietf.org>; Fri, 17 Nov 2017 03:23:52 -0800 (PST)
Received: by mail-wm0-x234.google.com with SMTP id 9so5736028wme.4 for <ietf@ietf.org>; Fri, 17 Nov 2017 03:23:52 -0800 (PST)
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:content-language; bh=hX2DC9aC7B9AB0L/9cMNo4/ZShadzTwMqBb3ekQeFu4=; b=uL+YtYTcW3K8PuqN/5vt4YDky+BHObV6h1AXDvKCUEi1e3zpZkof2qRrpdJ3Tbm/tm NoO6pobwYaiJpsTmnsFsiRnl7q+LCD+j1JDCYqR3/tZbVkjaI+dlOWZfw/lC6KvbD60t lqjdNSYvKVWtUapVOQ/tshpbjovZEvnCkSDrNnAEDqb0pyFh52ylS5zE9aq+h2KbKnZH KtzHRBcnQ4sYFBP+kfZNgajj3UG71rX9aWzcv/tEMpimxXlgSSRF5lfWPgdCborbE0d7 dYmXaALuzW9CdVHxuUmlZStYjsvm+P2kBEbj47PW5cEf4SNXbyKvq6R+Z7yLAz+NKH4+ 8yRQ==
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 :content-language; bh=hX2DC9aC7B9AB0L/9cMNo4/ZShadzTwMqBb3ekQeFu4=; b=NKv7smvssfAEtUc+APR9XwecW6BSpCj8FxYSb2TuWc6l5iXDAfWamH+9NXRJ7C9p9w a3/qeAtWogcCjpQGlwVpnNgiaPiiFByzt1948BJRm35igHfXzSIqMenP/7EXG3mYqstM aPWpdesN9bndcCbqK4lsjbyjEwDDRbQnM/0ACeoxfXsOFxRYesdITBNht69LJoHYSat4 6SDa7l2H1GV2fkfzqUOJ6vwnWzVa/xUh9rPhlaZp3TyYfyjhpFpjcwI43UZYcjSkjPMX jY3dBLJxocXpkq0VybnSLW6zY0jSOVfM4P+9Pf/bNXcgPn0cXG23vpiSiYtnu4+ituW5 s+RQ==
X-Gm-Message-State: AJaThX7hUp2oAtMxDAHV6pNRUDAST6CbHrfLYq0P7ghKJvogE5NtDtz7 X37PhF4ZpCTntipwLHeO5+8ll+BG
X-Google-Smtp-Source: AGs4zMYfIPjodVwz7ytowoEr0o8FgkGCWvAghUGykpjuAQNZ1WbqoAB6ARNi8D9XuwRtW1RCq+ziyw==
X-Received: by 10.80.174.2 with SMTP id c2mr2002260edd.93.1510917831271; Fri, 17 Nov 2017 03:23:51 -0800 (PST)
Received: from ?IPv6:2001:67c:1232:144:acb6:b599:d1bf:fff3? ([2001:67c:1232:144:acb6:b599:d1bf:fff3]) by smtp.gmail.com with ESMTPSA id w28sm2452983edl.16.2017.11.17.03.23.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 03:23:50 -0800 (PST)
Subject: Re: On audio quality requirements for IETF meetings
To: adrian@olddog.co.uk, jordi.palet@consulintel.es, ietf@ietf.org
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <ca53972b-72ac-5aa9-8465-c8d51703daaa@gmail.com>
Date: Fri, 17 Nov 2017 11:23:47 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tLN2t_hEBgrW0jqK23ZKyXppQZY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 11:23:55 -0000

+1

I know my hearing is not as good as it once was but it is normally OK at 
IETF. Not so this time. It was hard to hear the presenter at times and 
partiularly hard to hear the questions from the Mic when I was 
presenting. We need much clearer audion going forwards.

- Stewart

On 17/11/2017 03:14, Adrian Farrel wrote:
> You are not alone!
> Conference centre PA not good.
> Mics very distance-sensitive.
> Not so bad that unusable, but hard work.
> Adrian
>
>> By the way … maybe I’m starting to suffer hearing problems, don’t noticed
>> before, but in this meeting, I’ve real difficulties to heard and consequently
>> understand people at the mike when I was presenting.
>>
>> I think it will be interesting to know if Ingemar and I, are alone on this …


From nobody Fri Nov 17 07:30:29 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 71D0F126FB3 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 07:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2Lo2TDLcBFy for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 07:30:25 -0800 (PST)
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 221FB1270A0 for <ietf@ietf.org>; Fri, 17 Nov 2017 07:30:25 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eFib0-0000Vk-5l; Fri, 17 Nov 2017 10:30:22 -0500
Date: Fri, 17 Nov 2017 10:30:16 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
Subject: Re: IETF 100 MeetEcho connectivity
Message-ID: <CCC7DBB542CE27C082DD4B5F@PSB>
In-Reply-To: <6.2.5.6.2.20171116204548.1076f1a0@elandnews.com>
References: <5A08F73B.5040602@isdg.net> <20171113015919.GG26425@kduck.kaduk.org> <5A0C6E8F.4060105@isdg.net> <1db4c72e-7bb5-342f-b243-5d771005679f@gmail.com> <m2shdf55ol.wl-randy@psg.com> <5d369ad8-377f-ab24-be63-944ef6e25717@gmail.com> <4B1B3C4884E0809C0B360928@PSB> <6.2.5.6.2.20171116131140.114da858@elandnews.com> <E46F5E2121CB0D6474779767@PSB> <76ea9dff-441e-c262-00fa-a9b934b25538@meetecho.com> <6.2.5.6.2.20171116204548.1076f1a0@elandnews.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.10
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/FYrm7uhyjH9-x8uXZEOrLvaaFjU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 15:30:27 -0000

--On Thursday, November 16, 2017 20:53 -0800 S Moonesamy
<sm+ietf@elandsys.com> wrote:

> Hi John,
> At 07:02 PM 16-11-2017, Meetecho IETF support wrote:
>> It hasn't. Meetecho "Observer" mode still has audio + video +
>> slides  + jabber + etherpad. The only thing that is missing
>> is the  possibility to raise your hand to make comments
>> through the virtual queue.
> 
> The change where registration is required for Observer mode
> occurred as from IETF99.  Prior to that, registration was
> optional.

That is a different issue (see Mark Andrew's note).  

That change was made for the reasons Brian and I described in
earlier notes plus, IIR< a desire to get a little better handle
on who was using Meetecho and for what.  In particular, it may
make some difference -- in planning in prioritization of some
possible features -- what the proportions are between people who
are using it and actually remote and people using it while
sitting in a different WG meeting, an on-site hotel room, even
in the meeting room to get a better view of the slides, or the
NOC or some conference area.   The granularity by which those
distinctions can be made by distinguishing between people with
onsite registration IDs and those whose registration numbers are
offsite only are very poor; I assume we will sooner or later ask
at least the latter to check a "where are you" box.

Personally, because I'm very concerned about the issues of not
being able to identify those who are influencing decisions, if I
could choose to require that anyone making comments over an
official jabber  channel (e.g., a jabber room that is accessible
via the agenda, kept archivally as part of IETF activities,
and/or tracked by a jabber scribe) should be required to be
registered.  That is probably infeasible technically or more
trouble than it is worth, but that does not affect the
preference.  YNMD, especially if you see the risks differently.

best,
    john


From nobody Fri Nov 17 08:07: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 650BF128B27 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 08:07:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNB4JoikK_vT for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 08:07:52 -0800 (PST)
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 8272C1243FE for <ietf@ietf.org>; Fri, 17 Nov 2017 08:07:52 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eFjBE-0000YV-9J; Fri, 17 Nov 2017 11:07:48 -0500
Date: Fri, 17 Nov 2017 11:07:43 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <mellon@fugue.com>, adrian@olddog.co.uk
cc: ietf@ietf.org, jordi.palet@consulintel.es
Subject: Re: On audio quality requirements for IETF meetings
Message-ID: <0BE7DA22F8B14110F7EFFB66@PSB>
In-Reply-To: <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.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.10
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/xzvxLof3cI1ajJJa-n3a923mo2E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 16:07:54 -0000

--On Friday, November 17, 2017 11:21 +0800 Ted Lemon
<mellon@fugue.com> wrote:

> On Nov 17, 2017, at 11:14 AM, Adrian Farrel
> <adrian@olddog.co.uk> wrote:
>> Conference centre PA not good.
>> Mics very distance-sensitive.
>> Not so bad that unusable, but hard work.
> 
> Another issue is that the microphones kept running out of
> power, and there's no way to charge them.   Either we need
> someone other than the participants doing this, or else there
> needs to be resources in each room that chairs or others can
> use to get microphones working when they fail.

One difficulty is that every equipment requirement we impose is
likely to turn into another box (crate? but see below) of stuff
the secretariat or other provider has to drag to meetings, which
means more aggravation, higher costs and more customs risks,
etc.  A hotel that tells us exactly what audio and video
equipment they will have on hand as far in advance as we seem to
make decisions is probably lying, or at least saying something
for which they could reasonably say "things change and we had to
replace some gear when the meeting rolls around.   And testing
equipment several years in advance and making a facility
decisions on that basis is likely to be a really good, but not
particularly useful, way to overconstrain the choices.

That said, two observations:

(1) I know wires are unfashionable these days, but traditional
wired microphones rarely have problems with either running out
of power or with in-room EMI, including EMI caused by WiFi,
Bluetooth, and lots of other wireless things.  I have not yet
found out what a conference room or plenary would be like with
500 people running Wifi and Bluetooth keyboards, headsets, or
mice, but I'm fairly sure I don't want to.

(2) It appears to me that an increasing number of wireless
microphones, like many other wireless things, are either
USB-powered or USB-charged.  If we could somehow prefer, or
restrict ourselves to, such devices, preferably ones that can
run off external power rather than just requiring that the
batteries be charged, a small collection of "portable chargers"
might allow prevention and/or quick fixes to microphones with
dead or dying batteries.   

However, remember that such chargers and probably even the
microphones themselves typically use Li-ion batteries that are
increasingly restricted in transit because of fire concerns.
I've also been through airports that try to ban batteries over
some fairly low capacity entirely, whether in checked or
carry-on baggage.  So there may be significant constraints on
ways to address the problem.   At the same time, Jordi, you
could write a requirement that a facility have sufficient spares
or alternatives on hand to run however many microphones we need
all day, every day, for a week... or we could require wired
microphones with no internal batteries.   Not saying either
would be a good idea, but, if you are looking for something to
write down, that wouldn't be too hard.

best,
   john






From nobody Fri Nov 17 09:06:13 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 39933128CD5 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 09:06:11 -0800 (PST)
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=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 i0sA-np4eiJU for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 09:06:09 -0800 (PST)
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 8039B1243FE for <ietf@ietf.org>; Fri, 17 Nov 2017 09:06:09 -0800 (PST)
Received: by mail-pf0-x22a.google.com with SMTP id x7so2370206pfa.1 for <ietf@ietf.org>; Fri, 17 Nov 2017 09:06:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LabsvHt15/yhQrQyiOeB6QlpvFIstSI8bIUei7SBxaE=; b=qvDtm1K1/rv0OMbl9SI4sISUkPvvaZbOPdbRDD86CtlDOBXRSDLqG6YCfNS84NhQug yMuAAieliCLet6+JACa392Kb1QbehrP13xm599/h+Q/ix4nBtkW4Le4Ud3JWn/VYT2ZJ 9U8N2q3Y7k8VIVYXX3xeJNQX0bToeBabeU0g4P6aCVH3+YZmdAQYkUrUS45WDqrENfEP UhD8KPGpkHb02QAHpuGxU8iYpfZfETlM5gpBANVxBeo+WMJG1tvSjvjiDI8wsPzbiecu e03n42aHLuAivz1lHItY+FsJNauZ/WfbkylKnLwrMq9ATeTj4TvZUwNz2fsmI67BYb9s EzHw==
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=LabsvHt15/yhQrQyiOeB6QlpvFIstSI8bIUei7SBxaE=; b=rbFC21RGxoXeeELpxz5UBnKlwFVRlww+CpZf49rROAUwM0SGDWAQvc7MHeiJINofSc qnR3G/l3/Vi11atdxgKqeN4+rBq/WLZbVEcf3CiaiMAnl5Wjwnz8EUCypoFXaziK3xAz I+EjhjOyY7W7S1hM+PvFN8mMr8438raKf2dVHVWXxp54EIbW0BiPF1h4BEkN+U0lorxx 23rfuydW0AvsA3d5GAhRTMgS+/5TAV+RZ36Krt8XZC9KrZRSX4Z9NMq/9hLq5fQd+dOK IgjWtDiiIa4mxT0+LLTOiMOA6f2A7iS4lezyiHLmHVlkHZwxMzkvKDiudyaCnlpSHyBQ kZgg==
X-Gm-Message-State: AJaThX4LSNW5n8DR7keiLcxa6GRx5C1wFZf9QruVeVYrngtqCNvuswUG Q1lnbAFVitx1fXXB40c1jBJ17g==
X-Google-Smtp-Source: AGs4zMbsLvz1DY7zZZnTeo2rqS0+ug0h2bUDVOS7QMoKGQPk3g/my1c5GbhIraRWZ8DDJrXtYABVqA==
X-Received: by 10.98.217.133 with SMTP id b5mr2712305pfl.173.1510938368743; Fri, 17 Nov 2017 09:06:08 -0800 (PST)
Received: from ?IPv6:2001:67c:1232:144:1938:ace1:95ff:9e4a? ([2001:67c:1232:144:1938:ace1:95ff:9e4a]) by smtp.gmail.com with ESMTPSA id l13sm8157880pfj.73.2017.11.17.09.06.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Nov 2017 09:06:07 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: On audio quality requirements for IETF meetings
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <0BE7DA22F8B14110F7EFFB66@PSB>
Date: Sat, 18 Nov 2017 01:06:00 +0800
Cc: Adrian Farrel <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>, jordi.palet@consulintel.es
Content-Transfer-Encoding: quoted-printable
Message-Id: <DDD66A45-8A88-4CF5-8095-9614F9AD3BA3@fugue.com>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com> <0BE7DA22F8B14110F7EFFB66@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lsrPE7ZY_hEbIabak_QplCjZp7s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 17:06:11 -0000

These are all good points, John.   What I'm really arguing for is that =
whatever equipment is present at the venue, there should be sufficient =
information in the room, available to the chairs and their deputies, to =
manage it.   We wind up engaging in ad-hoc debugging when the mics go =
down anyway, so might as well empower us to actually fix them.   I think =
a lot of them just use 9-volt batteries or stacks of AA batteries =
anyway, so that's very easy to facilitate and relatively cheap as well.  =
 Just a matter of doing that inventory before the meeting starts, in the =
secretariat's copious and not-at-all-constrained free time during that =
period.   Or getting a volunteer to do it.   :)


From nobody Fri Nov 17 09:27:56 2017
Return-Path: <barryleiba@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 810F0128DE5; Fri, 17 Nov 2017 09:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.718
X-Spam-Level: 
X-Spam-Status: No, score=-1.718 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, 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, 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 Ob5WXW7-Cfri; Fri, 17 Nov 2017 09:27:46 -0800 (PST)
Received: from mail-it0-f47.google.com (mail-it0-f47.google.com [209.85.214.47]) (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 567121242F5; Fri, 17 Nov 2017 09:27:46 -0800 (PST)
Received: by mail-it0-f47.google.com with SMTP id y15so4900706ita.4; Fri, 17 Nov 2017 09:27:46 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QOPIMPnffGsZyG7CvyOrBTz8+m9ph1SLsr814Y3JxaE=; b=Oyhe4FUvsPYHt6bGYvDTnTxsrgoHNoAYl5F7g8+EiAVBcbM7kFwLMhENeVFVo+Ct88 X+9Xj8TS8a6hwlee+G341UZaxwluNzGY7Q4+kJ1s98coMKh9nSnNERZT+itDsyNP3qeU 2Nnnz0vH6otX2o0q58xdiyByCB4bWYd1rtSEdq5OsGk9MOcdmx4ibIzfDzeOX6CJJJky Duy9eXFNWmMMszt3yybyh9EpDInmDIR5+zw0uoed9DerUi0MWvlmtXSLLcpk/fw9PMZb 3fxSsx4j89ffAgvjgow/BqD8VCu8QjVaK+H4ebdXYQGaFpePl5jro9d2ujo1zpGFizAN 4qrA==
X-Gm-Message-State: AJaThX4w1Mu8weDBL+bcz+YwQ3BsFbgSyy7oWy0xmdhiOkTjpSZ5Mk2U aB5oC5qB7/wnvtZim+p1bbl9xmjcnnFqjZVQ164=
X-Google-Smtp-Source: AGs4zMaWrhVWQw99R0xVP7SzZXnGNCd6INipi9qJJRYZYBw0Tn8e8357k8fMqd0xSIXNaoQeTiKE36JhqO8UxcVeBXs=
X-Received: by 10.36.164.75 with SMTP id v11mr8124121iti.33.1510939665335; Fri, 17 Nov 2017 09:27:45 -0800 (PST)
MIME-Version: 1.0
References: <151046377334.30804.5873766900092971520@ietfa.amsl.com> <20171117081354.GC57159@scs.stanford.edu>
In-Reply-To: <20171117081354.GC57159@scs.stanford.edu>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 17 Nov 2017 17:27:33 +0000
Message-ID: <CALaySJLEzY8j3Kamavkk3dyfV=c-OvMpu+nauR5-BBBYqFoAAg@mail.gmail.com>
Subject: Re: Secdir telechat review of draft-ietf-tcpinc-tcpcrypt-09
To: Daniel B Giffin <dbg@scs.stanford.edu>
Cc: draft-ietf-tcpinc-tcpcrypt.all@ietf.org, ietf@ietf.org, secdir@ietf.org,  tcpinc@ietf.org
Content-Type: multipart/alternative; boundary="f403045fbba80788f8055e310ed0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-774a-3qVw2sg42sS7Ztm-Kf0Xc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 17:27:49 -0000

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

All responses perfect; thanks.  I don=E2=80=99t think there=E2=80=99s a nee=
d for a formal
citation to TCP-ENO for the registry, as it won=E2=80=99t be needed once th=
e
registry is created.  It=E2=80=99s only needed for review now, so people li=
ke me
don=E2=80=99t scratch our heads.

Carry on...

Barry


On Fri, Nov 17, 2017 at 12:16 AM Daniel B Giffin <dbg@scs.stanford.edu>
wrote:

> Thanks for the review!
>
> Barry Leiba wrote:
> > Reviewer: Barry Leiba
> > Review result: Has Issues
> >
> > I=E2=80=99ve looked at Stephen Kent=E2=80=99s review and the discussion=
 thereof, and have
> > little to add to that.  A couple of small things:
> >
> > 1. Section 3 says that the subsections =E2=80=9Cdescribes the tcpcrypt =
protocol
> at an
> > abstract level.=E2=80=9D  There is no sense in which this description i=
s
> abstract, and
> > I=E2=80=99d prefer that we not try to say it is, because that gives a r=
eader an
> > expectation that it will be high-level, and perhaps even non-normative.
> Maybe
> > this?:
> >
> > NEW
> >    This section provides details of the operation of the tcpcrypt
> protocol.
> >    The wire format of all messages is specified in Section 4.
> > END
>
> Good point, thanks -- for the next draft I've gone with
> something very similar:
>
>    This section describes the operation of the tcpcrypt protocol.  The
>    wire format of all messages is specified in Section 4.
>
> > 2. In Section 7 (IANA), you say:
> >
> >    Tcpcrypt's TEP identifiers will need to be incorporated in IANA's
> >    "TCP encryption protocol identifiers" registry under the
> >    "Transmission Control Protocol (TCP) Parameters" registry
> >
> > I can find no such registry.  Can you help me here, maybe give me a URL=
?
>
> Right, that registry is defined in TCP-ENO, which I
> understand would be published in tandem with this draft.
> Does that solve the problem, or ought we provide a reference
> to TCP-ENO here?
>
> For now, I've provided at least a hint by mentioning TCP-ENO
> at the beginning of that sentence:
>
>    For use with TCP-ENO's negotiation mechanism, tcpcrypt's TEP
>    identifiers will need to be incorporated in IANA's "TCP encryption
>    protocol identifiers" registry under the "Transmission Control
>    Protocol (TCP) Parameters" registry, as in Table 4 below.  The
>          [...]
>
> > Also, with respect to the new =E2=80=9Ctcpcrypt AEAD Algorithm" registr=
y:
> >
> >    Future assignments are to be made under the "RFC Required" policy
> >
> > Note that that policy allows for assignments to be made in any RFC
> stream,
> > which includes the IRTF, the IAB, and the Independent Stream.  Do you
> really
> > want people to be able to send documents to the Independent Stream
> Editor, and
> > to have them published and make assignments with minimal review?
> >
> > You might consider whether =E2=80=9CIETF Review=E2=80=9D is more approp=
riate.  That
> allows RFCs
> > of any type (Standards Track, Informational, Experimental, BCP), but
> requires
> > that they be in the IETF stream and have a formal IETF last call.
>
> Following the discussion about assignment policy in another
> thread, I've updated this to use the same policy as TCP-ENO.
> The paragraph on the "tcpcrypt AEAD Algorithm" registry now
> reads:
>
>    In Section 4.1, this document defines "sym_cipher" specifiers in the
>    range 0x0001 to 0xFFFF inclusive, for which IANA is to maintain a new
>    "tcpcrypt AEAD Algorithm" registry under the "Transmission Control
>    Protocol (TCP) Parameters" registry.  The initial values for this
>    registry are given in Table 5 below.  The AEAD algorithms named there
>    are defined in Section 6.  Future assignments are to be made upon
>    satisfying either of two policies defined in [RFC8126]: "IETF Review"
>    or (for non-IETF stream specifications) "Expert Review with RFC
>    Required."  IANA will furthermore provide early allocation [RFC7120]
>    to facilitate testing before RFCs are finalized.
>
>
> > It will also help IANA if you make it clear what the valid range of
> values is
> > for the =E2=80=9CValue=E2=80=9D column.  Is 0x0000 valid?  Is 0xFFFF th=
e maximum?
> Explicitly
> > saying that values must be in the range 0x0001 to 0xFFFF inclusive will
> be
> > helpful.  (I say this with particular note that you changed how the
> Value field
> > is specified between -07 and -09, so this clearly has not even been
> clear to
> > the spec developers.)
>
> Thanks, I've added that as you can see above.
>
> daniel
>
> --
Barry
--
Barry Leiba  (barryleiba@computer.org)
http://internetmessagingtechnology.org/

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

<div dir=3D"auto">All responses perfect; thanks.=C2=A0 I don=E2=80=99t thin=
k there=E2=80=99s a need for a formal citation to TCP-ENO for the registry,=
 as it won=E2=80=99t be needed once the registry is created.=C2=A0 It=E2=80=
=99s only needed for review now, so people like me don=E2=80=99t scratch ou=
r heads.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Carry on...</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto">Barry</div><div dir=3D"auto=
"><br></div><div><br><div class=3D"gmail_quote"><div>On Fri, Nov 17, 2017 a=
t 12:16 AM Daniel B Giffin &lt;<a href=3D"mailto:dbg@scs.stanford.edu">dbg@=
scs.stanford.edu</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">Tha=
nks for the review!<br>
<br>
Barry Leiba wrote:<br>
&gt; Reviewer: Barry Leiba<br>
&gt; Review result: Has Issues<br>
&gt;<br>
&gt; I=E2=80=99ve looked at Stephen Kent=E2=80=99s review and the discussio=
n thereof, and have<br>
&gt; little to add to that.=C2=A0 A couple of small things:<br>
&gt;<br>
&gt; 1. Section 3 says that the subsections =E2=80=9Cdescribes the tcpcrypt=
 protocol at an<br>
&gt; abstract level.=E2=80=9D=C2=A0 There is no sense in which this descrip=
tion is abstract, and<br>
&gt; I=E2=80=99d prefer that we not try to say it is, because that gives a =
reader an<br>
&gt; expectation that it will be high-level, and perhaps even non-normative=
.=C2=A0 Maybe<br>
&gt; this?:<br>
&gt;<br>
&gt; NEW<br>
&gt;=C2=A0 =C2=A0 This section provides details of the operation of the tcp=
crypt protocol.<br>
&gt;=C2=A0 =C2=A0 The wire format of all messages is specified in Section 4=
.<br>
&gt; END<br>
<br>
Good point, thanks -- for the next draft I&#39;ve gone with<br>
something very similar:<br>
<br>
=C2=A0 =C2=A0This section describes the operation of the tcpcrypt protocol.=
=C2=A0 The<br>
=C2=A0 =C2=A0wire format of all messages is specified in Section 4.<br>
<br>
&gt; 2. In Section 7 (IANA), you say:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Tcpcrypt&#39;s TEP identifiers will need to be incorporat=
ed in IANA&#39;s<br>
&gt;=C2=A0 =C2=A0 &quot;TCP encryption protocol identifiers&quot; registry =
under the<br>
&gt;=C2=A0 =C2=A0 &quot;Transmission Control Protocol (TCP) Parameters&quot=
; registry<br>
&gt;<br>
&gt; I can find no such registry.=C2=A0 Can you help me here, maybe give me=
 a URL?<br>
<br>
Right, that registry is defined in TCP-ENO, which I<br>
understand would be published in tandem with this draft.<br>
Does that solve the problem, or ought we provide a reference<br>
to TCP-ENO here?<br>
<br>
For now, I&#39;ve provided at least a hint by mentioning TCP-ENO<br>
at the beginning of that sentence:<br>
<br>
=C2=A0 =C2=A0For use with TCP-ENO&#39;s negotiation mechanism, tcpcrypt&#39=
;s TEP<br>
=C2=A0 =C2=A0identifiers will need to be incorporated in IANA&#39;s &quot;T=
CP encryption<br>
=C2=A0 =C2=A0protocol identifiers&quot; registry under the &quot;Transmissi=
on Control<br>
=C2=A0 =C2=A0Protocol (TCP) Parameters&quot; registry, as in Table 4 below.=
=C2=A0 The<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[...]<br>
<br>
&gt; Also, with respect to the new =E2=80=9Ctcpcrypt AEAD Algorithm&quot; r=
egistry:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 Future assignments are to be made under the &quot;RFC Req=
uired&quot; policy<br>
&gt;<br>
&gt; Note that that policy allows for assignments to be made in any RFC str=
eam,<br>
&gt; which includes the IRTF, the IAB, and the Independent Stream.=C2=A0 Do=
 you really<br>
&gt; want people to be able to send documents to the Independent Stream Edi=
tor, and<br>
&gt; to have them published and make assignments with minimal review?<br>
&gt;<br>
&gt; You might consider whether =E2=80=9CIETF Review=E2=80=9D is more appro=
priate.=C2=A0 That allows RFCs<br>
&gt; of any type (Standards Track, Informational, Experimental, BCP), but r=
equires<br>
&gt; that they be in the IETF stream and have a formal IETF last call.<br>
<br>
Following the discussion about assignment policy in another<br>
thread, I&#39;ve updated this to use the same policy as TCP-ENO.<br>
The paragraph on the &quot;tcpcrypt AEAD Algorithm&quot; registry now<br>
reads:<br>
<br>
=C2=A0 =C2=A0In Section 4.1, this document defines &quot;sym_cipher&quot; s=
pecifiers in the<br>
=C2=A0 =C2=A0range 0x0001 to 0xFFFF inclusive, for which IANA is to maintai=
n a new<br>
=C2=A0 =C2=A0&quot;tcpcrypt AEAD Algorithm&quot; registry under the &quot;T=
ransmission Control<br>
=C2=A0 =C2=A0Protocol (TCP) Parameters&quot; registry.=C2=A0 The initial va=
lues for this<br>
=C2=A0 =C2=A0registry are given in Table 5 below.=C2=A0 The AEAD algorithms=
 named there<br>
=C2=A0 =C2=A0are defined in Section 6.=C2=A0 Future assignments are to be m=
ade upon<br>
=C2=A0 =C2=A0satisfying either of two policies defined in [RFC8126]: &quot;=
IETF Review&quot;<br>
=C2=A0 =C2=A0or (for non-IETF stream specifications) &quot;Expert Review wi=
th RFC<br>
=C2=A0 =C2=A0Required.&quot;=C2=A0 IANA will furthermore provide early allo=
cation [RFC7120]<br>
=C2=A0 =C2=A0to facilitate testing before RFCs are finalized.<br>
<br>
<br>
&gt; It will also help IANA if you make it clear what the valid range of va=
lues is<br>
&gt; for the =E2=80=9CValue=E2=80=9D column.=C2=A0 Is 0x0000 valid?=C2=A0 I=
s 0xFFFF the maximum?=C2=A0 Explicitly<br>
&gt; saying that values must be in the range 0x0001 to 0xFFFF inclusive wil=
l be<br>
&gt; helpful.=C2=A0 (I say this with particular note that you changed how t=
he Value field<br>
&gt; is specified between -07 and -09, so this clearly has not even been cl=
ear to<br>
&gt; the spec developers.)<br>
<br>
Thanks, I&#39;ve added that as you can see above.<br>
<br>
daniel<br>
<br>
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div class=3D"gmail_=
signature" data-smartmail=3D"gmail_signature">Barry<br>--<br>Barry Leiba =
=C2=A0(<a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryle=
iba@computer.org</a>)<br><a href=3D"http://internetmessagingtechnology.org/=
" target=3D"_blank">http://internetmessagingtechnology.org/</a></div>

--f403045fbba80788f8055e310ed0--


From nobody Fri Nov 17 10:08:45 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 8DFFE1241FC for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 10:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ub1v2AZGYOsy for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 10:08:41 -0800 (PST)
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 C44A21200FC for <ietf@ietf.org>; Fri, 17 Nov 2017 10:08:41 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 99FA320072; Fri, 17 Nov 2017 13:10:29 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6D1C382B25; Fri, 17 Nov 2017 13:08:40 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: John C Klensin <john-ietf@jck.com>
cc: Ted Lemon <mellon@fugue.com>, adrian@olddog.co.uk, ietf@ietf.org, jordi.palet@consulintel.es
Subject: Re: On audio quality requirements for IETF meetings
In-Reply-To: <0BE7DA22F8B14110F7EFFB66@PSB>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com> <0BE7DA22F8B14110F7EFFB66@PSB>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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, 17 Nov 2017 13:08:40 -0500
Message-ID: <21658.1510942120@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ymd4bHyBz31NYK0p1oBEh2mI_FQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 18:08:43 -0000

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


John C Klensin <john-ietf@jck.com> wrote:
    > etc.  A hotel that tells us exactly what audio and video
    > equipment they will have on hand as far in advance as we seem to
    > make decisions is probably lying, or at least saying something

The NOC team visits a month or so in advance of each meeting, and maybe they
could verify what the audio situation is, and if really unacceptable, could
tell the secretariat to bring the extra box of stuff.

--
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+93Q3WUFAloPJagACgkQgItw+93Q
3WXbnAf6AwFx2c1/2RYk9xEJx6WdTT1pAb6n+DhxZHNxM+D0+8RAuO/fi9IiNiuS
eF3rJsofda6TP6qvhJ+enLZoILI6NJkZp2ZHoXqauW4nhc2hYxkc1K9xoxQy2JBL
K47qwnkTULWEqI2e3tnfgzHKye6BPV93IuUpm4lQkcPVC3ZHqKgiXG320VrsKYxY
IlieXtnFANIZQ1bY5XsCwf2bBCbaGBI2CzWCURf21DJABE6iRUMSvb7RmsU/JrIq
Z2fRyqvNrmlP91qESwRF+HUOsG9ZcIQZ4gpXDzX/iQUH4v509/AdouxfL8ixRNpa
kxFHJMcvAqCN5sDIaQ0vyWnCt8XEaQ==
=0neh
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Nov 17 10:11: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 428AE1292F5 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 10:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GToczGVeQb7H for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 10:11:21 -0800 (PST)
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 AF14E128D6F for <ietf@ietf.org>; Fri, 17 Nov 2017 10:11:21 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eFl6l-0000hB-Fo; Fri, 17 Nov 2017 13:11:19 -0500
Date: Fri, 17 Nov 2017 13:11:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <mellon@fugue.com>
cc: Adrian Farrel <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>, jordi.palet@consulintel.es
Subject: Re: On audio quality requirements for IETF meetings
Message-ID: <4AF2CBE17FC22EA2E3361A14@PSB>
In-Reply-To: <DDD66A45-8A88-4CF5-8095-9614F9AD3BA3@fugue.com>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com> <0BE7DA22F8B14110F7EFFB66@PSB> <DDD66A45-8A88-4CF5-8095-9614F9AD3BA3@fugue.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.10
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/Plz9kwzQ3gyaaIQNzEu46JKhfs0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 18:11:23 -0000

Ted,

I think we are on exactly the same page.  Dead batteries are
something that we can predict and have seen many times before.
There is little excuse for not being prepared to adjust and
repair in very close to real time rather than treating each
incident as new and then starting to scramble.  .  

And, yes, if the batteries are 9 volt or AAs, the issues I'm
concerned about with built-in rechargeables don't apply and
supplies can be obtained locally almost anywhere in the world,
so the logistical problems I mentioned really are no impediments.

Partially because of the time difference and unrelated
exhaustion, I got to fewer sessions than I usually do, but my
own impression was of things working nearly flawlessly from an
audio and video transmission and receipt standpoint.

   john

--On Saturday, November 18, 2017 01:06 +0800 Ted Lemon
<mellon@fugue.com> wrote:

> These are all good points, John.   What I'm really arguing for
> is that whatever equipment is present at the venue, there
> should be sufficient information in the room, available to the
> chairs and their deputies, to manage it.   We wind up engaging
> in ad-hoc debugging when the mics go down anyway, so might as
> well empower us to actually fix them.   I think a lot of them
> just use 9-volt batteries or stacks of AA batteries anyway, so
> that's very easy to facilitate and relatively cheap as well.
> Just a matter of doing that inventory before the meeting
> starts, in the secretariat's copious and
> not-at-all-constrained free time during that period.   Or
> getting a volunteer to do it.   :)





From nobody Fri Nov 17 10:18:46 2017
Return-Path: <prvs=1494ff0e50=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 635241243FE for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 10:18:45 -0800 (PST)
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 RBN-ftPfqEv0 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 10:18:43 -0800 (PST)
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 CE5C61200FC for <ietf@ietf.org>; Fri, 17 Nov 2017 10:18:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510942718; x=1511547518; 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=ppg56e7TDqIplrKn67niONzcx hf74Jf3+ydqVtdxn1A=; b=ZV2ABVKp8/NMiyzULAHuvZqXHgYORbM6//67BZm9g /UzVgtBrU2wFCKokV0B8/O2dx9f5mGIOLSdtPRFqB7FEGPCG9VEM5xKIzSYXd5BS J0fFa2mbQ7u177fCvrhIN6lkczeqIaKTEExCyftiSENOPfGos90XXWerrxlS/ZGv Ls=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=nsT7BxqtEXz2rjcA9QOCU7IUVYm2RTwKBo7TQIujlQ/qVtJksgubdRJCDs70 3330vjDUnUVRdiCB9TIO3Dm2JeFKCTaCP8YUiAz9KUykXP25IE5XzGAdy DeELYzloLkMj7GBv5myPujuPOUkX0OhZqZkVpfY/882WF1AjeudGR4=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Nov 2017 19:18:38 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Nov 2017 19:18:37 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005627478.msg for <ietf@ietf.org>; Fri, 17 Nov 2017 19:18:37 +0100
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:171117:md50005627478::GdZ4KWAWwomJmHZ9:00001Ggy
X-Return-Path: prvs=1494ff0e50=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Sat, 18 Nov 2017 02:18:21 +0800
Subject: Re: On audio quality requirements for IETF meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <2D51FAA9-D45B-468C-B5FD-A6CF729A0337@consulintel.es>
Thread-Topic: On audio quality requirements for IETF meetings
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com> <0BE7DA22F8B14110F7EFFB66@PSB> <21658.1510942120@obiwan.sandelman.ca>
In-Reply-To: <21658.1510942120@obiwan.sandelman.ca>
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/6tXXD40lE5wrVx67apgL8BrdbLc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 18:18:45 -0000

Depending on what and the quantity that you need to bring it may not be pos=
sible in one month, may need a customs process (temporary import and then c=
ancelling that via export).

If is only batteries, make sense probably sourcing locally, or even on-line=
 (amazon, e-bay, etc.). Otherwise, a local audio company.

But what I was asking was more on the line of =E2=80=9Cwhat audio quality=
=E2=80=9D we need for our meetings, in whatever terms an audio expert can d=
efine =E2=80=A6 There must be a way to fix that in the document.

I think all that is contracted by the secretariat, probably as part of the =
venue contract, but we are missing defining some more concrete =E2=80=9Caud=
io quality=E2=80=9D parameters.

I will ask directly the secretariat what is the actual =E2=80=9Cmodel=E2=80=
=9D for this.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Michael Richardson <mcr+ietf@=
sandelman.ca>
Responder a: <mcr+ietf@sandelman.ca>
Fecha: s=C3=A1bado, 18 de noviembre de 2017, 2:09
Para: John C Klensin <john-ietf@jck.com>
CC: <ietf@ietf.org>, <jordi.palet@consulintel.es>
Asunto: Re: On audio quality requirements for IETF meetings

   =20
    John C Klensin <john-ietf@jck.com> wrote:
        > etc.  A hotel that tells us exactly what audio and video
        > equipment they will have on hand as far in advance as we seem to
        > make decisions is probably lying, or at least saying something
   =20
    The NOC team visits a month or so in advance of each meeting, and maybe=
 they
    could verify what the audio situation is, and if really unacceptable, c=
ould
    tell the secretariat to bring the extra box of stuff.
   =20
    --
    Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
     -=3D IPv6 IoT consulting =3D-
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Fri Nov 17 12:27:30 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 06B961201F2 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 12:27:30 -0800 (PST)
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 Ejgd_0EGDxof for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 12:27:27 -0800 (PST)
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 CE20912008A for <ietf@ietf.org>; Fri, 17 Nov 2017 12:27:27 -0800 (PST)
X-AuditID: c6180641-835ff70000007a40-76-5a0f462dd604
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usplmg21.ericsson.net (Symantec Mail Security) with SMTP id CE.C0.31296.D264F0A5; Fri, 17 Nov 2017 21:27:26 +0100 (CET)
Received: from EUSAAMB104.ericsson.se ([147.117.188.121]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0352.000; Fri, 17 Nov 2017 15:27:25 -0500
From: Eric Gray <eric.gray@ericsson.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: On audio quality requirements for IETF meetings
Thread-Topic: On audio quality requirements for IETF meetings
Thread-Index: AQHTX04+kaOnMerF+ECdkMrfcfZ+UaMYOamAgACInYCAAEFScA==
Date: Fri, 17 Nov 2017 20:27:25 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF64B88E262@eusaamb104.ericsson.se>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <ca53972b-72ac-5aa9-8465-c8d51703daaa@gmail.com>
In-Reply-To: <ca53972b-72ac-5aa9-8465-c8d51703daaa@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_48E1A67CB9CA044EADFEAB87D814BFF64B88E262eusaamb104erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphkeLIzCtJLcpLzFFi42KZXLonUFfPjT/K4ESfkMWPnhvMFs82zmex +Hv8M7PFqQeJDiwe6/YHeOycdZfdY8mSn0weKzavZAxgieKySUnNySxLLdK3S+DKuLDwAVvB qYCKy9dnsTcwrvHrYmTnkBAwkTgh1cXIxSEkcIRRYtufM8wQznJGiQXf1jN1MXJysAloSBy7 s5YRJCEisItRomn3ZBaQhLCAjcTlKzdYQWwRAVuJlVe2skPYThIHDvwEq2ERUJWY1d4MNohX wFeiaeY2sBohgXVMEkvPp4HYnEC9S85tBZvDKCAm8f3UGrB6ZgFxiVtP5oPZEgICEkv2nGeG sEUlXj7+xwphK0rs65/ODlGfL7F4/VM2iF2CEidnPmGZwCg8C8moWUjKZiEpm8XIARTXlFi/ Sx+iRFFiSvdDdghbQ6J1zlx2ZPEFjOyrGDlKiwtyctONDDcxAuPomASb4w7Gvb2ehxgFOBiV eHhnOPFHCbEmlhVX5h5ilOBgVhLhnbGcL0qINyWxsiq1KD++qDQntfgQozQHi5I47zlP3igh gfTEktTs1NSC1CKYLBMHp1QDY+vR0qJCPtWMpxbzdMwlcn1MsuJmh1WunZhisufGAn/xec/3 PqtJ0AsKv3jpx/uvVc6rG7yOLuNYM0XEJuxqltscGcGdbxMj1kzYd7LVlf3tGu015idv7Uhl /sbB93K/03LP9XIyIjtLHVWzmFlKr106G12602r29UlvGb+Efj3i16TB8jFASYmlOCPRUIu5 qDgRAC7YpEGfAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zrKNDzMqtmNiL-CJbPgqSHNNATI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 20:27:30 -0000

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

KzENCg0KDQoNCkkgd2FzIHRyeWluZyB0byBhdHRlbmQgbWVldGluZyB0aGlzIHdlZWsgcmVtb3Rl
bHkuICBJbiBzcGl0ZSBvZiB0aGUgZmFjdCB0aGF0IEkgaGF2ZSB2ZXJ5IGdvb2QgYXVkaW8gZXF1
aXBtZW50IGF0IG15IGVuZCwgdGhlIGF1ZGlvIGZvciByZW1vdGUgcGFydGljaXBhbnRzIHZhcmll
ZCBmcm9tIG5lYXJseSBub24tZXhpc3RlbnQgdG8gYWxtb3N0IGF1ZGlibGUgaW4gYXQgbGVhc3Qg
YSBmZXcgb2YgdGhlIG1lZXRpbmdzIGZvciBhdCBsZWFzdCBzb21lIG9mIHRoZSBtZWV0aW5nIHRp
bWUuDQoNCg0KDQpPZiBjb3Vyc2UsIHRoaXMgd2FzIGNvbXBvdW5kZWQgYnkgbmV0d29yayBpc3N1
ZXMuICBJIGZvdW5kIGl0IHdhcyBuZWNlc3NhcnkgdG8gYXR0ZW5kIG9ubHkgYXMgYW4gb2JzZXJ2
ZXIgaW4gb3JkZXIgdG8ga2VlcCBmcm9tIGRyb3BwaW5nIG15IGNvbm5lY3Rpb24gZXZlcnkgMTAt
MjAgbWludXRlcyBvciBzby4NCg0KDQoNCkJ1dCBJIGZvdW5kIHRoZSBvdmVyYWxsIGV4cGVyaWVu
Y2Ugc29tZXdoYXQgbW9yZSByZXdhcmRpbmcgdGhhbiBJIGV4cGVjdGVkLCBpbiBzcGl0ZSBvZiB0
aGUgZmFjdCB0aGF0IHRoZSB0aW1pbmcgbWFkZSBhdHRlbmRhbmNlIGEgMToxIHJlcGxhY2VtZW50
IGZvciBzbGVlcCAobW9zdCBtZWV0aW5ncyB3ZXJlIGJldHdlZW4gODozMCBQTSBhbmQgNTowMCBB
TSBFYXN0ZXJuIFVTIHRpbWUpLiAgQ3Jvd2RpbmcsIHBvd2VyIGFuZCBzZWF0aW5nIHdhcyBtdWNo
IGJldHRlciwgZm9yIGluc3RhbmNlLiAg8J+Yig0KDQoNCg0KLS0NCg0KRXJpYw0KDQoNCg0KLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYgW21haWx0bzppZXRmLWJvdW5jZXNA
aWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBTdGV3YXJ0IEJyeWFudA0KU2VudDogRnJpZGF5LCBOb3Zl
bWJlciAxNywgMjAxNyA2OjI0IEFNDQpUbzogYWRyaWFuQG9sZGRvZy5jby51azsgam9yZGkucGFs
ZXRAY29uc3VsaW50ZWwuZXM7IGlldGZAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBPbiBhdWRpbyBx
dWFsaXR5IHJlcXVpcmVtZW50cyBmb3IgSUVURiBtZWV0aW5ncw0KDQoNCg0KKzENCg0KDQoNCkkg
a25vdyBteSBoZWFyaW5nIGlzIG5vdCBhcyBnb29kIGFzIGl0IG9uY2Ugd2FzIGJ1dCBpdCBpcyBu
b3JtYWxseSBPSyBhdCBJRVRGLiBOb3Qgc28gdGhpcyB0aW1lLiBJdCB3YXMgaGFyZCB0byBoZWFy
IHRoZSBwcmVzZW50ZXIgYXQgdGltZXMgYW5kIHBhcnRpdWxhcmx5IGhhcmQgdG8gaGVhciB0aGUg
cXVlc3Rpb25zIGZyb20gdGhlIE1pYyB3aGVuIEkgd2FzIHByZXNlbnRpbmcuIFdlIG5lZWQgbXVj
aCBjbGVhcmVyIGF1ZGlvbiBnb2luZyBmb3J3YXJkcy4NCg0KDQoNCi0gU3Rld2FydA0KDQoNCg0K
T24gMTcvMTEvMjAxNyAwMzoxNCwgQWRyaWFuIEZhcnJlbCB3cm90ZToNCg0KPiBZb3UgYXJlIG5v
dCBhbG9uZSENCg0KPiBDb25mZXJlbmNlIGNlbnRyZSBQQSBub3QgZ29vZC4NCg0KPiBNaWNzIHZl
cnkgZGlzdGFuY2Utc2Vuc2l0aXZlLg0KDQo+IE5vdCBzbyBiYWQgdGhhdCB1bnVzYWJsZSwgYnV0
IGhhcmQgd29yay4NCg0KPiBBZHJpYW4NCg0KPg0KDQo+PiBCeSB0aGUgd2F5IOKApiBtYXliZSBJ
4oCZbSBzdGFydGluZyB0byBzdWZmZXIgaGVhcmluZyBwcm9ibGVtcywgZG9u4oCZdA0KDQo+PiBu
b3RpY2VkIGJlZm9yZSwgYnV0IGluIHRoaXMgbWVldGluZywgSeKAmXZlIHJlYWwgZGlmZmljdWx0
aWVzIHRvIGhlYXJkDQoNCj4+IGFuZCBjb25zZXF1ZW50bHkgdW5kZXJzdGFuZCBwZW9wbGUgYXQg
dGhlIG1pa2Ugd2hlbiBJIHdhcyBwcmVzZW50aW5nLg0KDQo+Pg0KDQo+PiBJIHRoaW5rIGl0IHdp
bGwgYmUgaW50ZXJlc3RpbmcgdG8ga25vdyBpZiBJbmdlbWFyIGFuZCBJLCBhcmUgYWxvbmUgb24N
Cg0KPj4gdGhpcyDigKYNCg0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAx
IDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUg
NSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxARGVuZ1hpYW4i
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBp
bjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlv
bjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjojOTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxpLk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWlu
VGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRl
eHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1z
aXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLlBs
YWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUt
dHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEu
MGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7
fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg
djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw
IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm
XS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIj
OTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij4mIzQzOzE8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+SSB3YXMgdHJ5aW5nIHRv
IGF0dGVuZCBtZWV0aW5nIHRoaXMgd2VlayByZW1vdGVseS4gJm5ic3A7SW4gc3BpdGUgb2YgdGhl
IGZhY3QgdGhhdCBJIGhhdmUgdmVyeSBnb29kIGF1ZGlvIGVxdWlwbWVudCBhdCBteSBlbmQsIHRo
ZSBhdWRpbyBmb3IgcmVtb3RlIHBhcnRpY2lwYW50cyB2YXJpZWQgZnJvbSBuZWFybHkgbm9uLWV4
aXN0ZW50IHRvIGFsbW9zdCBhdWRpYmxlIGluIGF0IGxlYXN0IGEgZmV3IG9mIHRoZSBtZWV0aW5n
cw0KIGZvciBhdCBsZWFzdCBzb21lIG9mIHRoZSBtZWV0aW5nIHRpbWUuPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPk9mIGNvdXJzZSwgdGhpcyB3YXMgY29tcG91bmRlZCBieSBuZXR3b3Jr
IGlzc3Vlcy4mbmJzcDsgSSBmb3VuZCBpdCB3YXMgbmVjZXNzYXJ5IHRvIGF0dGVuZCBvbmx5IGFz
IGFuIG9ic2VydmVyIGluIG9yZGVyIHRvIGtlZXAgZnJvbSBkcm9wcGluZyBteSBjb25uZWN0aW9u
IGV2ZXJ5IDEwLTIwIG1pbnV0ZXMgb3Igc28uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PkJ1dCBJIGZvdW5kIHRoZSBvdmVyYWxsIGV4cGVyaWVuY2Ugc29tZXdoYXQgbW9yZSByZXdhcmRp
bmcgdGhhbiBJIGV4cGVjdGVkLCBpbiBzcGl0ZSBvZiB0aGUgZmFjdCB0aGF0IHRoZSB0aW1pbmcg
bWFkZSBhdHRlbmRhbmNlIGEgMToxIHJlcGxhY2VtZW50IGZvciBzbGVlcCAobW9zdCBtZWV0aW5n
cyB3ZXJlIGJldHdlZW4gODozMCBQTSBhbmQgNTowMCBBTSBFYXN0ZXJuIFVTIHRpbWUpLiZuYnNw
OyBDcm93ZGluZywNCiBwb3dlciBhbmQgc2VhdGluZyB3YXMgbXVjaCBiZXR0ZXIsIGZvciBpbnN0
YW5jZS4mbmJzcDsgPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJIEVtb2pp
JnF1b3Q7LHNhbnMtc2VyaWYiPg0K8J+Yijwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+LS08bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkVyaWM8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+
DQpGcm9tOiBpZXRmIFttYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Yg
U3Rld2FydCBCcnlhbnQ8YnI+DQpTZW50OiBGcmlkYXksIE5vdmVtYmVyIDE3LCAyMDE3IDY6MjQg
QU08YnI+DQpUbzogYWRyaWFuQG9sZGRvZy5jby51azsgam9yZGkucGFsZXRAY29uc3VsaW50ZWwu
ZXM7IGlldGZAaWV0Zi5vcmc8YnI+DQpTdWJqZWN0OiBSZTogT24gYXVkaW8gcXVhbGl0eSByZXF1
aXJlbWVudHMgZm9yIElFVEYgbWVldGluZ3M8L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiYjNDM7MTxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5JIGtub3cgbXkgaGVhcmluZyBpcyBub3QgYXMgZ29v
ZCBhcyBpdCBvbmNlIHdhcyBidXQgaXQgaXMgbm9ybWFsbHkgT0sgYXQgSUVURi4gTm90IHNvIHRo
aXMgdGltZS4gSXQgd2FzIGhhcmQgdG8gaGVhciB0aGUgcHJlc2VudGVyIGF0IHRpbWVzIGFuZCBw
YXJ0aXVsYXJseSBoYXJkIHRvIGhlYXIgdGhlIHF1ZXN0aW9ucyBmcm9tIHRoZSBNaWMgd2hlbiBJ
IHdhcyBwcmVzZW50aW5nLiBXZSBuZWVkIG11Y2ggY2xlYXJlcg0KIGF1ZGlvbiBnb2luZyBmb3J3
YXJkcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+LSBTdGV3YXJ0PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPk9uIDE3LzExLzIwMTcgMDM6MTQsIEFkcmlhbiBGYXJyZWwgd3Jv
dGU6PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IFlvdSBhcmUg
bm90IGFsb25lITxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBD
b25mZXJlbmNlIGNlbnRyZSBQQSBub3QgZ29vZC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZndDsgTWljcyB2ZXJ5IGRpc3RhbmNlLXNlbnNpdGl2ZS48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgTm90IHNvIGJhZCB0aGF0IHVudXNh
YmxlLCBidXQgaGFyZCB3b3JrLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+Jmd0OyBBZHJpYW48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZn
dDs8bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsmZ3Q7
IEJ5IHRoZSB3YXkg4oCmIG1heWJlIEnigJltIHN0YXJ0aW5nIHRvIHN1ZmZlciBoZWFyaW5nIHBy
b2JsZW1zLCBkb27igJl0DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PiZndDsmZ3Q7IG5vdGljZWQgYmVmb3JlLCBidXQgaW4gdGhpcyBtZWV0aW5nLCBJ4oCZdmUgcmVh
bCBkaWZmaWN1bHRpZXMgdG8gaGVhcmQNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+Jmd0OyZndDsgYW5kIGNvbnNlcXVlbnRseSB1bmRlcnN0YW5kIHBlb3BsZSBhdCB0
aGUgbWlrZSB3aGVuIEkgd2FzIHByZXNlbnRpbmcuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mZ3Q7Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jmd0OyZndDsgSSB0aGluayBpdCB3aWxsIGJlIGludGVyZXN0aW5nIHRvIGtu
b3cgaWYgSW5nZW1hciBhbmQgSSwgYXJlIGFsb25lIG9uDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZndDsmZ3Q7IHRoaXMg4oCmPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5
Pg0KPC9odG1sPg0K

--_000_48E1A67CB9CA044EADFEAB87D814BFF64B88E262eusaamb104erics_--


From nobody Fri Nov 17 14:02:21 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 16C1412751F for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 14:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnqFz7_VJ3F2 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 14:02:17 -0800 (PST)
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 838AB126BFD for <ietf@ietf.org>; Fri, 17 Nov 2017 14:02:17 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0B90F20072; Fri, 17 Nov 2017 17:04:06 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 46E3E80CFA; Fri, 17 Nov 2017 17:02:16 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: jordi.palet@consulintel.es
cc: ietf@ietf.org
Subject: Re: On audio quality requirements for IETF meetings
In-Reply-To: <2D51FAA9-D45B-468C-B5FD-A6CF729A0337@consulintel.es>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com> <0BE7DA22F8B14110F7EFFB66@PSB> <21658.1510942120@obiwan.sandelman.ca> <2D51FAA9-D45B-468C-B5FD-A6CF729A0337@consulintel.es>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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, 17 Nov 2017 17:02:16 -0500
Message-ID: <12241.1510956136@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fPtSwiNs-ztQhFG6n0boMTuvUN4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Nov 2017 22:02:19 -0000

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


JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
    > But what I was asking was more on the line of =E2=80=9Cwhat audio qua=
lity=E2=80=9D we
    > need for our meetings, in whatever terms an audio expert can define =
=E2=80=A6
    > There must be a way to fix that in the document.

So you are thinking about things like:
   1) dB of absorption by walls (to prevent echo)
   2) dB of audio isolation between rooms
   3) amount of phase that the PA amplifier can echo cancel

?? (and that's the most technical I can get)

I was half thinking that we should have IPv6 enabled microphones in every
badge, and then:
  a) we don't have to run the mic
  b) jabber scribe will know who is in the "line"
  c) the badge/mic can be professional positioned each morning so that
     everyone can be "levelled"

Only half of of me thought it was a bad idea.

=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+93Q3WUFAloPXGcACgkQgItw+93Q
3WVSFwf/etEznA2L59qnsAzQVVDEFoQlr9PpNYqp0Cqt5dRCRPQ7ZgJwbL9Z1O7g
2Aj+HbBnv7aJZOSq6jERKHGW3OYkxaqadYoiV585UuUEgnU7XI2CYZNvl38la2RD
P/MOCLd8ob+SO414TlxBUodCwlhg6gSXZaIlab7knPInBQdTrgldiCwj3OXLKHk4
gIEAibduh3IKq5FwbMWZx08ON994a5C5KcciQ7MzYu9vp9DNxHSfk9O7dLEGg3Qd
ZJEssDqPm9O6Azisa6e2mv74xDtzwEDL9cqqvtL9o1lklXZ+ygdvfzhB7HAlsuIQ
xUH/A4wqGvsCMDNz+UNF/+nx/Ix8SQ==
=uIJx
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Nov 17 17:06:50 2017
Return-Path: <prvs=1495fd3244=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 E594B128B27 for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 17:06:48 -0800 (PST)
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 O3P3qGgFXKwA for <ietf@ietfa.amsl.com>; Fri, 17 Nov 2017 17:06:47 -0800 (PST)
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 9B002120725 for <ietf@ietf.org>; Fri, 17 Nov 2017 17:06:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1510967203; x=1511572003; 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=ZJkUpPSZ2wIUpF7cglrJcaVbT r6syfsT0wGpzVPnKec=; b=ndAQULrF7KBvGZlvP6zyE8fJxUPlZNrwGGa5mKY3N sqqx2nY8xZOrk+ezMgWH0bn+96kRfUECqwZtnVcUZdS42HUquSYjiL4SwpcnOSMg PKXmqvugpAxcGkXnflU5N7MIQ73r6zsQZOvETaTSXNKI2oJJg8Gg0IW2RlkzutVE 18=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=Gi68+sLX/F+anRjQ9XMkwz8xBsdcUx+nkusqCtcWGxjzIUMqbWKb1MUmceS/ sfQjIJ4OSDYUtxAwLaCtvFbzd5u4xA8sRQhMv8SscfGXFYjD3D2XTG74m x01iiUGNsbEYlOpH12X4YdXqSTiGbQMpajyHt9RfZPJUl9EXuMDR/4=;
X-MDAV-Processed: mail.consulintel.es, Sat, 18 Nov 2017 02:06:43 +0100
X-Spam-Processed: mail.consulintel.es, Sat, 18 Nov 2017 02:06:42 +0100
Received: from [172.20.60.6] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005627855.msg for <ietf@ietf.org>; Sat, 18 Nov 2017 02:06:41 +0100
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:171118:md50005627855::drKnDnm0dx0V3k2T:00008A8n
X-Return-Path: prvs=1495fd3244=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Sat, 18 Nov 2017 09:06:22 +0800
Subject: Re: On audio quality requirements for IETF meetings
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <7F9D85E7-9736-4AF4-9453-36E54C5869F7@consulintel.es>
Thread-Topic: On audio quality requirements for IETF meetings
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <B70AFFE2-95DB-44C8-932E-E61DECA7EA30@fugue.com> <0BE7DA22F8B14110F7EFFB66@PSB> <21658.1510942120@obiwan.sandelman.ca> <2D51FAA9-D45B-468C-B5FD-A6CF729A0337@consulintel.es> <12241.1510956136@obiwan.sandelman.ca>
In-Reply-To: <12241.1510956136@obiwan.sandelman.ca>
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/97O8eYd37_Ld4P3ds5dgRt6yUoA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Nov 2017 01:06:49 -0000

I=E2=80=99ve not seen mics with IPv6 =E2=80=A6 however there are IPv6 IP ca=
meras, so may be the point is replacing the mics with those and instead of =
mic holder we need red boxes for the location where the cameras are pointin=
g (by default). Depending on the camera mic capabilities, the problem may b=
e the distance for having a good audio.

As the badges have the name in both sides =E2=80=A6 I guess using IP camera=
s with zoom, pant and tilt, could be a way for the scribes to look for the =
name and a very small software modification to allow them to zoom in-read-z=
oom out.

What I=E2=80=99m not sure is if we can rely on the WiFi for that, or a spec=
ific access point/radio, or if we use RJ45 for all those.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Michael Richardson <mcr+ietf@=
sandelman.ca>
Responder a: <mcr+ietf@sandelman.ca>
Fecha: s=C3=A1bado, 18 de noviembre de 2017, 6:02
Para: <jordi.palet@consulintel.es>
CC: <ietf@ietf.org>
Asunto: Re: On audio quality requirements for IETF meetings

   =20
    JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
        > But what I was asking was more on the line of =E2=80=9Cwhat audio=
 quality=E2=80=9D we
        > need for our meetings, in whatever terms an audio expert can defi=
ne =E2=80=A6
        > There must be a way to fix that in the document.
   =20
    So you are thinking about things like:
       1) dB of absorption by walls (to prevent echo)
       2) dB of audio isolation between rooms
       3) amount of phase that the PA amplifier can echo cancel
   =20
    ?? (and that's the most technical I can get)
   =20
    I was half thinking that we should have IPv6 enabled microphones in eve=
ry
    badge, and then:
      a) we don't have to run the mic
      b) jabber scribe will know who is in the "line"
      c) the badge/mic can be professional positioned each morning so that
         everyone can be "levelled"
   =20
    Only half of of me thought it was a bad idea.
   =20
    --
    Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
     -=3D IPv6 IoT consulting =3D-
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Fri Nov 17 23:59:22 2017
Return-Path: <christer.holmberg@ericsson.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 5CD82126C26; Fri, 17 Nov 2017 23:59:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: <gen-art@ietf.org>
Cc: ipsec@ietf.org, ietf@ietf.org, draft-ietf-ipsecme-eddsa.all@ietf.org
Subject: Genart last call review of draft-ietf-ipsecme-eddsa-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151099196129.9056.6462331514698284743@ietfa.amsl.com>
Date: Fri, 17 Nov 2017 23:59:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SluMSMJEAWpIvieOBRW_xjxGf80>
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, 18 Nov 2017 07:59:21 -0000

Reviewer: Christer Holmberg
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

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

Document: draft-ietf-ipsecme-eddsa-04
Reviewer: Christer Holmberg
Review Date: 2017-11-17
IETF LC End Date: 2017-12-04
IESG Telechat date: Not scheduled for a telechat

Summary: The document is well written, and almost ready for publication.
However, I have some editorial change suggestions that I think would improve
the readability of the document.

Major issues: None

Minor issues: None

Nits/editorial comments:

Q1:
----

In the Abstract the text says " Edwards-curve digital signature algorithm",
without the EdDSA abbreviation, and in the Introduction the text says "EdDSA"
without the enhancement.

I suggest to say "Edwards-curve digital signature algorithm (EdDSA)" in the
first occurrences within the Abstract and the Introduction.

Q2:
----

In the Introduction the text says "The latter RFC" and "that document". I
suggest to explicitly use the RFC numbers instead.

That makes it easier to read, and there is always a theoretical change that
someone files an errata, or update the text within another RFC, that changes
the order to the RFCs so that "The latter" etc points to the wrong RFC...

Q3:
----

In the Introduction the text says:

   "EdDSA defines the binary format of the signatures that should be used
   in the "Signature Value" field of the Authentication Data Format in
   section 3."

Section 3 of what? I assume you refer section 3 of RFC 8032, so I suggest to
explicitly say that. Otherwise someone (at least I did) may jump to section 3
of the draft and start looking.

The same thing applies to "Appendix A". Please indicate the RFC number.

Q4:
----

In the Introduction the text says:

"we define a new value"

I suggest to say "this document defines a new value".

Or, you could even say "section 2 of this document defines a new value".

Q5:
----

In section 3, I suggest to add a reference (URL?) to the hash algorithm
registry.



From nobody Sat Nov 18 01:37:38 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 5C9AA12421A for <ietf@ietfa.amsl.com>; Sat, 18 Nov 2017 01:37:37 -0800 (PST)
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 J4wLGXANmBzm for <ietf@ietfa.amsl.com>; Sat, 18 Nov 2017 01:37:35 -0800 (PST)
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 9FFD81200E5 for <ietf@ietf.org>; Sat, 18 Nov 2017 01:37:34 -0800 (PST)
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 vAI9bUVU010896; Sat, 18 Nov 2017 10:37:30 +0100 (CET)
Received: from [10.54.145.203] (unknown [88.128.81.5]) (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 3yf8yy4fNkzDX2h; Sat, 18 Nov 2017 10:37:30 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: On audio quality requirements for IETF meetings
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CA878EBF-4EF9-4E17-9AB1-1A868D0A58E9@consulintel.es>
Date: Sat, 18 Nov 2017 10:37:30 +0100
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 532690649.939597-d7fb402149e168374b3d107728dc3141
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C0C37A4-587E-4CB4-82A1-3D6677817260@tzi.org>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <CA878EBF-4EF9-4E17-9AB1-1A868D0A58E9@consulintel.es>
To: ingemar.s.johansson@ericsson.com
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mxH4gtc0n4dybgIJtKU7TICZj_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: Sat, 18 Nov 2017 09:37:37 -0000

>    I believe that improved acoustics would non only benefit people =
with bad hearing, it would also reduce fatigue for people with good =
hearing

+100.  I=E2=80=99ve been using English in a professional context for =
more than 35 years now, but English via bad audio really exhausts me.

I don=E2=80=99t think we should meddle with the actual A/V engineering =
(although the DECT microphones that Telefonica had for the STRINT =
workshop in 2014 were amazing).  But we can show that we care about =
audio by asking for some simple specifications (RT60 was suggested, =
maybe frequency response if installed ceiling speakers are to be used =
=E2=80=94 a high pass might help with some rooms).

ISTR that the microphones I looked at in Singapore said they were SM58s, =
so unless they were cheap fakes, the problems with them were mostly lack =
of training (you need to be very close to those, and unless you are an =
accomplished singer, this means you need to hold them as opposed to =
using them on a stand).  There were some microphones though that needed =
to be tapped or shaken now and then, pointing to badly maintained =
battery contacts.  And battery discipline apparently was lacking as well =
=E2=80=94 batteries need to be replaced in a regular process and not =
after they finally fail.

There were some serious speaker placement problems in some rooms, with =
no direct sound at all in significant parts of the room (including the =
presenter and chair areas themselves).  Maybe we can complement the =
presenter TV with a monitor speaker (which would also help the presenter =
with knowing when they are close enough to the microphone), but the =
speaker placement for the rest of the room simply needs to be checked in =
place and corrections made where needed.

If we really want to help people who can benefit from that, there could =
be a monitor frequency per room that can be picked up by a receiver =
(I=E2=80=99ve used those with specific students in large-room lectures). =
 Those of course require additional planning, as they are regional and =
licensed; instead of doing it per room there could also be a set per =
person needing it, with a place in the room to plug the transmitter in.  =
(I have used meetecho as a cheap version of that when I happened to sit =
down in a bad area of the room, but the delay is generally too high =
compared to an analog solution.)

At least the leakage from adjacent rooms (another spec we could ask for) =
was limited this time.

Audio problems excepted, this was definitely one of the better venues we =
had.

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


From nobody Sat Nov 18 02:23:15 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 A077D12025C for <ietf@ietfa.amsl.com>; Sat, 18 Nov 2017 02:23:14 -0800 (PST)
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 WbBJpZd0Sy16 for <ietf@ietfa.amsl.com>; Sat, 18 Nov 2017 02:23:13 -0800 (PST)
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 630F71200C5 for <ietf@ietf.org>; Sat, 18 Nov 2017 02:23:13 -0800 (PST)
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 vAIAN6Ag022263; Sat, 18 Nov 2017 11:23:06 +0100 (CET)
Received: from [10.54.145.203] (unknown [88.128.81.5]) (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 3yf9zZ1K5szDX32; Sat, 18 Nov 2017 11:23:06 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: On audio quality requirements for IETF meetings
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <48E1A67CB9CA044EADFEAB87D814BFF64B88E262@eusaamb104.ericsson.se>
Date: Sat, 18 Nov 2017 11:23:05 +0100
Cc: Stewart Bryant <stewart.bryant@gmail.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>, "ietf@ietf.org" <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 532693385.454504-48db28fffc075f0437d0787fdf6c63d3
Content-Transfer-Encoding: quoted-printable
Message-Id: <D997A073-91AB-47B0-9A68-1364BCBF877F@tzi.org>
References: <DB4PR07MB3486DCE0D9F9559A15D8634C22F0@DB4PR07MB348.eurprd07.prod.outlook.com> <6DB237E9-160F-4EF4-80E2-5B7F9D864F21@consulintel.es> <1A447EAC-6986-4D90-BBB6-A52CFAF6B1D0@consulintel.es> <170901d35f52$3c4a0fc0$b4de2f40$@olddog.co.uk> <ca53972b-72ac-5aa9-8465-c8d51703daaa@gmail.com> <48E1A67CB9CA044EADFEAB87D814BFF64B88E262@eusaamb104.ericsson.se>
To: Eric Gray <eric.gray@ericsson.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8R79w6V2kQoEKyMpqbtZytUAKsA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Nov 2017 10:23:14 -0000

On Nov 17, 2017, at 21:27, Eric Gray <eric.gray@ericsson.com> wrote:
>=20
> the audio for remote participants varied from nearly non-existent to =
almost audible in at least a few of the meetings for at least some of =
the meeting time

When listening to the IETF audio, I run it through a dynamics =
compressor(*) (also very useful for the very irregular levels you get =
with WebEx audio in interim meetings).  That does not help with noise, =
but it sure does with bad levels.

I have always wondered if the dynamics compression could not be done at =
the source.

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

(*) For those with a Mac: Install soundflower and a VST tool of your =
choice (I use Audio Hijack), run the system audio to soundflower, and =
run the VST plugin AUDynamics (comes with the Mac) from that to the =
speaker output you want to use.
Configure AUDynamics for an about 40 dB (I=E2=80=99m not joking) knee.  =
Don=E2=80=99t forget to reset system audio to your speaker output when =
you switch back to a sane audio source=E2=80=A6


From nobody Mon Nov 20 09:41:28 2017
Return-Path: <john.lemon@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 074B4126FDC for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 09:41:27 -0800 (PST)
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, 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 (1024-bit key) header.d=broadcom.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kLKd_UWEH1N4 for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 09:41:25 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c: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 2149B12E037 for <ietf@ietf.org>; Mon, 20 Nov 2017 09:41:24 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id b189so20477878wmd.0 for <ietf@ietf.org>; Mon, 20 Nov 2017 09:41:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=GNa03OSX/WU9WptXUz7sunCehhfl3ee3McDdLvTFchE=; b=TJ/iGA9IfRM8RNJOCRKYD1wp3CfKaBYhuCgsxpZXm8cJwTStw6ejFGkvAHI1vXQZyw 8DTo0Qa9WYYcKY3/jfPXNIdmpJ0GNVQ2W619i4rjwzati7mlVhatflRBiV79d3wsOg0k 2TlcD+Np8jTm7tWcS48doGv3FLQmnjed9L5oo=
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=GNa03OSX/WU9WptXUz7sunCehhfl3ee3McDdLvTFchE=; b=CBFr8rmXyALtzhmvyE6kTPwGQrW7Bnp6j6/72+GOOhlW2KnTQRwUhNAyyFyJAgy2Rd TV1gr3ZflSzvzPwo5NX/vjptOrPaWJC8Zzrd2cpdPs9Ojg8P05JWs+tpiXphy3/V/exI v+tbc0/4l7h7r9xI+GS651b4OL2c4jK3Yt6jW4VKTHKKPKbHBdLAFXajNPWAMXIM2zcb tTjeBaNkFsY5RRlVETIMoaHv70H8Z3eQ0RYQijryjIy+6VI8ly3I2zR7nOFqK9datxFH uJRNEDJOoBoUVOYAeY5iLe29AtmbbHIk+QQXn6dNlIwqlWojk6zJuTA/qxc9hNEq33wL cQzQ==
X-Gm-Message-State: AJaThX7i0GjDrfA0Jpr3SVkUvCUwCAu0N/130Gp3PUmIINkFAu7W2AP3 L0VysWkewoJFwt0OYjihsaaPdxf4IVnLg9Htdg7YVw==
X-Google-Smtp-Source: AGs4zMY/FCBpXpDqaTDGRRI0JAScqsXeDnqvY0B9f5adsAVJjOHYgaIAZ922G1UWm6Kescr/ueYf72Rb0+Zf9VY/7cE=
X-Received: by 10.28.104.6 with SMTP id d6mr7703978wmc.101.1511199682391; Mon, 20 Nov 2017 09:41:22 -0800 (PST)
MIME-Version: 1.0
References: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com>
In-Reply-To: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com>
From: John Lemon <john.lemon@broadcom.com>
Date: Mon, 20 Nov 2017 17:41:11 +0000
Message-ID: <CAPOJaHxQc1O0SWFSaQi_KEXZnB7C0J3ihvVr_NiodueR9SJOPw@mail.gmail.com>
Subject: Re: [100all] Very Few T-shirts Left
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary="001a114b2a524126d6055e6d98c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-Keu_v5BbCCpTui2o9YYuP8--M8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Nov 2017 17:41:27 -0000

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

I=E2=80=99m probably way too late. But, on the off chance that 1 remains, I=
 would
very muck like to have it for my rather huge son.

I assume you would post it, in which case the address would be:
John Lemon
2868 Holmes Place
Santa Clara, CA 95051

408-314-5254
jalemon@meus.us

Thanks, John


On Thu, Nov 16, 2017 at 7:03 PM IESG Secretary <iesg-secretary@ietf.org>
wrote:

> But if you want one there are a very few 3XL size t-shirts available.
> First come first served.
>
> Again, 3XL only.
>
> _______________________________________________
> 100all mailing list
> 100all@ietf.org
> https://www.ietf.org/mailman/listinfo/100all
>

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

<div><div dir=3D"auto">I=E2=80=99m probably way too late. But, on the off c=
hance that 1 remains, I would very muck like to have it for my rather huge =
son.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">I assume you =
would post it, in which case the address would be:</div><div dir=3D"auto">J=
ohn Lemon</div><div dir=3D"auto">2868 Holmes Place=C2=A0</div><div dir=3D"a=
uto">Santa Clara, CA 95051</div><div dir=3D"auto"><br></div><div dir=3D"aut=
o">408-314-5254</div><div dir=3D"auto"><a href=3D"mailto:jalemon@meus.us">j=
alemon@meus.us</a>=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"=
>Thanks, John</div><div dir=3D"auto"><br></div><br><div class=3D"gmail_quot=
e"><div>On Thu, Nov 16, 2017 at 7:03 PM IESG Secretary &lt;<a href=3D"mailt=
o:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">But if you want one there are a very few 3XL=
 size t-shirts available. First come first served.<br>
<br>
Again, 3XL only.<br>
<br>
_______________________________________________<br>
100all mailing list<br>
<a href=3D"mailto:100all@ietf.org" target=3D"_blank">100all@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/100all" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/100all</a><br>
</blockquote></div></div>

--001a114b2a524126d6055e6d98c0--


From nobody Mon Nov 20 10:29:01 2017
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DDDE12E056 for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 10:29:00 -0800 (PST)
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 ZAs8zTbokBe6 for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 10:28:58 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B067F12E050 for <ietf@ietf.org>; Mon, 20 Nov 2017 10:28:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 455601CAC30; Mon, 20 Nov 2017 10:28:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o_RvLC8eNxTe; Mon, 20 Nov 2017 10:28:55 -0800 (PST)
Received: from [IPv6:2601:647:4201:b392:4501:68c5:2cab:f159] (unknown [IPv6:2601:647:4201:b392:4501:68c5:2cab:f159]) by c8a.amsl.com (Postfix) with ESMTPSA id 20AA91C9E5E; Mon, 20 Nov 2017 10:28:55 -0800 (PST)
From: Alexa Morris <amorris@amsl.com>
Message-Id: <663EDC98-86C1-4A0D-AA84-0D1BFDB10FB9@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E55F0390-F9E4-4910-9C4A-75D89B765A2D"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [100all] Very Few T-shirts Left
Date: Mon, 20 Nov 2017 10:30:40 -0800
In-Reply-To: <CAPOJaHxQc1O0SWFSaQi_KEXZnB7C0J3ihvVr_NiodueR9SJOPw@mail.gmail.com>
Cc: ietf@ietf.org
To: John Lemon <john.lemon@broadcom.com>
References: <151088774189.22157.13123147911890586271.idtracker@ietfa.amsl.com> <CAPOJaHxQc1O0SWFSaQi_KEXZnB7C0J3ihvVr_NiodueR9SJOPw@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yioKkrIHrhC4EbFRTSesRGzXGPk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Nov 2017 18:29:00 -0000

--Apple-Mail=_E55F0390-F9E4-4910-9C4A-75D89B765A2D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

John,

Unfortunately, we distribute all t-shirts onsite and do not bring them =
back to the office with us.=20

Alexa

> On Nov 20, 2017, at 9:41 AM, John Lemon <john.lemon@broadcom.com> =
wrote:
>=20
> I=E2=80=99m probably way too late. But, on the off chance that 1 =
remains, I would very muck like to have it for my rather huge son.=20
>=20
> I assume you would post it, in which case the address would be:
> John Lemon
> 2868 Holmes Place=20
> Santa Clara, CA 95051
>=20
> 408-314-5254
> jalemon@meus.us <mailto:jalemon@meus.us>=20
>=20
> Thanks, John
>=20
>=20
> On Thu, Nov 16, 2017 at 7:03 PM IESG Secretary =
<iesg-secretary@ietf.org <mailto:iesg-secretary@ietf.org>> wrote:
> But if you want one there are a very few 3XL size t-shirts available. =
First come first served.
>=20
> Again, 3XL only.
>=20
> _______________________________________________
> 100all mailing list
> 100all@ietf.org <mailto:100all@ietf.org>
> https://www.ietf.org/mailman/listinfo/100all =
<https://www.ietf.org/mailman/listinfo/100all>


--Apple-Mail=_E55F0390-F9E4-4910-9C4A-75D89B765A2D
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"">John,<div class=3D""><br class=3D""></div><div =
class=3D"">Unfortunately, we distribute all t-shirts onsite and do not =
bring them back to the office with us.&nbsp;</div><div class=3D""><br =
class=3D""></div><div class=3D"">Alexa</div><div class=3D""><br =
class=3D""><div class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Nov 20, 2017, at 9:41 AM, John Lemon &lt;<a =
href=3D"mailto:john.lemon@broadcom.com" =
class=3D"">john.lemon@broadcom.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D""><div =
dir=3D"auto" class=3D"">I=E2=80=99m probably way too late. But, on the =
off chance that 1 remains, I would very muck like to have it for my =
rather huge son.&nbsp;</div><div dir=3D"auto" class=3D""><br =
class=3D""></div><div dir=3D"auto" class=3D"">I assume you would post =
it, in which case the address would be:</div><div dir=3D"auto" =
class=3D"">John Lemon</div><div dir=3D"auto" class=3D"">2868 Holmes =
Place&nbsp;</div><div dir=3D"auto" class=3D"">Santa Clara, CA =
95051</div><div dir=3D"auto" class=3D""><br class=3D""></div><div =
dir=3D"auto" class=3D"">408-314-5254</div><div dir=3D"auto" class=3D""><a =
href=3D"mailto:jalemon@meus.us" =
class=3D"">jalemon@meus.us</a>&nbsp;</div><div dir=3D"auto" class=3D""><br=
 class=3D""></div><div dir=3D"auto" class=3D"">Thanks, John</div><div =
dir=3D"auto" class=3D""><br class=3D""></div><br class=3D""><div =
class=3D"gmail_quote"><div class=3D"">On Thu, Nov 16, 2017 at 7:03 PM =
IESG Secretary &lt;<a href=3D"mailto:iesg-secretary@ietf.org" =
class=3D"">iesg-secretary@ietf.org</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">But if you want one =
there are a very few 3XL size t-shirts available. First come first =
served.<br class=3D"">
<br class=3D"">
Again, 3XL only.<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
100all mailing list<br class=3D"">
<a href=3D"mailto:100all@ietf.org" target=3D"_blank" =
class=3D"">100all@ietf.org</a><br class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/100all" =
rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.ietf.org/mailman/listinfo/100all</a><br class=3D"">=

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

--Apple-Mail=_E55F0390-F9E4-4910-9C4A-75D89B765A2D--


From nobody Mon Nov 20 16:37:25 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 F018A12EAFA for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 16:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.209
X-Spam-Level: 
X-Spam-Status: No, score=0.209 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, 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 BggRaShvgMt6 for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 16:37:22 -0800 (PST)
Received: from sonic306-21.consmr.mail.ir2.yahoo.com (sonic306-21.consmr.mail.ir2.yahoo.com [77.238.176.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 90071129A9D for <ietf@ietf.org>; Mon, 20 Nov 2017 16:37:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1511224640; bh=OqQoPvzvxR2OaPMRyYYTUFESAOtslxSmTkysMv5pcDo=;  h=Date:From:Reply-To:To:Subject:References:From:Subject; b=LsRdiMTkLnVr0LzBWNGi4QF49Hg7xobbEO2EfpTjm8dPzqzDB14Sevr575mppvlmp4t7s76VREwTJ8w26BBGUFPruKbgcyeZdAsZynKsiG6aqA18FonHkCm0xrbYJzfjPukcYku3JuXVvaptelTuYkdTuIXO3XbXiv+i0PvHDiJztwITbDeVL2UYBhIJzp3BJcbnsHpIjseUJvjp6RD0SFIaRD0fE1sbv+qrOUpBAX7OTe0KNyGjxulXRB7maj0rq/aVaW6mxAZ7ryQjGswnXKLtczsOIDvz0plpPcdZTxxonFxDw82rU7axjk7T8KahiQBxjHAactD2kV6aN7i4Hg==
X-YMail-OSG: 5yLfSUoVM1kw3_O_21nyea1G0MI67_uovfdI4WMwPlGyRxtSIM834hhyP0bMH7Z .OxkSbtaIHVWzv0p2oS2Y4gZN67NU8NmHvkSCZMYN3oD2BepQELo3Su6.AxbgrKh6cuo1YkYxSKl Kq9dBiiwGcAsb6D.37BVJWO8h6uUpMBNm9Kv_4dJJ7gEB7Dv0LoyVVZV7QZXNTqSjeYPRQC4dILg uz5JaOWXZfMXpiSC80iqNJlREq9V5EL07j0frHW_lZRVjrWS5r7IJGPiS9Kqg6HgBHfA7PRU6LpQ AzYHmw3Vsrkh__pBD.Qf2bNGdlGSchI3na3_GatJWtsfzSwlIYWmrDx.um61B39Pfu1Q.2mPQRmS NP.xHJOaVz1yyWn5Aet0j3IXbGasX3YzKaJrWMIITqJuc5RpdV_ARnl6Q0D4eNVgfxZmE8xCVn.j aWlhaUVINLjddH1sb0pgb9upQF.yA1kttq7jxX6uEZq_lczjcXysS93uj7_6x5q6QeonewLfPhUC l46qIkYXNaliNjFi1YAe2g2GcMOEYfVkF91LuZgdYzCxoBv7aNgNUYepmy51KzUhAL2neQmflWy_ uwlzctb7t3v_0IErbYeI1lrMDo2c2R9eD0Jqqz1_CdZK0XJX6xIghKlFM3oCauZCgvyVs
Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ir2.yahoo.com with HTTP; Tue, 21 Nov 2017 00:37:20 +0000
Date: Tue, 21 Nov 2017 00:37:12 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <339747207.368008.1511224632283@mail.yahoo.com>
Subject: a list observation
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <339747207.368008.1511224632283.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.10982 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8zDxndkiaYpauhWWcs6_p7Ozdpo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 00:37:24 -0000

Most of the comments on this list are about lack of
audio quality, or about T-shirts.

So, when did the IETF turn into a Nickelback concert?

L.

Didn=E2=80=99t mean to waste your time. Thanks for wasting mine.=20
-Nickelback, Detangler
 Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood=20


From nobody Mon Nov 20 17:01:42 2017
Return-Path: <marka@isc.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 241981205F0 for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:01:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0PM7QDI6be0X for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:01:39 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA9461201FA for <ietf@ietf.org>; Mon, 20 Nov 2017 17:01:39 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id BEC4A3AB1D9; Tue, 21 Nov 2017 01:01:37 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id AE10B160082; Tue, 21 Nov 2017 01:01:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A002216006A; Tue, 21 Nov 2017 01:01:37 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id n-bAJeHvjUDU; Tue, 21 Nov 2017 01:01:37 +0000 (UTC)
Received: from [172.30.42.89] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 09A71160054; Tue, 21 Nov 2017 01:01:36 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: a list observation
From: Mark Andrews <marka@isc.org>
In-Reply-To: <339747207.368008.1511224632283@mail.yahoo.com>
Date: Tue, 21 Nov 2017 12:01:34 +1100
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <646156EE-5216-4A55-A21B-FF652E09A800@isc.org>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com>
To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oz4IPVeZ7Dcql2UozlFz8H54h0M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 01:01:41 -0000

> On 21 Nov 2017, at 11:37 am, Lloyd Wood <lloyd.wood@yahoo.co.uk> =
wrote:
>=20
> Most of the comments on this list are about lack of
> audio quality, or about T-shirts.
>=20
> So, when did the IETF turn into a Nickelback concert?
>=20
> L.
>=20
> Didn=E2=80=99t mean to waste your time. Thanks for wasting mine.=20
> -Nickelback, Detangler
> Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood=20

Audio quality is important for remote participation.  This includes good =
echo cancellation.  It really is hard to talk when you own voice is =
echoed back with a large delay.  I needed to manually mute the audio =
stream while talking which isn=E2=80=99t the best.

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


From nobody Mon Nov 20 17:06:50 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 768791201FA for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:06:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.592
X-Spam-Level: 
X-Spam-Status: No, score=-0.592 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=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 O0-fY51m1pgd for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:06:48 -0800 (PST)
Received: from sonic311-32.consmr.mail.ir2.yahoo.com (sonic311-32.consmr.mail.ir2.yahoo.com [77.238.176.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 DD07C12EB05 for <ietf@ietf.org>; Mon, 20 Nov 2017 17:06:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.uk; s=s2048;  t=1511226406; bh=WaghoKnne8+JMwI6Eoi8+ypNrO89QNnPGk1vGJ2B32w=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=Pf5Y3riu2XOgVhrMl+kX56PHEocuFGZqMVogfG5uQ+YGDuXQgQxegc0ROLHl2CkOpL/FUM4cYb05YkklNzZuvmyuz+5f+0xysnTI0RPxBYDdPe9023NVjY4orA8bDGggziRb/RhhwqR/lFL62f+RDCwlzAvYwM5/zBI4IV3RkWMkEXGVJXm9RoZkhZzALhkNvwkbdT5td8x8FZmeulwrPPIvkY25fQStxrNRuXVaIMvD7aBlV/IRA5qsj9ih2tWhO05170yr7A93FgkteIaGa8o6jS+FaiC8tMzE7dWO+7lLTtvk7sFwKHv6r5xmI+9tkuHovXAoycpTeuYdOERnZw==
X-YMail-OSG: 2292V.sVM1nR0EFhsUkERlEpPGXGsrQypthti74RiZhuKw06VpeZx2hkh.3V5Vv s0mThz6WgqoKrrXvPX3KglU6gBUk2LQuQsvlnQvA4.JMmO7EuaXuMFEBghvH14TPwZ.uqEEtinV0 pFJgL.7DW6vtPoVVpdz4d4V7wCvDRxkgmJvl.RypajxBcTitQVxbgT6PRSJgE8AOufGwSWuvy8i3 .6lmdItSFoE9aUuxKTi_KcI1FcJRGNXa7mkUuG7zy82uHYkzGBbkQ2f0Cr9xxZTnYRgGhL67ddgN y95tMczpZm4QFCnXIyRHhtPgU2aC6hd838EherCcNY2FqBCRUoCRZwIvn7gk_h5lxnZtXayADILK iIZ.oxtdng4lmoyIRcs6lS4hlb3hMpa2tIWi.28VD7lApHxT53ZHRvz.0Y_6KtH6CTSlbfKXJnnc QoyL5dzw5RopqnV0FIeZnaQg68i1.HqUiST_kLg9oegTkIdELJrE6UnXTy8QcMBxSQiwZXYlwsNx Rv7s_Lc0kzyqLmbgTc9d94DWaSH_bpb_ho2moqe059U7U8hmh8FWPASds4xkBxE9LbKXCFBQVmdz jjQe_sjFArGldBHLB0QWeMMEHsGhscfvBWg9iW0UjM64FPjaRTSSu3vJAI7YsMK6ROVIS
Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.ir2.yahoo.com with HTTP; Tue, 21 Nov 2017 01:06:46 +0000
Date: Tue, 21 Nov 2017 01:05:01 +0000 (UTC)
From: Lloyd Wood <lloyd.wood@yahoo.co.uk>
Reply-To: Lloyd Wood <lloyd.wood@yahoo.co.uk>
To: Mark Andrews <marka@isc.org>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <1868365181.3850266.1511226301270@mail.yahoo.com>
In-Reply-To: <646156EE-5216-4A55-A21B-FF652E09A800@isc.org>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com> <646156EE-5216-4A55-A21B-FF652E09A800@isc.org>
Subject: Re: a list observation
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailer: WebService/1.1.10976 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/30ENPU2EtcEZTHSC6nMslm_pgKM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 01:06:49 -0000

> Audio quality is important for remote participation.  This includes good =
echo cancellation.
> It really is hard to talk when you own voice is echoed back with a large =
delay.
> I needed to manually mute the audio stream while talking which isn=E2=80=
=99t the best.

Well, there's a reason it's called MeetEcho.

Lloyd Wood lloyd.wood@yahoo.co.uk http://about.me/lloydwood=20


From nobody Mon Nov 20 17:21:10 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 14F9612EB0D for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:21:09 -0800 (PST)
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 J4NYJrXV_2L0 for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:21:07 -0800 (PST)
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 948331205F0 for <ietf@ietf.org>; Mon, 20 Nov 2017 17:21:07 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eGxFI-0009TU-2S; Mon, 20 Nov 2017 20:21:04 -0500
Date: Mon, 20 Nov 2017 20:20:59 -0500
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>, Lloyd Wood <lloyd.wood@yahoo.co.uk>
cc: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: a list observation
Message-ID: <EB776714EFDEDE10566B7B9A@PSB>
In-Reply-To: <646156EE-5216-4A55-A21B-FF652E09A800@isc.org>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com> <646156EE-5216-4A55-A21B-FF652E09A800@isc.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.10
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/H2_gpocOXnJ2WaCj527YOwB5Sc4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 01:21:09 -0000

--On Tuesday, November 21, 2017 12:01 +1100 Mark Andrews
<marka@isc.org> wrote:

> Audio quality is important for remote participation.  This
> includes good echo cancellation.  It really is hard to talk
> when you own voice is echoed back with a large delay.  I
> needed to manually mute the audio stream while talking which
> isn't the best.

+1
While doing a presentation, I decided to use a headset (rarely
needed because I've got high-end echo canceling gear) and just
ignored hearing myself in the room on delay.  I guess I didn't
find that as hard as you did, but it wasn't pleasant.  What I
don't know is what to do about it -- while I suppose it would be
possible to mute the in-room microphones while someone remote
has the virtual floor, I suspect that would not be compatible
with Meetecho's remote presenter mode.

    john




From nobody Mon Nov 20 17:34:47 2017
Return-Path: <marka@isc.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 F2AC4124BAC for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:34:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Q78nseBXaAQ for <ietf@ietfa.amsl.com>; Mon, 20 Nov 2017 17:34:44 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 758AC124319 for <ietf@ietf.org>; Mon, 20 Nov 2017 17:34:44 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 7B44D3B89C2; Tue, 21 Nov 2017 01:34:42 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 4FD93160054; Tue, 21 Nov 2017 01:34:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 34CD316006A; Tue, 21 Nov 2017 01:34:42 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lx262KfRF37m; Tue, 21 Nov 2017 01:34:42 +0000 (UTC)
Received: from [172.30.42.89] (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 57562160054; Tue, 21 Nov 2017 01:34:41 +0000 (UTC)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: a list observation
From: Mark Andrews <marka@isc.org>
In-Reply-To: <EB776714EFDEDE10566B7B9A@PSB>
Date: Tue, 21 Nov 2017 12:34:38 +1100
Cc: Lloyd Wood <lloyd.wood@yahoo.co.uk>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D891B92-0FD1-41C0-B38B-3EFF7E0108A5@isc.org>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com> <646156EE-5216-4A55-A21B-FF652E09A800@isc.org> <EB776714EFDEDE10566B7B9A@PSB>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R4fXxWnCLYKXEg_WkzzL-UqQt2g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 01:34:46 -0000

> On 21 Nov 2017, at 12:20 pm, John C Klensin <john-ietf@jck.com> wrote:
>=20
>=20
>=20
> --On Tuesday, November 21, 2017 12:01 +1100 Mark Andrews
> <marka@isc.org> wrote:
>=20
>> Audio quality is important for remote participation.  This
>> includes good echo cancellation.  It really is hard to talk
>> when you own voice is echoed back with a large delay.  I
>> needed to manually mute the audio stream while talking which
>> isn't the best.
>=20
> +1
> While doing a presentation, I decided to use a headset (rarely
> needed because I've got high-end echo canceling gear) and just
> ignored hearing myself in the room on delay.  I guess I didn't
> find that as hard as you did, but it wasn't pleasant.  What I
> don't know is what to do about it -- while I suppose it would be
> possible to mute the in-room microphones while someone remote
> has the virtual floor, I suspect that would not be compatible
> with Meetecho's remote presenter mode.
>=20
>    john

Echo cancellation should be possible in the room.  They have the feed =
they are sending to the room speakers and the feeds from the various =
mics.  After that it is delay detection and feeding in a negative signal =
at the right level for each mic.  How much the audio gear to do this =
costs is I don=E2=80=99t know.=20

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


From nobody Mon Nov 20 18:35:39 2017
Return-Path: <nomcom-chair-2017@ietf.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 771871200E5; Mon, 20 Nov 2017 18:35:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2017 <nomcom-chair-2017@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: NomCom 2016-2017: LastCall for Feedback
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <151123173846.14722.8273207509958496439.idtracker@ietfa.amsl.com>
Date: Mon, 20 Nov 2017 18:35:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ac3iWRPIvDkuwDcS8HeD28LJkjI>
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, 21 Nov 2017 02:35:38 -0000

Just a reminder that feedback for the current Nominees for IETF and IAB 
leadership is due by 23:59 UTC on Friday, November 24, 2017.

You can view the list of nominees and enter feedback via the datatracker:

https://datatracker.ietf.org/nomcom/2017/feedback/

or you can provide your input by sending email to:

nomcom-2017 at ietf dot org

You can also send general feedback about Areas, the IESG, the IAB, and
the IAOC to the same email address.

The NomCom is starting to digest the nominee interviews from IETF 100 last
week and community feedback is a crucial element of choosing candidates for
the open positions.  We would like to encourage feedback on all of
the nominees. Please take a few moments to comment on the full range
of nominees in areas where you are active. We have good responses for
some but not all of our pool and would appreciate additional input.

Peter Yee
NomCom Chair 2017-2018
peter at akayla dot com (preferred for SPF reasons)
nomcom-chair-2017 at ietf dot org


From nobody Mon Nov 20 19:02:18 2017
Return-Path: <nomcom-chair-2017@ietf.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 DC0961200E5; Mon, 20 Nov 2017 19:02:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2017 <nomcom-chair-2017@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: ietf@ietf.org
Subject: RE: NomCom 2016-2017: LastCall for Feedback
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <151123333085.14666.2776213553008692501.idtracker@ietfa.amsl.com>
Date: Mon, 20 Nov 2017 19:02:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9gL6IZecyGfnHeErPYHTRgnJ2d8>
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, 21 Nov 2017 03:02:11 -0000

No, you haven't entered a time loop or the twilight zone.  Needless to say, that should read "NomCom 2017-2018: Last Call for Feedback".  Sometimes flapping fingers revert perfectly good edits. :-)

-Peter


From nobody Tue Nov 21 07:19:23 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE4C01294A1 for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 07:19:17 -0800 (PST)
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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1v-PDFl42k2d for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 07:19:15 -0800 (PST)
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 8FAE61294B2 for <ietf@ietf.org>; Tue, 21 Nov 2017 07:19:15 -0800 (PST)
Received: by mail-qt0-x22c.google.com with SMTP id i40so8377088qti.8 for <ietf@ietf.org>; Tue, 21 Nov 2017 07:19:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wdfq8VECaJiXJAC6DQrG5cU2aOJLrDv7GpabiriqxLI=; b=IvZPq0SQpmW3vR24xSd4WrskNz/Cxbx1rKlE95c3MbuPFp9gMgyCYLL5dYYAxbWsjj kPKWiPcbkvWYxvkQRkhmt0HZU0+hGQ6fkaOTzdX4d9GyXm7ZoDa97+SoRoGpjk+/vo9X DzRORZ9ue8ebHENiVzBhRXmbUo3P8l3cxh3Ec=
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=wdfq8VECaJiXJAC6DQrG5cU2aOJLrDv7GpabiriqxLI=; b=k938Ss6lw6su6crdrVmXRsDLHVbB0aZ7F8UV6I+dhkWfd+i9vAvEk69Cucjt9NEAq8 zT8VgcctDWC1H2lUfH1DNqVHRmxi1sTHWK6VXYhiTDoKYAQpYS9v115Ok1glt9IFmNFu Nb/u9zP04mJDMWDFMWP5V2Us9l5h88oIvksRcg0KKCURn8+2gLniF95V09dZn/F4B8xW NRrwLGoP/D8UI0gb/0clp2LLEDc8f6Aj6X1k6Qm14yYEZS/Et7QgWvW0qWaDAlLvTSpa X/RqjzdHjG908Aoe02k0LD542pd3trF/llzVJtyYri/xkIp0LwGM5hBc5uTM1hZBWZZj sUfg==
X-Gm-Message-State: AJaThX6bDRvGJDKyMz5ZaoekqHLcMkKllDhtjtBVIqwOM6NB9RCj0Y0d 70fUrlDRfdA06SDb6+mFBX01SQN31sg=
X-Google-Smtp-Source: AGs4zMY0gMngoQnXbootTJLn25w+Ido0C3vzFMRBhLIjrlbfHshVpzqv+cijgcQV1qnzzKPLsXpGfw==
X-Received: by 10.237.37.162 with SMTP id x31mr28424033qtc.58.1511277554641; Tue, 21 Nov 2017 07:19:14 -0800 (PST)
Received: from [172.16.0.18] ([96.231.220.27]) by smtp.gmail.com with ESMTPSA id w23sm8898246qtj.35.2017.11.21.07.19.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Nov 2017 07:19:13 -0800 (PST)
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-stir-certificates-15
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <151090177468.22136.5281729043778955691@ietfa.amsl.com>
Date: Tue, 21 Nov 2017 10:19:12 -0500
Cc: gen-art@ietf.org, draft-ietf-stir-certificates.all@ietf.org, stir@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3A0F58AA-1397-445F-AD99-CED165E4EAE4@sn3rd.com>
References: <151090177468.22136.5281729043778955691@ietfa.amsl.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ID9x4JiI0R6vdJlwcytbRnz1e4w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 15:19:18 -0000

> On Nov 17, 2017, at 14:56, Joel Halpern <jmh@joelhalpern.com> wrote:
>=20
> Reviewer: Joel Halpern
> Review result: Ready
>=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-stir-certificates-15
> Reviewer: Joel Halpern
> Review Date: 2017-11-16
> IETF LC End Date: 2017-11-30
> IESG Telechat date: 2017-12-14
>=20
> Summary:
>=20
> Major issues:
>=20
> Minor issues:
>    Section 4 bullet 4 in naming the crypto algorithms refers quite =
clearly to
>    2 algorithms.  It then references one of them as RS256.  I assume =
those
>    versed in the field will know which one is meant.  But it would be =
better
>    if the abbreviation RS256 appeared next to the first reference to =
whichever
>    algorithm it means.

Ah okay I see what=E2=80=99s going on, the two algorithms are introduced =
in the previous sentence but we use the registered value as opposed to =
the name in the next sentence.  How about I replace =E2=80=9CRS256" with =
the =E2=80=9Clatter=E2=80=9D as it is the 2nd algorithm discussed in the =
previous sentence.

>    The security considerations section points to RFC 5280 security
>    considerations for most issues.  I presume that the intention is to =
use
>    that section regarding trusting CAs.  However, it seems that there =
is an
>    issue here much like that of classic web CAs.  The number of CAs =
that must
>    be trusted seems to be on the order of the number of countries in =
the
>    world.  That seems to leave a large window for false or misleading
>    certifications, as I can see nothing which restricts what numbers =
for which
>    those top level CAs can provide attestation.  I presume we do not =
want to
>    go down the path of requiring an uber-CA for all national =
authorities.  I
>    would expect some explicit recognition of this issue in this =
document.

Two points intertwined here:

- uber-CA: The WG explicitly agreed to say nothing about this topic.  I =
agree with you that we should not add any text concerning this point.

- Trust Anchor/Delegation: RFC5280=E2=80=99s SecCons already state that =
determining the Trusted CA (aka Trust Anchor) is out of scope.  The same =
is true here and I guess I could copy that text over, but it seems =
unnecessary in my mind given that a) half the time I get chastised for =
copying forward SecCons, and more importantly b) there=E2=80=99s are =
more specifications required to implement this including but not limited =
to a CP (Certification Policy) and CPS (Certification Practice =
Statement); these additional specifications get =
written/approved/published by National Numbering Authorities.

spt=


From nobody Tue Nov 21 07:25:05 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 57A7F1294DF; Tue, 21 Nov 2017 07:24:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 3uM8Thhhnxpv; Tue, 21 Nov 2017 07:24:56 -0800 (PST)
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 7928C1294AC; Tue, 21 Nov 2017 07:24:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 51A8A6A00EF; Tue, 21 Nov 2017 07:24:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1511277896; bh=Bd4pyA6hVKJw/gIUoEXIBL44lVNQxPIa8RuLG3UfcIU=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=akZveQYPGgXNy9WKC5ylrRBW4+KY1KLX6asd4qe3ERoMJhhqbeIFi88k2Lvb6EO0s KBy85+NcJd5K29wxeeWj2OyxDdW+OcVH4LCUoY/mCMwz5kwkMFqU7xeIugph3gq82L kEDSHEpclPQdlWkNbvi7CxiajAVZXtHVzJTWFE3w=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (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 69D506A1432; Tue, 21 Nov 2017 07:24:55 -0800 (PST)
Subject: Re: Genart last call review of draft-ietf-stir-certificates-15
To: Sean Turner <sean@sn3rd.com>
Cc: gen-art@ietf.org, draft-ietf-stir-certificates.all@ietf.org, stir@ietf.org, ietf@ietf.org
References: <151090177468.22136.5281729043778955691@ietfa.amsl.com> <3A0F58AA-1397-445F-AD99-CED165E4EAE4@sn3rd.com>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <09f05bf5-c23a-ba1f-116a-a94b44680f59@joelhalpern.com>
Date: Tue, 21 Nov 2017 10:24:54 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <3A0F58AA-1397-445F-AD99-CED165E4EAE4@sn3rd.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/E3Ope3YyfK1pdh_rkPQeYpd6xy4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 15:24:58 -0000

Thanbks Sean.  On the first point, using "latter" will fix the problem 
nicely.

On the point about CA conflicts, I understand the desire to stay out of 
the swamp.  Given that calls are frequently international, I am unclear 
how National Numbering Authorities can address the issue of 
inappropriate assertions from foreign CAs.  Each country can protect 
itself from folks pretending to be it.  But they can't protect 
themselves from other-A authorizing numbers within other-B.
I could well understand identifying the problem and saying that this 
work does not attempt to resolve it.  I would not consider that to be 
copying text, given that the referenced section is MUCH vaguer than that.
Having said that, I do consider it minor, and if you feel it would harm 
the document then that is more important.

Yours,
Joel

On 11/21/17 10:19 AM, Sean Turner wrote:
> 
>> On Nov 17, 2017, at 14:56, Joel Halpern <jmh@joelhalpern.com> wrote:
>>
>> 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 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-stir-certificates-15
>> Reviewer: Joel Halpern
>> Review Date: 2017-11-16
>> IETF LC End Date: 2017-11-30
>> IESG Telechat date: 2017-12-14
>>
>> Summary:
>>
>> Major issues:
>>
>> Minor issues:
>>     Section 4 bullet 4 in naming the crypto algorithms refers quite clearly to
>>     2 algorithms.  It then references one of them as RS256.  I assume those
>>     versed in the field will know which one is meant.  But it would be better
>>     if the abbreviation RS256 appeared next to the first reference to whichever
>>     algorithm it means.
> 
> Ah okay I see what’s going on, the two algorithms are introduced in the previous sentence but we use the registered value as opposed to the name in the next sentence.  How about I replace “RS256" with the “latter” as it is the 2nd algorithm discussed in the previous sentence.
> 
>>     The security considerations section points to RFC 5280 security
>>     considerations for most issues.  I presume that the intention is to use
>>     that section regarding trusting CAs.  However, it seems that there is an
>>     issue here much like that of classic web CAs.  The number of CAs that must
>>     be trusted seems to be on the order of the number of countries in the
>>     world.  That seems to leave a large window for false or misleading
>>     certifications, as I can see nothing which restricts what numbers for which
>>     those top level CAs can provide attestation.  I presume we do not want to
>>     go down the path of requiring an uber-CA for all national authorities.  I
>>     would expect some explicit recognition of this issue in this document.
> 
> Two points intertwined here:
> 
> - uber-CA: The WG explicitly agreed to say nothing about this topic.  I agree with you that we should not add any text concerning this point.
> 
> - Trust Anchor/Delegation: RFC5280’s SecCons already state that determining the Trusted CA (aka Trust Anchor) is out of scope.  The same is true here and I guess I could copy that text over, but it seems unnecessary in my mind given that a) half the time I get chastised for copying forward SecCons, and more importantly b) there’s are more specifications required to implement this including but not limited to a CP (Certification Policy) and CPS (Certification Practice Statement); these additional specifications get written/approved/published by National Numbering Authorities.
> 
> spt
> 


From nobody Tue Nov 21 10:32:27 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 571AF129B79 for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 10:32:26 -0800 (PST)
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 DkJeRgO6BNQ2 for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 10:32:24 -0800 (PST)
Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::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 91FB8129A9A for <ietf@ietf.org>; Tue, 21 Nov 2017 10:32:24 -0800 (PST)
Received: by mail-wr0-x22d.google.com with SMTP id k61so12186614wrc.4 for <ietf@ietf.org>; Tue, 21 Nov 2017 10:32:24 -0800 (PST)
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=sZde7AhqkO4OR3R4kfzU0IICVD8MS3heEzAl/wsJ3IU=; b=XCDTRAOaipCHn1Myocu3N/7Qt/DFkKmST4MM0hytKU0oCpfff9lhPXELslOJ8CKJv0 EgtydOgSr8fXZ3KdC+nfMVYJ2FQGtbU0K7y6Ouaq4EyqdUR+SF+dAwS99e6kuWbn59d2 FwJ/eDzaNrTAkM+cH8mGSXJbJfscl7baqHkpRXnv7ehZWocAZ2n5zoUPriZmrDNyfqIW 1ghAn+D5ZDYdbw8RetwrmVy+NF5J1Li7S5NoKNSv7Q3hbsSDnAbab3aKOOl8G6oBsU0Z rqyDebZ+GN+On3iu1O1NRpFOdnwSCM8dZb82a+Xet0F9aaYV4ZRGVbHyv5a0mcI/yYv4 5vkA==
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=sZde7AhqkO4OR3R4kfzU0IICVD8MS3heEzAl/wsJ3IU=; b=Y9FiN3eyUaqjJy2xRKJX8ua0FoiqY3muE1IO1CZSx/4uWMp8S+9yB8S/hHOFy5CXip Fdg/AfNi0AxnI1GqW7x+ZTko/0sE85ny9BLHmHppe23onK6Gm5V0VCo//FJrIMeFqYak jd6HTB/mHRKojgfm0RcA4fn9oNqhrAxBdaHavI+SURHtaEtXL6hX9L5x2FAZJdEDmW+m rCcDDA8u/hCX6nhc36jjZLkitSm0V05Z+5g8QZ4C0cDXayyxM8k7VpxAFIhimRYHwxTO stqe3F0nt3XfW/0+p2o6OhdcmHH4SfyNec+flr7hq3KYPF2dohfX3gdvXIBFjjRTPEGt 7OLQ==
X-Gm-Message-State: AJaThX5+yoydzVB5NVv5E8TlmnZFqysVp19wFsVWnaBjFleze9D9v0Va +WdLDAuPRw8O0oMy1pswnu0=
X-Google-Smtp-Source: AGs4zMYHkB1N5sTcmpcv/ZJzyixxdV4o1C5PcRn0e5j5h1icWVVZLQZJqHmtj6iu8RSOsABQW6Vzrw==
X-Received: by 10.223.185.3 with SMTP id k3mr9664945wrf.40.1511289143133; Tue, 21 Nov 2017 10:32:23 -0800 (PST)
Received: from [10.4.86.225] ([82.132.187.198]) by smtp.gmail.com with ESMTPSA id 19sm2595683wmv.41.2017.11.21.10.32.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Nov 2017 10:32:22 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: a list observation
From: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: iPhone Mail (15B150)
In-Reply-To: <6D891B92-0FD1-41C0-B38B-3EFF7E0108A5@isc.org>
Date: Tue, 21 Nov 2017 18:32:20 +0000
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BCB6555-2BFD-4816-9A54-FE81ED56D026@gmail.com>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com> <646156EE-5216-4A55-A21B-FF652E09A800@isc.org> <EB776714EFDEDE10566B7B9A@PSB> <6D891B92-0FD1-41C0-B38B-3EFF7E0108A5@isc.org>
To: Mark Andrews <marka@isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2fznjYzYmkqdSuXnmcU5nn932Bs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 18:32:26 -0000

> On 21 Nov 2017, at 1:34 am, Mark Andrews <marka@isc.org> wrote:
>=20
>=20
>> On 21 Nov 2017, at 12:20 pm, John C Klensin <john-ietf@jck.com> wrote:
>>=20
>>=20
>>=20
>> --On Tuesday, November 21, 2017 12:01 +1100 Mark Andrews
>> <marka@isc.org> wrote:
>>=20
>>> Audio quality is important for remote participation.=20

It is also important for those in the room.

The audio was as bad as I have ever experienced, and at times made it very h=
ard to understand what the speakers or those on the mic line were saying.

Stewart=


From nobody Tue Nov 21 10:40:13 2017
Return-Path: <d3e3e3@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 AC857129B97 for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 10:40:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 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, 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 SYXXH6lBVz4v for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 10:40:10 -0800 (PST)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::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 809B3129B77 for <ietf@ietf.org>; Tue, 21 Nov 2017 10:40:10 -0800 (PST)
Received: by mail-ot0-x230.google.com with SMTP id u10so11378605otc.12 for <ietf@ietf.org>; Tue, 21 Nov 2017 10:40:10 -0800 (PST)
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=c+Dh1pIWcqVg31mLjDWbRyMrG0yKuG8AlBistpAqBcM=; b=nd52xjaBxtLoiaxx9qDQvksposSwQdY8piAq9TUy6s2Q+hwcQQG+0qlQG5ANULykTK OIWpVcxK9U0D1NLnnDH6VOa5jqm7y4QSyGZk9dinNjXYoTfVxWJAmAcLlk7mWXwrArRf /cYlzdyCJvI3jbpLt7JA1o0KLkXLortN4nNxFPUR79NgSq9GNBAgOgFz232KWnPnj1Qr PnJxMqTDAI3NKDdt9bGNG/qFeE6Yj6YPW6zZH7ZNnXc6WcAQZYpQeXYcOFgT218BPJ7S Qqbhf2sCo6Ev+HJ2cog7m2PA23m3/+U3wKIrKlrBEbSI1+Wpzr6ytoB369YARHUebGPp azBw==
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=c+Dh1pIWcqVg31mLjDWbRyMrG0yKuG8AlBistpAqBcM=; b=TxjjNPHdoD0Jn9MTRcAEZaE5xffAvdDqIQJ3I2WHUVF7noOLo5PmJsJLIrMN7wvCgr AIHL/YYc87K3OKH7l9n+V6JOUn2p6R1JkvJp7WaxFVRj8eiJAJ/K5rJjspujY2TKLLY9 kNVNs6mRVEe+3npaBPR9jG1MYikQOGXcjnAlJvcioOoGeWc0hvRAWHQp7GgEDJGU9VuH kuLGyRXavk5GobjcLXDbpWKD9IAUtVpiAL23jO/FMjU3jUkGZAL/+vMKvPlNa2T6QkyB 1CXSd0/K7QXhBqc/Lmp6o00lKHAM4qeAHE8+hOu48/D6lgG/tCnx8X55kgvealwdnbAt loxA==
X-Gm-Message-State: AJaThX5BAVRrZh/368V35+SeRXiNUqfUvmYsbCoe35GuOUXwB53V3fpu PDn7I0v3tlhT1TgO9V4P0/8MuvF3YGMiPTR+cGw=
X-Google-Smtp-Source: AGs4zMYD2w3GRAfoVATQoUF6Z7dFMZgAwjZsCLFouOKfjNd+DOVRkO4oO7R84W41qtivmkRd+Z3nU1uSTZsKNLI8ZNA=
X-Received: by 10.157.48.123 with SMTP id w56mr6800187otd.55.1511289609792; Tue, 21 Nov 2017 10:40:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.168.73.194 with HTTP; Tue, 21 Nov 2017 10:39:54 -0800 (PST)
In-Reply-To: <7BCB6555-2BFD-4816-9A54-FE81ED56D026@gmail.com>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com> <646156EE-5216-4A55-A21B-FF652E09A800@isc.org> <EB776714EFDEDE10566B7B9A@PSB> <6D891B92-0FD1-41C0-B38B-3EFF7E0108A5@isc.org> <7BCB6555-2BFD-4816-9A54-FE81ED56D026@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 21 Nov 2017 13:39:54 -0500
Message-ID: <CAF4+nEHhuU52ZjW1L95iZFRW8DjxwmShc8+pnaebFR686W66_w@mail.gmail.com>
Subject: Re: a list observation
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Mark Andrews <marka@isc.org>, John C Klensin <john-ietf@jck.com>,  IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g6YOf9hWqfclIprBP76VmY5k_1E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 18:40:12 -0000

I noticed the low quality of the audio in the rooms as well. I maybe
it was just me but it looks like I was not alone. Frequently sounded
like loud, muddy lower frequency audio drowning out voices...

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, Nov 21, 2017 at 1:32 PM, Stewart Bryant
<stewart.bryant@gmail.com> wrote:
>
>
>> On 21 Nov 2017, at 1:34 am, Mark Andrews <marka@isc.org> wrote:
>>
>>
>>> On 21 Nov 2017, at 12:20 pm, John C Klensin <john-ietf@jck.com> wrote:
>>>
>>>
>>>
>>> --On Tuesday, November 21, 2017 12:01 +1100 Mark Andrews
>>> <marka@isc.org> wrote:
>>>
>>>> Audio quality is important for remote participation.
>
> It is also important for those in the room.
>
> The audio was as bad as I have ever experienced, and at times made it very hard to understand what the speakers or those on the mic line were saying.
>
> Stewart


From nobody Tue Nov 21 10:41:44 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 0AFD0129B9E for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 10:41:42 -0800 (PST)
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, 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=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 uVNPjoc0hIpq for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 10:41:40 -0800 (PST)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d: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 25FC9129B95 for <ietf@ietf.org>; Tue, 21 Nov 2017 10:41:40 -0800 (PST)
Received: by mail-qk0-x235.google.com with SMTP id a142so13416672qkb.5 for <ietf@ietf.org>; Tue, 21 Nov 2017 10:41:40 -0800 (PST)
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=kU7vZ4tUmWkSnIxqdUSN2Plp6Ndva1cxsJOsk7rhwnQ=; b=umltZ0kCetc3m3HJxjU/iLQwsPuOjXkOFBA1c1qCD0VCJWChxkb9VB9IWko/xTm1zu I447g9BwIHvgXjnH5/HXAK707ZVbzJukxfHAODpbZ4SJGLj1NcOj/4vJpyEo75ksXD1b NZ52yQQwSuKGr+5BZDzslIeGlnHJzrJaJuQX//OF85HQYbj9Y0Gsdsb3AQdSbxOPUx3T VjPZy+xCs9YG2frobKTAQH/uaeL3J7zi/IQBcPbsjjRwYe1HSgUFI4xd+An7pp5/xZ4w 7aR4hNeLYWVaNdz3IizD7rJXskzHKulSKZQxluweRw256bDXdBdSCLa8YLEBaAtm4ayO 6GZQ==
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=kU7vZ4tUmWkSnIxqdUSN2Plp6Ndva1cxsJOsk7rhwnQ=; b=i5TbZZs9vitJg1LsEn8E2kF8DwbRkPg3yaakpyqnvOP6ByjcINE7Cne5VuTnDYXpIW GXGXG+OaYjOgn3fJZsWPuvw1TZZ93v6Sk2eHkv7sSmmtrTOaBMi8LfoZvb983/corC6B Y/vugsvdq0wDlXTtIRkdS4e8uTe6i/VYMPgXOiu6VuB2rySrhGP0YLJ+1DV06SKr1UwJ mxn704XTkvNuwJmJvQnb46bMxUnYcqTZJyjAGCMJuRo6gUQTTltY0XKC2fpkAGHrDkON 6/ZxwpSPY5sNzT4z+hM2iq7JeEqAi7yPak+F2GLVapIqGp1QtdJjJ8JqIkHitsqhaoN/ tzuQ==
X-Gm-Message-State: AJaThX4tNIhqBYBtNzCVJrUD2ljBbS1fdn7If5tth1Nxq+Q1rPQiaCgp 9Hn+r3n44ws4CUxqS3GaDBPhQw==
X-Google-Smtp-Source: AGs4zMbY2t9KbSyxBCEDH+C2HkTM8FprWtpfR+AJKrt77gBQsej6GPzzYSvZIpYrf2iiSp2YT4WcTw==
X-Received: by 10.55.166.81 with SMTP id p78mr28276605qke.191.1511289699224; Tue, 21 Nov 2017 10:41:39 -0800 (PST)
Received: from cavall.lan (c-24-60-163-103.hsd1.ma.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id 46sm9535952qtx.65.2017.11.21.10.41.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Nov 2017 10:41:38 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <94E611DE-18C4-4316-ADCB-FC4A3E8BA5C2@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C4AF0072-37C3-48C5-B450-CC21B1F56899"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: a list observation
Date: Tue, 21 Nov 2017 13:41:37 -0500
In-Reply-To: <CAF4+nEHhuU52ZjW1L95iZFRW8DjxwmShc8+pnaebFR686W66_w@mail.gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
To: Donald Eastlake <d3e3e3@gmail.com>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com> <646156EE-5216-4A55-A21B-FF652E09A800@isc.org> <EB776714EFDEDE10566B7B9A@PSB> <6D891B92-0FD1-41C0-B38B-3EFF7E0108A5@isc.org> <7BCB6555-2BFD-4816-9A54-FE81ED56D026@gmail.com> <CAF4+nEHhuU52ZjW1L95iZFRW8DjxwmShc8+pnaebFR686W66_w@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VVvcFckzcOynepJsUpvM0RWj1T4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 18:41:42 -0000

--Apple-Mail=_C4AF0072-37C3-48C5-B450-CC21B1F56899
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 21, 2017, at 1:39 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> I noticed the low quality of the audio in the rooms as well. I maybe
> it was just me but it looks like I was not alone. Frequently sounded
> like loud, muddy lower frequency audio drowning out voices...

Yes, it sounded like they'd seriously notched out certain frequencies to =
avoid feedback.   Getting this stuff right is a bit of an art form.


--Apple-Mail=_C4AF0072-37C3-48C5-B450-CC21B1F56899
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; line-break: after-white-space;" class=3D"">On =
Nov 21, 2017, at 1:39 PM, Donald Eastlake &lt;<a =
href=3D"mailto:d3e3e3@gmail.com" class=3D"">d3e3e3@gmail.com</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"">I noticed the low =
quality of the audio in the rooms as well. I maybe</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""><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"">it was just me but it looks like I was not =
alone. Frequently sounded</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""><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"">like loud, muddy =
lower frequency audio drowning out =
voices...</span></div></blockquote></div><br class=3D""><div =
class=3D"">Yes, it sounded like they'd seriously notched out certain =
frequencies to avoid feedback. &nbsp; Getting this stuff right is a bit =
of an art form.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_C4AF0072-37C3-48C5-B450-CC21B1F56899--


From nobody Tue Nov 21 15:34:43 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 6F52B126C22 for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 15:34:42 -0800 (PST)
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] 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 UACwgSilXah3 for <ietf@ietfa.amsl.com>; Tue, 21 Nov 2017 15:34:41 -0800 (PST)
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 1BD1312947B for <ietf@ietf.org>; Tue, 21 Nov 2017 15:34:41 -0800 (PST)
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 7081958C4ED; Wed, 22 Nov 2017 00:34:37 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id 55437B0D238; Wed, 22 Nov 2017 00:34:37 +0100 (CET)
Date: Wed, 22 Nov 2017 00:34:37 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Ted Lemon <mellon@fugue.com>
Cc: Donald Eastlake <d3e3e3@gmail.com>, John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>, ietf-team@meetecho.com
Subject: Re: a list observation
Message-ID: <20171121233437.GB14650@faui40p.informatik.uni-erlangen.de>
References: <339747207.368008.1511224632283.ref@mail.yahoo.com> <339747207.368008.1511224632283@mail.yahoo.com> <646156EE-5216-4A55-A21B-FF652E09A800@isc.org> <EB776714EFDEDE10566B7B9A@PSB> <6D891B92-0FD1-41C0-B38B-3EFF7E0108A5@isc.org> <7BCB6555-2BFD-4816-9A54-FE81ED56D026@gmail.com> <CAF4+nEHhuU52ZjW1L95iZFRW8DjxwmShc8+pnaebFR686W66_w@mail.gmail.com> <94E611DE-18C4-4316-ADCB-FC4A3E8BA5C2@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <94E611DE-18C4-4316-ADCB-FC4A3E8BA5C2@fugue.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H6C9dFYMmEonWXP0pXimemfPM3s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Nov 2017 23:34:42 -0000

Adding ietf-team@meetecho.com (is there an actual open ietf mailing list to
move this discussion to instead of ietf ML ?)

Remote echo cancellation software/devices typically have a maximum supported
RTT. The larger, there more difficult it becomes AFAIK. Maybe the explanation
for lower than normal remote attendents quality is as simple as having longer RTT
because we where at the other side of the planet from the cranky remote
participants ?

Cheers
    Toerless

On Tue, Nov 21, 2017 at 01:41:37PM -0500, Ted Lemon wrote:
> On Nov 21, 2017, at 1:39 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
> > I noticed the low quality of the audio in the rooms as well. I maybe
> > it was just me but it looks like I was not alone. Frequently sounded
> > like loud, muddy lower frequency audio drowning out voices...
> 
> Yes, it sounded like they'd seriously notched out certain frequencies to avoid feedback.   Getting this stuff right is a bit of an art form.
> 


From nobody Wed Nov 22 06:55:33 2017
Return-Path: <Pierce.Gorman@sprint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4548A12783A; Wed, 22 Nov 2017 06:55:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQdGlVJkVfbU; Wed, 22 Nov 2017 06:55:24 -0800 (PST)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0100.outbound.protection.outlook.com [104.47.41.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55F801200FC; Wed, 22 Nov 2017 06:55:24 -0800 (PST)
Received: from DM5PR05CA0034.namprd05.prod.outlook.com (10.174.188.151) by CY4PR05MB3159.namprd05.prod.outlook.com (10.172.155.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.260.2; Wed, 22 Nov 2017 14:55:22 +0000
Received: from SN1NAM01FT049.eop-nam01.prod.protection.outlook.com (2a01:111:f400:7e40::200) by DM5PR05CA0034.outlook.office365.com (2603:10b6:4:39::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.260.2 via Frontend Transport; Wed, 22 Nov 2017 14:55:22 +0000
Received-SPF: Pass (protection.outlook.com: domain of sprint.com designates 144.230.172.39 as permitted sender) receiver=protection.outlook.com; client-ip=144.230.172.39; helo=plsapdm3.corp.sprint.com;
Received: from plsapdm3.corp.sprint.com (144.230.172.39) by SN1NAM01FT049.mail.protection.outlook.com (10.152.64.252) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.239.4 via Frontend Transport; Wed, 22 Nov 2017 14:55:21 +0000
Received: from pps.filterd (plsapdm3.corp.sprint.com [127.0.0.1]) by plsapdm3.corp.sprint.com (8.16.0.21/8.16.0.21) with SMTP id vAMEneqF016771;  Wed, 22 Nov 2017 08:55:21 -0600
Received: from prewe13m04.ad.sprint.com (prewe13m04.corp.sprint.com [144.226.128.23]) by plsapdm3.corp.sprint.com with ESMTP id 2eak0e7vgu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 22 Nov 2017 08:55:21 -0600
Received: from PLSWE13M04.ad.sprint.com (2002:90e5:d617::90e5:d617) by PREWE13M04.ad.sprint.com (2002:90e2:8017::90e2:8017) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 22 Nov 2017 09:55:19 -0500
Received: from PLSWE13M04.ad.sprint.com ([fe80::2c01:fcb8:e729:4a7a]) by plswe13m04.ad.sprint.com ([fe80::2c01:fcb8:e729:4a7a%24]) with mapi id 15.00.1347.000; Wed, 22 Nov 2017 08:55:19 -0600
From: "Gorman, Pierce A [CTO]" <Pierce.Gorman@sprint.com>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>, Sean Turner <sean@sn3rd.com>
CC: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-stir-certificates.all@ietf.org" <draft-ietf-stir-certificates.all@ietf.org>, "stir@ietf.org" <stir@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [stir] Genart last call review of draft-ietf-stir-certificates-15
Thread-Topic: [stir] Genart last call review of draft-ietf-stir-certificates-15
Thread-Index: AQHTYwNb6hhFWqukmUCZ9HdusJxwVqMgfZhQ
Date: Wed, 22 Nov 2017 14:55:19 +0000
Message-ID: <640a7ab6132c462b9b1baafeb31caee9@plswe13m04.ad.sprint.com>
References: <151090177468.22136.5281729043778955691@ietfa.amsl.com> <3A0F58AA-1397-445F-AD99-CED165E4EAE4@sn3rd.com> <09f05bf5-c23a-ba1f-116a-a94b44680f59@joelhalpern.com>
In-Reply-To: <09f05bf5-c23a-ba1f-116a-a94b44680f59@joelhalpern.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.123.104.29]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-MS-Office365-Filtering-HT: Tenant
X-Forefront-Antispam-Report: CIP:144.230.172.39; IPV:NLI; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(39860400002)(2980300002)(438002)(13464003)(377424004)(199003)(189002)(24454002)(305945005)(6246003)(24736003)(14454004)(230783001)(53936002)(72206003)(47776003)(86362001)(478600001)(97736004)(4001150100001)(50466002)(108616004)(8936002)(229853002)(3846002)(2486003)(4326008)(2906002)(7696004)(5660300001)(2950100002)(102836003)(6116002)(106466001)(5250100002)(53546010)(2900100001)(7736002)(33646002)(6306002)(68736007)(189998001)(110136005)(81156014)(316002)(8676002)(106002)(50986999)(76176999)(81166006)(23676004)(54356999)(356003)(54906003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR05MB3159; H:plsapdm3.corp.sprint.com; FPR:; SPF:Pass; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-Microsoft-Exchange-Diagnostics: 1; SN1NAM01FT049; 1:jOxOA5sPw9N0KPuRRiCHu5lWzIaHSoa7SVREXtK136H/bqp+y5QpoN1zAekJDbL+x3jn5wiVaFGf5rvlZP5XQaECtiM6rWyHCQazGxhZS2YaX2ccPzxMXzJiKvewZBMV
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 3d38e31d-a34d-4d47-4198-08d531b90e4c
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600022)(4604075)(4608076)(2017052603258); SRVR:CY4PR05MB3159; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3159; 3:ErQCespIDRzwhCs4G58d6HOb8onmlVwXM6bsN75V6LrnJmuFvvac8mtpNY+/5BpT/GUe076HI0/L+lzyLYHQQaHLpZ/3Im3Tgti85ueux7CdhCeOqjrmjW2cuy8pB0dce4yNPb8qEkqiySPmcGFDWAw8ugsHWI3YvUQEoRA+zwj58FfSE136xak81ZrnvOfRR3jvXjOMswLzQkmt5ZZWKTTwcuLDIrrrwt/gIKB377Bl7pmkFDW7ekWVM/nZFIPX4VoUr3wB5DtR6LZx86lu9JxFKU25vrbDBLpX8QWGipueztxvtHt13RyArZrdcGCzlEOu/VydpOsfYi53MbcqgSprTLaTn5A6MCA2lXtl3JI=; 25:CDjACcrUFE7+3mQ9sqchaUqsqx48fEmSwGEXZXvyaHvhg7UjZuK6EtdIw4sWqtJj/f7H93pyyY3IBDY1M0HSkSNQEjLHEMD2d56HhW11O/s0Zx/GjZcRMNqy0yNLOICQq39O539WeEWafwC/gy9ehMxfIPJgKDpVtPM9kMrBs58RG1UIlwrzTG9N6Ug4kMZxS7bsDxsxphIzhNmcvS5G6biv0a+X1RLHBURGoysGFnc458Bt5YnBUzdvqoC9idsdUOAAWDP6DB2RYQaPCffTIUVs5sMAw8XRAHT7FMq9nYY5uqcfzA9O1qhvwGNJRF/PqLm3GDmIZaC40u192XKzMQ==
X-MS-TrafficTypeDiagnostic: CY4PR05MB3159:
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3159; 31:dOsVSJbrb8d9WZSFOJ5DW+ontLSZ0w64kMv1lhgSsq6bj9hKzFKKMqQNAYwAR+e3XhbtuQvd1iGixTrN9UiIBcPBug5vF2VcQjUOV+zEZqS8+UShQh2Sy0ldiM8V35fFcE70cwLNWKa7virrT6fhs/lbs5tHuI+anrg6qVc7F8HCt5h/dB1mnwHfoA47bMuILroEJhK0NwumVQkAxaSDa23Hie/HwHMPlQ6oxUP6Yxo=; 20:pCquSPuFxi5PxQhDI+HZfy1yxxP3KfC3swQ8dMplouC1NKwUu9OMTEHGb0gVS1iVEAB7ZOFQanBWTMEd/ek5YzsULVN3DxhkBlkcq2Kyi8RR4EGwRP4RY3EmgqNaej0Lp7oPX+OmqVlNbXFNQh1KoER71/hZmAh52da5UGlIU+OWP6reGjSiPVRYSOXAhCKV38nRO5CMebtipQCQdDx/fIz/uSclB+E1sOSM7+mMXYtWsGWb/riTXQx54Ev1dCqUDfHlO6EpVHfRp4mfeWXbtgj/hYVSd4Rm/8HPLX8miGgVONJdi0Zsq7jJjH7e38bByWPGPtzT6JlHPDpsEWYsvfcnDFpSQy1f2MR11itZpumRj5lyOLazEjjUy0KbLgc40ucuXORx2yaGK28TRP71QLB9Ug9WpZCPP5NuL63oHkuPAPflD+EzD1s6hfU/5f5B+zqMCUXoqxCIuamX9IlnfcOfbF9q1MM+9PSmwQn0ThRoc/GFWTXCBeQustRMd46y
X-Microsoft-Antispam-PRVS: <CY4PR05MB3159D6A177ECC6FEF661588E89200@CY4PR05MB3159.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(192374486261705)(788757137089);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93004095)(3002001)(100000703101)(100105400095)(3231022)(6055026)(6041248)(20161123558100)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123562025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR05MB3159; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR05MB3159; 
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3159; 4:F6ttSvdQCbmttUAtJGTz8Bv+v/51J97clwBtgUW7j7ZZxk95Kk0G/jYHfBRX25lVOFco8nzrdiXBFDdpnM+3TfEiorX82ePGDHz9jPtpOsBzHz+QCSKq5qPk4kGpYK0m07MqVccFXxH9h6SV4121+e2V4z4ntwYijQUEFxWRlBawa5UHLka9YtUJXHhlyjMfrNXxSbYQ3OWm1LKkPOb1SJiD0oJ1HL92zRmRaDk8YwRbF5xVyKGn0/jwOlfZiOWlqqcAR8LZymtBNU04qpoJh8XxnlUMQjjzImjR0fRAtcWA545v/0NvYGZvqkoO5KY871X0y0twB5UnTlsNVnXkRw==
X-Forefront-PRVS: 0499DAF22A
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtDWTRQUjA1TUIzMTU5OzIzOkxkaFRXM2hQM296OXFVbURDVlNrZXB0L0Mr?= =?utf-8?B?WmJqWjBCb2JQanNaZm5idWlacWpyMmJtOWdUek9YY3ZIRmhyc0lpWDBHcEIz?= =?utf-8?B?OWF2czl5NUQ3cllLRGtSOXduVHI4UWo0WEg5aUF1QVVUOFcyYnRjZXdKYTFy?= =?utf-8?B?WmZOS3RjYWxjeWdhek5iZlJIV3RDSWVEYloweG0wa0FRWGtPby9XREdVcWUr?= =?utf-8?B?RWY5TWpaVUZwVFpTQzVrMkhWTGR3RDgvalFoQnVJdzdSQmJuZE1UMnVHNEN3?= =?utf-8?B?VTVLU3lzQ3pDVXMzQi9jWTFnTXQ5MzJBWnNvTkVVcTM1OXVBWmxGNkVPUmFy?= =?utf-8?B?Z2c2ejlpME1HNTVDWGx2dzk2UFduTFpIUTlObnZHdjlaVkpDYUlZMjZXcWpC?= =?utf-8?B?UWxweHJTWU9mMU4rRGs3WHpneldxYnRkZlBkdXU4bEpVNzVETHNKWjZCRlBL?= =?utf-8?B?eWxGVWxrYzliWlBaQk5zYmxRUDdJQjRDMERDSDFLemk2RUp6dWZ1OE1iaEVC?= =?utf-8?B?YmVSWWpyNkJLRG5SUXovSHA0VXR2SDl3V29rK3NwWDBHUFd5dFhoZSt6V1FL?= =?utf-8?B?YkNqNnB6SHY2RjhOaEowdUhSWnFqVXZFdXRWRU1wS0FQeVN5KzB5cHVJRnpu?= =?utf-8?B?RWNkenQxd0NQcXJOS2lMTDkrZWtqNHVwY3R4TGgyQms2YkZ5WHkrL1RTUXZw?= =?utf-8?B?eUlacWpKdjdub1QrcmI4N3ZJbmllQ0dVdkVyT2ovckJIQWVrZmw1eVhrTXB2?= =?utf-8?B?RUYzZ3NrazVkZWlta2VFU1FtT3ZkWW1OWTJKWEtRbG1UVkZXalVpSDJZOVNN?= =?utf-8?B?aXVGcjV2SnZTZkw0NDg4OHlJQ0tNNTlCTGRoMFZFNjRDYXpiUkRRVElJYTU1?= =?utf-8?B?TjhadVcwckxVMXI2bktHb3hwR1M0VUgwT0d0RWFPRU9xbUdwR0pYNEJ1MXRC?= =?utf-8?B?dEZtNlFwZlJwRkgyZTJVaHdoeXA4QTNWdzd0YXY1cStnZGRQWkJJYzFoTUQ5?= =?utf-8?B?M0FQZVM2Vlk5UXNMekJseGY2MXFLbmY4TTRtVWozbEt5S1JFRWJuRzBLVHdV?= =?utf-8?B?Z3dNOFg4UDlBRmQrUE9ZTmpYMTZ5UFE5U2pLcUJqWGdrdTR6Tm9IcU1qL09H?= =?utf-8?B?V1RxRk4xQnd4TUVPZGg2b0lCbEZMdzQ5a3ZNeWZaN3A5UnZlYmdMVGpreWZS?= =?utf-8?B?bW13S1RlUkgyYXloQldReW9nT1VGYm1UM25YaFJDbVVkY2ZTVS9TM2pRVGJV?= =?utf-8?B?QUxVajdFeUdjU2hpYTRMdHE1c1BMUGttRzIxbHhjV0N0OFk1d0g3M1NSbDAy?= =?utf-8?B?MUdTRngzUEozclFQNzhaV1RoMVkyNGtHSXF6eEg5Y0xpV1BvaWRRQnNjQlJT?= =?utf-8?B?ZFlqK0s4OHgwMUplekNIVFJ4d3FKMFgySU9KZE56NHAxaFh2VzIzZ1JKanIx?= =?utf-8?B?S2IrcmFCdS8rZDNCamorZ0g2TG9OL2ZOWnFKSGNvejJCRVZPaENrc284SGI4?= =?utf-8?B?N052YjhFZzZEc1pMaVRTT1J4TDZ4WDNnUkdCOW5Vb1hHdnRkK1pwNnp0MmV6?= =?utf-8?B?cFFaZjl5NnpLeEVJTDNkV240ak9SYnYyMktxR0pYM3JsbC9HZVJTY3B2UzVh?= =?utf-8?B?N0p1NWp3SHlqcFZsTkEyTkxjU3FYMS9IWWNRVEFPb2ZaRERZM3hmTWI4cjE4?= =?utf-8?B?OUx3OTJ1UWNIb0syWUFJNHliT0NaWCtlbzhpZWpodC80NjgyMTdDendCdTdN?= =?utf-8?B?RGllK0pNczBEUjZERElTNmZFTnBmV3Y2ZldTM0VBeExOcW0yemZqZW1qejdT?= =?utf-8?Q?rHtq9KeKkvkZi?=
X-Microsoft-Exchange-Diagnostics: 1; CY4PR05MB3159; 6:4EPYOFD3rjcK8I9RivRc4uzBaxtuq7ExM0UKQm21+EWTq/rBLtoAWUxMCJS8ffI28dlSq/QocrjEPphmCic+bq51m2mUBs1JEDe0V7wMK4W/q4zTnuA3IgGhG0kI+Yq5moHiu6wgBn4WnE8uVKiT5J7pI529sNkQf13223fVwx3XZmBstCrg838vQz+2bHNRawYZFt5gsPwVEaNnZkrEwnAoIK7AANgxC78uY2Jnziv6P+swTXSjF73WqHHKMxhcnr2a/eUdrudzjTa305p9Hr74mkG6nQHi/o8/Beg6/zT1ep9vyrGZlJSSVycmTfqEySTmYXXDIF7Kc31d+h3V8Rn4VGp0OY+RcpxiWzlQ2II=; 5:CBRw0zSecZ5BiDnP43/sdQ7ozbX73swmG+WkGqPGKKarC9v92jZNHNO3wKUhEPwn/tISkme4yFsg+bkZ4Jrsxyi6pjOqGTm1vGIWQa80c0RFz4Jxw08Dl81M5oBQPE1pqq2p1eS3rH8vJ8YW7n3TRHk1LRGvzhPVVaoKgWv9U28=; 24:kpMiQ95CrW0ORvvikekynHZx4tEFcYL0IzmLXEH2c0PYOYxm62FlQrsG1ij31Zvl1v1qeyRCf+WzeUdK1g/MxAeY+bFVa4A2MylpSUn3FhU=; 7:F4sM0xKnMra3GfEVDi2rQYvEaOmaExrRtN5f5/0v4KbylSPMD2LddUtTTwzZn1WEROYmb8qD5Yn/JrBzYtSp1KNW9Na/o7W9JSORuiFecGrgO1af254pjY6oAKQPSJtCRmJGTAypYY5VHFf7uBFx93Co/TORtF6C0IxKWZYnTqkzQ3Mfj3LOFqLSTTFSYj2dCudJOZV4EjXDnryEXef2hCEgHVbKhcTYWkcOWhSCwRP1gtv5P8oJu1P56v7j/QiO
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-OriginatorOrg: sprint.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Nov 2017 14:55:21.8882 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 3d38e31d-a34d-4d47-4198-08d531b90e4c
X-MS-Exchange-CrossTenant-Id: 4f8bc0ac-bd78-4bf5-b55f-1b31301d9adf
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=4f8bc0ac-bd78-4bf5-b55f-1b31301d9adf; Ip=[144.230.172.39];  Helo=[plsapdm3.corp.sprint.com]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR05MB3159
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u8IONBFivPMvcB6xifzUiZI6ElY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Nov 2017 14:55:27 -0000

RldJVy4uLg0KDQorMSBAICJJIGNvdWxkIHdlbGwgdW5kZXJzdGFuZCBpZGVudGlmeWluZyB0aGUg
cHJvYmxlbSBhbmQgc2F5aW5nIHRoYXQgdGhpcyB3b3JrIGRvZXMgbm90IGF0dGVtcHQgdG8gcmVz
b2x2ZSBpdC4iDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IEpvZWwgSGFs
cGVybiBEaXJlY3QgW21haWx0bzpqbWguZGlyZWN0QGpvZWxoYWxwZXJuLmNvbV0NClNlbnQ6IFR1
ZXNkYXksIE5vdmVtYmVyIDIxLCAyMDE3IDk6MjUgQU0NClRvOiBTZWFuIFR1cm5lciA8c2VhbkBz
bjNyZC5jb20+DQpDYzogZ2VuLWFydEBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1zdGlyLWNlcnRpZmlj
YXRlcy5hbGxAaWV0Zi5vcmc7IHN0aXJAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNClN1YmplY3Q6
IFJlOiBbc3Rpcl0gR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1zdGlyLWNl
cnRpZmljYXRlcy0xNQ0KDQpUaGFuYmtzIFNlYW4uICBPbiB0aGUgZmlyc3QgcG9pbnQsIHVzaW5n
ICJsYXR0ZXIiIHdpbGwgZml4IHRoZSBwcm9ibGVtIG5pY2VseS4NCg0KT24gdGhlIHBvaW50IGFi
b3V0IENBIGNvbmZsaWN0cywgSSB1bmRlcnN0YW5kIHRoZSBkZXNpcmUgdG8gc3RheSBvdXQgb2Yg
dGhlIHN3YW1wLiAgR2l2ZW4gdGhhdCBjYWxscyBhcmUgZnJlcXVlbnRseSBpbnRlcm5hdGlvbmFs
LCBJIGFtIHVuY2xlYXIgaG93IE5hdGlvbmFsIE51bWJlcmluZyBBdXRob3JpdGllcyBjYW4gYWRk
cmVzcyB0aGUgaXNzdWUgb2YgaW5hcHByb3ByaWF0ZSBhc3NlcnRpb25zIGZyb20gZm9yZWlnbiBD
QXMuICBFYWNoIGNvdW50cnkgY2FuIHByb3RlY3QgaXRzZWxmIGZyb20gZm9sa3MgcHJldGVuZGlu
ZyB0byBiZSBpdC4gIEJ1dCB0aGV5IGNhbid0IHByb3RlY3QgdGhlbXNlbHZlcyBmcm9tIG90aGVy
LUEgYXV0aG9yaXppbmcgbnVtYmVycyB3aXRoaW4gb3RoZXItQi4NCkkgY291bGQgd2VsbCB1bmRl
cnN0YW5kIGlkZW50aWZ5aW5nIHRoZSBwcm9ibGVtIGFuZCBzYXlpbmcgdGhhdCB0aGlzIHdvcmsg
ZG9lcyBub3QgYXR0ZW1wdCB0byByZXNvbHZlIGl0LiAgSSB3b3VsZCBub3QgY29uc2lkZXIgdGhh
dCB0byBiZSBjb3B5aW5nIHRleHQsIGdpdmVuIHRoYXQgdGhlIHJlZmVyZW5jZWQgc2VjdGlvbiBp
cyBNVUNIIHZhZ3VlciB0aGFuIHRoYXQuDQpIYXZpbmcgc2FpZCB0aGF0LCBJIGRvIGNvbnNpZGVy
IGl0IG1pbm9yLCBhbmQgaWYgeW91IGZlZWwgaXQgd291bGQgaGFybSB0aGUgZG9jdW1lbnQgdGhl
biB0aGF0IGlzIG1vcmUgaW1wb3J0YW50Lg0KDQpZb3VycywNCkpvZWwNCg0KT24gMTEvMjEvMTcg
MTA6MTkgQU0sIFNlYW4gVHVybmVyIHdyb3RlOg0KPg0KPj4gT24gTm92IDE3LCAyMDE3LCBhdCAx
NDo1NiwgSm9lbCBIYWxwZXJuIDxqbWhAam9lbGhhbHBlcm4uY29tPiB3cm90ZToNCj4+DQo+PiBS
ZXZpZXdlcjogSm9lbCBIYWxwZXJuDQo+PiBSZXZpZXcgcmVzdWx0OiBSZWFkeQ0KPj4NCj4+IEkg
YW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5l
cmFsIEFyZWENCj4+IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3Vt
ZW50cyBiZWluZyBwcm9jZXNzZWQgYnkNCj4+IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4g
IFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0IGxpa2UNCj4+IGFueSBvdGhlciBsYXN0
IGNhbGwgY29tbWVudHMuDQo+Pg0KPj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUg
dGhlIEZBUSBhdA0KPj4NCj4+IDxodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9H
ZW5BcnRmYXE+Lg0KPj4NCj4+IERvY3VtZW50OiBkcmFmdC1pZXRmLXN0aXItY2VydGlmaWNhdGVz
LTE1DQo+PiBSZXZpZXdlcjogSm9lbCBIYWxwZXJuDQo+PiBSZXZpZXcgRGF0ZTogMjAxNy0xMS0x
Ng0KPj4gSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0xMS0zMA0KPj4gSUVTRyBUZWxlY2hhdCBkYXRl
OiAyMDE3LTEyLTE0DQo+Pg0KPj4gU3VtbWFyeToNCj4+DQo+PiBNYWpvciBpc3N1ZXM6DQo+Pg0K
Pj4gTWlub3IgaXNzdWVzOg0KPj4gICAgIFNlY3Rpb24gNCBidWxsZXQgNCBpbiBuYW1pbmcgdGhl
IGNyeXB0byBhbGdvcml0aG1zIHJlZmVycyBxdWl0ZSBjbGVhcmx5IHRvDQo+PiAgICAgMiBhbGdv
cml0aG1zLiAgSXQgdGhlbiByZWZlcmVuY2VzIG9uZSBvZiB0aGVtIGFzIFJTMjU2LiAgSSBhc3N1
bWUgdGhvc2UNCj4+ICAgICB2ZXJzZWQgaW4gdGhlIGZpZWxkIHdpbGwga25vdyB3aGljaCBvbmUg
aXMgbWVhbnQuICBCdXQgaXQgd291bGQgYmUgYmV0dGVyDQo+PiAgICAgaWYgdGhlIGFiYnJldmlh
dGlvbiBSUzI1NiBhcHBlYXJlZCBuZXh0IHRvIHRoZSBmaXJzdCByZWZlcmVuY2UgdG8gd2hpY2hl
dmVyDQo+PiAgICAgYWxnb3JpdGhtIGl0IG1lYW5zLg0KPg0KPiBBaCBva2F5IEkgc2VlIHdoYXTi
gJlzIGdvaW5nIG9uLCB0aGUgdHdvIGFsZ29yaXRobXMgYXJlIGludHJvZHVjZWQgaW4gdGhlIHBy
ZXZpb3VzIHNlbnRlbmNlIGJ1dCB3ZSB1c2UgdGhlIHJlZ2lzdGVyZWQgdmFsdWUgYXMgb3Bwb3Nl
ZCB0byB0aGUgbmFtZSBpbiB0aGUgbmV4dCBzZW50ZW5jZS4gIEhvdyBhYm91dCBJIHJlcGxhY2Ug
4oCcUlMyNTYiIHdpdGggdGhlIOKAnGxhdHRlcuKAnSBhcyBpdCBpcyB0aGUgMm5kIGFsZ29yaXRo
bSBkaXNjdXNzZWQgaW4gdGhlIHByZXZpb3VzIHNlbnRlbmNlLg0KPg0KPj4gICAgIFRoZSBzZWN1
cml0eSBjb25zaWRlcmF0aW9ucyBzZWN0aW9uIHBvaW50cyB0byBSRkMgNTI4MCBzZWN1cml0eQ0K
Pj4gICAgIGNvbnNpZGVyYXRpb25zIGZvciBtb3N0IGlzc3Vlcy4gIEkgcHJlc3VtZSB0aGF0IHRo
ZSBpbnRlbnRpb24gaXMgdG8gdXNlDQo+PiAgICAgdGhhdCBzZWN0aW9uIHJlZ2FyZGluZyB0cnVz
dGluZyBDQXMuICBIb3dldmVyLCBpdCBzZWVtcyB0aGF0IHRoZXJlIGlzIGFuDQo+PiAgICAgaXNz
dWUgaGVyZSBtdWNoIGxpa2UgdGhhdCBvZiBjbGFzc2ljIHdlYiBDQXMuICBUaGUgbnVtYmVyIG9m
IENBcyB0aGF0IG11c3QNCj4+ICAgICBiZSB0cnVzdGVkIHNlZW1zIHRvIGJlIG9uIHRoZSBvcmRl
ciBvZiB0aGUgbnVtYmVyIG9mIGNvdW50cmllcyBpbiB0aGUNCj4+ICAgICB3b3JsZC4gIFRoYXQg
c2VlbXMgdG8gbGVhdmUgYSBsYXJnZSB3aW5kb3cgZm9yIGZhbHNlIG9yIG1pc2xlYWRpbmcNCj4+
ICAgICBjZXJ0aWZpY2F0aW9ucywgYXMgSSBjYW4gc2VlIG5vdGhpbmcgd2hpY2ggcmVzdHJpY3Rz
IHdoYXQgbnVtYmVycyBmb3Igd2hpY2gNCj4+ICAgICB0aG9zZSB0b3AgbGV2ZWwgQ0FzIGNhbiBw
cm92aWRlIGF0dGVzdGF0aW9uLiAgSSBwcmVzdW1lIHdlIGRvIG5vdCB3YW50IHRvDQo+PiAgICAg
Z28gZG93biB0aGUgcGF0aCBvZiByZXF1aXJpbmcgYW4gdWJlci1DQSBmb3IgYWxsIG5hdGlvbmFs
IGF1dGhvcml0aWVzLiAgSQ0KPj4gICAgIHdvdWxkIGV4cGVjdCBzb21lIGV4cGxpY2l0IHJlY29n
bml0aW9uIG9mIHRoaXMgaXNzdWUgaW4gdGhpcyBkb2N1bWVudC4NCj4NCj4gVHdvIHBvaW50cyBp
bnRlcnR3aW5lZCBoZXJlOg0KPg0KPiAtIHViZXItQ0E6IFRoZSBXRyBleHBsaWNpdGx5IGFncmVl
ZCB0byBzYXkgbm90aGluZyBhYm91dCB0aGlzIHRvcGljLiAgSSBhZ3JlZSB3aXRoIHlvdSB0aGF0
IHdlIHNob3VsZCBub3QgYWRkIGFueSB0ZXh0IGNvbmNlcm5pbmcgdGhpcyBwb2ludC4NCj4NCj4g
LSBUcnVzdCBBbmNob3IvRGVsZWdhdGlvbjogUkZDNTI4MOKAmXMgU2VjQ29ucyBhbHJlYWR5IHN0
YXRlIHRoYXQgZGV0ZXJtaW5pbmcgdGhlIFRydXN0ZWQgQ0EgKGFrYSBUcnVzdCBBbmNob3IpIGlz
IG91dCBvZiBzY29wZS4gIFRoZSBzYW1lIGlzIHRydWUgaGVyZSBhbmQgSSBndWVzcyBJIGNvdWxk
IGNvcHkgdGhhdCB0ZXh0IG92ZXIsIGJ1dCBpdCBzZWVtcyB1bm5lY2Vzc2FyeSBpbiBteSBtaW5k
IGdpdmVuIHRoYXQgYSkgaGFsZiB0aGUgdGltZSBJIGdldCBjaGFzdGlzZWQgZm9yIGNvcHlpbmcg
Zm9yd2FyZCBTZWNDb25zLCBhbmQgbW9yZSBpbXBvcnRhbnRseSBiKSB0aGVyZeKAmXMgYXJlIG1v
cmUgc3BlY2lmaWNhdGlvbnMgcmVxdWlyZWQgdG8gaW1wbGVtZW50IHRoaXMgaW5jbHVkaW5nIGJ1
dCBub3QgbGltaXRlZCB0byBhIENQIChDZXJ0aWZpY2F0aW9uIFBvbGljeSkgYW5kIENQUyAoQ2Vy
dGlmaWNhdGlvbiBQcmFjdGljZSBTdGF0ZW1lbnQpOyB0aGVzZSBhZGRpdGlvbmFsIHNwZWNpZmlj
YXRpb25zIGdldCB3cml0dGVuL2FwcHJvdmVkL3B1Ymxpc2hlZCBieSBOYXRpb25hbCBOdW1iZXJp
bmcgQXV0aG9yaXRpZXMuDQo+DQo+IHNwdA0KPg0KDQoNCg0KX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCg0KVGhpcyBlLW1haWwgbWF5IGNvbnRhaW4gU3ByaW50IHByb3ByaWV0YXJ5
IGluZm9ybWF0aW9uIGludGVuZGVkIGZvciB0aGUgc29sZSB1c2Ugb2YgdGhlIHJlY2lwaWVudChz
KS4gQW55IHVzZSBieSBvdGhlcnMgaXMgcHJvaGliaXRlZC4gSWYgeW91IGFyZSBub3QgdGhlIGlu
dGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIGNvbnRhY3QgdGhlIHNlbmRlciBhbmQgZGVsZXRlIGFs
bCBjb3BpZXMgb2YgdGhlIG1lc3NhZ2UuDQo=


From nobody Wed Nov 22 07:01:54 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 18A7F129447 for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 07:01:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level: 
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 noe1iEqErjlj for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 07:01:51 -0800 (PST)
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 81EA412783A for <ietf@ietf.org>; Wed, 22 Nov 2017 07:01:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=973; q=dns/txt; s=iport; t=1511362911; x=1512572511; h=to:from:subject:message-id:date:mime-version; bh=RPnEa132GJpBuikayN/ErB9vbpp5v+2Cyh0KrQQftfA=; b=MTEMYcJAJtEBIhOiFXwAohZ/0ri6eNd7+rB2YBgY0TOf+8CACrllgMv9 0p0A+1ijXEo0KdeT54gpxi6zYhOYgWOnNeZXwzrm3FUOzBIeTsPKbGsWk VClTV6Vcq/15Xtja59IwxeuGudfY4XW0e7f3ga8l4/rbHXb5CUewvkF3S E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AlAgB7kBVa/xbLJq1cGgEBAQEBAgEBA?= =?us-ascii?q?QEIAQEBAYQiboQmixOPeJFChVmCAQolinYVAQEBAQEBAQEBayiFFTN0AQI8Al8?= =?us-ascii?q?NCAEBih4QqCqCJyaKUgEBAQEGAQEBAQEeBYM6g1yCEguEQIMag02CYwWMX4xFi?= =?us-ascii?q?RyVDIwEh0mOQ4d0gTo1I4F1NCEIHRWDLoJngXhAjDIBAQE?=
X-IronPort-AV: E=Sophos;i="5.44,436,1505779200"; d="scan'208,217";a="366345"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Nov 2017 15:01:49 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id vAMF1nS9013368 for <ietf@ietf.org>; Wed, 22 Nov 2017 15:01:49 GMT
To: IETF-Discussion list <ietf@ietf.org>
From: Benoit Claise <bclaise@cisco.com>
Subject: Blog: YANG Catalog Latest Developments (IETF 100 Hackathon)
Message-ID: <8e4cec79-e248-56fa-7168-e9a31b5e5eff@cisco.com>
Date: Wed, 22 Nov 2017 16:01:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------FAF9F8F65294AFF6E899ECE5"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QbTknfWqjWwAIoK3nVzb9sa6rZg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Nov 2017 15:01:53 -0000

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

Dear all,

https://www.ietf.org/blog/2017/11/yang-catalog-latest-developments-ietf-100-hackathon/ 

Enjoy.

Regards, Benoit


--------------FAF9F8F65294AFF6E899ECE5
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">
    Dear all,
    <br>
    <br>
    <a moz-do-not-send="true"
href="https://www.ietf.org/blog/2017/11/yang-catalog-latest-developments-ietf-100-hackathon/">https://www.ietf.org/blog/2017/11/yang-catalog-latest-developments-ietf-100-hackathon/
    </a><br>
    Enjoy.
    <br>
    <br>
    Regards, Benoit
    <br>
    <br>
  </body>
</html>

--------------FAF9F8F65294AFF6E899ECE5--


From nobody Wed Nov 22 09:32:23 2017
Return-Path: <jtk@depaul.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 AE5BF129492 for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 09:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2nNubiPb7tEA for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 09:32:19 -0800 (PST)
Received: from aharp.iorc.depaul.edu (aharp.iorc.depaul.edu [IPv6:2620:0:2250:2115:c0a7:18f5:bca1:ba92]) by ietfa.amsl.com (Postfix) with ESMTP id 391D41294C4 for <ietf@ietf.org>; Wed, 22 Nov 2017 09:32:10 -0800 (PST)
Received: from p50.localdomain (localhost [127.0.0.1]) by aharp.iorc.depaul.edu (Postfix) with ESMTP id 4033E1F08 for <ietf@ietf.org>; Wed, 22 Nov 2017 17:32:09 +0000 (UTC)
Date: Wed, 22 Nov 2017 11:32:09 -0600
From: John Kristoff <jtk@depaul.edu>
To: IETF general list <ietf@ietf.org>
Subject: Archive of uoregon.edu recordings?
Message-ID: <20171122113209.306c0d6a@p50.localdomain>
Reply-To: jtk@aharp.iorc.depaul.edu
X-Trump: Sucks
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YAmPDC2ce2bDqQRhJg1vab-9E1s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Nov 2017 17:32:22 -0000

A number of years ago the fine folks from uoregon captured the audio
or video of a number of IETF meetings (and others).  They were stored
on videolab|limestone.uoregon.edu as I recall.

There are a couple of old drafts from Joel Jaeggli documenting some of
this work and it is suggested there was a non-public archive of it.

Does any know if those recordings survive somewhere that are or could
be made available? I didn't find anything on archive.org or in a
rudimentary net search.

John


From nobody Wed Nov 22 09:43:03 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 592A31294C7 for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 09:43:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AtT0T_YN491F for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 09:43:00 -0800 (PST)
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 B88F412949A for <ietf@ietf.org>; Wed, 22 Nov 2017 09:43:00 -0800 (PST)
Received: from mb.local (209-58-196-114.static-ip.telepacific.net [209.58.196.114]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id vAMHgxtA057081 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 22 Nov 2017 17:42:59 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host 209-58-196-114.static-ip.telepacific.net [209.58.196.114] claimed to be mb.local
Subject: Re: Archive of uoregon.edu recordings?
To: John Kristoff <jtk@depaul.edu>, IETF general list <ietf@ietf.org>
References: <20171122113209.306c0d6a@p50.localdomain>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <75508722-7b65-cda4-30cd-bf04e1d50bd2@bogus.com>
Date: Wed, 22 Nov 2017 09:42:58 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:57.0) Gecko/20100101 Thunderbird/57.0
MIME-Version: 1.0
In-Reply-To: <20171122113209.306c0d6a@p50.localdomain>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c-tgJINNyy6VspeMlBNr-CHIrxw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Nov 2017 17:43:02 -0000

On 11/22/17 09:32, John Kristoff wrote:
> A number of years ago the fine folks from uoregon captured the audio
> or video of a number of IETF meetings (and others).  They were stored
> on videolab|limestone.uoregon.edu as I recall.
> 
> There are a couple of old drafts from Joel Jaeggli documenting some of
> this work and it is suggested there was a non-public archive of it.
> 
> Does any know if those recordings survive somewhere that are or could
> be made available? I didn't find anything on archive.org or in a
> rudimentary net search.

https://www.ietf.org/audio/

back to 49

Kevin Almeroth had some rtp recordings from the mbone era, those weren't
in our archive.

> John
> 


From nobody Wed Nov 22 09:49:34 2017
Return-Path: <jtk@depaul.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 C9309129501 for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 09:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6iif0MHYynVj for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 09:49:31 -0800 (PST)
Received: from aharp.iorc.depaul.edu (aharp.iorc.depaul.edu [140.192.218.132]) by ietfa.amsl.com (Postfix) with ESMTP id 954B21294F8 for <ietf@ietf.org>; Wed, 22 Nov 2017 09:49:30 -0800 (PST)
Received: from p50.localdomain (localhost [127.0.0.1]) by aharp.iorc.depaul.edu (Postfix) with ESMTP id F36321F08; Wed, 22 Nov 2017 17:49:29 +0000 (UTC)
Date: Wed, 22 Nov 2017 11:49:29 -0600
From: John Kristoff <jtk@depaul.edu>
To: joel jaeggli <joelja@bogus.com>
Cc: IETF general list <ietf@ietf.org>
Subject: Re: Archive of uoregon.edu recordings?
Message-ID: <20171122114929.20d480d7@p50.localdomain>
In-Reply-To: <13b6fca4bcce46b6b68fd8e1561b6a16@XCASPRD02-DFT.dpu.depaul.edu>
References: <20171122113209.306c0d6a@p50.localdomain> <13b6fca4bcce46b6b68fd8e1561b6a16@XCASPRD02-DFT.dpu.depaul.edu>
Reply-To: jtk@aharp.iorc.depaul.edu
X-Trump: Sucks
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vFycBZyr32P43Wn5um7sgaaqodU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Nov 2017 17:49:33 -0000

On Wed, 22 Nov 2017 17:42:58 +0000
joel jaeggli <joelja@bogus.com> wrote:

> https://www.ietf.org/audio/
> 
> back to 49

Thanks Joel, I hadn't realized the old ones were put there.  I miss the
video that used to be available and some of the other meetings you had
recorded, but that is very helpful for my immediate needs.

John


From nobody Wed Nov 22 14:22:07 2017
Return-Path: <corazza@incert.com.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A82DB129BBB for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 14:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUg7bFRL6bBF for <ietf@ietfa.amsl.com>; Wed, 22 Nov 2017 14:22:05 -0800 (PST)
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E46E3126CF9 for <ietf@ietf.org>; Wed, 22 Nov 2017 14:22:04 -0800 (PST)
Received: from n264957 (131.108.216.32 [131.108.216.32]) by mx.zohomail.com with SMTPS id 1511389318708555.9281851284056; Wed, 22 Nov 2017 14:21:58 -0800 (PST)
From: "Junior Corazza" <corazza@incert.com.br>
To: <ietf@ietf.org>
Subject: RES: IP's for point-to-point and loopbacks 
Date: Wed, 22 Nov 2017 20:21:54 -0200
Message-ID: <000501d363e0$4f67c060$ee374120$@incert.com.br>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AdNj3wIE5AjRo6vpRBetjgT36LU4rQ==
Content-Language: pt-br
X-ZohoMailClient: External
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b-1OrCkz__pN6cVxb1GP2FV1jWQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Nov 2017 22:22:07 -0000

Reviving the topic.
Carlos, thanks for the reply.

My idea is really this, why not create an RFC and define a blocks of IPs =
for
that use? So RFC2544 (which in my opinion is obsolete) has a block /15
reserved, why not break that block in 2 /16? The first /16 continues =
with
RFC 2544 and the second /16 we could use for network interconnect,
point-to-point and loopback.

That would be an RFC draft, right?

Pe=E7o a ajuda da comunidade para tentarmos viabilizar essa ideia


------------

Message: 1
Date: Wed, 01 Nov 2017 17:25:59 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
To: "Paul Wouters" <paul@nohats.ca>
Cc: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: IP's for point-to-point and loopbacks
Message-ID: <8BC77937-BBB0-4DC7-997D-09A1138691F3@gmail.com>
Content-Type: text/plain; charset=3D"utf-8"; Format=3D"flowed"

Hi!

On 27 Oct 2017, at 16:54, Paul Wouters wrote:

> However, there is a lot of unused multicast and reserved space left to =

> do assignments from. I?m not sure why we haven?t started nibbling on=20
> those yet, other then wanting to promote ipv6?

It?s been said around that those ranges would present problems if used =
on
the public Internet. Namely, there is zero guarantee that they will be
widely routable.

Now, if we were to carve blocks for p2p and loopbacks from them _under =
the
assumption that they are_ a kind ?extended/special use? private space, =
maybe
it?s not such a bad idea.



From nobody Thu Nov 23 05:24:13 2017
Return-Path: <davidjtrapp@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 B8EBF12426E; Thu, 23 Nov 2017 05:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.491
X-Spam-Level: 
X-Spam-Status: No, score=-5.491 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, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] 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 yCXZCJmtXGEr; Thu, 23 Nov 2017 05:24:09 -0800 (PST)
Received: from pv35p10im-ztdg05011101.me.com (pv35p10im-ztdg05011101.me.com [17.133.186.85]) (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 E4D34120046; Thu, 23 Nov 2017 05:24:09 -0800 (PST)
Received: from process-dkim-sign-daemon.pv35p10im-ztdg05011101.me.com by pv35p10im-ztdg05011101.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0OZV00C00H2BXS00@pv35p10im-ztdg05011101.me.com>; Thu, 23 Nov 2017 13:24:09 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1511443449;	bh=8Nyy5Qlthrjv9aKFj7iVACjI2W1nMOv2eaH3dpmykYc=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=OrJCww7ezOvZWSo8qAqfhDDscdyKkXVILHtORl6Bvv+WBR+4cx1QqptG0THwzvlBK n1bdi5C20JQ++0Dg6rKcSJG6ayIdDDXI2I5IU1EMCiObIK4Wp/JsI8Xjx711o5zrX+ QTi7/cmROy1i8/eyJmWey0uchdkHYaXw7Pb8hcuNRmB/IZMyKj0r84SWhQ5wJjL7vd FlOZ6ocUV0TzD17+SDaGs8FdrC/yKvZxCv1QX98CZzoKc3Bii0+dCkYydZL280uVHQ VgbUUVc/qAsdQ3JJoIISTOGgpOVZoTKgYv6Qzd17NuaONOAH6OOvntiY/MQoG+aP4r R5wqSR5fNSjaA==
Received: from icloud.com ([127.0.0.1]) by pv35p10im-ztdg05011101.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0OZV0060LH860050@pv35p10im-ztdg05011101.me.com>; Thu, 23 Nov 2017 13:24:09 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-23_05:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711230185
From: David Trapp <davidjtrapp@icloud.com>
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: quoted-printable
MIME-version: 1.0 (Mac OS X Mail 11.0 \(3445.1.7\))
Subject: Re: Formal IESG Teleconference WebEx and Dial-in Information: 30 November 2017
Date: Thu, 23 Nov 2017 08:24:05 -0500
References: <151144327485.13107.13440696018611730563.idtracker@ietfa.amsl.com>
To: ietf@ietf.org, The IESG <iesg-secretary@ietf.org>
In-reply-to: <151144327485.13107.13440696018611730563.idtracker@ietfa.amsl.com>
Message-id: <BA7724DD-9163-40AA-A7FA-4CF9B9178B68@icloud.com>
X-Mailer: Apple Mail (2.3445.1.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/75zhJ0Anmv3-IF9xkh3MwI5MOO0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Nov 2017 13:24:12 -0000

Unusbscribe

> On Nov 23, 2017, at 8:21 AM, IESG Secretary <iesg-secretary@ietf.org> =
wrote:
>=20
> As previously announced [1], all members of the community are welcome =
to=20
> attend formal IESG telechats as observers.
>=20
> The next formal IESG telechat will be held on Thursday, November 30,=20=

> 2017 at 07:00 PT (14:00 UTC).  WebEx and Dial-in information is at the =
bottom of this message.
>=20
> The agenda for the upcoming telechat can be found at
> <https://datatracker.ietf.org/iesg/agenda/>
>=20
> A calendar of upcoming public telechats can be downloaded or =
subscribed=20
> to at:=20
> https://www.ietf.org/webdav/calendars/iesg/iesgpublic.ics
>=20
>=20
> Topic: IESG Formal Telechat
> Date: Thursday, November 30, 2017
> Time: 	07:00 PDT (San Francisco, UTC-07:00)
> 	09:00 CDT
> 	10:00 EDT
> 	14:00 UTC
> 	15:00 UK, Ireland
> 	16:00 Germany, Belgium
> 	17:00 Finland
>        01:00 (next day) Australia (Queensland)
>=20
>=20
> -------------------------------------------------------=20
> JOIN WEBEX MEETING
> =
https://ietf.webex.com/ietf/j.php?MTID=3Dm343b1173b6e1ed21d30db16ee0202473=

> Meeting number: 642 944 708
> Meeting password: 1234
>=20
>=20
> JOIN BY PHONE
> 1-877-668-4493 Call-in toll free number (US/Canada)=20
> 1-650-479-3208 Call-in toll number (US/Canada)
> Access code: 642 944 708
> -------------------------------------------------------=20
> To join the audio conference using Skype=20
> -------------------------------------------------------=20
> 1.  Bring up your Skype application.
> 2.  Bring up your browser, and go to the WebEx URL.
> 3.  Enter your name and email address.
> 4.  Close the WebEx window prompting for a phone number.
> 5.  Select the "info" tab at the top of the WebEx browser page.
> 6.  Go to Skype, and dial the U.S. Toll-Free number from the meeting=20=

>    announcement.
> 7.  Click on the DialPad tab on the Skype window.
> 8.  Use the virtual keypad to enter the meeting number followed by #.
> 9.  Use the virtual keypad to enter your attendee ID followed by #.
>=20
> The playback of UCF (Universal Communications Format) rich media files
> requires appropriate players. To view this type of rich media files in
> the meeting, please check whether you have the players installed on =
your
> computer by going to https://workgreen.webex.com/workgreen/
> systemdiagnosis.php.
>=20
> Sign up for a free trial of WebEx
> http://www.webex.com/go/mcemfreetrial
>=20
> http://www.webex.com
>=20
> CCP:+14087926300x960506070#
>=20
> IMPORTANT NOTICE: This WebEx service includes a feature that allows
> audio and any documents and other materials exchanged or viewed during
> the session to be recorded. By joining this session, you automatically
> consent to such recordings. If you do not consent to the recording,
> discuss your concerns with the meeting host prior to the start of the
> recording or do not join the session. Please note that any such
> recordings may be subject to discovery in the event of litigation.
>=20
> [1] =
https://mailarchive.ietf.org/arch/msg/ietf-announce/Eackc8-MgJw8IbdquLuPlc=
oDZpo
>=20


From nobody Thu Nov 23 08:42: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 0901D12EBA0 for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 08:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ey7hcJWdCTCh for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 08:42:53 -0800 (PST)
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 98B32129464 for <ietf@ietf.org>; Thu, 23 Nov 2017 08:42:53 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 763D92008C for <ietf@ietf.org>; Thu, 23 Nov 2017 11:45:02 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C11AA8068A for <ietf@ietf.org>; Thu, 23 Nov 2017 11:42:52 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: new things that ISOC could do: collect data on breakage
In-Reply-To: <a8da1861-7db3-39c9-13de-f69ff4a514b1@gmail.com>
References: <m1eEGbJ-0000EhC@stereo.hq.phicoh.net> <CAFU7BARoXgodiTJfTGc1dUfQ8-ER_r8UOE1c3h-+G0KTeCgBew@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300A07C625@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <7EE41034-132E-45F0-8F76-6BA6AFE3E916@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D481@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0C83562D-859B-438C-9A90-2480BB166737@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D534@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <26A31D20-46C2-473E-9565-59E5BA85ED8B@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D63D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F9E3BD88-38E0-4329-A4BF-22083A023268@employees.org> <f673d6c7-570e-b2b8-e8aa-15d73ea8ba3f@gmail.com> <46365c7f-f9e9-0559-9f09-d6b565ff7f99@nlogic.no> <0a13ea07-6b60-9ae6-659e-c054acdc156d@gmail.com> <2bbae231-d57e-4ba7-8ac5-65dbba9a9da2@gmail.com> <CAD6AjGR=g4M-=ndPugaLcGPrGCne284fY60kfO5MBaWoU1y4NA@mail.gmail.com> <a8da1861-7db3-39c9-13de-f69ff4a514b1@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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: Thu, 23 Nov 2017 11:42:52 -0500
Message-ID: <4462.1511455372@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b0mLcuWVtYsxg-PjarUhRBVSD8g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Nov 2017 16:42:56 -0000

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


{Many people expressed various amounts of outrage privately that I should
suggest that ISOC do any kind of conformance testing.}

So, let me suggest something slightly less which just occured to me from a
6man thread which I include below.  Please read Brian's imagined letter in
quotes, and think about how "corporate travel plan" can get the data that it
needs to make such a decision.

ipv6-test.com actually does a pretty good job of a lot of the testing I have
in mind for travellers at hotels.  And they collect data about which
ISP/country is involved: http://ipv6-test.com/stats/

What's missing is the ability to collect the information in a useful way ba=
ck
to the people/organizations that paid for the hotel such that they have
enough data.   i.e. a way to volunteer non-anonymous statistics to a private
collection.

And ipv6-test.com only works if you minimally can get online at least a bit,
although since it's javascript maybe a file:// URL version could be created.

This is something that ISOC could do:  help collect measurements of problem=
s.
I know that people and places like kc@caida and Geoff Houston do a lot of
systematic testing of some things, but not random stuff.


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> I like to refer back to Occam=E2=80=99s Razor e2e v6 rather than tra=
nsition Rube
    >> Goldberg

    > I think we all agree on the long-term fix. The issue seems to be how
    > we can best (or least badly) deal with legacy hosts and apps that
    > will be out there for years, generating help desk calls or lost
    > business.

    > "Hi! Your hotel group has been removed from our corporate travel
    > plan because none of our employees can connect to our corporate VPN
    > from your hotels any more, as confirmed by your WiFi supplier."

So, I've been hoping that between sunset4, bahave, capport and ipsecme, that
we'd get some set of tests that could be run on a laptop/smartphone which
would characterize the nature of the breakage better.

ipv6-test.com actually gets 60% of the way there, but when the breakage
occurs, we do not really have a place to report/collate the information.


=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+93Q3WUFAloW+owACgkQgItw+93Q
3WUa2AgAgnB7v4UnfkKDhlL/CO8pRNvQB7xK4NfO10Dc/eiUJuC9ptABqj1ELfrq
xuezp+VemIo87fPG96E1eKLsYfE+TRsYjgw6JHyOjy8NUN5obklh8PYZT7qFGy2x
nXKPwKqYxWdM0qp9ZhQ4otxewAbl7ymKMjlOzQKA7CCF9hfkJ5Me2co7e68OWCjA
Ka2eKmom/22iHImP6XhhniYsKT/CL5JzQ7bART08b/qYMEsi30MQ5BA75xJ7EWB6
PrIKCsNn6D3//twO0KUM57TS/Lc48AXEnPiyOIcBIbe9MAUT+Aai2LPAse1rgKpR
FFPMAbkrCt3JlJvGP/NJ+eBS6AFEMw==
=CgRB
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Nov 23 09:47:10 2017
Return-Path: <prvs=1500d7d9e5=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 432FB12948F for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 09:47:08 -0800 (PST)
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 LZSWKTri4t7x for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 09:47:06 -0800 (PST)
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 D45BD1293F9 for <ietf@ietf.org>; Thu, 23 Nov 2017 09:47:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1511459224; x=1512064024; 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=ntQeDwHXIrn1hBnYhfXwcbcIg hsrsKHQ+tQ9VUc6bTk=; b=f5fROsFpVivVgRdL9w/NMxmAMZEBU9MbeTfvmbTR7 8yMbUP+FqDQ2IQ8wwSYd9ANmiob6KzHdZlXIk1DkCYByQKM5Rsi4Ip63gcP1VjnA oeR4nKszrRlslSvVjD3CQY7KVWngXcGt1LcbrnQ6UyHcfxhCVQgGda12Sn8votzA Rk=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=CGgQka71KsU7KGuc5FImX7jYFN0QRAJ/T9o2VhEL6X/E0v00WwArxyHbglKg xIhNKOU9hb8765B7wDk3jt2Z7pB60AKhpywLqYp1hhi00TcbMcxQYDoN1 69RL2tErotZA3WFbzV/GuSt1y+qIjo1iNlBP54xrKbytAdQ2uG/SsI=;
X-MDAV-Processed: mail.consulintel.es, Thu, 23 Nov 2017 18:47:03 +0100
X-Spam-Processed: mail.consulintel.es, Thu, 23 Nov 2017 18:47:02 +0100
Received: from [192.168.48.77] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005636894.msg for <ietf@ietf.org>; Thu, 23 Nov 2017 18:47:01 +0100
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:171123:md50005636894::TGlwgiGtGryodH21:00001Obs
X-Return-Path: prvs=1500d7d9e5=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.27.0.171010
Date: Thu, 23 Nov 2017 18:46:53 +0100
Subject: Re: new things that ISOC could do: collect data on breakage
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf@ietf.org>
Message-ID: <FCE69734-A232-4B0C-8C65-C2EC11EF8243@consulintel.es>
Thread-Topic: new things that ISOC could do: collect data on breakage
References: <m1eEGbJ-0000EhC@stereo.hq.phicoh.net> <CAFU7BARoXgodiTJfTGc1dUfQ8-ER_r8UOE1c3h-+G0KTeCgBew@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300A07C625@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <7EE41034-132E-45F0-8F76-6BA6AFE3E916@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D481@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0C83562D-859B-438C-9A90-2480BB166737@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D534@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <26A31D20-46C2-473E-9565-59E5BA85ED8B@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D63D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F9E3BD88-38E0-4329-A4BF-22083A023268@employees.org> <f673d6c7-570e-b2b8-e8aa-15d73ea8ba3f@gmail.com> <46365c7f-f9e9-0559-9f09-d6b565ff7f99@nlogic.no> <0a13ea07-6b60-9ae6-659e-c054acdc156d@gmail.com> <2bbae231-d57e-4ba7-8ac5-65dbba9a9da2@gmail.com> <CAD6AjGR=g4M-=ndPugaLcGPrGCne284fY60kfO5MBaWoU1y4NA@mail.gmail.com> <a8da1861-7db3-39c9-13de-f69ff4a514b1@gmail.com> <4462.1511455372@obiwan.sandelman.ca>
In-Reply-To: <4462.1511455372@obiwan.sandelman.ca>
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/yk2JtY_SD33vuoRRoyan2HqSsHY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Nov 2017 17:47:08 -0000

Well =E2=80=A6.

This is somehow related to this work:

https://datatracker.ietf.org/doc/draft-palet-v6ops-he-reporting/

I=E2=80=99m just trying to figure out how to make easy an automatic reporti=
ng to a common system among ISPs, while avoiding possible privacy issues.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Michael Richardson <mcr+ietf@=
sandelman.ca>
Responder a: <mcr+ietf@sandelman.ca>
Fecha: jueves, 23 de noviembre de 2017, 17:43
Para: <ietf@ietf.org>
Asunto: new things that ISOC could do: collect data on breakage

   =20
    {Many people expressed various amounts of outrage privately that I shou=
ld
    suggest that ISOC do any kind of conformance testing.}
   =20
    So, let me suggest something slightly less which just occured to me fro=
m a
    6man thread which I include below.  Please read Brian's imagined letter=
 in
    quotes, and think about how "corporate travel plan" can get the data th=
at it
    needs to make such a decision.
   =20
    ipv6-test.com actually does a pretty good job of a lot of the testing I=
 have
    in mind for travellers at hotels.  And they collect data about which
    ISP/country is involved: http://ipv6-test.com/stats/
   =20
    What's missing is the ability to collect the information in a useful wa=
y back
    to the people/organizations that paid for the hotel such that they have
    enough data.   i.e. a way to volunteer non-anonymous statistics to a pr=
ivate
    collection.
   =20
    And ipv6-test.com only works if you minimally can get online at least a=
 bit,
    although since it's javascript maybe a file:// URL version could be cre=
ated.
   =20
    This is something that ISOC could do:  help collect measurements of pro=
blems.
    I know that people and places like kc@caida and Geoff Houston do a lot =
of
    systematic testing of some things, but not random stuff.
   =20
   =20
    Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
        >> I like to refer back to Occam=E2=80=99s Razor e2e v6 rather than=
 transition Rube
        >> Goldberg
   =20
        > I think we all agree on the long-term fix. The issue seems to be =
how
        > we can best (or least badly) deal with legacy hosts and apps that
        > will be out there for years, generating help desk calls or lost
        > business.
   =20
        > "Hi! Your hotel group has been removed from our corporate travel
        > plan because none of our employees can connect to our corporate V=
PN
        > from your hotels any more, as confirmed by your WiFi supplier."
   =20
    So, I've been hoping that between sunset4, bahave, capport and ipsecme,=
 that
    we'd get some set of tests that could be run on a laptop/smartphone whi=
ch
    would characterize the nature of the breakage better.
   =20
    ipv6-test.com actually gets 60% of the way there, but when the breakage
    occurs, we do not really have a place to report/collate the information=
.
   =20
   =20
    --
    Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
     -=3D IPv6 IoT consulting =3D-
   =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 exclusive use of the i=
ndividual(s) named above and further non-explicilty authorized disclosure, =
copying, distribution or use of the contents of this information, even if p=
artially, including attached files, is strictly prohibited and will be cons=
idered a criminal offense. If you are not the intended recipient be aware t=
hat any disclosure, copying, distribution or use of the contents of this in=
formation, even if partially, including attached files, is strictly prohibi=
ted, will be considered a criminal offense, so you must reply to the origin=
al sender to inform about this communication and delete it.




From nobody Thu Nov 23 13:12: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 E4F411243F3 for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 13:12:04 -0800 (PST)
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 YpIYQ8f398mn for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 13:12:03 -0800 (PST)
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 2FF0212025C for <ietf@ietf.org>; Thu, 23 Nov 2017 13:12:03 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B18432008C; Thu, 23 Nov 2017 16:14:12 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 598AF8068A; Thu, 23 Nov 2017 16:12:02 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: jordi.palet@consulintel.es
cc: ietf@ietf.org
Subject: Re: new things that ISOC could do: collect data on breakage
In-Reply-To: <FCE69734-A232-4B0C-8C65-C2EC11EF8243@consulintel.es>
References: <m1eEGbJ-0000EhC@stereo.hq.phicoh.net> <CAFU7BARoXgodiTJfTGc1dUfQ8-ER_r8UOE1c3h-+G0KTeCgBew@mail.gmail.com> <787AE7BB302AE849A7480A190F8B93300A07C625@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <7EE41034-132E-45F0-8F76-6BA6AFE3E916@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D481@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <0C83562D-859B-438C-9A90-2480BB166737@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D534@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <26A31D20-46C2-473E-9565-59E5BA85ED8B@employees.org> <787AE7BB302AE849A7480A190F8B93300A07D63D@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <F9E3BD88-38E0-4329-A4BF-22083A023268@employees.org> <f673d6c7-570e-b2b8-e8aa-15d73ea8ba3f@gmail.com> <46365c7f-f9e9-0559-9f09-d6b565ff7f99@nlogic.no> <0a13ea07-6b60-9ae6-659e-c054acdc156d@gmail.com> <2bbae231-d57e-4ba7-8ac5-65dbba9a9da2@gmail.com> <CAD6AjGR=g4M-=ndPugaLcGPrGCne284fY60kfO5MBaWoU1y4NA@mail.gmail.com> <a8da1861-7db3-39c9-13de-f69ff4a514b1@gmail.com> <4462.15 11455372@obiwan.sandelman.ca> <FCE69734-A232-4B0C-8C65-C2EC11EF8243@consulintel.es>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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: Thu, 23 Nov 2017 16:12:02 -0500
Message-ID: <5838.1511471522@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LinkBg5x3UtVPMsMGSCYu8W2JI8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Nov 2017 21:12:05 -0000

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


JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
    > This is somehow related to this work:

    > https://datatracker.ietf.org/doc/draft-palet-v6ops-he-reporting/

   In order to simplify the reporting of the HE failures, syslog
   ([RFC5424]) over UDP ([RFC5426]), MUST be used, by means of the
   default port (514) with IPv6-only.

btw, TCP port 514 is "rlogin" and both UDP and TCP are often blocked because
of lazyness....  And syslog is often blocked intentionally.
I suggest that the MILE work might provide a better structure for that.

When you write "operator" is that the operator of the web site, or the
operator of the network you are in?

Given that most hotel networks feature absentee landlords, this is
why I want to involve ISOC.

    >> "Hi! Your hotel group has been removed from our corporate travel
    >> plan because none of our employees can connect to our corporate VPN
    >> from your hotels any more, as confirmed by your WiFi supplier."


--
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+93Q3WUFAloXOaIACgkQgItw+93Q
3WWvuwf/apvOFszJF3ay8alrMchEdSx/+EojFjqEGCaGGJPBnTstX8/tK5PXeUEl
bcVRLBF1+xE4Yvs+Yup2trsp9Wp6iLD3MTqm4fwl5nnY+KRBvNc/uZDlh1L3YaSi
RcIrCdWoJuv1RJuHZPsYCCSqy6HUlDVkOd4VoyeqmW72M1RBwZs8Cd/oKJFU3NOB
GYlCwQwsP6OiPCS5oN9/o4usGa8YKi33bVHGRM5Svpxg4ZDVdg6mxSJagLNUxIVd
+0PCnZ1Mjx8yWmdBLi8cLImjoKWeX9lBleByammO+7Y68LcN9ylIxDPKUzvqe5k1
fJaJmkxGBi0A0xPXA9dRaJMcj8/YWA==
=+d94
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Nov 23 21:53:13 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 D0ECE129AAD for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 21:53:11 -0800 (PST)
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 ccPZYlzpz2OD for <ietf@ietfa.amsl.com>; Thu, 23 Nov 2017 21:53:09 -0800 (PST)
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 8BA96129AA3 for <ietf@ietf.org>; Thu, 23 Nov 2017 21:53:09 -0800 (PST)
Received: from pps.filterd (m0098419.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vAO5nnue033511 for <ietf@ietf.org>; Fri, 24 Nov 2017 00:53:08 -0500
Received: from e14.ny.us.ibm.com (e14.ny.us.ibm.com [129.33.205.204]) by mx0b-001b2d01.pphosted.com with ESMTP id 2eeb3s70xn-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 24 Nov 2017 00:53:08 -0500
Received: from localhost by e14.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, 24 Nov 2017 00:53:07 -0500
Received: from b01cxnp23032.gho.pok.ibm.com (9.57.198.27) by e14.ny.us.ibm.com (146.89.104.201) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 24 Nov 2017 00:53:05 -0500
Received: from b01ledav002.gho.pok.ibm.com (b01ledav002.gho.pok.ibm.com [9.57.199.107]) by b01cxnp23032.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id vAO5r5fu40632538 for <ietf@ietf.org>; Fri, 24 Nov 2017 05:53:05 GMT
Received: from b01ledav002.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id BBB7212403D for <ietf@ietf.org>; Fri, 24 Nov 2017 00:50:07 -0500 (EST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav002.gho.pok.ibm.com (Postfix) with ESMTPS id A8722124035 for <ietf@ietf.org>; Fri, 24 Nov 2017 00:50:07 -0500 (EST)
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 vAO5r4BO025880 for <ietf@ietf.org>; Fri, 24 Nov 2017 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id vAO5r36q025799 for ietf@ietf.org; Fri, 24 Nov 2017 00:53:03 -0500
From: narten@us.ibm.com
Date: Fri, 24 Nov 2017 00:53:02 -0500
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: 17112405-0052-0000-0000-000002876F69
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00008111; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000241; SDB=6.00950367; UDB=6.00479970; IPR=6.00730476;  BA=6.00005708; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00018160; XFM=3.00000015; UTC=2017-11-24 05:53:06
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17112405-0053-0000-0000-000052B7631F
Message-Id: <201711240553.vAO5r36q025799@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-11-24_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=13 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-1709140000 definitions=main-1711240079
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E0qY2gMbIijvtDDeqDXDomP-U-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: Fri, 24 Nov 2017 05:53:12 -0000

Total of 47 messages in the last 7 days.
 
script run at: Fri Nov 24 00:53:02 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.64% |    5 | 12.35% |    60493 | jordi.palet@consulintel.es
  8.51% |    4 |  7.72% |    37789 | mcr+ietf@sandelman.ca
  8.51% |    4 |  7.18% |    35153 | john-ietf@jck.com
  6.38% |    3 |  5.34% |    26125 | marka@isc.org
  4.26% |    2 |  4.43% |    21679 | mellon@fugue.com
  4.26% |    2 |  3.84% |    18804 | stewart.bryant@gmail.com
  4.26% |    2 |  3.74% |    18291 | cabo@tzi.org
  4.26% |    2 |  3.62% |    17712 | lloyd.wood@yahoo.co.uk
  4.26% |    2 |  2.59% |    12686 | nomcom-chair-2017@ietf.org
  2.13% |    1 |  4.55% |    22255 | pierce.gorman@sprint.com
  2.13% |    1 |  3.92% |    19191 | barryleiba@computer.org
  2.13% |    1 |  3.79% |    18580 | eric.gray@ericsson.com
  2.13% |    1 |  2.69% |    13188 | davidjtrapp@icloud.com
  2.13% |    1 |  2.53% |    12404 | narten@us.ibm.com
  2.13% |    1 |  2.45% |    11979 | amorris@amsl.com
  2.13% |    1 |  2.42% |    11849 | jmh.direct@joelhalpern.com
  2.13% |    1 |  2.37% |    11591 | sean@sn3rd.com
  2.13% |    1 |  2.24% |    10979 | john.lemon@broadcom.com
  2.13% |    1 |  2.22% |    10880 | mersue@gmail.com
  2.13% |    1 |  2.15% |    10528 | dbg@scs.stanford.edu
  2.13% |    1 |  2.14% |    10466 | shahanajabc@gmail.com
  2.13% |    1 |  2.00% |     9776 | olejacobsen@me.com
  2.13% |    1 |  1.94% |     9483 | d3e3e3@gmail.com
  2.13% |    1 |  1.89% |     9250 | bclaise@cisco.com
  2.13% |    1 |  1.73% |     8491 | ajs@crankycanuck.ca
  2.13% |    1 |  1.67% |     8180 | christer.holmberg@ericsson.com
  2.13% |    1 |  1.67% |     8170 | tte@cs.fau.de
  2.13% |    1 |  1.66% |     8107 | corazza@incert.com.br
  2.13% |    1 |  1.63% |     7970 | joelja@bogus.com
  2.13% |    1 |  1.55% |     7594 | jmh@joelhalpern.com
--------+------+--------+----------+------------------------
100.00% |   47 |100.00% |   489643 | Total


From nobody Fri Nov 24 06:06:47 2017
Return-Path: <gonzalo.camarillo@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 DBE4D1286B1 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 06:06:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 uIw4CY7PdhEd for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 06:06:42 -0800 (PST)
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 20ED612871F for <ietf@ietf.org>; Fri, 24 Nov 2017 06:06:41 -0800 (PST)
X-AuditID: c1b4fb30-a25ff70000002554-27-5a1827700b9d
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.183.42]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id C1.C9.09556.077281A5; Fri, 24 Nov 2017 15:06:40 +0100 (CET)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.42) with Microsoft SMTP Server (TLS) id 14.3.352.0; Fri, 24 Nov 2017 15:06:39 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qKZUycQTeiaqA5F4diHgU/lyUbLTfSKekskO0e6D00I=; b=kAEeRI0yTHRV6f4hApV+jn1R2WdqQ6Je2nqYJg9cK3LqtDxvhpB9BTSYXFPRWpZs5Mqb9oIO2ssGmvH/jImkVT7onUiucoYrjs1yZ7UqWMcND7NnyqUiakxNEmtwRuoXEUl/ZV/9XJ0DQHG8WuCITzkjZEz4DXKRCEY5ya9KFBI=
Received: from [131.160.50.141] (89.166.49.243) by DB3PR07MB0634.eurprd07.prod.outlook.com (2a01:111:e400:943c::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.260.2; Fri, 24 Nov 2017 14:06:38 +0000
Subject: Re: Proposal to revise ISOC's mission statement
To: <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com>
Date: Fri, 24 Nov 2017 16:06:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [89.166.49.243]
X-ClientProxiedBy: LNXP265CA0061.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5d::25) To DB3PR07MB0634.eurprd07.prod.outlook.com (2a01:111:e400:943c::24)
X-MS-PublicTrafficType: Email
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:DB3PR07MB0634; 
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0634; 3:cNZ5wkmZ4AzTr10FgRERH8tVZTLLm85s4nvcrAruj8yAjo3a6BX6CLrtqU6t1Fll0ecrul2H43P9mv9nEWduwIIKoBIb/5RJriBV9nj2dRLhKdtE/gTawtwwJhCTMc5bhozXh3PARCghmwM1of0cdH0x9kzLyTln3QN+RQJYCgYhDC93FZ9y5iit7OuRdWwAuYf/5rzwoYjl9MSGB5qk4DPmumejGNii3DcCcMThtYXEJprL5UBpzJMgWO8a3BIE; 25:iz4Svc7BKCLFS5m4vS3FONYBBFfaNXwZGSEPxiUoegXL8pQlhIbgtQSkEfau0gm1bjuLGph9qNkqIEyVIYggv9BEUhDONhJgOv2GKek5wNAJ6+NXJ23oC0f6Ko75IM+bIlSLjCGS7646foVIz5NDOTM69mMCg+ceaI6Ww6CgNwOosJiTz3ITs4teyetwuOuxYb/6f2zEop30Qkv/CNaUNTGTRhLzbl0DJU3Z0aXF7H868HyvrbpGhC+jqLIgaLMxiqt/QaIrglfJX/bGAeShOWGH0anpF6nkorHN7KgKXSCRvZNAELyRdnsvddumSIs0h45jI5vyUhf8+XMxVD4M2yLH8PxT2VR91Nl/UbB9Lxc=; 31:AaiN6Z3XAkBP8N5anCeLPiKb/4mdbfVPDBprell8yHIWV1WRcktj4jInGBik7jMccAEN5zBdk0IhKQ/lzmkHPAFeqJIR3uE/ei4kOdWIHXA9VaMVAoP7Pdp0vh2KffLdfB3ltLPhRYgifxQhmvNgLkpmx2XeK/yRiY817q8WxodCy5XPW9eubReWPk6oHPs3Y654vW580UbDCeeKMr9BhGVnYtRJbWaIkz5VzulFLMA=
X-MS-TrafficTypeDiagnostic: DB3PR07MB0634:
X-MS-Office365-Filtering-Correlation-Id: 0af95c38-cc67-46da-17b9-08d533449456
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0634; 20:PLk5cGQ73JZetZ1DUPvG9N63vsNBANhcfKlkTUs+mZa9pilS6BLFpnerTq5FuJsLJmKQMyNTT4QJml8wIP1DdtcVL5ru0CptdFwiJ2XCey5QMah80nn1gzeD7vnfaPPFfj1FT0JfBNy1Jj4YnJuYUK846Em3Rll6ioCy/6AKoGZ66reZa0JK4jZHonQIzq794AJAWoNfsvgkMe9ZgD/Nz+O83KLOHfubBjNfg9nZOBi6XEjwty4U9c/gjWAlYbCbDESo6C9TtXmVwT1wijBLS+8ezU7K6nH47DvgpitDgFCF2BZIyCj57ELdRRWe79rf0lgPEEyhm7VGdHhaB5AI1pkyLo/9gVs1UlsYuc+8p6e2YtrMTG1ggfrsHbADd8ui38PG9fdxgvuIPQahVkDUMhsFJnI2TS26JX8EXv9kcAA1AHjmvEHETX0yTfMuMlr4X0EZeVZAM7puT4J1a4Rhb/UZtL93jzLi/oO65lxbK4qIOfkS0nQ+PaKG7roKQylw; 4:eTLb6WII07qrqtWKMbqtNnnFdnW9wry61SXEm6u3udSe8FzdTwmdZlMXZMlw9eKrnKgvyOJZMwP65qDyuDA+XSBEmggDcG198WZI7YSi3McSeYjVGBtoTjLyunbO0Kl1nR265ovLorP0A1EHVlHs2ogjjARdgLflORr+3wZ1AHHsu5X4dgk7SLWbkJ387hRgiO/RycUDS9Kgcz12feeJ+QObK43vpMHlcVAhsBMShGCDWnBU2FTb0HHPs5qFvlUsW+MoGjI9eaTe7OGs3aHHoA==
X-Microsoft-Antispam-PRVS: <DB3PR07MB063468723E8EF33AA3B63E0B83260@DB3PR07MB0634.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231022)(6041248)(20161123555025)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(6072148)(201708071742011); SRVR:DB3PR07MB0634; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:DB3PR07MB0634; 
X-Forefront-PRVS: 05015EB482
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(39860400002)(376002)(346002)(366004)(189002)(199003)(111735001)(50466002)(561944003)(68736007)(478600001)(81156014)(101416001)(50986999)(966005)(81166006)(8676002)(76176999)(16576012)(54356999)(316002)(58126008)(16526018)(49976008)(31686004)(5660300001)(6916009)(2950100002)(2906002)(2361001)(2351001)(64126003)(6666003)(25786009)(106356001)(65826007)(8936002)(97736004)(52146003)(33646002)(189998001)(6116002)(3846002)(229853002)(7736002)(31696002)(36756003)(6486002)(23676004)(6246003)(86362001)(52116002)(230700001)(83506002)(53936002)(2486003)(65806001)(66066001)(47776003)(305945005)(65956001)(6306002)(105586002)(78286006); DIR:OUT; SFP:1101; SCL:1; SRVR:DB3PR07MB0634; H:[131.160.50.141]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjNQUjA3TUIwNjM0OzIzOmhoL3dkRWNPdU1Tb005MHhjOURYQnBpczVO?= =?utf-8?B?V3VIMkxBc2E4RTBySG5oYVQyL3pGeFpXUThTNjQwNWtKelY1cmRJeHo1ZVFC?= =?utf-8?B?S3lUcnNwLytNR3JoRDY4RnAyVExyT2tsdXMvK0NGZ2VxUE5ZcWwrUGxpZU5J?= =?utf-8?B?MUlTZ29mZkNobG8zelRSVXk4MWluRm1FN3ZoTjFEZHdMcUh0MW03Vi9sYnU2?= =?utf-8?B?bWZvQUNLbFdCRE10bkF0SUQvaGtWR1BMNTFqUkh2d0tFVmlPWEQ2WG9FamlD?= =?utf-8?B?VU5lM1l0WStNWnQrSHVPOUQ2bjlqaW01ZmNWWldiQkFURDlnSkdkR2ZCd01C?= =?utf-8?B?Z0pHayt5Tm5YbzdSZy9LekhJTDVXNXFBd1hnN29XK1FBN0YreDl6cnRTVlp0?= =?utf-8?B?MmsvMC9MZis2cUtGZndFd2VXM3Z3ZGVCaUEvVGg2YmFFY3NBM2o0bzJlSEhQ?= =?utf-8?B?UC9EdDZabUkrRjgzNHk4MzMxTEIwdS9uVVVCRmxtSDhZSndiWDQ0N1hBN2Z1?= =?utf-8?B?UytHMUdkSGtJcmtVM0pRd1MrUlplZGxFRFhVREE3bHNjL3U5NlgvSHdlSkV2?= =?utf-8?B?YWRoeHpXem4zcUJHc1N6ZTViV3JRdjRMSnZxSUlEcDIrZXdGRUlkRE1IR1ZL?= =?utf-8?B?U09KUHdQQWgxaGhlbmFVMlArUXhQeEV5WDdoT2lNY0FJZW1vK0ltUzVpdmx0?= =?utf-8?B?a2xZMEErT1RjQVlvcFRRYUc5eHQ5VlVlVy9WbTY4RlY0NGxuZ2VhMHA1aGFE?= =?utf-8?B?ZzdzbVBzVjVZKzUrRnJUTTlMZllvcVVVdW00Y09LZUNhUklDejdoWU5JaFhh?= =?utf-8?B?V3pNVzRaTkY0ek4zckh5VnIrWnNrNHV5WVF2M0ZXS08zWjBNL3JoVCtPZ0xV?= =?utf-8?B?bGsrZktZU3JMOGhSdEwvRnZzUmJ5TWt5czkrQTJMZkdrNEMrUWRRYlFUUlll?= =?utf-8?B?T2FxcWJmaGlJMlFBRXQwbzBFZkRhYlVGdmkwL2t5dW5XUEM1UWNTOU1JVG9s?= =?utf-8?B?OUM2RWloaExvc2phV0cwWHNDYk5CdXFXdEFTcHdIS3hTRUdKVVVLN2owb3ZQ?= =?utf-8?B?SDVDOFZlYjFDekFFeGhIeDhwTHczRU1LS2lKd2hRTzdoOWU0NzZaSDl4bkxT?= =?utf-8?B?US9jN29EUzN5NitNVU5tNzdQMi9idkFUeFExNmkrZHBpVE9KMzExUlF0MmY5?= =?utf-8?B?T2NFUkY2SHVCOXc5azRpREYwRVVsdG5YYjNTc3h3TlZrcDFCZXpvS2cydll5?= =?utf-8?B?NjlxUGNsenVEQTZNcUpIK3U4WHZ6OC9qWUx1NU1GZUFGc0p2U25QN09YV2VN?= =?utf-8?B?WjQveWZ3MWhlb003ZGJtOHdIWldhV0J0Q1F5Z0c0SnZ1eE44OFVmbEpzbmtj?= =?utf-8?B?dXJWVUY5ZGQwd1V1ZGxrN0ZQTkM3YWdZR0JXTjU0Q2dtRy8xb2tGQlpUTUJn?= =?utf-8?B?bkhhOEhhSFhPSHFvb0RMa2s3VVdkOUg1UFU0TUJERmdkSVRsaC9RSHNhdDBi?= =?utf-8?B?R2ZWcEI1LzN0UEtWdUNlaVA0NVhqYlIrYVlLcHZiTnhrUkRUOEkzTlMrY2RW?= =?utf-8?B?YTliOG5rM21vZHJiRytuSXZxSldXdGRzbEwrNVhKVU55K2JRUGpBcmQrY0tV?= =?utf-8?B?dUx0ZlVxWTJramRuU2FiajY0TFQrYWFhelVSbjRPRHRkdnpUUHE4cFNLc1Nj?= =?utf-8?B?T3Z2WDIvRFprNDZkdlhjcGpsUlpvN0xQcHArdURNQThWSEVNSjBYV0JzZUxs?= =?utf-8?B?QUpkbFd2anc2eXlHZ0M2SGtvRDZ5MHBGZmxDb0J1MHBWTkp4V2N2bDgyMUYv?= =?utf-8?B?ZHNybjl6Ujg4cFhsdkdjckFjTytDTUttR0lWZE45UzRzTHFSeFMxK09lcldq?= =?utf-8?B?c29DVXJUMEdNV0dESWdLcXJBRnpPSWxOdmRaS1AwUmRqY1QyL01oS3pueklk?= =?utf-8?B?enZlY2FKM3prcllsR3ZWMlltbGZkSDlXNkIrMWZoQUtMd3JQbFpqd09odVor?= =?utf-8?B?NDZpQjA0RzVqbkZnYVQrdjRoOGVIMUtiUFZtdz09?=
X-Microsoft-Exchange-Diagnostics: 1; DB3PR07MB0634; 6:sOJeBOwRyt7uEjQCxlQkqx3sQxBMa13azKedyhDL0F9fIrhZmUTgsODAYrU7RRxLLPfygVDiDMC/TTanIKThvYqLAva7lpLjUR2z5sOuIVmUzHBYn44+M/TyrsmAgjLhTIdm9tlQLTtbSfKoWKoWgTWDbDNYdmFZSehPxnz69VspoyWsIDHyPKe2abSmjgdt/MOULHSbZqkqXa8UVFKmP8nesPj31SuqntAAHJKtPUDI5hMKeGXbngMKAwHgNUy4xm9Yg9zFYTSr6FyQ68Eivw/UpOCfZKT97L6opWmWe+5M9gBYvWiwhBtXPqX7MozXLp94ZVXp6Y9I078W3dECNp5P5N1540/j/tSAwFeKdCk=; 5:ht+MNjdrMIQJIEHM+x62eG4Olqgi/i1FeFRi/Q4Bgb30iq0VbC/qTRamGI0e5xXD32Aitqv15offdHNlYGCssZkuXcHKpqonr/fUbVxG9qsP0x2pYEGVLjVBbPNjBPb/yImV4yGSKDt4TQeA/2LLNie+Nh1IaXIc6OkpiGet+ig=; 24:JvMcrB7dSMHvL4LbpksLuYGq6Q1GJyzhJkOOsiO8gB69Vm2wb9WoAvImrusQs9z6BtGNSCYDF7b4+rLw3Orf95q8T1o9XNqYmAaZ6ycbXq0=; 7:7CzcI3OYQzfTFCNQbCjdnhDcOiHh3GJr+VgeTr4SfrF1v/6zF3cYGZnv9BZ7qFPkLLEMdRjer2rnQu3ECCGNCSPGGvNq0QdfSld/SoKGIqxuCYVrzn+w2sQS89xnyfr4EkEr/+kQlbyokv/XT6IAXkTb63MDhP/PNhocTnQNo23LNv+KojcON7AUQtaG5mLA5guKw/S9pX/TTYySj7g5MrCyp6Mwg7xVwiyEqBDvFEPxnzz/MUjul0J6S0pqxZx6
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Nov 2017 14:06:38.0693 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 0af95c38-cc67-46da-17b9-08d533449456
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB3PR07MB0634
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfUhTYRTGeXfvdq/T4duceTJDWkQ18ZNlKtEMAjUQor9sGrX0pqLOca8N FQJNCRtpGn3okqZhhZ+jGipl0OZaKikaCDKplqgRaKFhMYzZbneS/z3nPL/n5Tzw0oTcS0bS xfoKhtXrSpUSKdmWM6SKNRwCbULLSGjK8jMLmY4yu7q8ojNIKz1ewJQWGxk2/sRFadGYLcdg Ca3sbRkmapAjxISCaMBqcE70ESYkpeV4FIFvwCUWhjEEr/pWKH4gcSMBf+69pgTHJIImjxfx +TCcAp5pn5jXChwGzgUfxWs51sDEaJ2I1xI/Y3N/Jnkt8++HXVaJCdH+Vw/CSncGvw7HedDi mUECsgvG2xb/4UE4HbzOJxSPE/gIWF/G82sCR4B70SISdDQMrbYTPAJ4P6wvlPNXAm5F8N16 XyxcEwNPl+tJofE+eDvZHtC3EWz1U0LgDgXddc6AoQLLrJsSdDYMfqoXC9C0BOxbAwGoBDrd N9F2YGB2jRCgDgKu+TYD6Shw2eoCRo8Emt8sIeEmBmxz9ZJmFGPe0dr8v6l5R1PzjqYdiOxB 4RzDXSorTEqKY9jifI4r18fpmYrnyP8h7LbNhGH07etJB8I0UobIWgG0crHOyFWVORDQhFIh i17arZXLCnRV1QxbfoG9UspwDrSXJpURsvEsmVaOC3UVTAnDGBh22xXRQZE1aDA1+2eqBre+ kF5OnEyuVU8d1Vcb8/KNqzORsb/UUx4b+UP+Gx17lDbS8PHwiqRzPm3jbvC7G1fHND7k6m3a 2HNWHby+ZqRF/Q9vebSZGVJmM8l3IPf0+y+50Jg8Y75uOKVVhKvS5oxFDyrtHxCCx6sKe8O6 Juv8uVoUNa8kuSJdoopgOd1fcyWEowwDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JN_EDjECxQ_nV9oGzXOf3822Kms>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 14:06:45 -0000

Hi,

in my initial email, which started this thread, I discussed the
process we were following to gather feedback on the proposal to revise
ISOC's mission statement. The iterative process we used resulted in
the involvement of the board, emeriti trustees, staff, and the
community at large. We want to thank all of you for all the
constructive comments and suggestions. We have updated the proposed
mission statement in order to address all that feedback.

We just concluded a meeting of the Internet Society Board of Trustees
in Singapore.  As part of that meeting, the ISOC board approved the
new mission statement. The agreed-upon text is our best effort at
incorporating the dialogue that we have had with all parts of our
community. You can find the result on our new web page:

https://www.internetsociety.org/mission/

Obviously not every single piece of feedback has made it explicitly
into the final version of the mission statement. Nevertheless, the
board has processed all the comments received and will be taking them
into account when working on strategies, targets, and action plans for
ISOC.

As I noted in my initial email, in addition to resulting in the final
revised mission statement, the whole process has been useful in
itself. The process has helped both the board get a better
understanding of ISOC's purpose and the community to get a healthy
sense of ownership.

In our meeting in Singapore the Board also approved ISOC's 2018 Action
Plan:

https://www.internetsociety.org/action-plan/2018/

This plan provides the foundation for the work of the organization
both next year and in the years that follow. Our statement at the end
of the board meeting, where we also recognized the success of this
eventful 25th year for the organization, is at:

https://www.internetsociety.org/news/statements/2017/internet-society-board-updated-mission-and-2018-action-plan/

Cheers,

Gonzalo


From nobody Fri Nov 24 06:44:26 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D94731287A7 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 06:44:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level: 
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, 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 wxMTLwER-PBG for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 06:44:23 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AD2C126D0C for <ietf@ietf.org>; Fri, 24 Nov 2017 06:44:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id D0BA955BC86E; Fri, 24 Nov 2017 09:44:20 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d3ZmnTE7S__m; Fri, 24 Nov 2017 09:44:16 -0500 (EST)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 1122D55BC860; Fri, 24 Nov 2017 09:44:16 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Proposal to revise ISOC's mission statement
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com>
Date: Fri, 24 Nov 2017 09:44:15 -0500
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/12CUqZ_LbipiZgxia8WPEtr6Xto>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 14:44:25 -0000

IMO - it will be harder to raise funds from some parties since there is =
no mention of the IETF on=20
https://www.internetsociety.org/mission/

I was talking with the CEO of a major Internet-related company a week or =
so ago
and he brought up the ISOC seeming to soft sell its support of the IETF =
- his
company has made significant donations in the past but he is now =
rethinking that

I find it irresponsible, at the least, that there is no mention of the =
IETF at least under=20
=E2=80=9CHighlights of Activities=E2=80=9D if one knows about ISOC=E2=80=99=
s support for IETF and squints just right one can read the IETF into a =
bullet - but why not just say it - is the ISOC ashamed of the IETF?  if =
so, why?

Scott


> On Nov 24, 2017, at 9:06 AM, Gonzalo Camarillo =
<gonzalo.camarillo@ericsson.com> wrote:
>=20
> Hi,
>=20
> in my initial email, which started this thread, I discussed the
> process we were following to gather feedback on the proposal to revise
> ISOC's mission statement. The iterative process we used resulted in
> the involvement of the board, emeriti trustees, staff, and the
> community at large. We want to thank all of you for all the
> constructive comments and suggestions. We have updated the proposed
> mission statement in order to address all that feedback.
>=20
> We just concluded a meeting of the Internet Society Board of Trustees
> in Singapore.  As part of that meeting, the ISOC board approved the
> new mission statement. The agreed-upon text is our best effort at
> incorporating the dialogue that we have had with all parts of our
> community. You can find the result on our new web page:
>=20
> https://www.internetsociety.org/mission/
>=20
> Obviously not every single piece of feedback has made it explicitly
> into the final version of the mission statement. Nevertheless, the
> board has processed all the comments received and will be taking them
> into account when working on strategies, targets, and action plans for
> ISOC.
>=20
> As I noted in my initial email, in addition to resulting in the final
> revised mission statement, the whole process has been useful in
> itself. The process has helped both the board get a better
> understanding of ISOC's purpose and the community to get a healthy
> sense of ownership.
>=20
> In our meeting in Singapore the Board also approved ISOC's 2018 Action
> Plan:
>=20
> https://www.internetsociety.org/action-plan/2018/
>=20
> This plan provides the foundation for the work of the organization
> both next year and in the years that follow. Our statement at the end
> of the board meeting, where we also recognized the success of this
> eventful 25th year for the organization, is at:
>=20
> =
https://www.internetsociety.org/news/statements/2017/internet-society-boar=
d-updated-mission-and-2018-action-plan/
>=20
> Cheers,
>=20
> Gonzalo
>=20


From nobody Fri Nov 24 07:20:54 2017
Return-Path: <gonzalo.camarillo@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 84714128891 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 07:20:52 -0800 (PST)
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 E3lzAV3-A6Gm for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 07:20:51 -0800 (PST)
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 D96DA127869 for <ietf@ietf.org>; Fri, 24 Nov 2017 07:20:50 -0800 (PST)
X-AuditID: c1b4fb2d-2ec699c000001e3d-03-5a1838d093b8
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 51.FE.07741.0D8381A5; Fri, 24 Nov 2017 16:20:48 +0100 (CET)
Received: from [131.160.50.141] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.77) with Microsoft SMTP Server id 14.3.352.0; Fri, 24 Nov 2017 16:20:46 +0100
Subject: Re: Proposal to revise ISOC's mission statement
To: "Scott O. Bradner" <sob@sobco.com>
CC: <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <89cc4345-f884-dca8-de47-969b52167600@ericsson.com>
Date: Fri, 24 Nov 2017 17:20:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUyM2K7t+4FC4kog69fzC2ebZzPYnG8U9mB yWPJkp9MHi8OfGMOYIrisklJzcksSy3St0vgypjU9pm54Lx0xabLE9gbGGeLdTFyckgImEjM 3dfO2sXIxSEkcJhR4syVC4wQzhpGiWfrZ7CDVAkLWEg8uPCPFcQWEVCTeDq1CSzOLCAs8W7d bBaIhhWMEhf7boEl2IAatty6zwJi8wrYSzy+tYURxGYRUJV4/PQgWFxUIEZi4oOLjBA1ghIn Zz4Bi3MK2ErcPncXaA4H0AJNifW79CF2iUvcejKfCcKWl2jeOpsZxBYS0JZY/qyFZQKj4Cwk k2YhdM9C0j0LSfcCRpZVjKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIFBfHDLb90djKtfOx5i FOBgVOLhrTWQiBJiTSwrrsw9xCjBwawkwiv/VCxKiDclsbIqtSg/vqg0J7X4EKM0B4uSOO9J T94oIYH0xJLU7NTUgtQimCwTB6dUA2O18RdjMa8bfJETvvgvYInZuXxu/1kftpk85310Alu8 vNzPXTbWbO6cZ/1NQSK9y7C1tM3+WwF/oNuOs/NSWtbX6j+If9l0JyXW8sXT5+4TNxmVl/ht 6oq/H/KJVaJFUNV6TuMMuetBU1V6SvelWT/fPffd18rw06ezZRqjHR9ukHQ5cXD3diWW4oxE Qy3mouJEALkkID5eAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pC31db3Dj2k_PFBEwIqb2Mz68mg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 15:20:52 -0000

Hi Scott,

as you know, based on (among other things) your input, we have *not*
modified or removed the existing list of highlighted activities.
Additionally, the old mission statement did not mention the IETF
explicitly either. In short, nobody has removed the IETF from the
statements.

In any case, at some point we can think of updating the highlights of
activities in order to include the IETF explicitly and to update some of
the bullets.

With respect to raising funds for the IETF, I assume you are following
the IASA 2.0 discussions?

Cheers,

Gonzalo

On 24/11/2017 4:44 PM, Scott O. Bradner wrote:
> IMO - it will be harder to raise funds from some parties since there is no mention of the IETF on 
> https://www.internetsociety.org/mission/
> 
> I was talking with the CEO of a major Internet-related company a week or so ago
> and he brought up the ISOC seeming to soft sell its support of the IETF - his
> company has made significant donations in the past but he is now rethinking that
> 
> I find it irresponsible, at the least, that there is no mention of the IETF at least under 
> “Highlights of Activities” if one knows about ISOC’s support for IETF and squints just right one can read the IETF into a bullet - but why not just say it - is the ISOC ashamed of the IETF?  if so, why?
> 
> Scott
> 
> 
>> On Nov 24, 2017, at 9:06 AM, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> wrote:
>>
>> Hi,
>>
>> in my initial email, which started this thread, I discussed the
>> process we were following to gather feedback on the proposal to revise
>> ISOC's mission statement. The iterative process we used resulted in
>> the involvement of the board, emeriti trustees, staff, and the
>> community at large. We want to thank all of you for all the
>> constructive comments and suggestions. We have updated the proposed
>> mission statement in order to address all that feedback.
>>
>> We just concluded a meeting of the Internet Society Board of Trustees
>> in Singapore.  As part of that meeting, the ISOC board approved the
>> new mission statement. The agreed-upon text is our best effort at
>> incorporating the dialogue that we have had with all parts of our
>> community. You can find the result on our new web page:
>>
>> https://www.internetsociety.org/mission/
>>
>> Obviously not every single piece of feedback has made it explicitly
>> into the final version of the mission statement. Nevertheless, the
>> board has processed all the comments received and will be taking them
>> into account when working on strategies, targets, and action plans for
>> ISOC.
>>
>> As I noted in my initial email, in addition to resulting in the final
>> revised mission statement, the whole process has been useful in
>> itself. The process has helped both the board get a better
>> understanding of ISOC's purpose and the community to get a healthy
>> sense of ownership.
>>
>> In our meeting in Singapore the Board also approved ISOC's 2018 Action
>> Plan:
>>
>> https://www.internetsociety.org/action-plan/2018/
>>
>> This plan provides the foundation for the work of the organization
>> both next year and in the years that follow. Our statement at the end
>> of the board meeting, where we also recognized the success of this
>> eventful 25th year for the organization, is at:
>>
>> https://www.internetsociety.org/news/statements/2017/internet-society-board-updated-mission-and-2018-action-plan/
>>
>> Cheers,
>>
>> Gonzalo
>>
> 


From nobody Fri Nov 24 08:47:30 2017
Return-Path: <mfidelman@meetinghouse.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 8AF91128796 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 08:47:29 -0800 (PST)
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 obrtMuNcRsTc for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 08:47:27 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6C44112783A for <ietf@ietf.org>; Fri, 24 Nov 2017 08:47:27 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id D8745CC1E6 for <ietf@ietf.org>; Fri, 24 Nov 2017 11:47:24 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8Pru40ilF-+v for <ietf@ietf.org>; Fri, 24 Nov 2017 11:30:52 -0500 (EST)
Received: from Miless-MacBook-Pro.local (70-59-240-225.phnx.qwest.net [70.59.240.225]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 1E7B6CC07D for <ietf@ietf.org>; Fri, 24 Nov 2017 11:30:51 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
To: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net>
Date: Fri, 24 Nov 2017 09:30:49 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v0LLCQ6qvGaj2rEkYGpWx0IrH40>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 16:47:29 -0000

Particularly odd, in that ISOC's original raison d'etre was to provide a 
non-government umbrella for IETF.  And arguably, there's really very 
little else that ISOC does that has serious substance.  It's never 
really grown into a serious, broad-based professional organization, 
policy organization or even a serious membership organization.  It just 
hacks at the edges.

Miles Fidelman


On 11/24/17 7:44 AM, Scott O. Bradner wrote:
> IMO - it will be harder to raise funds from some parties since there is no mention of the IETF on
> https://www.internetsociety.org/mission/
>
> I was talking with the CEO of a major Internet-related company a week or so ago
> and he brought up the ISOC seeming to soft sell its support of the IETF - his
> company has made significant donations in the past but he is now rethinking that
>
> I find it irresponsible, at the least, that there is no mention of the IETF at least under
> “Highlights of Activities” if one knows about ISOC’s support for IETF and squints just right one can read the IETF into a bullet - but why not just say it - is the ISOC ashamed of the IETF?  if so, why?
>
> Scott
>
>
>> On Nov 24, 2017, at 9:06 AM, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> wrote:
>>
>> Hi,
>>
>> in my initial email, which started this thread, I discussed the
>> process we were following to gather feedback on the proposal to revise
>> ISOC's mission statement. The iterative process we used resulted in
>> the involvement of the board, emeriti trustees, staff, and the
>> community at large. We want to thank all of you for all the
>> constructive comments and suggestions. We have updated the proposed
>> mission statement in order to address all that feedback.
>>
>> We just concluded a meeting of the Internet Society Board of Trustees
>> in Singapore.  As part of that meeting, the ISOC board approved the
>> new mission statement. The agreed-upon text is our best effort at
>> incorporating the dialogue that we have had with all parts of our
>> community. You can find the result on our new web page:
>>
>> https://www.internetsociety.org/mission/
>>
>> Obviously not every single piece of feedback has made it explicitly
>> into the final version of the mission statement. Nevertheless, the
>> board has processed all the comments received and will be taking them
>> into account when working on strategies, targets, and action plans for
>> ISOC.
>>
>> As I noted in my initial email, in addition to resulting in the final
>> revised mission statement, the whole process has been useful in
>> itself. The process has helped both the board get a better
>> understanding of ISOC's purpose and the community to get a healthy
>> sense of ownership.
>>
>> In our meeting in Singapore the Board also approved ISOC's 2018 Action
>> Plan:
>>
>> https://www.internetsociety.org/action-plan/2018/
>>
>> This plan provides the foundation for the work of the organization
>> both next year and in the years that follow. Our statement at the end
>> of the board meeting, where we also recognized the success of this
>> eventful 25th year for the organization, is at:
>>
>> https://www.internetsociety.org/news/statements/2017/internet-society-board-updated-mission-and-2018-action-plan/
>>
>> Cheers,
>>
>> Gonzalo
>>

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Fri Nov 24 10:47:23 2017
Return-Path: <gonzalo.camarillo@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 547E5128CD5 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 10:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 WrOH2VD3xx0m for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 10:47:18 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 576CD1252BA for <ietf@ietf.org>; Fri, 24 Nov 2017 10:47:18 -0800 (PST)
X-AuditID: c1b4fb25-d91ff700000020f7-c1-5a186934ce5f
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id 91.FC.08439.439681A5; Fri, 24 Nov 2017 19:47:16 +0100 (CET)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.90) with Microsoft SMTP Server (TLS) id 14.3.352.0; Fri, 24 Nov 2017 19:47:15 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=AQea/2OkQFGcn/4h8HNZM3NDLCEeEwhVwhmtqz4ET7k=; b=NL8d0mnw8z0bRQpxb0Kjcc+OPucDUwEGSOzpyB6FGkZS9x4PlEAeFCRBPRvruEX2OLjTEwuhOgJq4oeJdqHIotIc+cL93Iy6Jq2SE/lxq6svIValEZpQGK7k2VxTeekb22cVHr1zUbFj3Q5AugXcDumsEUaizgrkIS1KF9D9fOk=
Received: from [192.168.1.7] (37.136.86.88) by AM3PR07MB0630.eurprd07.prod.outlook.com (2a01:111:e400:8835::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.260.2; Fri, 24 Nov 2017 18:47:14 +0000
Subject: Re: Proposal to revise ISOC's mission statement
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
To: "Scott O. Bradner" <sob@sobco.com>
CC: <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <89cc4345-f884-dca8-de47-969b52167600@ericsson.com>
Message-ID: <14cce36c-6b37-c4ad-b4c5-53ba0114bbcf@ericsson.com>
Date: Fri, 24 Nov 2017 20:47:09 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <89cc4345-f884-dca8-de47-969b52167600@ericsson.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1P192CA0009.EURP192.PROD.OUTLOOK.COM (2603:10a6:3:fe::19) To AM3PR07MB0630.eurprd07.prod.outlook.com (2a01:111:e400:8835::28)
X-MS-PublicTrafficType: Email
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(2017052603199); SRVR:AM3PR07MB0630; 
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0630; 3:GGMLnGUlL8RAmKXGLHEGTfFADQZgDScPIeETuAbEnpmJ2/DE0kXwR+s+f2fP6G+8DXzjeQ8PUE2ldr9HFIVvETpfdKToBEYNAnPlZKqjw7CwCTzeJg6bJdJhDw3thVDOOf0ZZC0fnVxpygA19mKC8fqT7KHvfb/MNE16JoiP30mWKiJgQ4xVGLWleadAhOy+2ATzH94uL1dardnqgWXsXzYX3XjtyDiL52JlvMH3qUO4AGp9pEZpEz0tMnPpWokA; 25:UH4GshvIukRO39TpqsrglZl3sxDU83LlN1dPz6/Y4UnlRWK6ngtKWxhGTTJdswxrqvDgp+KONMeoWxR33sjhk0v2xSR3Vx+w8+SXB7QbugjeefSi7+48ZHCCLn5owYywsBlr19aHmJTZ+U2chg8Hd/qhi2d2BLbHoOKzcTtXneOKkLFQr4rtVfL0vHzHDeDSaFqHesMDc2u0nWq69RommbMrBdtH96+YbfzkDqsMiFh1eJOBu0kX5ToO5ZqLB9E1ipQLJCIRd6APEsmhVb+quJD4RDCOuS8VbvISIu9gialmZOrj/KVBWu6h23EsICnrgnyEixMpq70CjexU1JtKUq4Mvz688sxud2MO/eFUSP4=; 31:1eH311HTi7yBNSnHmW7ba2QfTeGRJDupGUO1P7CRRfQMvsDVnSWHqdwiYJVHNj29eeusL96onvQZ08EIHkHSxqIq6xfbHe/dB8u2lu0Pitg/3cAbQWGCFVtkz184L0/UkjyZWaFabKyvuPJQBym5sHCDOl8bqLa2+yqO0A4g4gGSH3uVjhcQXGpv52CEyIFNWvvFIQhBJncsfliln1RImImLzFYa6fcPvrC+aVm6YSY=
X-MS-TrafficTypeDiagnostic: AM3PR07MB0630:
X-MS-Office365-Filtering-Correlation-Id: 2f50d9da-4802-4a89-8a15-08d5336bc7ed
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0630; 20:WtMNHS+EHAryRfdGT9N4+Ve7EEPtNE1v6h1mnWYz1xd4lCjdNwSUvl+fDZ1gUiwFhGOe19T10II5kTlVroFv5FTBZi+LLvFHaVebkC10zdlUKAPeboJWbwu+TGMqDoYkvIiaiUIIrQwv56C2SkZ2wDL/ieGTFjcwFmsKDnBMXD+XevxpnRBmMUJJspKi4Ejs80XRU2gND8LXZLbZ7hFbGd/rsDAkh/P++w3g3waW2459Fkhmpo3dYg+A5seb9+4Ut+vT9B4+vV1JMd6KeKPzXS7yhI2SABfHaT2YTYJhDEWdq6M7Q93WK1b05oiVK7GR7sVm27xDP/fkq5vydyw2FIEl7tS16WnGmBBExXLgGi7mU46KGUNy4rwP5pkCd6hjkV1fWxnK3OpYyNUMbl9tjXGYkDxSCK5Pxt2YQsblTkwa7+gRi5F89mHhRln9z0UVNK2/srwmaFt1EV6xyqzhcRDjMZCFI/pETe1+Jh+OrbLb+8Kg3Vmw0SQa1J4gUENj; 4:vmjHtkz6+uZIphS2GDFkrZVSZxKd2Hr1zSiEwZgOVzvXwNPaExZVNV9hmJfM0wQjoOqyFqRGlvQducEZSbLpDkYW3GWDoWMybHO7pQWaHLxGtFqsJ5+Uip3wkQ8uoornee73shRso10w4i9P4xk1oHpzRceJEet+cLhrgrojdGtc255UWalQSBAA2nq1yVuyl0qt8drWqjKHmme7pSZZG+IlrftwRPttrapW1jqD59cKc9ncrI/pc9IflgceXxxbRmpejVAsJBqLUQd+MgAKS2tQQtYccZhFrf6wTq+iOopiZXLD9+OjlO2IL3+Zdvq/
X-Microsoft-Antispam-PRVS: <AM3PR07MB06306A7F602F9914EF501FE383260@AM3PR07MB0630.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(37575265505322);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(3002001)(3231022)(93006095)(93001095)(10201501046)(6041248)(20161123555025)(20161123564025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123560025)(6072148)(201708071742011); SRVR:AM3PR07MB0630; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:AM3PR07MB0630; 
X-Forefront-PRVS: 05015EB482
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(366004)(376002)(39860400002)(346002)(24454002)(111735001)(189002)(199003)(53234004)(101416001)(4326008)(2870700001)(316002)(966005)(2906002)(229853002)(53936002)(7736002)(47776003)(25786009)(6306002)(77096006)(6246003)(6486002)(86362001)(66066001)(65956001)(52146003)(478600001)(52116002)(31696002)(117156002)(189998001)(50986999)(65806001)(54356999)(68736007)(305945005)(53546010)(23676004)(6916009)(81156014)(50466002)(33646002)(561944003)(36756003)(64126003)(105586002)(31686004)(76176999)(3846002)(2950100002)(106356001)(93886005)(5660300001)(83506002)(8676002)(81166006)(8936002)(65826007)(6666003)(97736004)(2486003)(16526018)(58126008)(6116002)(16576012); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB0630; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTNQUjA3TUIwNjMwOzIzOnAvR24rak1FVzA1bzVPc0pJUHR1REljS0tJ?= =?utf-8?B?bEpxYnhYWkN6OFF6aURxTzFYYngyZ3JqSW10UTh3Q2s1STJsNWs1ZG9VS0Ni?= =?utf-8?B?UlNaY2FzakZ1SjBFdU10d0REVldnWUp4aVphQXdKODFYTjZtek5HbnY2dUhU?= =?utf-8?B?SlFoV2tFaG9kenFlbWJvRS9VaEtVbW1USXEyMi8wRVJWeUN5bGZ2THJnM04y?= =?utf-8?B?bTBMSWtlUTJzUHBWQnpxbEk4WkFqNzcvZFJRWllQS3ByVnU5NVd1RUJ3ZXNK?= =?utf-8?B?UlpPSXloTGsxaTNwNkdaYlNKRFBxVkhPYUtXdW5tWWl5dkJjUjN3UHlqRnNE?= =?utf-8?B?ZVJzTE1FelhmclE3bTNtWitKaHdDN1ZpWjdJNG14ZTZEWENZUEpGWFJ0TG5u?= =?utf-8?B?eTdlNkQwV1k5ekJhdkpjc0tTSG9tZzV1T2hOZ2pXd2J4S0hKU2tHdkNReDcx?= =?utf-8?B?MTRDVzBwSXNhZ1k4U3JCZ3A4QTZlVW0rMVFYYWJsYjFaOHkrUlBxWXhYU05L?= =?utf-8?B?SmZaaGo2dzZidWN4dmlCOW5SWnlvVFlkQzBlZVk1bWcwY2xIZEV4eTBYdFJh?= =?utf-8?B?dy9HZTdQbGcrVzlUVWE4RXRUTTZDU2YwRG5MaHc4MDladWJoL3JPdTBMMXRP?= =?utf-8?B?bSt5RENRMWxKZExKZHFOZzNXc3Zkd1JEMUgrVGRaeUI5UlZBdUVWOUo5WVov?= =?utf-8?B?R2hEMWltWmd0bG1qd1FUVnZhUHp5TkhWWUtBZ0cvWGJWZHlxV2ZKSlJON0ZQ?= =?utf-8?B?bkNhQkpWOVIyS01yUnZwRnkvclZ0Rk5wMnBlcm1jRnJXUDhlQW4vR0xCanVG?= =?utf-8?B?Ti9ORHc0VDJaV1ROZTZtZFUyMitOWGRWYnNhSERldUcwd3BrNjBTVW5UcmFO?= =?utf-8?B?c2E4T3doV0hZcXE3cWtoaWpIbkxFNDYrRFQyRmQwVkt2R1dQMFNpUXk4ZWNr?= =?utf-8?B?YU5uT1FFYWIyZGtWbSt5QXltdXRyWVNUUUx6Z25rVTlWak1iU2J2bGl5bFJl?= =?utf-8?B?NTIwZ0lEVUM4UzdlK0FxY095Rk0zUU5ITTN2T0FHWTVxVXhjM1hKRnJualpp?= =?utf-8?B?cVUrWVRWWCs1YUhJTmRCNmJ5N21VMjdOTHJhcHdwNUk1eEZWZUdsZE1NWFhZ?= =?utf-8?B?RVk0RU5nSlFpT1BaS0RtYktSN3pKd0JUblpKMXU3MGo2QS8yeUlxLzZpTWZP?= =?utf-8?B?MUIzb0N6amh1SXg4REs1WFhJWXpIMHZEMXZUQ0lLK0ZRcUdZTkhRZnhmcHBy?= =?utf-8?B?ZXdVRThJY3dSUjFJU2JBQWVsWXo0R2VPY3NEM0U5UkNEbTRIcjBPMVdEZU1n?= =?utf-8?B?bUlEbU5XUmx1cWFrbXFyTWVYdEFDWGpTK25Kcm1LWDZ3cXFHdVoyMnlOcGY4?= =?utf-8?B?cGJsRHpqcDlMdW1LdEVyWExmcGEwTGtkeEtneEhMWjFFc0Y2dUk3UTUzNXpT?= =?utf-8?B?bDdVNHVIY3NVL1JaS2lubW9hZU5JOTdLMytiOUhuTHpZQlRyb2d6WWNweDFz?= =?utf-8?B?dmpMVTNUTmV5bDFEb1didU5BeHBsYWpmK21ZSFlTbm1KdTg5a01jaEs4NjA0?= =?utf-8?B?aTRxYU9kMnNwcmV2alJNcGR1dnNDc3EwVVNPTzk4c1JpRHdwZTVOck0xaUlq?= =?utf-8?B?NWdpUnd5WmNwT3U0emtWRXprZld0dXZUZ2hwaEpoSEw2OS9uc1UweTMzVG9m?= =?utf-8?B?Q0V3UEhPU0VXTEZoSGZFbTFrSHFGZTk4VCtjY2hJSU9PZVBFZzJzWXIxdGJ4?= =?utf-8?B?VmxRM1c0SGVkNTJxUzFSelNWZVZVVk5jYTlHazg4RXBKRXNndUFWZXdCNnpD?= =?utf-8?B?L2NQNFBGbzhyMUdzOGxmYXdYeTR2UENWM0ZGOVIxMGllRE1oYm1oc2JPNGZR?= =?utf-8?B?VmU2c3Z6NHhBeXFlRW0yRmlNeFdGL094MnQzaUk0Rm04M081VWJFcnRhV2Rz?= =?utf-8?B?Z0JlZVhmcXd3V1pZRTlyc21OaVd4anQ0YzR2ZWc5MWFzTHNjbDhkdjMzbEY5?= =?utf-8?B?ZXBnNldUd2RiM2V6djQrZnpIRnN1bkhZeGNjQko1MkRWeEtzVG1hT2o0aStx?= =?utf-8?B?ZzRnSGpVSmhBSU51V3l6NGd6WDVpWUljSzNsK0R3YVg2dXkwMk5yRTdmQmZX?= =?utf-8?Q?5m9QTRvuL4tcSgwJN1Z/ChM=3D?=
X-Microsoft-Exchange-Diagnostics: 1; AM3PR07MB0630; 6:MAls286wFaE4yQl7emOZYspayIh3SgLWpXoHwUWYl3UbUexkvIYoQcTMZjNacg0P/yoHFi96ShHzRtW/S+O7uXIsM06uY3RyjNrYQHOJuKFxjrLEcw/h+U02+zJUhnrTqKJsg3a5JkgIOxL8KU7GGjip2hyDJYVUbetj+9FMKgO6NUlj/cTcaaPm6GF5dReVDwPL6Sq/GT38vrJGsVHp1+sHUKFMF0pgLxMAYcIIhud9sZhp9TbTnjz9F+FQl1EStaaPV2boEm1KEYDBUPV7BwibLxM4urCqrGj6tw7SN8qI+zW7h998ZANp2MWxO12KQI4s9Eqy7xAmhQTBOwLD+ACUyjxf6Up9QfUADXEtzic=; 5:0IDx5Dw3CF8ikWeo4J04HylJDN8Bt5yf17ogJ7wDrdPfKTDZHBQvLYLBuymxQMh8kuZlwZ2DCL45YzblfDffhP5TdTmDBqNtsYZ1hfw6IOc9TpPOUHNID5yVwraiT8m/q5qCaRM05n9oFAbrGyN7vCdihYoAsbVp/wj/LHrFWp4=; 24:P23lppimXopUTuiEme8mAj39sxAGKw+BrUOyYD64MO01z2qDogxFhuz+m1chO6/BEMVzzaaMXdNTEAiUPMTMW8pmcDTpt7HROHES9lfJ2y4=; 7:bHXWZRw/yL5l+wjd45ZHF4415icdcFqOv9r8/BaDtI06FhBXPD4POFgjHn6OSLTCqam5hfvbT0Ms5sUKRSw9tM+WwCsJlItif5MwrdY4HgdUXddt7vWjkIKcxO+Ip5gXF21InwLdGd7EPVRJ9ZVdwQbXAe+1ms/yMbVdeXLiY3D2gr8Hld74yTITSGyoPlioegPXF2CC8KX8GKqpP3EvQVgOrwPCtXVhKvEMDgkCV8pnWoxyoYLWrwoeS5hiwI2T
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Nov 2017 18:47:14.7637 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 2f50d9da-4802-4a89-8a15-08d5336bc7ed
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB0630
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmphleLIzCtJLcpLzFFi42KZGbE9StckUyLK4PdUVYtnG+ezWBzvVHZg 8liy5CeTx4sD35gDmKK4bFJSczLLUov07RK4Mta9fsxc0CVfsfHQSdYGxu8SXYycHBICJhK9 b8+zgNhCAocZJQ5/9epi5AKyTzBKnL/azwTisAj0MkssOdnKCpFpY5I41nudDaRFWMBC4sGF f6wgNhuQveXWfbBRIgJqEk+nNrGD2MwCwhLv1s1mgWi+xyixY/0JZpAEr4C9xIXJr8GKWARU JW6t3wxmiwrESEx8cJERokZQ4uTMJ2BDOQUcJCYuWwvUywE0VFNi/S59iPniEreezGeCsOUl mrfOZoZ4TUFi/4+VbBD2FEaJDQ3eEG9qSyx/1sICEZeVOHp2DthtEgKTGCWWn3rCBOFMYZdY fXMzK0SVlsTO32+YIGxfiU2T3kLZP9gkFs6UhbCzJea9vQO12Uri9a/vjBCDFjBLzP7XD9Ug I3FsSzMzROIEm8SVR7/ZJzDqzELy6SyE72Yh+W4Wku8WMLKsYhQtTi1Oyk03MtZLLcpMLi7O z9PLSy3ZxAhMGwe3/FbdwXj5jeMhRgEORiUe3unpElFCrIllxZW5hxglOJiVRHjln4pFCfGm JFZWpRblxxeV5qQWH2KU5mBREuc96ckbJSSQnliSmp2aWpBaBJNl4uCUamB0e3LqaueMkrAA 5aMX2Y3brvA8Nluqkcv+3CDL4WeLz5OqqYe/pZx6/jrrnu194Rn3T1yeL/C4zPeMo/ujiWov t//mvWZpfnl2nV518eLsxA/OtkfMbzO55BrddrDNSUozTVipyKN45d85T+EZjP3z3I//yjew db60Jj7E+czJO7ZvFx98cSJOiaU4I9FQi7moOBEATrW98BcDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GSUcVH33dTp_uPCzoogHuSHP-Sw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 18:47:21 -0000

Hi again, Scott,

to be clear, since I did not address the main point of your email in my
response below; I agree with you the IETF should appear more prominently
on ISOC's web page. ISOC's comms team is looking into how to make that
happen on the new web page.

Cheers,

Gonzalo


On 24/11/2017 5:20 PM, Gonzalo Camarillo wrote:
> Hi Scott,
> 
> as you know, based on (among other things) your input, we have *not*
> modified or removed the existing list of highlighted activities.
> Additionally, the old mission statement did not mention the IETF
> explicitly either. In short, nobody has removed the IETF from the
> statements.
> 
> In any case, at some point we can think of updating the highlights of
> activities in order to include the IETF explicitly and to update some of
> the bullets.
> 
> With respect to raising funds for the IETF, I assume you are following
> the IASA 2.0 discussions?
> 
> Cheers,
> 
> Gonzalo
> 
> On 24/11/2017 4:44 PM, Scott O. Bradner wrote:
>> IMO - it will be harder to raise funds from some parties since there is no mention of the IETF on 
>> https://www.internetsociety.org/mission/
>>
>> I was talking with the CEO of a major Internet-related company a week or so ago
>> and he brought up the ISOC seeming to soft sell its support of the IETF - his
>> company has made significant donations in the past but he is now rethinking that
>>
>> I find it irresponsible, at the least, that there is no mention of the IETF at least under 
>> “Highlights of Activities” if one knows about ISOC’s support for IETF and squints just right one can read the IETF into a bullet - but why not just say it - is the ISOC ashamed of the IETF?  if so, why?
>>
>> Scott
>>
>>
>>> On Nov 24, 2017, at 9:06 AM, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com> wrote:
>>>
>>> Hi,
>>>
>>> in my initial email, which started this thread, I discussed the
>>> process we were following to gather feedback on the proposal to revise
>>> ISOC's mission statement. The iterative process we used resulted in
>>> the involvement of the board, emeriti trustees, staff, and the
>>> community at large. We want to thank all of you for all the
>>> constructive comments and suggestions. We have updated the proposed
>>> mission statement in order to address all that feedback.
>>>
>>> We just concluded a meeting of the Internet Society Board of Trustees
>>> in Singapore.  As part of that meeting, the ISOC board approved the
>>> new mission statement. The agreed-upon text is our best effort at
>>> incorporating the dialogue that we have had with all parts of our
>>> community. You can find the result on our new web page:
>>>
>>> https://www.internetsociety.org/mission/
>>>
>>> Obviously not every single piece of feedback has made it explicitly
>>> into the final version of the mission statement. Nevertheless, the
>>> board has processed all the comments received and will be taking them
>>> into account when working on strategies, targets, and action plans for
>>> ISOC.
>>>
>>> As I noted in my initial email, in addition to resulting in the final
>>> revised mission statement, the whole process has been useful in
>>> itself. The process has helped both the board get a better
>>> understanding of ISOC's purpose and the community to get a healthy
>>> sense of ownership.
>>>
>>> In our meeting in Singapore the Board also approved ISOC's 2018 Action
>>> Plan:
>>>
>>> https://www.internetsociety.org/action-plan/2018/
>>>
>>> This plan provides the foundation for the work of the organization
>>> both next year and in the years that follow. Our statement at the end
>>> of the board meeting, where we also recognized the success of this
>>> eventful 25th year for the organization, is at:
>>>
>>> https://www.internetsociety.org/news/statements/2017/internet-society-board-updated-mission-and-2018-action-plan/
>>>
>>> Cheers,
>>>
>>> Gonzalo
>>>
>>
> 


From nobody Fri Nov 24 10:48:57 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1C0128CD5 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 10:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level: 
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, 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 aVhm_-59FVxM for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 10:48:54 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5A5A1252BA for <ietf@ietf.org>; Fri, 24 Nov 2017 10:48:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 7604155C1268; Fri, 24 Nov 2017 13:48:52 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id leiPcQq7ffvq; Fri, 24 Nov 2017 13:48:49 -0500 (EST)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 62D9955C125B; Fri, 24 Nov 2017 13:48:49 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Proposal to revise ISOC's mission statement
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <14cce36c-6b37-c4ad-b4c5-53ba0114bbcf@ericsson.com>
Date: Fri, 24 Nov 2017 13:48:48 -0500
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C7E3980-F916-4116-90B6-218FB916DB22@sobco.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <89cc4345-f884-dca8-de47-969b52167600@ericsson.com> <14cce36c-6b37-c4ad-b4c5-53ba0114bbcf@ericsson.com>
To: Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ixG4hYg_unSE0bo2FwBsca8Rzi0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 18:48:55 -0000

thanks

Scott


> On Nov 24, 2017, at 1:47 PM, Gonzalo Camarillo =
<gonzalo.camarillo@ericsson.com> wrote:
>=20
> Hi again, Scott,
>=20
> to be clear, since I did not address the main point of your email in =
my
> response below; I agree with you the IETF should appear more =
prominently
> on ISOC's web page. ISOC's comms team is looking into how to make that
> happen on the new web page.
>=20
> Cheers,
>=20
> Gonzalo
>=20
>=20
> On 24/11/2017 5:20 PM, Gonzalo Camarillo wrote:
>> Hi Scott,
>>=20
>> as you know, based on (among other things) your input, we have *not*
>> modified or removed the existing list of highlighted activities.
>> Additionally, the old mission statement did not mention the IETF
>> explicitly either. In short, nobody has removed the IETF from the
>> statements.
>>=20
>> In any case, at some point we can think of updating the highlights of
>> activities in order to include the IETF explicitly and to update some =
of
>> the bullets.
>>=20
>> With respect to raising funds for the IETF, I assume you are =
following
>> the IASA 2.0 discussions?
>>=20
>> Cheers,
>>=20
>> Gonzalo
>>=20
>> On 24/11/2017 4:44 PM, Scott O. Bradner wrote:
>>> IMO - it will be harder to raise funds from some parties since there =
is no mention of the IETF on=20
>>> https://www.internetsociety.org/mission/
>>>=20
>>> I was talking with the CEO of a major Internet-related company a =
week or so ago
>>> and he brought up the ISOC seeming to soft sell its support of the =
IETF - his
>>> company has made significant donations in the past but he is now =
rethinking that
>>>=20
>>> I find it irresponsible, at the least, that there is no mention of =
the IETF at least under=20
>>> =E2=80=9CHighlights of Activities=E2=80=9D if one knows about =
ISOC=E2=80=99s support for IETF and squints just right one can read the =
IETF into a bullet - but why not just say it - is the ISOC ashamed of =
the IETF?  if so, why?
>>>=20
>>> Scott
>>>=20
>>>=20
>>>> On Nov 24, 2017, at 9:06 AM, Gonzalo Camarillo =
<gonzalo.camarillo@ericsson.com> wrote:
>>>>=20
>>>> Hi,
>>>>=20
>>>> in my initial email, which started this thread, I discussed the
>>>> process we were following to gather feedback on the proposal to =
revise
>>>> ISOC's mission statement. The iterative process we used resulted in
>>>> the involvement of the board, emeriti trustees, staff, and the
>>>> community at large. We want to thank all of you for all the
>>>> constructive comments and suggestions. We have updated the proposed
>>>> mission statement in order to address all that feedback.
>>>>=20
>>>> We just concluded a meeting of the Internet Society Board of =
Trustees
>>>> in Singapore.  As part of that meeting, the ISOC board approved the
>>>> new mission statement. The agreed-upon text is our best effort at
>>>> incorporating the dialogue that we have had with all parts of our
>>>> community. You can find the result on our new web page:
>>>>=20
>>>> https://www.internetsociety.org/mission/
>>>>=20
>>>> Obviously not every single piece of feedback has made it explicitly
>>>> into the final version of the mission statement. Nevertheless, the
>>>> board has processed all the comments received and will be taking =
them
>>>> into account when working on strategies, targets, and action plans =
for
>>>> ISOC.
>>>>=20
>>>> As I noted in my initial email, in addition to resulting in the =
final
>>>> revised mission statement, the whole process has been useful in
>>>> itself. The process has helped both the board get a better
>>>> understanding of ISOC's purpose and the community to get a healthy
>>>> sense of ownership.
>>>>=20
>>>> In our meeting in Singapore the Board also approved ISOC's 2018 =
Action
>>>> Plan:
>>>>=20
>>>> https://www.internetsociety.org/action-plan/2018/
>>>>=20
>>>> This plan provides the foundation for the work of the organization
>>>> both next year and in the years that follow. Our statement at the =
end
>>>> of the board meeting, where we also recognized the success of this
>>>> eventful 25th year for the organization, is at:
>>>>=20
>>>> =
https://www.internetsociety.org/news/statements/2017/internet-society-boar=
d-updated-mission-and-2018-action-plan/
>>>>=20
>>>> Cheers,
>>>>=20
>>>> Gonzalo
>>>>=20
>>>=20
>>=20


From nobody Fri Nov 24 11:10:18 2017
Return-Path: <mfidelman@meetinghouse.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 5D71B128CD5 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 11:10:17 -0800 (PST)
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 WDPmaT20g2y7 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 11:10:15 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD681200C5 for <ietf@ietf.org>; Fri, 24 Nov 2017 11:10:15 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 00EA5CC07E; Fri, 24 Nov 2017 14:10:14 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id f3gkJ9WhpajC; Fri, 24 Nov 2017 14:10:13 -0500 (EST)
Received: from Miless-MacBook-Pro.local (70-59-240-225.phnx.qwest.net [70.59.240.225]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7EE38CC03C; Fri, 24 Nov 2017 14:10:13 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
To: "John R. Levine" <johnl@iecc.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Message-ID: <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net>
Date: Fri, 24 Nov 2017 12:10:11 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1711241329410.32540@ary.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ABfjHX01lrw9isaSuLSnmwwzubo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 19:10:17 -0000

On 11/24/17 11:31 AM, John R. Levine wrote:

>> Particularly odd, in that ISOC's original raison d'etre was to 
>> provide a non-government umbrella for IETF.  And arguably, there's 
>> really very little else that ISOC does that has serious substance.  
>> It's never really grown into a serious, broad-based professional 
>> organization, policy organization or even a serious membership 
>> organization.  It just hacks at the edges.
>
> I think I know a lot of people who would disagree with you.  ISOC does 
> a great deal of quiet policy stuff in DC and Brussels, and a lot of 
> development work in Africa and Asia.  If you haven't heard about it, 
> that's probably because you (and I) are not the target audience.
>

Well... quoting from 
https://www.internetsociety.org/internet/history-of-the-internet/ietf-internet-society/ 

"The Internet Society was formed by a number of people with long-term 
involvement in the Internet Engineering Task Force (IETF). As a result, 
one of its principal rationales was to provide an institutional home for 
and financial support for the Internet Standards process."
(though I heard this directly from Vint's mouth, back in the day)

At the time, ISOC was presented as a membership association representing 
the "Internet community," and I still carry my original membership card, 
dated 1992, and stamped "Pioneer" (and, somewhere, I also have the lapel 
pin that came with it) . I'm not sure ISOC was ever actually organized 
as a membership organization - I can't recall ever being called to vote 
on trustees, and the organizational documents no longer seem to be on 
the web site.  And over the years the notion of individual membership 
seems to have come & gone several times, along with individual dues.

The organization is certainly not a professional group, in the sense of 
IEEE or ACM.

And when it comes to policy involvement, it's not at all clear who ISOC 
represents or speaks for.  I've served on policy bodies for both IEEE & 
ACM, and ISOC certainly does not approach policy engagement in anything 
like the way those professional bodies do. Nor does it speak as an 
industry association (though it does seem to have the notion of 
corporate members).  Nor is it anywhere near as visible as EFF – which 
might well be the most effective policy group working in the Internet 
space (at least in the US).

Which brings us back to the one clear role that ISOC plays - "an 
institutional home for and financial support for the Internet Standards 
process."

Miles Fidelman



-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Fri Nov 24 11:19:28 2017
Return-Path: <ynir.ietf@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 B226C1293D6; Fri, 24 Nov 2017 11:19:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoav Nir <ynir.ietf@gmail.com>
To: <secdir@ietf.org>
Cc: draft-ietf-tokbind-protocol.all@ietf.org, unbearable@ietf.org, ietf@ietf.org
Subject: Secdir last call review of draft-ietf-tokbind-protocol-16
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151155116566.9001.9710010900094084736@ietfa.amsl.com>
Date: Fri, 24 Nov 2017 11:19:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0Kclq5JJ6afnzAWNbciaA5MsUHo>
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, 24 Nov 2017 19:19:26 -0000

Reviewer: Yoav Nir
Review result: Ready

The document seems ready with two minor editorial nits:

1. The first sentence is as follows:
  Often, servers generate various security tokens (e.g.  HTTP cookies, OAuth
  [RFC6749] tokens) If you reference the OAuth RFC, you should also reference
  the HTTP cookie RFC (RFC 6265)

2. The term "bound token" appears in section 2 without any definition. Perhaps
add something like "An application token contained in a token binding message
is called a bound token"

Other than that, the document is well written and the security issues are dealt
with well in sections 4 and 5 as well as the security considerations section
(7).


From nobody Fri Nov 24 12:03:18 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 20DCA127ABE for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 12:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, 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
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 ENZsuT96PTqf for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 12:03:15 -0800 (PST)
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 9C0B0126D73 for <ietf@ietf.org>; Fri, 24 Nov 2017 12:03:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 80DDF400497; Fri, 24 Nov 2017 12:03:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1511553795; bh=TE4j3ssU5psjWcdA6CohI5Bwvfnrzxeg3EeuIT9WYZE=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=igiWk9h1q7Wxc6qOnVKPAHWm+CmAmqK2f54Flx1l4Lra8/PUEBVQf46dlR9Q/4oAu uGxLlCakiYkhpdGaYvMT0NuaXjA+0Sy8D5SsbIkO3XeVfQBxVhihtdl7ME/tJ5/Jja WQKWKH5syw4/+2pQrnVRlTe9fsZd3TsV2mYErI5w=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (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 CBF0C400077; Fri, 24 Nov 2017 12:03:14 -0800 (PST)
Subject: Re: Proposal to revise ISOC's mission statement
To: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <010c0deb-0317-6891-052c-b836488faa58@joelhalpern.com>
Date: Fri, 24 Nov 2017 15:03:13 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net>
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/KGG1bh5-_0yrer65gG__549tWVo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 20:03:17 -0000

I think you are under-valuing in your analysis the positive impact on 
the goals of the IETF that ISOC's other activities have had in the past 
and are likely to have in the future.
For example, their experience and skill in working with governments was 
critical in preventing previous rounds of efforts by governments to 
significantly change the core governance of the Internet.  Which would 
have significantly harmed the IETF's efforts.

Yours,
Joel

On 11/24/17 2:10 PM, Miles Fidelman wrote:
> On 11/24/17 11:31 AM, John R. Levine wrote:
> 
>>> Particularly odd, in that ISOC's original raison d'etre was to 
>>> provide a non-government umbrella for IETF.  And arguably, there's 
>>> really very little else that ISOC does that has serious substance. 
>>> It's never really grown into a serious, broad-based professional 
>>> organization, policy organization or even a serious membership 
>>> organization.  It just hacks at the edges.
>>
>> I think I know a lot of people who would disagree with you.  ISOC does 
>> a great deal of quiet policy stuff in DC and Brussels, and a lot of 
>> development work in Africa and Asia.  If you haven't heard about it, 
>> that's probably because you (and I) are not the target audience.
>>
> 
> Well... quoting from 
> https://www.internetsociety.org/internet/history-of-the-internet/ietf-internet-society/ 
> 
> "The Internet Society was formed by a number of people with long-term 
> involvement in the Internet Engineering Task Force (IETF). As a result, 
> one of its principal rationales was to provide an institutional home for 
> and financial support for the Internet Standards process."
> (though I heard this directly from Vint's mouth, back in the day)
> 
> At the time, ISOC was presented as a membership association representing 
> the "Internet community," and I still carry my original membership card, 
> dated 1992, and stamped "Pioneer" (and, somewhere, I also have the lapel 
> pin that came with it) . I'm not sure ISOC was ever actually organized 
> as a membership organization - I can't recall ever being called to vote 
> on trustees, and the organizational documents no longer seem to be on 
> the web site.  And over the years the notion of individual membership 
> seems to have come & gone several times, along with individual dues.
> 
> The organization is certainly not a professional group, in the sense of 
> IEEE or ACM.
> 
> And when it comes to policy involvement, it's not at all clear who ISOC 
> represents or speaks for.  I've served on policy bodies for both IEEE & 
> ACM, and ISOC certainly does not approach policy engagement in anything 
> like the way those professional bodies do. Nor does it speak as an 
> industry association (though it does seem to have the notion of 
> corporate members).  Nor is it anywhere near as visible as EFF – which 
> might well be the most effective policy group working in the Internet 
> space (at least in the US).
> 
> Which brings us back to the one clear role that ISOC plays - "an 
> institutional home for and financial support for the Internet Standards 
> process."
> 
> Miles Fidelman
> 
> 
> 


From nobody Fri Nov 24 12:09:51 2017
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE19C1293DB for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 12:09:49 -0800 (PST)
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 (1536-bit key) header.d=iecc.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMHLrLzPV9Rf for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 12:09:48 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 7B89C129329 for <ietf@ietf.org>; Fri, 24 Nov 2017 12:09:48 -0800 (PST)
Received: (qmail 22351 invoked from network); 24 Nov 2017 20:09:46 -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=574d.5a187c8a.k1711; bh=kd8Kzjv1drlVbTubE3I1MXoxh5KuV94Dvly9sRBktXc=; b=IwJOgJ+IMQctNQ5QPe++NExu1J4e53OyxVuVOceHExqiX8v4GMdnJNW8C+RscXtz2pJTUUo7OFgNqR84lzWzP4x0ACBmoj07Uds5tlVVjHP7A5QDWG5vRh4yiYKcxGeap6LAcX/JCFZp0up4OQGgOOWM1dBTy01DPYmTVFVaCjNzDrnd7V1/X2yV0uaSPr3JmFAKRs+0b/1zy8UlrGDfWvnKk37JF0lb1lzPF/L2mSDp/xTqBh5TLJ5RwMzwQDt2
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; 24 Nov 2017 20:09:46 -0000
Date: 24 Nov 2017 15:09:45 -0500
Message-ID: <alpine.OSX.2.21.1711241507070.32660@ary.local>
From: "John R. Levine" <johnl@iecc.com>
To: "Miles Fidelman" <mfidelman@meetinghouse.net>
Cc: "IETF general list" <ietf@ietf.org>
Subject: Re: Proposal to revise ISOC's mission statement
In-Reply-To: <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1023174661-1511554186=:32660"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VlJGdeIFuzlCZ0tPRzD455h_svo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 20:09:50 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1023174661-1511554186=:32660
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

> Please don't send private responses to public comments.

Well, OK.

> Is it a membership organization?  It purported to be, at the beginning - but 
> individual membership has come and gone, doesn't carry a vote, or dues.  It's 
> a non-profit with a self-perpetuating board of trustees.  So it's not really 
> clear what is.

As is trivial to find out by looking at ISOC's web site, there are 
individual members, and the board is selected by a complex process, not by 
the existing trustees.

Since we seem to be arguing about easily checked facts, I'll stop here.

R's,
John
--0-1023174661-1511554186=:32660--


From nobody Fri Nov 24 12:21:14 2017
Return-Path: <mfidelman@meetinghouse.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 729B11270AC for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 12:21:12 -0800 (PST)
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 e6oswEuD4FNT for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 12:21:10 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id A4E551205F0 for <ietf@ietf.org>; Fri, 24 Nov 2017 12:21:10 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E767CCC1E6; Fri, 24 Nov 2017 15:21:09 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id icRnHvg9LGbP; Fri, 24 Nov 2017 15:21:08 -0500 (EST)
Received: from Miless-MacBook-Pro.local (70-59-240-225.phnx.qwest.net [70.59.240.225]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 3E74CCC04F; Fri, 24 Nov 2017 15:21:08 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <010c0deb-0317-6891-052c-b836488faa58@joelhalpern.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <8ae4773b-9cc9-ab3a-abef-84c1c52a6e38@meetinghouse.net>
Date: Fri, 24 Nov 2017 13:21:07 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <010c0deb-0317-6891-052c-b836488faa58@joelhalpern.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DU7FVKjtYkXRnpyaS00DHbaUSE4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 20:21:12 -0000

I think it's the other way around.

ISOC's "experience and skill in working with governments" stems 
primarily from the work of key individuals, many of them associated with 
IETF (and ARIN, and ICANN), who have both credibility and direct 
involvement in Internet governance.  ISOC, as an organization & a 
community has simply been along for the ride.

At the same time, I've been a longtime critic of the limited involvement 
that the bulk of the IETF community has had in the broader area of 
Internet governance and policy.  (E.g., this whole circle-jerk around 
"network neutrality" - because the community has long had a libertarian 
attitude when it comes to regulatory matters, and a knee-jerk negative 
reaction to such long-standing regulatory principles such as common 
carriage & anti-trust.)

Now, ISOC could be an effective stakeholder organization, if it got its 
act together in terms of its own organizational model, membership model, 
policy formation process.  But right now, it's a joke.

At least let's not devalue or compromise its critically important role 
as the organizational home for IETF - which remains (IMHO) ISOC's 
primary value to the world.

Miles Fidelman (note: spoken as a "pioneer member" of ISOC, who worked 
on building the early Internet while at BBN, built a policy shop for a 
while at The Center for Civic Networking, and served on policy groups 
for both IEEE & ACM)


On 11/24/17 1:03 PM, Joel M. Halpern wrote:
> I think you are under-valuing in your analysis the positive impact on 
> the goals of the IETF that ISOC's other activities have had in the 
> past and are likely to have in the future.
> For example, their experience and skill in working with governments 
> was critical in preventing previous rounds of efforts by governments 
> to significantly change the core governance of the Internet.  Which 
> would have significantly harmed the IETF's efforts.
>
> Yours,
> Joel
>
> On 11/24/17 2:10 PM, Miles Fidelman wrote:
>> On 11/24/17 11:31 AM, John R. Levine wrote:
>>
>>>> Particularly odd, in that ISOC's original raison d'etre was to 
>>>> provide a non-government umbrella for IETF.  And arguably, there's 
>>>> really very little else that ISOC does that has serious substance. 
>>>> It's never really grown into a serious, broad-based professional 
>>>> organization, policy organization or even a serious membership 
>>>> organization.  It just hacks at the edges.
>>>
>>> I think I know a lot of people who would disagree with you. ISOC 
>>> does a great deal of quiet policy stuff in DC and Brussels, and a 
>>> lot of development work in Africa and Asia. If you haven't heard 
>>> about it, that's probably because you (and I) are not the target 
>>> audience.
>>>
>>
>> Well... quoting from 
>> https://www.internetsociety.org/internet/history-of-the-internet/ietf-internet-society/ 
>>
>> "The Internet Society was formed by a number of people with long-term 
>> involvement in the Internet Engineering Task Force (IETF). As a 
>> result, one of its principal rationales was to provide an 
>> institutional home for and financial support for the Internet 
>> Standards process."
>> (though I heard this directly from Vint's mouth, back in the day)
>>
>> At the time, ISOC was presented as a membership association 
>> representing the "Internet community," and I still carry my original 
>> membership card, dated 1992, and stamped "Pioneer" (and, somewhere, I 
>> also have the lapel pin that came with it) . I'm not sure ISOC was 
>> ever actually organized as a membership organization - I can't recall 
>> ever being called to vote on trustees, and the organizational 
>> documents no longer seem to be on the web site.  And over the years 
>> the notion of individual membership seems to have come & gone several 
>> times, along with individual dues.
>>
>> The organization is certainly not a professional group, in the sense 
>> of IEEE or ACM.
>>
>> And when it comes to policy involvement, it's not at all clear who 
>> ISOC represents or speaks for.  I've served on policy bodies for both 
>> IEEE & ACM, and ISOC certainly does not approach policy engagement in 
>> anything like the way those professional bodies do. Nor does it speak 
>> as an industry association (though it does seem to have the notion of 
>> corporate members).  Nor is it anywhere near as visible as EFF – 
>> which might well be the most effective policy group working in the 
>> Internet space (at least in the US).
>>
>> Which brings us back to the one clear role that ISOC plays - "an 
>> institutional home for and financial support for the Internet 
>> Standards process."
>>
>> Miles Fidelman
>>
>>
>>

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Fri Nov 24 14:08:05 2017
Return-Path: <mfidelman@meetinghouse.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 96BF41293EC for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3YZ89aAOhFQ for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:08:02 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5558C126DCA for <ietf@ietf.org>; Fri, 24 Nov 2017 14:08:02 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id AA390CC220; Fri, 24 Nov 2017 17:08:01 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pmW9JR9h-Zdz; Fri, 24 Nov 2017 17:08:00 -0500 (EST)
Received: from Miless-MacBook-Pro.local (70-59-240-225.phnx.qwest.net [70.59.240.225]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 55418CC044; Fri, 24 Nov 2017 17:07:59 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
To: "John R. Levine" <johnl@iecc.com>
Cc: IETF general list <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net>
Date: Fri, 24 Nov 2017 15:07:57 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.21.1711241507070.32660@ary.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g4DSF4YP7xaFXkamvS2Fs0H2TSU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 22:08:03 -0000

On 11/24/17 1:09 PM, John R. Levine wrote:

>> Please don't send private responses to public comments.
>
> Well, OK.
>
>> Is it a membership organization?  It purported to be, at the 
>> beginning - but individual membership has come and gone, doesn't 
>> carry a vote, or dues.  It's a non-profit with a self-perpetuating 
>> board of trustees.  So it's not really clear what is.
>
> As is trivial to find out by looking at ISOC's web site, there are 
> individual members, and the board is selected by a complex process, 
> not by the existing trustees.
>
Well, yes, the articles of incorporation state:

"The corporation shall have classes of members, and the qualifications 
and rights of the members, including any right to vote, shall be as 
provided in the by-laws."

And the current by-laws state that "Individual members shall not have 
any voting rights with respect to the Society."  (To my recollection, 
they never have.)  At the beginning, there were dues levied on 
individual members, but no longer.

I also note that individual "membership" is equivalent to registering 
for the ISOC web site.

Given that the only folks who actually have a vote on anything are 
organizational members - which include carriers who might be subject to 
government action – ISOC starts to look a lot like an industry 
association, and does not really have a particularly legitimate standing 
to talk about policy in the public interest.  (I also note that the 
by-laws, which specify how Trustees are selected, can be amended by a 
vote of the Trustees.)

That bothers me, a lot (speaking as someone who carries a "pioneer" 
membership card, dated 1992.

Scott's original comment, about the IETF seeming to get lost in the 
mission statement bothers me more - as I remember, hearing directly from 
Vint, that (as now stated on ISOC's web site) "The Internet Society was 
formed by a number of people with long-term involvement in the Internet 
Engineering Task Force (IETF). As a result, one of its principal 
rationales was to provide an institutional home for and financial 
support for the Internet Standards process. This rationale still exists 
today."  And to my mind, it's the only place that ISOC is actually 
making a substantive impact.

Miles Fidelman







-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Fri Nov 24 14:17:51 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83D291293EC for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:17:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUaK_Jz1ikDD for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:17:48 -0800 (PST)
Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (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 C381C1243F3 for <ietf@ietf.org>; Fri, 24 Nov 2017 14:17:48 -0800 (PST)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp001.me.com by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0OZX00N00ZTAKM00@mr11p00im-asmtp001.me.com> for ietf@ietf.org; Fri, 24 Nov 2017 22:17:46 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1511561866; bh=GNVY4AjowMpccPuCrI8uX/bOWRAl4ZP/V1FpcG3yc2k=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=sPX7ufNBsQ1eGxCLES3mXh1IWr2Rlmk27dByMA9dHlsyb+Nf90dB3sbZndTyoBKaE RKi76e8YmKx2EFy252AflU4nx1fXJSlUBuuGsH6zWc7hgBYHF1CPB7n/5Quapv8oNG 3BoStKAX/WOOy8fIIaRBTYxY07xj36rLXdAbeuAnMN4DbAjiMtMFHlP6FH4JdXQ9ZI pc0mFxTO6nNElg5lRJmyXkh7uaoxZALB3ZADPBTtYgT8RGrWs7f+ODp3U9WxHUDLfy ws1NNQuuQKjEa2lggbEUamDXH8CM2TqEEUuiS50x4Rg28Cx6iqPsIFNpS3pTMkLo2l 4rsJhYV6Xburw==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0OZY004VI0LJJ610@mr11p00im-asmtp001.me.com>; Fri, 24 Nov 2017 22:17:44 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-24_07:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711240302
Date: Fri, 24 Nov 2017 14:17:42 -0800 (PST)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: "John R. Levine" <johnl@iecc.com>, IETF general list <ietf@ietf.org>
Subject: Re: Proposal to revise ISOC's mission statement
In-reply-to: <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net>
Message-id: <alpine.OSX.2.01.1711241416210.45333@ole-pro.local>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/b-euOg7p7IUjCzjAEhLKJNWu7ug>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 22:17:49 -0000

Miles,

Individual members of chapters have voting rights in their
respective chapter and the chapters are represented on the
board. You can look up the details just as easy as I can.


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office: +1 415-550-9433
Cell:   +1 415-370-4628
Docomo: +81 090 3337-9311
E-mail: olejacobsen@me.com
Skype: organdemo



From nobody Fri Nov 24 14:26:48 2017
Return-Path: <ocl@gih.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3307129407 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:26:46 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=gih.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 RUcOqVFCZ-If for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:26:44 -0800 (PST)
Received: from waikiki.gih.co.uk (salsa.gih.co.uk [IPv6:2a00:19e8:10:5::b]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6942F1293EC for <ietf@ietf.org>; Fri, 24 Nov 2017 14:26:44 -0800 (PST)
Received: from waikiki.gih.co.uk (localhost [IPv6:::1]) by waikiki.gih.co.uk (Postfix) with ESMTP id A0D5B320459; Fri, 24 Nov 2017 22:26:42 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=gih.co.uk; h=subject:to:cc :references:from:message-id:date:mime-version:in-reply-to :content-type; s=mahalo1; bh=YMW3W3HC+dQ4O2rmsgl90Kg2u5A=; b=kLa mtrEtN0uMug0gdrAu0TrEeHn4FbV9zqfGzto+kvUck8U0/21dAS73S5PDel8YJ8O J8QR1qGmcJVf/iInp25ZH9Y0ks/AT4o5kUaeEVA0gpGEXDwDXgcb9/+JfGFEdnuK HkCtEhVfAWWY8wHX1OyDrEc3kEe6HmhsZBaLGlKw=
Received: from [192.168.1.21] (LFbn-1-6998-80.w90-116.abo.wanadoo.fr [90.116.175.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by waikiki.gih.co.uk (Postfix) with ESMTPSA id CBEB632042A; Fri, 24 Nov 2017 22:26:41 +0000 (GMT)
Subject: Re: Proposal to revise ISOC's mission statement
To: Miles Fidelman <mfidelman@meetinghouse.net>, "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <010c0deb-0317-6891-052c-b836488faa58@joelhalpern.com> <8ae4773b-9cc9-ab3a-abef-84c1c52a6e38@meetinghouse.net>
From: =?UTF-8?Q?Olivier_MJ_Cr=c3=a9pin-Leblond?= <ocl@gih.com>
Message-ID: <5b7593e0-f5b3-0644-67c8-91ab7ec986ae@gih.com>
Date: Fri, 24 Nov 2017 23:26:39 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <8ae4773b-9cc9-ab3a-abef-84c1c52a6e38@meetinghouse.net>
Content-Type: multipart/alternative; boundary="------------02FC0967A6FDFAF753F0A08B"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ob2IuTN9J1oclO_el0eaibvFlKE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 22:26:47 -0000

This is a multi-part message in MIME format.
--------------02FC0967A6FDFAF753F0A08B
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Dear Miles,

two quick responses from two of your emails - that I have treated in one
email.

On 24/11/2017 21:21, Miles Fidelman wrote:
>
> ISOC's "experience and skill in working with governments" stems
> primarily from the work of key individuals, many of them associated
> with IETF (and ARIN, and ICANN), who have both credibility and direct
> involvement in Internet governance.=C2=A0 ISOC, as an organization & a
> community has simply been along for the ride.=20

Having been at ground zero at WCIT12 I can tell you that was not the
case at all. ISOC staff-developed white papers were key to many of the
arguments that governments which ended up not signing were reading to
develop their arguments. ISOC was a great fact resource. Key individuals
were indeed there too, but everything did not rest on their shoulders.
My understanding, although I have not had time to be on the ground at
ITU F2F meetings since then, whether Plenipot, WTSA, WTDC, is that ISOC
still fulfils that role well.

On 24/11/2017 23:07, Miles Fidelman wrote:
> Given that the only folks who actually have a vote on anything are
> organizational members - which include carriers who might be subject
> to government action =E2=80=93 ISOC starts to look a lot like an indust=
ry
> association, and does not really have a particularly legitimate
> standing to talk about policy in the public interest.=C2=A0 (I also not=
e
> that the by-laws, which specify how Trustees are selected, can be
> amended by a vote of the Trustees.)=20

The Chapters vote too. Part of the BoT is chosen by Chapters.
Kindest regards,

Olivier

--=20
Olivier MJ Cr=C3=A9pin-Leblond, PhD
http://www.gih.com/ocl.html


--------------02FC0967A6FDFAF753F0A08B
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=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    Dear Miles,<br>
    <br>
    two quick responses from two of your emails - that I have treated in
    one email.<br>
    <br>
    <div class=3D"moz-cite-prefix">On 24/11/2017 21:21, Miles Fidelman
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:8ae4773b-9cc9-ab3a-abef-84c1c52a6e38@meetinghouse.net">=
<br>
      ISOC's "experience and skill in working with governments" stems
      primarily from the work of key individuals, many of them
      associated with IETF (and ARIN, and ICANN), who have both
      credibility and direct involvement in Internet governance.=C2=A0 IS=
OC,
      as an organization &amp; a community has simply been along for the
      ride.
    </blockquote>
    <br>
    Having been at ground zero at WCIT12 I can tell you that was not the
    case at all. ISOC staff-developed white papers were key to many of
    the arguments that governments which ended up not signing were
    reading to develop their arguments. ISOC was a great fact resource.
    Key individuals were indeed there too, but everything did not rest
    on their shoulders. My understanding, although I have not had time
    to be on the ground at ITU F2F meetings since then, whether
    Plenipot, WTSA, WTDC, is that ISOC still fulfils that role well. <br>
    <br>
    <div class=3D"moz-cite-prefix">On 24/11/2017 23:07, Miles Fidelman
      wrote:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net">=
Given
      that the only folks who actually have a vote on anything are
      organizational members - which include carriers who might be
      subject to government action =E2=80=93 ISOC starts to look a lot li=
ke an
      industry association, and does not really have a particularly
      legitimate standing to talk about policy in the public interest.=C2=
=A0
      (I also note that the by-laws, which specify how Trustees are
      selected, can be amended by a vote of the Trustees.)
    </blockquote>
    <br>
    The Chapters vote too. Part of the BoT is chosen by Chapters.<br>
    Kindest regards,<br>
    <br>
    Olivier<br>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Olivier MJ Cr=C3=A9pin-Leblond, PhD
<a class=3D"moz-txt-link-freetext" href=3D"http://www.gih.com/ocl.html">h=
ttp://www.gih.com/ocl.html</a>
</pre>
  </body>
</html>

--------------02FC0967A6FDFAF753F0A08B--


From nobody Fri Nov 24 14:44:48 2017
Return-Path: <mfidelman@meetinghouse.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 8D72112940E for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:44:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OCoL7MAS-6NP for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 14:44:45 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 769F212940D for <ietf@ietf.org>; Fri, 24 Nov 2017 14:44:45 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E0152CC1E6; Fri, 24 Nov 2017 17:44:43 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id nm+oLLY9e357; Fri, 24 Nov 2017 17:44:43 -0500 (EST)
Received: from Miless-MacBook-Pro.local (70-59-240-225.phnx.qwest.net [70.59.240.225]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 31462CC03C; Fri, 24 Nov 2017 17:44:42 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
To: Ole Jacobsen <olejacobsen@me.com>
Cc: "John R. Levine" <johnl@iecc.com>, IETF general list <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net>
Date: Fri, 24 Nov 2017 15:44:40 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.01.1711241416210.45333@ole-pro.local>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rcTTW5pJtwqu1PcqsurwOKqwXGM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 22:44:46 -0000

Ole,

With all due respect,

On 11/24/17 3:17 PM, Ole Jacobsen wrote:

>
> Individual members of chapters have voting rights in their
> respective chapter and the chapters are represented on the
> board. You can look up the details just as easy as I can.
>
First off, that doesn't make one a voting member of ISOC, just of a 
chapter, nor does it make ISOC anything like a traditional membership 
association.

Second, there aren't, and as far as I recall never have been, any 
chapters in New England.  (A couple of time folks have tried to start 
one in Boston, and given up for lack of any reason to.)





-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Fri Nov 24 15:47:57 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099CB129431 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 15:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExB24Q_vXCSQ for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 15:47:55 -0800 (PST)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (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 19F2F126BF7 for <ietf@ietf.org>; Fri, 24 Nov 2017 15:47:55 -0800 (PST)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp003.me.com by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0OZY005002LB4C00@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Fri, 24 Nov 2017 23:47:37 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1511567257; bh=QG0BoVFexqEeYQyDyAHbXh5WJhXAnLAGuAjz7Or20rM=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=uVFC/J6KZ97bE9PMLSGlCtZoXu70VE4tYX3tTNupWqrsiIEOWtEXKaQkS0X7F50Bt TnSNjObkCXQH+fVBTQ/wPv7LrIpB3twzSTeJQUJLAKzvYi4Q7BNOao5SRyOew7Df+s +SRHW8jpaHKukBNAYYCQQAk86QOijNuTLLjj0QkUsR9dx4ilY17co0rlNTo+wxYQPt MvRk3IZPGB/B1Onb9waRTg1tbdVikmj/VOT+nkLHZLs6Iw63hsP6oL2ARIQq8pxBpX yo7qhdBEQtHuen2Ar7p19f+LjJhLWo7QopX8iA6h52Lo/EJ7TEEN7XQxMdD1M/tIL9 75EVj8vmve5gg==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0OZY00K8H4RCPP10@mr11p00im-asmtp003.me.com>; Fri, 24 Nov 2017 23:47:37 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-24_09:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711240322
Date: Fri, 24 Nov 2017 15:47:36 -0800 (PST)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: Ole Jacobsen <olejacobsen@me.com>, "John R. Levine" <johnl@iecc.com>, IETF general list <ietf@ietf.org>
Subject: Re: Proposal to revise ISOC's mission statement
In-reply-to: <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net>
Message-id: <alpine.OSX.2.01.1711241541270.45333@ole-pro.local>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="0-947385956-1511567257=:45333"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_KVtg-yth1MJxGqlICVPVF2qygU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Nov 2017 23:47:56 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-947385956-1511567257=:45333
Content-Type: TEXT/PLAIN; charset=utf-8
Content-Transfer-Encoding: 8BIT


On Fri, 24 Nov 2017, Miles Fidelman wrote:

> Ole,
> 
> With all due respect,
> 
> On 11/24/17 3:17 PM, Ole Jacobsen wrote:
> 
> >
> > Individual members of chapters have voting rights in their 
> > respective chapter and the chapters are represented on the board. 
> > You can look up the details just as easy as I can.
> >

> First off, that doesn't make one a voting member of ISOC, just of a chapter,
> nor does it make ISOC anything like a traditional membership association.

Did I say it was? 

You said: "It's a non-profit with a self-perpetuating board of 
trustees." 

> 
> Second, there aren't, and as far as I recall never have been, any chapters in
> New England.  (A couple of time folks have tried to start one in Boston, and
> given up for lack of any reason to.)

Residency may or may not be a requirement for voting. I am member of 
the Japan Chapter, their rules say that only folks living in Japan can
vote (and I don't), but that's probably not a general case rule. In 
other words: If you wanted to get involved in voting I am certain 
there are ways you could do it.

Ole

> 
> 
> 
> 
> 
> -- 
> In theory, there is no difference between theory and practice.
> In practice, there is.  .... Yogi Berra
> 
> 
--0-947385956-1511567257=:45333--


From nobody Fri Nov 24 19:37:37 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 4FC24124B0A for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 19:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lTbsSspf4miw for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 19:37:35 -0800 (PST)
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 0E3E6126DED for <ietf@ietf.org>; Fri, 24 Nov 2017 19:37:35 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eIRHW-0006mW-Js; Sat, 25 Nov 2017 03:37:30 +0000
Date: Sat, 25 Nov 2017 12:37:28 +0900
Message-ID: <m2o9nruiyv.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Scott O. Bradner" <sob@sobco.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Proposal to revise ISOC's mission statement
In-Reply-To: <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.2 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/OB2QO8HpK8b7aRMy2jKpgV4vZC8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 03:37:36 -0000

> IMO - it will be harder to raise funds from some parties since there
> is no mention of the IETF on https://www.internetsociety.org/mission/

this tells us a lot about isoc and its utter lack of clue and integrity.

future actions of ietf and those who support the ietf should be based
on this.

randy


From nobody Fri Nov 24 19:52:50 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 C4953126D3F for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 19:52:49 -0800 (PST)
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 cqvAgDPOKB81 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 19:52:48 -0800 (PST)
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 2568B1242F7 for <ietf@ietf.org>; Fri, 24 Nov 2017 19:52:48 -0800 (PST)
Received: by mail-pf0-x230.google.com with SMTP id q4so15071660pfg.13 for <ietf@ietf.org>; Fri, 24 Nov 2017 19:52:48 -0800 (PST)
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-language:content-transfer-encoding; bh=bsAxvcsoEMUYnu4yuOv7EqHLTfzCNIjA1s+Gt0/vXRU=; b=msLxTVQ6Xx7zzUZRFu4B9FBeruNjPZvVVc+Yx9Ze04DU8aeI6OERjd+Mqm4JLjztp7 9Z5RnCEWdvXe47R9zwvzaUbrOWQRld4QSlRNWGVWuYy85m4x32Z+42PoKKvTgYTvMGTE 6D6FWfY95IeE63pWkIxGOcCRCusmWdhZR+sJH0lscsMxoz36ZzlYOAH/gWDyJqmWTe3C wOgpE2wFunxBinLh6WWV0pnjCjkm1O5DcmQ+DrAvCx/taDwQRbeAV9uThdHuJqE5yDme v0/U/GfNqTjwJq+/3cvKJ1Uk/qxv3WUO8uXAi5IN1HDmrafHYtCGm4VBOGtWmJ6N/2bY nKbQ==
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-language:content-transfer-encoding; bh=bsAxvcsoEMUYnu4yuOv7EqHLTfzCNIjA1s+Gt0/vXRU=; b=YvQmRhcmaFN90Ah9poe22AXB0pt7C/S/ijzmSKhzQz1FkJme0ORSRdUZ7LethG5soO 2ZvYNdECXAzGfzjGIGpIhb7ExpTWUFCqf+XRY+I3nbCBVxwfagFjjJot0pTuFvQeu4R3 oaO02YIQKahLzuXnVDxqH98OzqydSPZ5dQqb2cSsuTZLcAIoiRUi7tYpp+QsoUcE4QfI DYpIEeReDusj8kOPqb73sH+HbV53PlvcY6YCYZt2G07fI39NSxeE/3JRYTnwmlyEeqX8 X+Rzun4OU1lcwAp2Cjr2FLTBNPZ3MRYKqdhMSOW78AnvKbM3+kwhA7mmu3BYIiuzo09o mfPQ==
X-Gm-Message-State: AJaThX5ciedTveU+1V0GrhlWknVCXFagpLSIl7sR9Cc072Gc0uBStv7h mSxpfxhGheP2KGbbOr/T8tp+mw==
X-Google-Smtp-Source: AGs4zMbq51Kb9ZLV6GFdEkHOSm8PHi/CymBFyeX3cDV07SYaJzyKNDxv3dcPVSRPEQ9SIfsAxop52g==
X-Received: by 10.98.161.25 with SMTP id b25mr29527838pff.103.1511581967357; Fri, 24 Nov 2017 19:52:47 -0800 (PST)
Received: from ?IPv6:2406:e007:6f17:1:28cc:dc4c:9703:6781? ([2406:e007:6f17:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u12sm42815240pfi.87.2017.11.24.19.52.44 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Nov 2017 19:52:46 -0800 (PST)
Subject: Re: Proposal to revise ISOC's mission statement
To: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com>
Date: Sat, 25 Nov 2017 16:52:55 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l1Fp9YmZhoySpMlWaedMrITK-v8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 03:52:50 -0000

On 25/11/2017 11:44, Miles Fidelman wrote:
> Ole,
>=20
> With all due respect,
>=20
> On 11/24/17 3:17 PM, Ole Jacobsen wrote:
>=20
>>
>> Individual members of chapters have voting rights in their
>> respective chapter and the chapters are represented on the
>> board. You can look up the details just as easy as I can.
>>
> First off, that doesn't make one a voting member of ISOC, just of a=20
> chapter, nor does it make ISOC anything like a traditional membership=20
> association.

That's correct. As ISOC Board Chair at the time when the current
constitutional arrangements were put in place, I could tell you a
lot about the whys and wherefores over a couple of beers.

But whoever said that the *Internet* Society should work like a
*traditional* membership association? We had to find something that
would work at world scale, allow for multiple types of stakeholder,
and not be subject to capture by special interests or populist
politics.

> Second, there aren't, and as far as I recall never have been, any=20
> chapters in New England.=C2=A0 (A couple of time folks have tried to st=
art=20
> one in Boston, and given up for lack of any reason to.)

Local chapters wax and wane, and are very subject to the personalities
and motivations of their founders. Some work, some don't. (The Geneva
chapter, of which I was the first President in ~1995 iirc, crashed
and burned by 2009 due to lack of activity, but was followed by the
current active Swiss chpater. But most of the chapters today are in
the developing world, which is great.)

    Brian


From nobody Fri Nov 24 20:39:24 2017
Return-Path: <mfidelman@meetinghouse.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 ABD2A1270A7 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 20:39:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5kTcoD7_gJj9 for <ietf@ietfa.amsl.com>; Fri, 24 Nov 2017 20:39:21 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 11908126C25 for <ietf@ietf.org>; Fri, 24 Nov 2017 20:39:20 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 2EA59CC545 for <ietf@ietf.org>; Fri, 24 Nov 2017 23:39:20 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id vcs790EQW4MI for <ietf@ietf.org>; Fri, 24 Nov 2017 23:39:19 -0500 (EST)
Received: from Miless-MacBook-Pro.local (70-59-240-225.phnx.qwest.net [70.59.240.225]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 8F52BCC531 for <ietf@ietf.org>; Fri, 24 Nov 2017 23:39:18 -0500 (EST)
Subject: Re: Proposal to revise ISOC's mission statement
To: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <753b0a2d-54f5-39cf-b414-3e4f80fc6b14@meetinghouse.net>
Date: Fri, 24 Nov 2017 21:39:14 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o2PeHAx3vSO4kMZPd4SPh48IwvY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 04:39:23 -0000

Hi Brian,

On 11/24/17 8:52 PM, Brian E Carpenter wrote:

> On 25/11/2017 11:44, Miles Fidelman wrote:
>> Ole,
>>
>> With all due respect,
>>
>> On 11/24/17 3:17 PM, Ole Jacobsen wrote:
>>
>>> Individual members of chapters have voting rights in their
>>> respective chapter and the chapters are represented on the
>>> board. You can look up the details just as easy as I can.
>>>
>> First off, that doesn't make one a voting member of ISOC, just of a
>> chapter, nor does it make ISOC anything like a traditional membership
>> association.
> That's correct. As ISOC Board Chair at the time when the current
> constitutional arrangements were put in place, I could tell you a
> lot about the whys and wherefores over a couple of beers.

Love to take you up on those beers at some point.  Though I do know some 
of the reasons - and they had more to do with the techno-politics of why 
ISOC was created in the first place.
>
> But whoever said that the *Internet* Society should work like a
> *traditional* membership association? We had to find something that
> would work at world scale, allow for multiple types of stakeholder,
> and not be subject to capture by special interests or populist
> politics.

Well true, but for a very short time it presented as such (you know, 
membership cards & levels, dues, and so forth.

Personally, I would have gone for either the self-perpetuating board of 
trustees model, or a professional association model.  (IMHO, IEEE does 
pretty well as both a standards body and as a policy shop; though the 
IETF does better in terms of standards process.)

>> Second, there aren't, and as far as I recall never have been, any
>> chapters in New England.  (A couple of time folks have tried to start
>> one in Boston, and given up for lack of any reason to.)
> Local chapters wax and wane, and are very subject to the personalities
> and motivations of their founders. Some work, some don't. (The Geneva
> chapter, of which I was the first President in ~1995 iirc, crashed
> and burned by 2009 due to lack of activity, but was followed by the
> current active Swiss chpater. But most of the chapters today are in
> the developing world, which is great.)

I've never quite figured out the logic of chapters, absent operating as 
a true professional association.  There's certainly room for a true 
professional association in the networking space - but absent one, IEEE 
& ACM (plus more specialized groups like AFCEA) fill the gap quite 
nicely when it comes to talks, conferences, professional networking.  
Perhaps there's more of a vacuum to fill in the developing world?

Regards,

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Sat Nov 25 05:49:34 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 1F48212711A for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 05:49:33 -0800 (PST)
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 SKsSEOHAu670 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 05:49:31 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF174126BF3 for <ietf@ietf.org>; Sat, 25 Nov 2017 05:49:31 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eIapk-000DPq-ED; Sat, 25 Nov 2017 08:49:28 -0500
Date: Sat, 25 Nov 2017 08:49:23 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: ISOC chapter and board compositon (was: Re: Proposal to revise ISOC's mission statement)
Message-ID: <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
In-Reply-To: <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FEie8D-vO8LNV4jYjxk-EMstkfg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 13:49:33 -0000

(Trying to change the subject line because this really isn't
about the mission statement)

--On Saturday, November 25, 2017 4:52 PM +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> Second, there aren't, and as far as I recall never have been,
>> any  chapters in New England.=C2=A0 (A couple of time folks =
have
>> tried to start  one in Boston, and given up for lack of any
>> reason to.)

Miles, I think "no reason" is a mis-characterization.  At least
from my perspective, a very significant part of the problem was
that the folks who would have needed to be the core of an ISOC
chapter (or, if you prefer, without whom an ISOC chapter would
not be credible) have been too busy with other things, notably,
as the IETF has been putting it, "Making the Internet work
better" in technical and substantive ways.  Speaking for myself
only, although I suspect some who are even more active
contributors to the technical work of the IETF may share my
view, I'd rather have no ISOC chapter than one that would be of
very high risk of being captured by folks who wanted to pursue
specific social or political causes in the name of such a
chapter and whose take on those issues might be very different
than mine, and to do so in an environment in which I wouldn't
have time or energy to make counterarguments.   Normally, I
ignore such things, or on the assumption that diversity of
opinions is a good thing, encourage them, but I have been
confident that a Boston chapter would be taken (or promoted) as
speaking for me whether or not I had anything to do with it.
The success of the IETF Boston Hub (or whatever it is called
these days) may or may not reinforce that view of the
appropriateness of an ISOC Chapter and that, along with the GBC
ACM-IEEE collaboration may, further cut into available cycles.

Is that fair from an ISOC voting standpoint to those of us for
whom an active chapter structure does not seem appropriate?   I
don't think so either.  But, as Brian and others have pointed
out, no one has come up with a better suggested arrangement yet.

> Local chapters wax and wane, and are very subject to the
> personalities and motivations of their founders. Some work,
> some don't. (The Geneva chapter, of which I was the first
> President in ~1995 iirc, crashed and burned by 2009 due to
> lack of activity, but was followed by the current active Swiss
> chpater. But most of the chapters today are in the developing
> world, which is great.)

Great except for one thing, which is that, AFAICT, several,
perhaps many, of those chapters have been captured by a small
number of people who, judging from appearances, have found them
very useful as personal platforms or career-boosters.  Maybe
that is ok (or the best that can be done in the short term) for
a given chapter, but, to the extent to which is gives a
relatively small number of people with a focus on very local
concerns (even if they have global ambitions) disproportionate
representation on the Board, it is something that should at
least be monitored as we go forward.

best,
   john


From nobody Sat Nov 25 06:24: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 000AE12420B for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 06:24:12 -0800 (PST)
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 mqJfXC1hAv4f for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 06:24:11 -0800 (PST)
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 14D1212711A for <ietf@ietf.org>; Sat, 25 Nov 2017 06:24:08 -0800 (PST)
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 vAPEO55X012725; Sat, 25 Nov 2017 15:24:05 +0100 (CET)
Received: from [192.168.217.119] (p5DC7E827.dip0.t-ipconnect.de [93.199.232.39]) (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 3ykb0P2205zDXRw; Sat, 25 Nov 2017 15:24:05 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: ISOC chapter and board compositon (was: Re: Proposal to revise ISOC's mission statement)
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
Date: Sat, 25 Nov 2017 15:24:04 +0100
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
X-Mao-Original-Outgoing-Id: 533312644.318825-954fb65d640710f40e465bdd80c8fb18
Content-Transfer-Encoding: quoted-printable
Message-Id: <531489C9-7B5C-4AE6-AB35-4D3FA7C40817@tzi.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com> <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UF7ZxmXCIDGzZSurIEAZZUnG-9A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 14:24:13 -0000

On Nov 25, 2017, at 14:49, John C Klensin <john-ietf@jck.com> wrote:
> [=E2=80=A6]
> I'd rather have no ISOC chapter than one that would be of
> very high risk of being captured by folks who wanted to pursue
> specific social or political causes in the name of such a
> chapter and whose take on those issues might be very different
> than mine, and to do so in an environment in which I wouldn't
> have time or energy to make counterarguments.

That is a nice summary of the core problem that those who actually do, =
tend to have with attempts to organize/getting organized [sic!].

In the end, we all have to recognize that we have to speak if we don=E2=80=
=99t want others to speak for us.

But, amazingly, we often have been able to find people who did want to =
run an organization without too many ulterior motives.
Finding those people, and finding the structures that enable us to =
protect them, is key.
(As is giving them the leeway that allows them to justify the effort.)

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


From nobody Sat Nov 25 06:25:00 2017
Return-Path: <dburk@burkov.aha.ru>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B056127333 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 06:24:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QdsHXrkzC2za for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 06:24:57 -0800 (PST)
Received: from aha.ru (backend13.aha.ru [62.113.86.202]) by ietfa.amsl.com (Postfix) with ESMTP id E66E11271DF for <ietf@ietf.org>; Sat, 25 Nov 2017 06:24:56 -0800 (PST)
Received: from [188.170.72.6] (account dburk@burkov.aha.ru HELO GSP.local) by backend13.aha.ru (CommuniGate Pro SMTP 4.3.11) with ESMTPSA id 518935837 for ietf@ietf.org; Sat, 25 Nov 2017 17:24:55 +0300
Subject: Re: Proposal to revise ISOC's mission statement
To: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local>
From: Dmitry Burkov <dburk@burkov.aha.ru>
Message-ID: <5c2bb753-f056-9706-fbdb-ec997cd31c12@burkov.aha.ru>
Date: Sat, 25 Nov 2017 17:24:54 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <alpine.OSX.2.01.1711241416210.45333@ole-pro.local>
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/De6qnlHgjZh75EkL8yCixRZ9LXw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 14:24:59 -0000

This is a good example how to manipulate the world.

Dima

On 11/25/17 1:17 AM, Ole Jacobsen wrote:
> Miles,
>
> Individual members of chapters have voting rights in their
> respective chapter and the chapters are represented on the
> board. You can look up the details just as easy as I can.
>
>
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office: +1 415-550-9433
> Cell:   +1 415-370-4628
> Docomo: +81 090 3337-9311
> E-mail: olejacobsen@me.com
> Skype: organdemo
>
>


From nobody Sat Nov 25 07:04:30 2017
Return-Path: <cdel@firsthand.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 839C0127342 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 07:04:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=firsthand.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 mFQ18DewNaHu for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 07:04:27 -0800 (PST)
Received: from tranquility.default.cdelarrinaga.uk0.bigv.io (tranquility.default.cdelarrinaga.uk0.bigv.io [213.138.114.184]) (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 5FED7127333 for <ietf@ietf.org>; Sat, 25 Nov 2017 07:04:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=firsthand.net; s=tranquility;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:Reply-To:From:Date:Message-ID; bh=/4eMemrJYhEDpzDywdIebRJicVWPTTIp/1wCRNsUUZ4=;  b=OpQCsKPomrmy8eNb7bMLHgKFVhWDZgY8SZSPy/QNAllDKYpVmfD32+HJGHEtU/AaXrad/oyPJVP7vaQcWBBgD0JA4Ew0UbKiey23EbfFe1LkiDE4ZZa9DbXNgIgf8G5z6mE1wEMiejMurXplMzcaZOvzBWUFDThuFf65DzjpZ9w=;
Received: from [37.18.142.235] (helo=Christians-MacBook-Pro.local) by tranquility.default.cdelarrinaga.uk0.bigv.io with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <cdel@firsthand.net>) id 1eIc0E-0003kv-85; Sat, 25 Nov 2017 15:04:22 +0000
Message-ID: <5A198671.6090901@firsthand.net>
Date: Sat, 25 Nov 2017 15:04:17 +0000
From: Christian de Larrinaga <cdel@firsthand.net>
Reply-To: cdel@firsthand.net
User-Agent: Postbox 5.0.20 (Macintosh/20171012)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
CC: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: ISOC chapter and board compositon
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com> <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
In-Reply-To: <6966AE3A48A46EA095384A10@JcK-HP5.jck.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/pBYTozMgrW3jh5ii_wnAJXwN0ag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 15:04:29 -0000

Would you not agree that the main way for people to ensure integrity (of
ISOC and its chapters) is by participating actively? Chapters need IETF
participants to take an active interest and not be shy of taking leading
roles in setting up working activities and joining local boards.
Political perceptions of the Internet get swayed much higher up the
stack than the IP layer. Particularly if a policy wonk sniffs a low
hanging fruit to solve a pet political agenda. It takes considerable
perseverance and patience as well as clue to engage the political sphere
with the implications of the underpinnings of an open network
infrastructure in face of these snake oil salesmen in the application
spaces.

I agree with Scott that ISOC ought to keep the principles that
distinguish the IETF front and centre of its own mission and actively
encourage participation of IETF people in ISOC, particularly in the
chapters which are volunteer led and barely supported by ISOC (although
changes to this are starting to happen I understand).  Just because IETF
votes for three or so trustees in ISOC should not be the end or even the
beginning of engagement by those in IETF in their local technical
community. An ISOC chapter can become a useful focal point. But only if
the technical community deigns to join in locally and participate that way.



Christian





John C Klensin wrote:
> (Trying to change the subject line because this really isn't
> about the mission statement)
>
> --On Saturday, November 25, 2017 4:52 PM +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
>>> Second, there aren't, and as far as I recall never have been,
>>> any  chapters in New England.  (A couple of time folks have
>>> tried to start  one in Boston, and given up for lack of any
>>> reason to.)
>
> Miles, I think "no reason" is a mis-characterization.  At least
> from my perspective, a very significant part of the problem was
> that the folks who would have needed to be the core of an ISOC
> chapter (or, if you prefer, without whom an ISOC chapter would
> not be credible) have been too busy with other things, notably,
> as the IETF has been putting it, "Making the Internet work
> better" in technical and substantive ways.  Speaking for myself
> only, although I suspect some who are even more active
> contributors to the technical work of the IETF may share my
> view, I'd rather have no ISOC chapter than one that would be of
> very high risk of being captured by folks who wanted to pursue
> specific social or political causes in the name of such a
> chapter and whose take on those issues might be very different
> than mine, and to do so in an environment in which I wouldn't
> have time or energy to make counterarguments.   Normally, I
> ignore such things, or on the assumption that diversity of
> opinions is a good thing, encourage them, but I have been
> confident that a Boston chapter would be taken (or promoted) as
> speaking for me whether or not I had anything to do with it.
> The success of the IETF Boston Hub (or whatever it is called
> these days) may or may not reinforce that view of the
> appropriateness of an ISOC Chapter and that, along with the GBC
> ACM-IEEE collaboration may, further cut into available cycles.
>
> Is that fair from an ISOC voting standpoint to those of us for
> whom an active chapter structure does not seem appropriate?   I
> don't think so either.  But, as Brian and others have pointed
> out, no one has come up with a better suggested arrangement yet.
>
>> Local chapters wax and wane, and are very subject to the
>> personalities and motivations of their founders. Some work,
>> some don't. (The Geneva chapter, of which I was the first
>> President in ~1995 iirc, crashed and burned by 2009 due to
>> lack of activity, but was followed by the current active Swiss
>> chpater. But most of the chapters today are in the developing
>> world, which is great.)
>
> Great except for one thing, which is that, AFAICT, several,
> perhaps many, of those chapters have been captured by a small
> number of people who, judging from appearances, have found them
> very useful as personal platforms or career-boosters.  Maybe
> that is ok (or the best that can be done in the short term) for
> a given chapter, but, to the extent to which is gives a
> relatively small number of people with a focus on very local
> concerns (even if they have global ambitions) disproportionate
> representation on the Board, it is something that should at
> least be monitored as we go forward.
>
> best,
>    john
>

-- 
Christian de Larrinaga  FBCS, CITP,
-------------------------
@ FirstHand
-------------------------
+44 7989 386778
cdel@firsthand.net
-------------------------


From nobody Sat Nov 25 09:26:09 2017
Return-Path: <mfidelman@meetinghouse.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 CCF14127863 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 09:26:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TRgs8ZKQ7pms for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 09:26:06 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4793A1204DA for <ietf@ietf.org>; Sat, 25 Nov 2017 09:26:06 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 84944CC4DB for <ietf@ietf.org>; Sat, 25 Nov 2017 12:26:05 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id g1LjHN-hNUFP for <ietf@ietf.org>; Sat, 25 Nov 2017 12:26:04 -0500 (EST)
Received: from Miless-MacBook-Pro.local (71-223-239-106.phnx.qwest.net [71.223.239.106]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A4CD3CC2E7 for <ietf@ietf.org>; Sat, 25 Nov 2017 12:26:03 -0500 (EST)
Subject: Re: ISOC chapter and board compositon
To: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com> <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <1adf3a95-7dd3-0976-ee9c-2ffcc463693d@meetinghouse.net>
Date: Sat, 25 Nov 2017 10:26:00 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FHeecVtEZTsW2J2i5yeXSwm-nvQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 17:26:08 -0000

On 11/25/17 6:49 AM, John C Klensin wrote:

> (Trying to change the subject line because this really isn't
> about the mission statement)
>
> --On Saturday, November 25, 2017 4:52 PM +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
>>> Second, there aren't, and as far as I recall never have been,
>>> any  chapters in New England.  (A couple of time folks have
>>> tried to start  one in Boston, and given up for lack of any
>>> reason to.)
> Miles, I think "no reason" is a mis-characterization.  At least
> from my perspective, a very significant part of the problem was
> that the folks who would have needed to be the core of an ISOC
> chapter (or, if you prefer, without whom an ISOC chapter would
> not be credible) have been too busy with other things, notably,
> as the IETF has been putting it, "Making the Internet work
> better" in technical and substantive ways.  Speaking for myself
> only, although I suspect some who are even more active
> contributors to the technical work of the IETF may share my
> view, I'd rather have no ISOC chapter than one that would be of
> very high risk of being captured by folks who wanted to pursue
> specific social or political causes in the name of such a
> chapter and whose take on those issues might be very different
> than mine, and to do so in an environment in which I wouldn't
> have time or energy to make counterarguments.   Normally, I
> ignore such things, or on the assumption that diversity of
> opinions is a good thing, encourage them, but I have been
> confident that a Boston chapter would be taken (or promoted) as
> speaking for me whether or not I had anything to do with it.
> The success of the IETF Boston Hub (or whatever it is called
> these days) may or may not reinforce that view of the
> appropriateness of an ISOC Chapter and that, along with the GBC
> ACM-IEEE collaboration may, further cut into available cycles.

I tend to agree with you on that.

 From a sample of one, my observations of the last attempt to form a 
Boston chapter - which managed to have a few rather uninspired meetings 
(I think I went to an attempt at an organizational meeting, and one 
other):  The organizers were a combination of some rather poor 
technologists (you know, the folks who "left" technical management jobs 
to form consulting shops - and saw involvement as a way to drum up 
business) and folks who had more of a social policy interest.  The real 
technologists were too busy working (Boston/Cambridge is kind of ground 
zero for a lot of the community - who needs an ISOC chapter when you've 
got MIT, BBN, et. al.).  And the real social policy types were involved 
in things like CPSR.  As you say, a Boston ISOC chapter certainly would 
not have been speaking for me.
>
> Is that fair from an ISOC voting standpoint to those of us for
> whom an active chapter structure does not seem appropriate?   I
> don't think so either.  But, as Brian and others have pointed
> out, no one has come up with a better suggested arrangement yet.

As I commented separately - I'd personally rather have seen ISOC start 
with a self-perpetuating Board or organize as a true professional 
association (akin to IEEE).  From both a governance standpoint and as a 
standards body & policy shop, it seems to "work" (I do think the IETF 
standards process is far better than IEEEs, but in terms of governance & 
administration, IEEE is a good model).

>> Local chapters wax and wane, and are very subject to the
>> personalities and motivations of their founders. Some work,
>> some don't. (The Geneva chapter, of which I was the first
>> President in ~1995 iirc, crashed and burned by 2009 due to
>> lack of activity, but was followed by the current active Swiss
>> chpater. But most of the chapters today are in the developing
>> world, which is great.)
> Great except for one thing, which is that, AFAICT, several,
> perhaps many, of those chapters have been captured by a small
> number of people who, judging from appearances, have found them
> very useful as personal platforms or career-boosters.  Maybe
> that is ok (or the best that can be done in the short term) for
> a given chapter, but, to the extent to which is gives a
> relatively small number of people with a focus on very local
> concerns (even if they have global ambitions) disproportionate
> representation on the Board, it is something that should at
> least be monitored as we go forward.
>
Agreed completely.

Which makes me think that the critical issues in ISOC governance really 
should  be:

1. Stewardship of the IETF as the Internet standards body (the original 
and still critical role of ISOC).

2. Providing a reputable policy voice regarding Internet issues.

Regarding 1:  I understand why IETF was not explicitly mentioned in the 
Articles of Incorporation - flying under the radar and all that, but in 
2017, when IETF isn't even mentioned in the mission statement, and only 
peripherally mentioned in the latest (2016) bylaws, it concerns me that 
the whole purpose of ISOC is getting lost.  Yes, IETF gets to fill a few 
board seats, but it still has become the tail, instead of the dog.  
(And, I note that this discussion is happening on the ietf e-list - 
where I would expect more people to be concerned.)

Regarding 2:  When votes only go to organizational members, and 
"Platinum Members," with a weighted vote, include Comcast and 
NBCUniversal, one gets a bit leery of ISOCs ability to give unbiased 
advise on things like Network Neutrality (excuse me, Common Carriage and 
Anti-Trust, to use regulatory language that has more of a clearly 
understood history & grounding).  One might also question the influence 
of groups like ICANN and ARIN, when IETF has a contractual relationship 
with them and sets standards to be implemented & managed (and enforced?) 
by them.  It's all just a bit to rife with conflict of interest.

Somehow, I see all of this getting lost in the discussion of the new 
mission statement.  It kind of suggests a lack of transparency 
surrounding the real issues of ISOC governance (which might be 
intentional, or not; and it might even be desirable, or not).

Miles




Miles


-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Sat Nov 25 09:41:43 2017
Return-Path: <gonzalo.camarillo@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 6C29A127A90 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 09:41:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 bOQgZ1DsVjea for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 09:41:39 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 4BCED127909 for <ietf@ietf.org>; Sat, 25 Nov 2017 09:41:39 -0800 (PST)
X-AuditID: c1b4fb3a-c73ff70000004c48-ea-5a19ab519e8b
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A3.F8.19528.15BA91A5; Sat, 25 Nov 2017 18:41:37 +0100 (CET)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.75) with Microsoft SMTP Server (TLS) id 14.3.352.0; Sat, 25 Nov 2017 18:41:36 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=peWgmCtKr/SvqUzWyyu04cEc1BxWDJN6ctkVi0TkPHE=; b=AzB0/U36HGM/a8TXZCySFMLoojIvhQtpIoNm+FuR0Cjub4gsOGvHt2gmb2MoiUj3ShOhNo0W98irMHkDk6jtcXQHBSBtDIWsKIaDGUy4zyEyZP6isOEo0r0+Q8a0t9/gUnTOeDwuNGh5wTr3Zq42OrbST3IrORD9OH3deoSbKl0=
Received: from [192.168.1.7] (37.136.86.88) by AM2PR07MB0625.eurprd07.prod.outlook.com (2a01:111:e400:840d::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.282.3; Sat, 25 Nov 2017 17:41:35 +0000
Subject: Re: ISOC chapter and board compositon
To: John C Klensin <john-ietf@jck.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, <ietf@ietf.org>
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com> <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Message-ID: <58fb7456-eb8a-59cf-4506-f0619c39818a@ericsson.com>
Date: Sat, 25 Nov 2017 19:41:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <6966AE3A48A46EA095384A10@JcK-HP5.jck.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [37.136.86.88]
X-ClientProxiedBy: HE1PR0902CA0021.eurprd09.prod.outlook.com (2603:10a6:3:e5::31) To AM2PR07MB0625.eurprd07.prod.outlook.com (2a01:111:e400:840d::24)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 1c3629bb-5144-404c-b446-08d5342bc669
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603258); SRVR:AM2PR07MB0625; 
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0625; 3:VYxS8YrsX6u1gJKUTndoszTDJraB3JJ5Qgzd1Yqi0lXa/g5a5yd+0cVF8xyfBuctgHJxf70i2gDZWBFnenYlCwIxacWQQTDouDbH4cbK2t+S79896dYXI6FexgH865ove9ncdIIiDk1ofrePootL/hDWh3XLFPR+5zLdzHGMXqJp+QhNtMsB4PX1PbJgiLx0BfMCH8Db7INBzfLzL4tMXxRV2pBir/bvaJZ0ubBK2KOzOnzNKz8cUB2Ew5dbHs43; 25:uaFhcUOklCKzFKFYrWvzUF5XNJsGxsU/ZmPGJVlRjQp97mDJdAueSIIS7fss7iFKKx3/NwiEzW3YZEQUYUyfbQyhIpSKWowEw7BnRGBQbJKvgzVGANgpF6dRGgxVFf+YJcCbZTyWRpep1G0Tz8ZuMGncHNzArpOFdAdHs7tv1LAbv59t2iG/8j2xIbXLlTCykrDnJ9iqL7aA08NkfSDnJf+pQYz3Zpa4mS4euUpDx6bhLphSYbAUpUX1ldqzdNQSUjyEsCLNILr6kQknRkN6BzuzqCNwOU5P7ESI7SckYjZsBvFUp0sekN77mYS3U9UhHaN99XsfZnPVkUHai4wbqg==; 31:WXAjA+y4zsjb6hEQuMm5XpNPP1uS/fTnS4QaImzl05O+9Bz8qEYMQn8LN3LdnW+MeLTfHgyEOhkKrDB0cuCrZXQJJNHp2DTws0wKu+bppvaWcZLLQNIfVSlD47o3oDJfeGmel17sU/MIvUXd/wbstfNsOwH2Sk+GinvKqPhczC0KluORB5bnDBl6WZgAegkND4PmRlegJnixSouSWw78E2n6M5Eg0RXYmdbpFCbMGBM=
X-MS-TrafficTypeDiagnostic: AM2PR07MB0625:
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0625; 20:f5W1Oqxd286wFnWvp1I9A0F91ABKOXf2cZJEWL1QmEqyEKjHkER+9bX7ueTQhZgZhgAVfBez39Fjfvugll/yDj2PRwSw66EQofRNyL4SjD8TZiJqtMlcOf8lUkMG2zloxzMnQETfT6ca9zwoDjV8gO17xrFgnkgDMuYMqdvKMUoIbgDYuwfer/I128/gOzHSPF0h75SvkS9aNunAZmkfSxf/RG126LQuvMUsUA75z09yDc7nsrmwv+oKoVeT+/gJL8rVE09+puU9sQRdMD97AbhFAd+JXiJ4olxxDtFQ6HRd0wi4bqzdb1ezzIweyGaTNTiQyLiFTjhpDT0RWbeT7QjVbmbouVdM+yD6zZRMcDmcfLAN4DOy2wC7hhv/DTjksJME0uhNCzsUmqIWr++VcOmkHFJGNi+j31PccHjcrdfBN2kobUAA8XxE52kfRqpnII09w35PYQwzoCLRoxrgF6DC81iKXZ7jLzYb8K7qMLcJwrwpF74dXjPWmcx75lhZ; 4:JF8fQ5ZjqYRicP3U+IwjG+QrGGJLoaGcXhyBrddo2ham/q4aZLZap7GctM9SJhfIZHyUPFimFQJqoT2bjCEmPJ+uiPNsN+/js0izUKO7/BbQNrvT2rDEhF6QNUDLJWnk6jTyKOPjtbodG1sedY3Zme/z1zD3N8hN2/ponWPKgF/I3li0BcSoZxMFArDvAR6JNqwSQx1lGHb4EF6aTnqhWmOKBDQu5tRC7rUqfM0ncN16GNS4BCySUASZrfJeqvJmgfdlBIIYf7MlZzv/KlAhrAO5OTNnpS4Zo53Ws+EFGZCX77YqlCrrBOmqMdJfuNeO
X-Microsoft-Antispam-PRVS: <AM2PR07MB0625F06CBE824EA3DCAEA04F83270@AM2PR07MB0625.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(21532816269658);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(3231022)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123564025)(20161123555025)(20161123562025)(6072148)(201708071742011); SRVR:AM2PR07MB0625; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:AM2PR07MB0625; 
X-Forefront-PRVS: 0502983C0E
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(6049001)(346002)(366004)(376002)(199003)(189002)(65826007)(83506002)(5660300001)(81166006)(64126003)(50466002)(81156014)(8676002)(97736004)(106356001)(2950100002)(68736007)(305945005)(86362001)(25786009)(52146003)(31696002)(110136005)(6246003)(8936002)(23676004)(77096006)(6486002)(2486003)(478600001)(16526018)(39060400002)(6666003)(7736002)(52116002)(117156002)(36756003)(66066001)(316002)(50986999)(65956001)(54356999)(229853002)(65806001)(58126008)(6116002)(3846002)(93886005)(101416001)(33646002)(2906002)(16576012)(53936002)(47776003)(105586002)(230700001)(189998001)(76176999)(31686004); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0625; H:[192.168.1.7]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTJQUjA3TUIwNjI1OzIzOkdiT0FITnBjRWgyV1BqN2JkaDFneE1jUkRJ?= =?utf-8?B?OTRxZThLMVBQZ3hWNUs4aU9VRFZJTGprNUVKUzlqZFdEQ2R1bzBMbmNBS1E2?= =?utf-8?B?WmZTNGwzTkZ5VWE4ZkEra2hsTXRhK3RGUGJRNHozdWdsMWJwbDg4WUw4UFlt?= =?utf-8?B?eFhXS0dwd3lEYzBxa3JoejQ2bnByVmNWRHdFUzMwd1FvOUI3RWl0Q3pWVmZ3?= =?utf-8?B?YjZBaVdqdlFidDBvcENCMktNekRiM25zcVZYV0xNL3pxL2I0eXVQM0JOSWxE?= =?utf-8?B?L0dpemRjS0h5WXlhMHlvd1JUMWJYbmM0OXFuYXpQOFlSam1Eb2xqdzFEVURk?= =?utf-8?B?U245amVFd1FTbWhPdGZRekhraXFVMEllUkRoK0JpaFJDQW8zOFF1U3BtcWlF?= =?utf-8?B?UUxuOGNPZE9tcnErb05DM1NrRVVlQ1lTYUlzS2JUOUdDaHNPTWYyRTFUOW9t?= =?utf-8?B?MzhZMGl3NnhMM0dXZ0dRSlRsRlQ5dlA2ZERtUk0rOCttVU16Skl3UDZ2ZUFN?= =?utf-8?B?YUhuUkRvbFh5ZUlsN25BdWcvYW90M2RnMzdJQ3N6OTR6TzlpY2w2SlVMcitT?= =?utf-8?B?eFRvSU90TndzQmxRZnFucmJkRVkwVXYzN1MrSnNibmpQY3ZxYVBrYVhvWnRx?= =?utf-8?B?WnlFc1dkY29RVi9ENjdzYVpCeUlKZkVkdWFpREh4eXpERmpreERMc3B6ZDNu?= =?utf-8?B?Y0hTVkk5aVord2h0V1RlNEN4ZlJ4dkZCNnF0T2FDenQ3dmJ2NkVMMnliOWFG?= =?utf-8?B?NTFEbGw2VFNFck4rQ3E4c2xERG14eDRlQUluS21kcmNZbkFVNWF4S0l3a2pO?= =?utf-8?B?L21FUmpNMHJYZDk5TUE1OVRERy9JOWNBekEvK2ZzZSsrL0orVW9sOVFaOE9R?= =?utf-8?B?MXUxS0Y0cTVPM0I0UmRtSFFwWnlZdTNNcVJ4aWR2aDRzYUVGbWdrV1pOcit1?= =?utf-8?B?VEF5c2VWSDY5YTlTN0VMbDZjZGhQSURHRjZzbEJaOE1CNjRBRFlNRVRUNUVq?= =?utf-8?B?UFp0Q0xmTnBLeDRaWGxRdXcwcFJUaFo2WEd6TmtPVVF1OGZkcTVmd214d2tU?= =?utf-8?B?VGUxZXZRYS91Mmx5a0cvTlprZXdlRDFxMHhmblFXVkI1NmdaRVQ0K0FSdjFN?= =?utf-8?B?aFNEcFlRNmhITHBQdndjUjhZdUZCM0dFNXFSd2x0TzE4QVZZaDVwejhJKy9u?= =?utf-8?B?QVR2MldYWS9KdEdpU3FpQldJcGJZRmx5bFd4UkpER2tEb0lqb04vTEg5MCtp?= =?utf-8?B?YUozYUU0a1psM3lPczB0a2VMcEMrcDJHSzNNTUlYL3N4cGE2UXNOZWY0SjRp?= =?utf-8?B?S0ZHcTN3VkRPYmxXaTI4WW83cVovUnJYcDJnQ1M3c28xUnBWVXZxUVQ0bXdN?= =?utf-8?B?MFFncTFNTXhsT2Q4Tm9kZVZTQnlkSFkwaTVnclYxT1dZSnV5WWxvSzRXV3Q1?= =?utf-8?B?MTdjQUpHNWJMNE8wUWgyZGkrTmltNU5uSjhFdDFPMmxrWDVKMlV6OE5LdWtr?= =?utf-8?B?UjJQZUdzcVJvK1RoRkIrNWs3aFFIazN2aW9XNUlDUjd4WVlOU1FlalIwU2hp?= =?utf-8?B?bkJHbFhPVnJ2dnVmM09nNHkrNWExNy82ZlMwNXBjU25MV1gyek1NWFZtM0JS?= =?utf-8?B?aHJXLys5VnBZcWRPMHZOV09vZVhwTHQxUmMvUEdqd2NMNUFBcDVRMXBBVnNG?= =?utf-8?B?YzZsT0s3U1pYSHRaVWRCSW51bFlBTElGazZLQzdFMEhmOHdQT2FoMGZjdThW?= =?utf-8?B?a3pSWXowb05uRWFTWk50ZmdicjNINEFma2NiMzlIRkhUUHFiZnRrS0h5V3Mw?= =?utf-8?B?cE11SStISnlxcjJEOS9oWjA4SzNsYi9lbCt6UFBJaUhWeEJOU3hFUUg0YnZx?= =?utf-8?Q?wxWVeX3xUHFUODZp3u+WXxOACS++Q81P?=
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0625; 6:EGbRvalMJoP65wDpWfnhok3t3HascZ44CHUp6vjLTBdF1p0s8sTqKv1FYbh2WNu/TnmxyRodbGtqxQ0riCdVvr1Mi9laAtnf4Olnl8x08feWW9APjxEVUAIIR6D1esJcaBEV5HCkDrGclhaUfmtha+MStYQ3aaG2zPAjdJWsIKPnJzHTiJfNaVxHFCnsGsMWS6KTS4QDr6ajOVMcb/CqKc4V819+uPMqtasxiLHB5T0NqHnD+wV5tn7N94j71T1Wabhe4buS15hWQs1IvgCW/JeSWxKHvlutedTJ4Loz1CHdtzSkamHCI2izvNWCsoR9TkZm8wGmSUWTpuSy9j9zNdM2M0HWes369WV0EFZdv+E=; 5:lVnqvGAO47BzykkfDcf0W0a9/JMutDaYtFFYadKR1t7ovmm8dsaJCrMUW3dTYUtloh39qGxjTGEx5jYXYJj+1bSvI3ZU0vOUzLgp+HytuLgKscz1jCGkIDyc7K5GeYSQxbbalJlQWmWWz2WRIHeHvMSeh/Gq5YLxFKlkX9FQ/20=; 24:5YT1cbPCUpGl98ioSnSRT+S0uo2NGSlb+lOG5u6Nkwa2FD2eaCMMtj3EsyEMRTL+076K0XOXAM5+b41DUcFvxmnvc63ZT+sHbHBKdkcaOHM=; 7:KYJp/LD9gudSjYMNjBJG5bBQ6VywRFMQqVvYyitQnSprDfOm27YL8xadiLkfU6xYsRciGmkIAzyXYPJT5EPiAHM18QNu5ycHGa3oLGgYBUCJJvP+j6Rg/OeiuTAVK3S79Qpi1DqHEtgIf8dEzE1E7JOfeg5teXo2gL/7Jjd0bMsAGE7pp0rjVkwlGszPY4OvKk7ldj9DbA60dB0WAL45VT0FHOeJ3rzu+cP0YI5xyflmZvcE2tIurNbjMzFROyr6
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Nov 2017 17:41:35.3909 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 1c3629bb-5144-404c-b446-08d5342bc669
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0625
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjleLIzCtJLcpLzFFi42KZGbHdWzdwtWSUwf67ihZtF/cxWTzbOJ/F ovXSHzYHZo+ds+6yeyxZ8pPJ4/LK18wBzFFcNimpOZllqUX6dglcGZdOOxdMYKs41nabrYHx DUsXIyeHhICJxK/5f9lBbCGBw4wSVx5bdzFyAdknGCW2P/3ICOKwCPQySzTMmMwOkWljkpje sogJpEVYQE9i1qmfzF2MHBwiAlkSb79GQdR8Y5W4O3EVG0gNm4CFxJZb98HW8QrYS2xd+h9s HYuAqsSr8/vB4qICMRITH1xkhKgRlDg58wlYnFPAXOL07blg85kFNCXW79IHCTMLiEvcejKf CcKWl9j+dg4zxDcKEvt/rGQDuUFCYCajxNVHe5ggXtOWWP6sBeplWYmjZ+dA2b4SbxueQTUs YZTYNeMbO0SigV1ixp9sCFtLYuaLzWAbGAUSJf7eewvV8INNYvP9BWwQRdkS5/ccY4WwrST6 dnayQxQtYJaY8B5mqozE9u8zWSASv1klvizdzTqBUXsWkrdnIbw6C8mrs5C8uoCRZRWjaHFq cXFuupGRXmpRZnJxcX6eXl5qySZGYCo5uOW31Q7Gg88dDzEKcDAq8fBGTZGMEmJNLCuuzD3E KMHBrCTCy9wEFOJNSaysSi3Kjy8qzUktPsQozcGiJM570pM3SkggPbEkNTs1tSC1CCbLxMEp 1cDIdHxV6UrnXXMuMbPfqrewM15g8enBsomn2XVf/pynNPeInkXX9YfvHPWf/Wj/3sIrsSnv Qhn/26u1Ib1fGnyuTZM/+7qsJo6xXm953s7ZIkIG0Rsv8FeYWKy25H6tM/HsjcpvIfnPNL4+ M9qe57ql680LC4kv+qnGGl+s7Tv37m87v8rui9NHJZbijERDLeai4kQAOUIuzSEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ggv8vvqKANPvn3rVz7CYpn-qcfY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 17:41:41 -0000

Hi John,

> Is that fair from an ISOC voting standpoint to those of us for
> whom an active chapter structure does not seem appropriate?   I
> don't think so either.  But, as Brian and others have pointed
> out, no one has come up with a better suggested arrangement yet.

Per our conversation in L.A., I am looking into how to enable ISOC
individual members to be more involved in ISOC's activities. It is clear
that some individual members cannot (or for whatever reason do not want
to) be part of a chapter (or a SIG) but are interested in some of ISOC's
activities nevertheless.

For example, I also sent the proposed mission statement to the Open
Forum mailing list (on the Connect platform) to get comments from
individual members as well.

Cheers,

Gonzalo


From nobody Sat Nov 25 11:55: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 336AD126D46 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 11:55:21 -0800 (PST)
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 ASXFCnbo9Nb3 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 11:55:20 -0800 (PST)
Received: from mail-pl0-x232.google.com (mail-pl0-x232.google.com [IPv6:2607:f8b0:400e:c01::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 E5487124207 for <ietf@ietf.org>; Sat, 25 Nov 2017 11:55:19 -0800 (PST)
Received: by mail-pl0-x232.google.com with SMTP id o17so6167802pli.1 for <ietf@ietf.org>; Sat, 25 Nov 2017 11:55:19 -0800 (PST)
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-language:content-transfer-encoding; bh=u9I2vW9PLshqGRxa1uMmlmsbhRQ47fUlVm4gs68AI7s=; b=dtRVyOwOoT7PaFyLKgb3gYDrbXcC051VoiXT/T+Du91hZfA+1SetAnBnrgi0H9UWHg Hnr1DYn+F11s5oq8DK7bwUPBUf67NVf/DqNOS9p81XgbS5V/HdcCamBytITkhBrc0ekX 7ELF5h785uNQIezlskDQ+wSFgnQLFK/jAhQ149FcAaFdW80MsoFwAwgZ8n74T5RWObVC DaScvf50DrXcktbYCbyMfwEv+gr0Ji6wnCPKLYZYUkSJsAMTpTg/lKxex/sCpbFNxa/Q gxuJCfw/8pcrbZCrZIT7lrIYtFOPfQ+ofluXzVfgAvO7eeHi8RqInc2So7zJai44+sji V1GA==
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-language:content-transfer-encoding; bh=u9I2vW9PLshqGRxa1uMmlmsbhRQ47fUlVm4gs68AI7s=; b=aqGnAENOLrA/BdXCfyN3RrP+Zk2weKQ+Luosn1NbeUQqalA2DgXljoDhZ6MxnqgyPz ak2qlJC6TBt604ENZ1MJVL+Iuwmbv9rXqqvKPEI5LnCGCvJpHzK/F91C/lxwFgWa1ZFo oN2nG0BAtqj+3ob913lKu6frTowc/ysDB5OqZI6NRaJkZXr/pg/bkT83J1PFjgrEqSAT /qtMic6Q7ndtqx6/n8TitMDfqsSqkfFJDg5KzYXhRl0mxfox2cfmmRIIAFje7uJHJU4k DzQywbve052/A6wkWpsVZZEtBC7ncSkVCpxnBbdx5MwxK3DOHixIi3J+bGsxakQYx4U+ WsAw==
X-Gm-Message-State: AJaThX5Ideh3kMNtL3jreB0AYq2jk66AMmGQG/WMm2QLD4F7IWGYiDTC RMuizcCaF7jgFbRn8Xq0He4GZQ==
X-Google-Smtp-Source: AGs4zMb/X+6I2sowbs7OPMLiihJ+/Yp79fQKeSThxlIHlLEAD+PT8mbcOsuSpcftLBrAxZbTFuI74w==
X-Received: by 10.84.132.34 with SMTP id 31mr26654048ple.395.1511639719097; Sat, 25 Nov 2017 11:55:19 -0800 (PST)
Received: from ?IPv6:2406:e007:6f17:1:28cc:dc4c:9703:6781? ([2406:e007:6f17:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m13sm33464717pgp.61.2017.11.25.11.55.16 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Nov 2017 11:55:18 -0800 (PST)
Subject: Re: ISOC chapter and board compositon
To: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com> <6966AE3A48A46EA095384A10@JcK-HP5.jck.com> <1adf3a95-7dd3-0976-ee9c-2ffcc463693d@meetinghouse.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <951b51b0-74aa-5b99-d81a-81460c861a1a@gmail.com>
Date: Sun, 26 Nov 2017 08:55:13 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <1adf3a95-7dd3-0976-ee9c-2ffcc463693d@meetinghouse.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ThaX4K1NGcLkhfC6DA7McTVmNR4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 19:55:21 -0000

On 26/11/2017 06:26, Miles Fidelman wrote:
=2E..
> Regarding 2:=C2=A0 When votes only go to organizational members, and=20
> "Platinum Members," with a weighted vote, include Comcast and=20
> NBCUniversal,=20

To be clear, the weighted voting applies only to the election of
the four Board members from the organizational members, i.e. at
most to one third of the Board. I don't see this as unduly susceptible
to vested interests.

> one gets a bit leery of ISOCs ability to give unbiased=20
> advise on things like Network Neutrality (excuse me, Common Carriage an=
d=20
> Anti-Trust, to use regulatory language that has more of a clearly=20
> understood history & grounding).=C2=A0 One might also question the infl=
uence=20
> of groups like ICANN and ARIN, when IETF has a contractual relationship=
=20
> with them and sets standards to be implemented & managed (and enforced?=
)=20
> by them.=C2=A0 It's all just a bit to rife with conflict of interest.

Exactly why the Board is set up with the checks and balances of having
three separate constituencies. Do you have any evidence that actual
conflicts have arisen without being declared? (The Board members have to
sign a conflict of interest declaration, of course.)

   Brian


From nobody Sat Nov 25 12:18:33 2017
Return-Path: <mfidelman@meetinghouse.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 2FD321200C5 for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 12:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qhwIprXxap8C for <ietf@ietfa.amsl.com>; Sat, 25 Nov 2017 12:18:29 -0800 (PST)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8F0126E3A for <ietf@ietf.org>; Sat, 25 Nov 2017 12:18:29 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 069C2CC519 for <ietf@ietf.org>; Sat, 25 Nov 2017 15:18:29 -0500 (EST)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8ey0zhyKu2bt for <ietf@ietf.org>; Sat, 25 Nov 2017 15:18:27 -0500 (EST)
Received: from Miless-MacBook-Pro.local (71-223-239-106.phnx.qwest.net [71.223.239.106]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 1446ECC482 for <ietf@ietf.org>; Sat, 25 Nov 2017 15:18:26 -0500 (EST)
Subject: Re: ISOC chapter and board compositon
To: ietf@ietf.org
References: <9bd4e3f2-b781-16cd-f486-56e491c239f7@ericsson.com> <819fea49-17ec-be90-8baf-cd5107ab288f@ericsson.com> <3BCFF023-5A8D-4DBE-8BA5-1D1B992C528B@sobco.com> <70d63ebd-3f68-69f0-6990-d890b2071f39@meetinghouse.net> <alpine.OSX.2.21.1711241329410.32540@ary.local> <da28822c-ce99-72d9-9ece-f3cf2af97e29@meetinghouse.net> <alpine.OSX.2.21.1711241426130.32594@ary.local> <f0cbf348-13d3-ed0a-636b-9b92c63dcfd6@meetinghouse.net> <alpine.OSX.2.21.1711241507070.32660@ary.local> <d579ce0d-bb31-dcb7-1fb8-2a8757f91c8c@meetinghouse.net> <alpine.OSX.2.01.1711241416210.45333@ole-pro.local> <75416480-404f-61dc-7593-2ab447ce67a0@meetinghouse.net> <dea8fda6-4ce1-7180-2900-92b67f761e9c@gmail.com> <6966AE3A48A46EA095384A10@JcK-HP5.jck.com> <1adf3a95-7dd3-0976-ee9c-2ffcc463693d@meetinghouse.net> <951b51b0-74aa-5b99-d81a-81460c861a1a@gmail.com>
From: Miles Fidelman <mfidelman@meetinghouse.net>
Message-ID: <cf4a875a-0741-1995-65ff-c6ef1c320e2f@meetinghouse.net>
Date: Sat, 25 Nov 2017 13:18:24 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <951b51b0-74aa-5b99-d81a-81460c861a1a@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lBpyPQnx_grz_4G9tgXJuHcSUJE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Nov 2017 20:18:31 -0000

On 11/25/17 12:55 PM, Brian E Carpenter wrote:

> On 26/11/2017 06:26, Miles Fidelman wrote:
> ...
>> Regarding 2:  When votes only go to organizational members, and
>> "Platinum Members," with a weighted vote, include Comcast and
>> NBCUniversal,
> To be clear, the weighted voting applies only to the election of
> the four Board members from the organizational members, i.e. at
> most to one third of the Board. I don't see this as unduly susceptible
> to vested interests.
>
>> one gets a bit leery of ISOCs ability to give unbiased
>> advise on things like Network Neutrality (excuse me, Common Carriage and
>> Anti-Trust, to use regulatory language that has more of a clearly
>> understood history & grounding).  One might also question the influence
>> of groups like ICANN and ARIN, when IETF has a contractual relationship
>> with them and sets standards to be implemented & managed (and enforced?)
>> by them.  It's all just a bit to rife with conflict of interest.
> Exactly why the Board is set up with the checks and balances of having
> three separate constituencies. Do you have any evidence that actual
> conflicts have arisen without being declared? (The Board members have to
> sign a conflict of interest declaration, of course.)
>
>     
No.  But the appearance of one is a concern.  Given the current 
"membership" structure (and membership), it is not at all clear who ISOC 
represents or speaks for when commenting on policy matters. Certainly it 
is not speaking for me, as an individual member, or as a member of the 
"Internet community."  When IEEE-USA, or US-ACM comments on policy, or 
advocate - the entire process is very transparent, as are how members 
sit on policy boards (been there, done that), and form policy 
statements.  Not so, when it comes to ISOC.

Now, personally, I'd be perfectly happy for ISOC to have a sole mission 
of providing an organizational home for IETF, and weighing in only on 
policy issues that specifically relate to IETF's role in Internet 
Governance.  We would still need a governance structure that ensures 
proper stewardship of the IETF.  There would still need to be some 
governance & transparency for a process by which IETF weighs in on 
policy matters - though that kind of worked pretty well when we were 
going through the whole bit about changes to the ICANN contract.

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.  .... Yogi Berra


From nobody Sun Nov 26 05:35:45 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 8E0E3129413; Sun, 26 Nov 2017 05:35:43 -0800 (PST)
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 XKfty3jB8q9j; Sun, 26 Nov 2017 05:35:40 -0800 (PST)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::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 BCD5312941D; Sun, 26 Nov 2017 05:35:40 -0800 (PST)
Received: by mail-qt0-x235.google.com with SMTP id d15so36076547qte.4; Sun, 26 Nov 2017 05:35:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=C8sxT8pNoWLvTgQktMSSvP3nH05aQ+3PEHSQNzUHM+Y=; b=AwBkd8+xOwvr5ejdDKaw0/r+2RKCJgqg1mmUIZcF6THB+8E8iRBAMcn23bJBKv4BEv HXZ9BjeW3sPm5dTByuUeU8LkPWdD+AbIrg8wtc4ojdbV+8L7L1RRH55vc/dxy0mp2lfP wrmWd21z+NpwBgWlV1dO9XFS6NkII4280q2KDJ+SMRL7Y5bJoVC0mh0O4yBEnbZgbdXR GGafMnBb9tT/rV+ED0/BgAfXuwt7isenkXlDr2MQxjmCDj+zpLd8COUffZmnmhOkXTJ9 nl67prCkbVEecw7kHqOarlUSPrgPsXC6FHHfZ6MZf3Z6YBwTEq2xsYBtz2fcUPUcQUJa cF1Q==
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:in-reply-to :references:mime-version; bh=C8sxT8pNoWLvTgQktMSSvP3nH05aQ+3PEHSQNzUHM+Y=; b=jpgOfQCgBsHY8pP3GcJFt5YNpjtWYKTkque/JdAGt33wiNmaxGyssLg3vz4m7lwLIY CX0GhRirtnNYCY5iUjbzF54NEYDlya12ovWU+M5vjOmacXBych7Uz+Mni386LXmf0HB3 UZfa0etPs5Z4obPViiDSplHg+10SmV5r1wrsqXjTCeZ8Tl63TCGrl2KLpa0dCnJm3aWM PQe8Uo0WYe99TejeDwL0GksF7EUKMtN6L4kNh/ACET7eOJy363CX1Pq9z6GXrm+pZ7EN Ur9XURWHP4YjUdqhWXvLWRd+Di1n17p3hozY7lN8vTP6Vi/IjUTMWVXUXDEmn8KUggd3 /ICA==
X-Gm-Message-State: AJaThX6TFpYW9LqR5dYv/JjOQiHDdPfgzlC9EcR+fM2EfK+imMngd4t5 ade8A4ermuPPgaL10vGcfBkfi3vG
X-Google-Smtp-Source: AGs4zMauadXSkw0PK19RVoc2nvGwZKR7cm+SJhG62D20uPIV9S8Q2fyyPkwUL+zirCqR3mpiTEk1Ow==
X-Received: by 10.200.39.122 with SMTP id h55mr53170558qth.56.1511703339318; Sun, 26 Nov 2017 05:35:39 -0800 (PST)
Received: from [172.19.33.45] ([2601:184:4980:a321:c818:7913:7310:7780]) by smtp.gmail.com with ESMTPSA id j30sm18712861qkh.61.2017.11.26.05.35.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Nov 2017 05:35:37 -0800 (PST)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "100attendees@ietf.org" <100attendees@ietf.org>
Subject: Re: CFP: PechaKucha at IETF-100
Date: Sun, 26 Nov 2017 08:35:35 -0500
Message-ID: <26028C9E-6634-4389-B5A7-0E1E7FDCEDE0@gmail.com>
In-Reply-To: <9B50505D-A7E7-40E0-B789-419DA14C6021@gmail.com>
References: <9B50505D-A7E7-40E0-B789-419DA14C6021@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.7r5425)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ypeFVUQA8wXSVU5hU7If4iIcL5c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Nov 2017 13:35:43 -0000

Videos from the Singapore PK now online at http://snaggletooth.akam.ai/

On 6 Nov 2017, at 12:36, Aaron Falk wrote:

> What is a PechaKucha, you ask? A PechaKucha is a lightning-talk 
> presentation format, originating in Japan, where a speaker presents 20 
> image-only slides that are each on the screen for 20 seconds and 
> advance automatically.  With each talk lasting for 6:40, it has the 
> feature of forcing presentations -- good or bad -- to be focused and 
> brief.
>
> This is an unofficial event. Topics are encouraged to be a 
> IETF-related and satirical or controversial in some way, although not 
> mean-spirited.  Anyone can participate in this social event.
>


From nobody Sun Nov 26 12:48:20 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 A455E127735; Sun, 26 Nov 2017 12:48:13 -0800 (PST)
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: ietf@ietf.org, anima@ietf.org, draft-ietf-anima-stable-connectivity.all@ietf.org
Subject: Genart last call review of draft-ietf-anima-stable-connectivity-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151172929363.16112.9800241520992164052@ietfa.amsl.com>
Date: Sun, 26 Nov 2017 12:48:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MAjeC-iZBOnuQ2AFuB7gZYrIO-I>
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, 26 Nov 2017 20:48:14 -0000

Reviewer: Matthew Miller
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

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

Document: draft-ietf-anima-stable-connectivity-07
Reviewer: Matthew A. Miller
Review Date: 2017-11-26
IETF LC End Date: 2017-11-26
IESG Telechat date: N/A

Summary:

This document is ready to be published as informational, but there are
a number of nits that ought be addressed before final publication.

Overall, the document is 

Major issues:  NONE

Minor issues:  NONE

Nits/editorial comments:

* Throughout, there is a mix of the term "data plane" and "data-plane".
  One form should be chosen and the rest corrected to match.

* In Section 1.2. "Data Communications Networks (DCNs)", first
  paragraph; "'th" should be "'s" (or just "s"): "In the late
  1990'th and ..." should be "In the late 1990s and ...".

* In Section 1.2. "Data Communications Networks (DCNs)", first
  paragraph; the word "where" should be "were" in the fragment
  "These where (and still are) ...".

* In Section 1.2. "Data Communications Networks (DCNs)", first
  paragraph; there is a missing "a" between "are" and "separate" in
  the fragment "they are separate network entirely".

* In Section 2.1.1. "Simple Connectivity for Non-ACP capable NMS
  Hosts", first paragraph; there is a mismatch in plurality in the
  third sentence; instead of:
  
  """
  They acts as the default router to those NMS hosts and provide them
  with IPv6 connectivity into the ACP.
  """
  
  it should be:
  
  """
  They act as the default routers to those NMS hosts and provide them
  with IPv6 connectivity into the ACP.
  """

* In Section 2.1.3. "Simultaneous ACP and Data Plane Connectivity",
  last paragraph; the following sentence seems to be missing a word
  or two:

  """
  If the secure ACP was extendable via untrusted routers then it would
  be a lot more verify the secure domain assertion.
  """

* In Section 2.1.4. "IPv4-only NMS Hosts", second paragraph after the
  ordered list; the word "thought" should be "through" in the fragment
  "... be reachable thought the IPv6/IPv4 ...".

* In Section 2.1.5. "Path Selection Policies", fourth paragraph from
  the section's end; there is an extra "of" between "shaping" and "at":
  
  """
  Traffic policing and/or shaping of at the ACP edge in the NOC can be
  used to throttle applications such as software download into the ACP.
  """

* In Section 2.2. "Stable Connectivity for Distributed Network/OAM",
  second paragraph; there is a missing "to" between "start" and
  "provide" in the fragment "... tried to start provide common ...".

* In Section 2.2. "Stable Connectivity for Distributed Network/OAM",
  second paragraph; the word "applicable" should be "applied" in the
  fragment "... how ell it applicable to a ...".

* In Section 3.1. "No IPv4 for ACP", third paragraph; the word "as"
  should be "to" in the fragment "... from a native transport as just
  a service on the edge."

* In Section 3.1. "No IPv4 for ACP", last paragraph; the word "type"
  should be "types" in the fragment "In other type of networks as
  well, ...".

* In Section 3.1. "No IPv4 for ACP", last paragraph; the word "support"
  should be "supported" in the fragment "... family will be support so
  all use...".



From nobody Sun Nov 26 15:01:12 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 3039C12708C; Sun, 26 Nov 2017 15:01:01 -0800 (PST)
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-tcpinc-tcpcrypt.all@ietf.org, tcpinc@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-ietf-tcpinc-tcpcrypt-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151173726115.30946.6601859817056753241@ietfa.amsl.com>
Date: Sun, 26 Nov 2017 15:01:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UhSfE9JpULbzJ5EzOUKEfRwur0Y>
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, 26 Nov 2017 23:01:01 -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.

For more information, please see the FAQ at
<https://wiki.tools.ietf.org/area/gen/wiki/GenArtfaq>.

Document:  review-draft-ietf-tcpinc-tcpcrypt-10
Reviewer:  Dale R. Worley
Review Date:  2017-11-26
IETF LC End Date:  2017-10-19
IESG Telechat date:  2017-11-30

Summary:

    This draft is basically ready for publication, but has nits
    that should be considered before publication.

I'm rather impressed that the authors have gone through three
revisions in little more than a month after LC.

The text prefixed by ">" is extracted from Daniel B Giffin's reply of
21 Oct 2017 to my Gen-Art review of draft-ietf-tcpinc-tcpcrypt-07.

    [in my review of draft-ietf-tcpinc-tcpcrypt-07:]
    6. It might be worth adjusting the rules for how the A and B roles are
    carried forward during session resumption.  Of course, each host
    should compute the resumption identifier that it expects to receive
    based on the role it had in the previous session.  But it's not clear
    to me why a host that used k_ab for encryption (i.e., had the A role)
    in the previous session must also use k_ab for encryption in the
    resumed session, since the two sequences of k_ab/k_ba are generated
    from the different session keys of the two sessions.  If you made the
    choice of k_ab/k_ba be dependent on the A/B roles established by
    TCP-ENO for *this* session, it seems like the specification of the
    protocol would be a bit simpler.

    > I'll explain this design choice under separate cover, when I
    > have a moment ...

I can't find the discussion of this design choice.

    > Yes, underscores are used to mark terms that are being
    > introduced for the first time and defined.

Contra this statement, _..._ is used in two places as an emphatic:

3.2.  Protocol Negotiation

   If a passive opener receives an ENO option including tcpcrypt TEPs it
   supports, it MAY then attach an ENO option to its SYN-ACK segment,
   including _solely_ the TEP it wishes to enable.

3.5.  Session Resumption

   If an active opener sends a resumption suboption with a particular
   TEP and the appropriate half of a resumption identifier and then, in
   the same TCP handshake, receives a resumption suboption with the same
   TEP and an identifier-half that does _not_ match that resumption
   identifier, it MUST ignore that suboption.

--

3.5.  Session Resumption

   Implementations that cache session secrets MUST provide a means for
   applications to control that caching.  In particular, when an
   application requests a new TCP connection, it must be able to specify
   that during the connection no session secrets will be cached and all
   resumption requests will be ignored in favor of fresh key exchange.
   And for an established connection, an application must be able to
   cause any cache state that was used in or resulted from establishing
   the connection to be flushed.  A companion document
   [I-D.ietf-tcpinc-api] describes recommended interfaces for this
   purpose.

The phrase "all resumption requests will be ignored in favor of fresh
key exchange" doesn't seem to carry quite the right meaning to me,
although what it must mean in this context is clear.  That phrase
seems to have some implication that it operates when a fresh key
exchange is provided along with a resumption request as an
alternative... which is implicitly what the situation is, but not
explicitly.  I would prefer "all resumption requests will be ignored
and a fresh key exchange will be required".

3.6.  Data Encryption and Authentication

   ...
   as above, and provides these and the ciphertext value to the the AEAD
   ...

s/the the/the/

    > I've gone through and used something like "negotiated TEP"
    > in a couple places where the document said that a parameter
    > depended on the "negotiated key-agreement scheme", and also
    > added various phrases to make clear that the TEP dictates
    > all the parameters.

Note that the current sections 4.3 and 5 show that the *lengths* are
determined by TEP, but the *constants* are fixed by tcpcrypt itself.

3.3.  Key exchange

   o  "PK_A", "PK_B": ephemeral public keys for hosts A and B,
      respectively.

    [in my review of draft-ietf-tcpinc-tcpcrypt-07:]
    The use of "PK" for a public key seems to be poorly mnemonic, as it is
    also the acronym of "private key".  There ought to be standard (and
    distinct!) abbreviations for these phrases, but I can't find any...

    > Yeah ... at least in this document we don't name private
    > keys, as they are never transmitted.

How about "Pub_A" and "Pub_B"?  (This suggests "Prv_A" and "Prv_B"
(which wouldn't be used in this document.))

[END]



From nobody Sun Nov 26 23:30:34 2017
Return-Path: <jiangsheng@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 0BA8E127B31; Sun, 26 Nov 2017 23:30:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sheng Jiang <jiangsheng@huawei.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-stir-certificates.all@ietf.org, stir@ietf.org, ietf@ietf.org, jiangsheng@huawei.com
Subject: Opsdir last call review of draft-ietf-stir-certificates-15
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151176783194.30763.7883112843929238883@ietfa.amsl.com>
Date: Sun, 26 Nov 2017 23:30:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8MQ2naM2RVgw8TKYunBo4_ejxCo>
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, 27 Nov 2017 07:30:32 -0000

Reviewer: Sheng Jiang
Review result: Has Nits

Hi, OPS-DIR, Authors,

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.

This standard stack document describes the use of certificates in establishing
authority over telephone numbers, as a component of a broader architecture for
managing telephone numbers as identities in protocols like SIP. This document
is well written.  It is ready with minor nits.

Major issue: no.

Nits issue:

RFC 8017, RFC 8224 and RFC 8225 are NOT the registered downref.  They are
normative reference to Informational RFCs.

Regards,

Sheng



From nobody Mon Nov 27 06:09:27 2017
Return-Path: <adam.w.montville@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 22B52128B8D; Mon, 27 Nov 2017 06:09:14 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Montville <adam.w.montville@gmail.com>
To: <secdir@ietf.org>
Cc: ipsec@ietf.org, ietf@ietf.org, draft-ietf-ipsecme-eddsa.all@ietf.org
Subject: Secdir last call review of draft-ietf-ipsecme-eddsa-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151179175411.30910.13010385715015417131@ietfa.amsl.com>
Date: Mon, 27 Nov 2017 06:09:14 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PwovCmA7BBWTc98dVzvzksCNnPY>
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, 27 Nov 2017 14:09:14 -0000

Reviewer: Adam Montville
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.

This document is ready.

A very straightforward, short document defining a new value in
SIGNATURE_HASH_ALGORITHMS notification of IKE, so that non-hashing signature
methods (specifically the Edwards-curve digital signature algorithm) can be
used.

One nit: s/or/of/ in last sentence of second introduction paragraph, so that it
reads, "See section 8.5 of RFC 8032...".



From nobody Mon Nov 27 06:29:59 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 E87C21242EA for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 06:29:56 -0800 (PST)
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 KE7faHnntCWW for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 06:29:55 -0800 (PST)
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 15ADF1200FC for <ietf@ietf.org>; Mon, 27 Nov 2017 06:29:55 -0800 (PST)
Received: from [192.168.43.77] (unknown [88.131.14.170]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 2BAE11B00A9A; Mon, 27 Nov 2017 14:29:54 +0000 (GMT)
Message-ID: <5A1C2160.3070601@erg.abdn.ac.uk>
Date: Mon, 27 Nov 2017 15:29:52 +0100
From: G Fairhurst <gorry@erg.abdn.ac.uk>
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 Discussion <ietf@ietf.org>
CC: "MORTON, ALFRED C (AL)" <acmorton@att.com>,  Kathleen.Moriarty.ietf@gmail.com, gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: Comments on draft-mm-wg-effect-encrypt rev 12
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VKsDa-hkmTv0EH-vREzYvI_KrMs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 14:29:57 -0000

Thank you for revising this draft I have read in detail several previous 
versions of this ID. I thought thart the much earlier versions were more 
annecdotal, but in the latest version the writing style if much more 
considered and probably better suits the needs of the IETF in 
documenting this space. I believe the current version is nearly ready to 
publish.

Specific comments (one major):

Section 1.2 (para 5)
- space needed before [RFC3550].
- /the/ needed before RTP/RTCP.

Section 1.2 (final para)
- I agree with what is written, but equally I would agree with the 
converse - and I think it is worth considering also stating that 
encryption has benefit to some application providers have noted benefits 
in avoiding out-dated in-network enhancement.

Section 2.1.3 (para 1)
-/This technique is sometimes used with clear text or encrypted sessions/
At least to me, I didn't really understand that sentence and what it was 
trying to say.


Section 3.2.1 (bullet 2)
- /causes of excess response time/
Should this be excessive?

Section 3.2.1 (final para)
- /Until application logging is sufficient ... will remain a gap/
I'm not quite sure what this intended to say: do you think loigs will 
provide equivalent function eventually? or is it better to say at 
present they do not provide that equivalent function?

Section 3.3.2.1
- Expand Data at Rest in the title?

Section 3.3.3.1
- There is a single sentence para at the start, that sort of intro 
sentence does not seem to exist in other subsections of the document?

Section 6.2
- /Soltuions/ spelling? (there are other spelling mistakes that would be 
caught by a spell checker).

Section 7.2 (bullet c).
- Here I have onetechnical comment;

I am really not sure what the implied issue is with DSCP-marking. I 
suspect that the text may be indicating that a network node can not use 
a Multi-Field (MF) classifier to assert a DSCP for traffic that is 
classified into a flow group with specific QoS properties... but the 
current text seems misleading. Because actually if the traffic *IS* 
DSCP-marked, and the network honours the DSCPs being used, then 
DSCP-based QoS *can* be used with encypted traffic.

And I think it would be super good to say this, because I recall old 
IPsec "guidance" that tried to assert traffic should not reveal a DSCP. 
This is of course a security/performance trade-off.

Section 7.3 (bullet 2).
- may be worth noting that QCI is a sub-IP property, just to avoid 
potential misunderstandings.

Best wishes,

Gorry




From nobody Mon Nov 27 10:52:05 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 EC24D1292CE; Mon, 27 Nov 2017 10:52:03 -0800 (PST)
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 8kDOm-KRJRbc; Mon, 27 Nov 2017 10:52:02 -0800 (PST)
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 166C71270A3; Mon, 27 Nov 2017 10:51:59 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id v186so36981622wma.2; Mon, 27 Nov 2017 10:51:59 -0800 (PST)
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=cH/zE46AO3nlnKLOl73KViBYRVJ/HvNksL6Sc05yNX4=; b=OUnzZZoZcZuBdXprcM8Q/rqpVUA1/VW5fsT50kDwiCukZgGyoHp3LGAf/cDZ7VS+r1 KbkVSgEqC2ArU4mJC1WtkSB+s8vRbgW0IgiorOHEdL37MC3KgT5G617f8M0pGsp/mifS PxwomtjuTHBgSPLHth91g7Czu9bRdf3VIVo2+DwItXAJRcLJ912h7IMbxqVGNK8dmouw Rlr0aHKGQdOVjnnGdy8YGv3aFCBi01x3/kE5qc46Kn1Yhgvt3L9cBXikCca/H/51G8wF s0LRoq8/d5cZ3E16AHi+uBsi1wctuQ0xcRUE/eQp97VgkJYV0PxRozSVEWYbToCxt6uo klOg==
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=cH/zE46AO3nlnKLOl73KViBYRVJ/HvNksL6Sc05yNX4=; b=sXBDYa/UBrlbR5jEjeWhpmaep2VMbpZy7Vd+Quy886fMAbEiCkrwj06F+PSu32We1Z AI4mP9DsgOOpJmCLiKZbaxENn+yHC+y1pX0QkR5gdidJCxDJRiP9w2qVe2lHMQCR497g k8JKcgmLbTJqJ5GnP0/8vsHTy/L++kuwMVzCSUOqWMIPI159AB9HCvqSOMCuvNeUmPjz rDOawhdfWROwRO/sGum3mVFAt7VAImS+GY4EguZxre86eRE3ntoxeYfCcDhutqpmBVU9 /jNibaL74Z2Fij05XO31No+hiMXvVmh1OO9sVX0reQDZq/xZ14V63pdca7q40iSzb8S9 YnYQ==
X-Gm-Message-State: AJaThX5HdSNaBcJJK36QtU46PofXbWOEWmH+/GTaR2vY6wGrSfOCAze5 gFS3rkrRtRBvno89vEb4Ijg=
X-Google-Smtp-Source: AGs4zMairR2sfNUYRGiwRdZC8XpTXzr30A0qTFwp5i3M+IJSUpwJI2H0MctvCCuS8Fjoep4YSTOj1w==
X-Received: by 10.28.138.12 with SMTP id m12mr19458997wmd.134.1511808717614; Mon, 27 Nov 2017 10:51:57 -0800 (PST)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id i55sm9385454wra.60.2017.11.27.10.51.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Nov 2017 10:51:56 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Secdir last call review of draft-ietf-ipsecme-eddsa-04
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <151179175411.30910.13010385715015417131@ietfa.amsl.com>
Date: Mon, 27 Nov 2017 20:51:54 +0200
Cc: secdir <secdir@ietf.org>, ipsec@ietf.org, ietf@ietf.org, draft-ietf-ipsecme-eddsa.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <23E34FAC-BF15-4523-91CE-88E3B2A7AA46@gmail.com>
References: <151179175411.30910.13010385715015417131@ietfa.amsl.com>
To: Adam Montville <adam.w.montville@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mmucmxOcdn_ZW9pNmBncYpbqevg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 18:52:04 -0000

> On 27 Nov 2017, at 16:09, Adam Montville <adam.w.montville@gmail.com> =
wrote:
>=20
> Reviewer: Adam Montville
> Review result: Ready
>=20
> 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.
>=20
> This document is ready.
>=20
> A very straightforward, short document defining a new value in
> SIGNATURE_HASH_ALGORITHMS notification of IKE, so that non-hashing =
signature
> methods (specifically the Edwards-curve digital signature algorithm) =
can be
> used.

Thanks, Adam.

>=20
> One nit: s/or/of/ in last sentence of second introduction paragraph, =
so that it
> reads, "See section 8.5 of RFC 8032=E2=80=A6=E2=80=9D

Unless something else comes up, I=E2=80=99ll leave this to AUTH48 =
(although the RFC Editor are likely to find it and fix it anyway).

Yoav=


From nobody Mon Nov 27 11:20:56 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 28EC5126C3D for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 11:20:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] 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 DFeSN86mCJ3T for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 11:20:54 -0800 (PST)
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 776DB126BFD for <ietf@ietf.org>; Mon, 27 Nov 2017 11:20:51 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E6613F15-B7AC-40E0-BA9F-814435B1931F"
Subject: Highlights from IETF 100
Message-Id: <BFC42244-AC47-4405-9BE6-12663DC65F21@ietf.org>
Date: Mon, 27 Nov 2017 14:20:50 -0500
To: IETF Discussion <ietf@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/AO1_OV34RNsk5KgEj3Tds1r2_ck>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 19:20:55 -0000

--Apple-Mail=_E6613F15-B7AC-40E0-BA9F-814435B1931F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

New post is up on the blog: =
https://www.ietf.org/blog/2017/11/highlights-from-ietf-100/ =
<https://www.ietf.org/blog/2017/11/highlights-from-ietf-100/>

Cheers,
Alissa=

--Apple-Mail=_E6613F15-B7AC-40E0-BA9F-814435B1931F
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">New post is up on the blog:&nbsp;<a href="https://www.ietf.org/blog/2017/11/highlights-from-ietf-100/" class="">https://www.ietf.org/blog/2017/11/highlights-from-ietf-100/</a><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Alissa</div></body></html>
--Apple-Mail=_E6613F15-B7AC-40E0-BA9F-814435B1931F--


From nobody Mon Nov 27 12:47:21 2017
Return-Path: <kwatsen@juniper.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 29BFA1293F4 for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 12:47:19 -0800 (PST)
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=juniper.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAWcK_BvT70a for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 12:47:17 -0800 (PST)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CE74126C0F for <ietf@ietf.org>; Mon, 27 Nov 2017 12:47:17 -0800 (PST)
Received: from pps.filterd (m0108161.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vARKiHrK017309 for <ietf@ietf.org>; Mon, 27 Nov 2017 12:47:15 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : subject : date : message-id : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=Q243fcwUkBsluTQMliw8djoH6rOaqB4bpCrNnBGFakY=; b=rPCqUtx1w2AkSqGu8hDHOMwAbO16Fq/ejJ8qLANa+lZdcG/GYOa/E4o2NLRY2tFIFh7b fW9H0i4+T1ZF0YSIqPrjXN7fpel+YrDnJR/KNbcyIL5C2PfXLO2uWF5XYYSTrvWRYuAn w84dA5Z87UOk4gSbt95lia1GnAYmS9cE6KpV5mpPJVFa7Ssj7+pqA5wJHCx6IhRvvnkP x8P+hvhhlMfsHO/V42zvlX0OozU7MTNCM+yBFm7s1xGcxJ9hJS6LGDIbrn2FQd56WdBx DwkZcdB2MyrTFZ6esmT6pJ44xUUTFUiY9G5ZAcfY+AzA9n23u7xwVR5pamLpqLqcX7Ul 2g== 
Received: from nam03-co1-obe.outbound.protection.outlook.com (mail-co1nam03lp0023.outbound.protection.outlook.com [216.32.181.23]) by mx0b-00273201.pphosted.com with ESMTP id 2egp8hghet-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 27 Nov 2017 12:47:14 -0800
Received: from BLUPR05MB275.namprd05.prod.outlook.com (10.141.22.149) by BLUPR05MB276.namprd05.prod.outlook.com (10.141.22.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.282.3; Mon, 27 Nov 2017 20:47:09 +0000
Received: from BLUPR05MB275.namprd05.prod.outlook.com ([10.141.22.149]) by BLUPR05MB275.namprd05.prod.outlook.com ([10.141.22.149]) with mapi id 15.20.0282.002; Mon, 27 Nov 2017 20:47:09 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: travelling home just before thanksgiving is hard
Thread-Topic: travelling home just before thanksgiving is hard
Thread-Index: AQHTZ8DkAegC96W7Jk63Zyyo+2c+1A==
Date: Mon, 27 Nov 2017 20:47:09 +0000
Message-ID: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
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-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BLUPR05MB276; 6:dyIpVtSf+zMqVfqMLVIul1XMdG+u5BiWMsq46Ghnto7//K5mzSIaQUp2llgUVCoxy4peHV5VqW87gd2qsE65J+kWg3GeNFVt+b4T5gmFiDVF7ain/G1i7sqFFlyTH6h7ikatQ4Eyr3Hq7+QgPwRqTgJjFtwkRX42Ax0S+idpXTbn/QcDSXfG1fJ4KHIPG5HDHdIw+u68ERF0pMzy2pAqO4KIDDk31nGKU524gWXAcxsqfGDLbk3/2jkWW0CmbuKuxf0Azx0K68GCd6XqFcubg/ckLsSGlXdGhgsk/liqLXh9KBpWeGYORJK98Lf3balGNAmqN9un9BKHcFtJcQzZLnseS5KlRl4vIg023huCtPA=; 5:6R6GEi4WA/dLCQS9gKMIb9P+PIhFX916dZQhBnC/kYrhkp0UoE4WF+QlxT7++CGCWrwK4i6w4K9YqfG5eMdyBcl7lumEbuBkpnwNpwnL/2tKBLTK7Gy3AMucPVLUIto4K2VTyxpWDtLs9kP629QjE/UW6MK2flfF3jkuLfv+tjM=; 24:/6ePSxi4z19MaiJtiia6ptVhP4RJCxokcYvbKg6rL0aaSYJytk9uLf2ORd9zEiNG8HPyqmA040uC0q8eaDPTZEgZXOx96g9ZrDi5C7nUFOI=; 7:OE/jT0km/gqIjpSjU7lXHVEoKK3eIdGl/Zgmiz/7aJFOhJh7sPdNdGmxwP6bXc5yojLdTVUm9qKgAkv7UwsN37UyQpn1TQUBlSWl0iMU4NLHbfwz8inNu7OCHWSpaEh+nenH/7eACCS1W2dzetdw0l+B+VA9GI29HvFo8/4/6EqdNCsCVkz0xHwCPCPZvXfjSE1QsgJRNDrK9HyeT+tiQ1J7fhigCfvVQw5YQiDxXe4vflYl586/Ols/1tkREuJx
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: cef36fb4-443b-4858-b802-08d535d80721
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5600026)(4604075)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603258); SRVR:BLUPR05MB276; 
x-ms-traffictypediagnostic: BLUPR05MB276:
x-microsoft-antispam-prvs: <BLUPR05MB276709EE8FAC4CCF3A46402A5250@BLUPR05MB276.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(8121501046)(5005006)(3231022)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123564025)(20161123560025)(20161123555025)(6072148)(201708071742011); SRVR:BLUPR05MB276; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BLUPR05MB276; 
x-forefront-prvs: 0504F29D72
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(366004)(39860400002)(376002)(346002)(199003)(189002)(8676002)(102836003)(3846002)(6116002)(305945005)(53936002)(25786009)(2906002)(2351001)(106356001)(68736007)(5660300001)(105586002)(50986999)(54356999)(2501003)(83716003)(316002)(36756003)(58126008)(7736002)(478600001)(77096006)(6486002)(101416001)(99286004)(6436002)(5640700003)(6506006)(6512007)(6916009)(3280700002)(14454004)(86362001)(81166006)(1730700003)(81156014)(66066001)(83506002)(82746002)(33656002)(97736004)(3660700001)(189998001)(8936002)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB276; H:BLUPR05MB275.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: kYDrO/REzCKMbpxubrSRU/xa2Cdnw77JP7JL0uysaxDbBsI4ncdqe5LNEbJgUMhriRBzE05Ys/gyVNTKyi3qMg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <D0E21BE3A26C5D4C97941373884925C6@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: cef36fb4-443b-4858-b802-08d535d80721
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Nov 2017 20:47:09.0557 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB276
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-11-27_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=51 spamscore=0 clxscore=1011 lowpriorityscore=51 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1711270277
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z7g54sSUIGYTkkOQBfqlQIHnD2I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 20:47:19 -0000

DQpJIGhhZCBhbiBhd2Z1bCBleHBlcmllbmNlIHRyYXZlbGxpbmcgaG9tZSBmcm9tIFNpbmdhcG9y
ZS4gIFdoYXQgd2FzIHN1cHBvc2VkIHRvIGJlIDIyLWhvdXJzIG9mIHRyYXZlbCBiZWNhbWUgNDAt
aG91cnMuICBNdWNoIG9mIHRoaXMgd2FzIGR1ZSB0byBteSBVUy1iYXNlZCBjb25uZWN0aW5nIGFp
cnBvcnQgYmVpbmcgZXhjZXB0aW9uYWxseSBidXN5LCByZWxhdGVkIHRvIHRoaXMgbW9zdC10cmF2
ZWxsZWQgaG9saWRheSBvZiB0aGUgeWVhciwgY2F1c2luZyBtZSB0byBtaXNzIG15IGdhdGUgYW5k
IG5vdCBiZSBhYmxlIHRvIGdldCBvbnRvIGVpdGhlciBvZiB0d28gc3RhbmRieXMuDQoNCkV2ZW4g
aWYgdGhlIHRyYXZlbC1jb25nZXN0aW9uIHdlcmUgbm90IGFuIGlzc3VlLCB0aGVyZSB0aGUgc2Vj
b25kYXJ5IGlzc3VlIG9mIGNvbWluZyBob21lIGludG8gYW4gYWxyZWFkeSBzaG9ydCB3ZWVrLiAg
TW9zdCBVUyBjb21wYW5pZXMgZ2l2ZSBUaHVyc2RheSBhbmQgRnJpZGF5IG9mZiBhbmQgbWFueSwg
aW5jbHVkaW5nIG15c2VsZiwgdGFrZSBXZWRuZXNkYXkgb2ZmIGFzIHdlbGwgKHRvIHRyYXZlbCB0
byBvdXIgVGhhbmtzZ2l2aW5nIGRlc3RpbmF0aW9ucykuICBUaGlzIGxlYWRzIHRoZSBzb21ld2hh
dCBmcmFudGljIHNpdHVhdGlvbiBvZiB0cnlpbmcgdG8gY2F0Y2gtdXAgb24gZW1haWwgZnJvbSB0
aGUgd2VlayBiZWZvcmUgd2hpbGUgY2xlYXJpbmcgdGhlIHdheSBmb3IgdGhlIHdlZWsgYWhlYWQu
DQoNCkkgdW5kZXJzdGFuZCB0aGF0IHRoaXMgaXMganVzdCBhbiBBbWVyaWNhbiBob2xpZGF5IGFu
ZCB0aGF0IGxlc3MgdGhhbiBoYWxmIG9mIHRoZSBJRVRGIGFyZSBBbWVyaWNhbnMgYnV0LCBpZiB0
aGVyZSBpcyBhbnkgZGlzY3JldGlvbiBpbiB0aGUgbWF0dGVyIGZvciBmdXR1cmUgbWVldGluZ3Ms
IEkgd291bGQgYmUgZXhjZXB0aW9uYWxseSBoYXBweSBpZiB0aGUgSUVURiBtYWRlIGFuIGVmZm9y
dCB0byBob2xkIHRoZSAzcmQtbWVldGluZyBvZiB0aGUgeWVhciBhIHdlZWsgZWFybGllci4NCg0K
VGhhbmtzLA0KS2VudA0KDQoNCg==


From nobody Mon Nov 27 12:51:51 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 8EF36126C0F for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 12:51:49 -0800 (PST)
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=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 g3riSluFom5o for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 12:51:48 -0800 (PST)
Received: from resqmta-po-04v.sys.comcast.net (resqmta-po-04v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:163]) (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 EF4E2120724 for <ietf@ietf.org>; Mon, 27 Nov 2017 12:51:47 -0800 (PST)
Received: from resomta-po-01v.sys.comcast.net ([96.114.154.225]) by resqmta-po-04v.sys.comcast.net with ESMTP id JQNQebMIIadjWJQNXez25O; Mon, 27 Nov 2017 20:51:47 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1511815907; bh=Y2+A02/NXQjyY3I9mqBLGxW125aUl2y1ognNs/x0ys0=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=UtSpqKzXbaZxkfznF5yQCCjOgmfwIcTdyMYcZB1huqEDUkbfC69RCRqmQbszRQwS2 okE3Hcwdh8reK+S5TcHxoDCbCt360aQYqTeI05ZxREjvJwD1nWSA2Xv/iguQMoDLOE zDJ0ndxiJQZnGje5amJK370EnFuUK8kDSvXh5ePycHiC8TKaDIRBcsjO5Ds+ZATkOx LfDDi6qckBoB0N+fJPLrkZ+suMLL9blB3ALUy7GrfmoYk/Jpn8qyghedjn/eJp448K gMdNuHgYmTY/T9k8xtb4CXzsQ0mzUDPOFWTtWiiq+BVm9ZALqBW44mlIGY6NdBpkkz 6PSMb+9bcOMJg==
Received: from [IPv6:2601:152:4400:720f::1005] ([IPv6:2601:152:4400:720f::1005]) by resomta-po-01v.sys.comcast.net with SMTP id JQNWe7T9RDnByJQNXebS8q; Mon, 27 Nov 2017 20:51:47 +0000
Subject: Re: travelling home just before thanksgiving is hard
To: ietf@ietf.org
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net>
Date: Mon, 27 Nov 2017 15:51:46 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
Content-Type: multipart/alternative; boundary="------------F729C16C5BE827654C6F598A"
Content-Language: en-US
X-CMAE-Envelope: MS4wfPkZt5N6vQiKlMb64Q2DBYgPqo0lAWH4VDemd7aj3tDOGnKmjerf8djvp/ogVSmriG2Ba+sb0oEpO+hKKPKOhsWg3im6gz40aHVXQXwNoksRqwqxv6ND PXS6NlvwHaYIFN42W3C/gNaq2JIhlCqvRFgXgOIO3nWLRi/mLenuYv11
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8um51aq-BuzaDZwvy-zE3a4Laoo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 20:51:49 -0000

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

On 11/27/2017 3:47 PM, Kent Watsen wrote:
> I had an awful experience travelling home from Singapore.  What was supposed to be 22-hours of travel became 40-hours.  Much of this was due to my US-based connecting airport being exceptionally busy, related to this most-travelled holiday of the year, causing me to miss my gate and not be able to get onto either of two standbys.
>
> Even if the travel-congestion were not an issue, there the secondary issue of coming home into an already short week.  Most US companies give Thursday and Friday off and many, including myself, take Wednesday off as well (to travel to our Thanksgiving destinations).  This leads the somewhat frantic situation of trying to catch-up on email from the week before while clearing the way for the week ahead.
>
> I understand that this is just an American holiday and that less than half of the IETF are Americans but, if there is any discretion in the matter for future meetings, I would be exceptionally happy if the IETF made an effort to hold the 3rd-meeting of the year a week earlier.
>
> Thanks,
> Kent
>
>
https://www.ietf.org/meeting/upcoming.html

Next year is early, but the following two years (at least) have the 
current property of being the week before US Thanksgiving. The 4th and 
5th years are earlier in the month.

Part of the problem is that we set the days way in advance to avoid 
conflicts with other organizations in the related space. It's actually 
somewhat easier to change locales than it is to change dates - even 
years in advance.


Mike


        November 2018 - IETF 103

November 3-9, 2018
Host: Please contact iad@ietf.org <mailto:iad@ietf.org> for hosting 
opportunities.
Location: TBD


        November 2019 - IETF 106

November 16-22, 2019
Host: Please contact iad@ietf.org <mailto:iad@ietf.org> for hosting 
opportunities.
Location: TBD


        November 2020 - IETF 109

November 14-20, 2020
Host: TBD
Location: TBD


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 11/27/2017 3:47 PM, Kent Watsen
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net">
      <pre wrap="">
I had an awful experience travelling home from Singapore.  What was supposed to be 22-hours of travel became 40-hours.  Much of this was due to my US-based connecting airport being exceptionally busy, related to this most-travelled holiday of the year, causing me to miss my gate and not be able to get onto either of two standbys.

Even if the travel-congestion were not an issue, there the secondary issue of coming home into an already short week.  Most US companies give Thursday and Friday off and many, including myself, take Wednesday off as well (to travel to our Thanksgiving destinations).  This leads the somewhat frantic situation of trying to catch-up on email from the week before while clearing the way for the week ahead.

I understand that this is just an American holiday and that less than half of the IETF are Americans but, if there is any discretion in the matter for future meetings, I would be exceptionally happy if the IETF made an effort to hold the 3rd-meeting of the year a week earlier.

Thanks,
Kent


</pre>
    </blockquote>
    <p><a class="moz-txt-link-freetext" href="https://www.ietf.org/meeting/upcoming.html">https://www.ietf.org/meeting/upcoming.html</a></p>
    <p>Next year is early, but the following two years (at least) have
      the current property of being the week before US Thanksgiving. 
      The 4th and 5th years are earlier in the month.</p>
    <p>Part of the problem is that we set the days way in advance to
      avoid conflicts with other organizations in the related space. 
      It's actually somewhat easier to change locales than it is to
      change dates - even years in advance.</p>
    <p><br>
    </p>
    <p>Mike</p>
    <p><br>
    </p>
    <h4>November 2018 - IETF 103</h4>
    <p>November 3-9, 2018<br>
      Host: Please contact <a href="mailto:iad@ietf.org">iad@ietf.org</a>
      for hosting opportunities.<br>
      Location: TBD</p>
    <h4>November 2019 - IETF 106</h4>
    <p>November 16-22, 2019<br>
      Host: Please contact <a href="mailto:iad@ietf.org">iad@ietf.org</a>
      for hosting opportunities.<br>
      Location: TBD</p>
    <h4>November 2020 - IETF 109</h4>
    <p>November 14-20, 2020<br>
      Host: TBD<br>
      Location: TBD</p>
  </body>
</html>

--------------F729C16C5BE827654C6F598A--


From nobody Mon Nov 27 13:25:15 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 42B0C1293FD for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 13:25:14 -0800 (PST)
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 Co7S_LOW1meH for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 13:25:13 -0800 (PST)
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 EA0CB124D6C for <ietf@ietf.org>; Mon, 27 Nov 2017 13:25:12 -0800 (PST)
Received: by mail-pg0-x22e.google.com with SMTP id m4so9347241pgc.4 for <ietf@ietf.org>; Mon, 27 Nov 2017 13:25:12 -0800 (PST)
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-language:content-transfer-encoding; bh=WeC5bjYM8cNQo+BoHfLPtnJuxIJCW6v24ess7uGHE9U=; b=mu38qzTgYW7ttiFOH6Sh/hwbEBs218r0GMTSoZck2KbLcoWg1MS0nD2hlIfnhRXajP mpT92ikQvGNMZVi4ec29KRpS3Y0qrks1GE5nGoJdIgCIrh8XzWzTn69L1tFwzhqG//1+ CJpDgjcqDoL4ZCo0W0OdxslizceFXGwp41XXyeO2+6tQvUn0SwpgW2CHUlS1Gg9lASgP 3pCH6m+0lsRwvuUBEC7+bcq/MYa7IocjiSX6FSp2MV38Wvw9M7umXTm7WevRUvnUHvg4 BCKaW2PLf4Rs649HzOpLgt0/ud/h/t3oZMRTrF8Yy6atfrUg77HgbM7DXEqnwVS2YrlY n0Hw==
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-language:content-transfer-encoding; bh=WeC5bjYM8cNQo+BoHfLPtnJuxIJCW6v24ess7uGHE9U=; b=aflESiDcj5Rg6G/OS2sHmR/qEuXmEwDz7AFPxD5+MDnyxx3d6u/FfXG1tCYqPJFAuj ERIUQ+8RAqAguIWsFxMeyw4zDe/JuJpmVKH4lcgxQLvodfoIPm9zPiaXd0miX3v8rILb BDJ/osLdcToghajDYEF0/yLoXAUT6980oP7jZom+IT2QE84gJ4jblhe49l3Po4a7mizz X+XRZKPNY1vZYN7bvoc69kQ6S0Cy4Pl6wDu5e5KNX+WiEOkeZ8UtXNHH6bMsd10j4zYQ 5ZEgoLZb2xJMGkFptzJkpv8X188422BpSt8V24DuNl4M0Ss//siPVDDfLeMZp3TppXqS 9qnw==
X-Gm-Message-State: AJaThX4eC3MiSTwRcvkULFgOMXraYnBOi8H1oJjH1XHIQSDxFbFYEF08 E4nTocTF9EFTqP0jzmoXqWQNdQ==
X-Google-Smtp-Source: AGs4zMaMGNAmpVMGfbEIygxL/u8PBNsOzAzqTTnP7SEcKg+jpFvWGMKcYLAUW1RkpA+gg/UfNRuQjQ==
X-Received: by 10.101.98.2 with SMTP id d2mr15558893pgv.287.1511817912178; Mon, 27 Nov 2017 13:25:12 -0800 (PST)
Received: from [130.216.38.112] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.112]) by smtp.gmail.com with ESMTPSA id 84sm39038037pfy.59.2017.11.27.13.25.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Nov 2017 13:25:10 -0800 (PST)
Subject: Re: travelling home just before thanksgiving is hard
To: Michael StJohns <mstjohns@comcast.net>, ietf@ietf.org
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com>
Date: Tue, 28 Nov 2017 10:25:09 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x6veuNHzWng4h8ysNBI7RLckZ0E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 21:25:14 -0000

On 28/11/2017 09:51, Michael StJohns wrote:
> On 11/27/2017 3:47 PM, Kent Watsen wrote:
>> I had an awful experience travelling home from Singapore.  What was supposed to be 22-hours of travel became 40-hours.  Much of this was due to my US-based connecting airport being exceptionally busy, related to this most-travelled holiday of the year, causing me to miss my gate and not be able to get onto either of two standbys.

Sorry to hear that. I have to say that I always try to get long
layovers to reduce that risk; a couple of wasted hours being bored
in an airport is a price worth paying.

> https://www.ietf.org/meeting/upcoming.html
> 
> Next year is early, but the following two years (at least) have the 
> current property of being the week before US Thanksgiving. The 4th and 
> 5th years are earlier in the month.
> 
> Part of the problem is that we set the days way in advance to avoid 
> conflicts with other organizations in the related space. It's actually 
> somewhat easier to change locales than it is to change dates - even 
> years in advance.

That, and one side-effect of the week before Thanksgiving for non-US
residents is having a very quiet week after the meeting for catch-up,
with email traffic being much less than normal.

Also, if we have to steer clear of Thanksgiving, in fairness we'd have
to steer clear of Chinese New Year and other such events.

There is no good solution to this.

    Brian


From nobody Mon Nov 27 13:38:22 2017
Return-Path: <rifaat.ietf@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 6E6A712702E; Mon, 27 Nov 2017 13:38:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
To: <secdir@ietf.org>
Cc: ietf@ietf.org, draft-wu-l3sm-rfc8049bis.all@ietf.org
Subject: Secdir telechat review of draft-wu-l3sm-rfc8049bis-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151181870041.30959.17144962798564184590@ietfa.amsl.com>
Date: Mon, 27 Nov 2017 13:38:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZttLdi7xhH04COL9QRbmvvlZWQQ>
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, 27 Nov 2017 21:38:20 -0000

Reviewer: Rifaat Shekh-Yusef
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.

The document defines a YANG data model that defines service configuration
elements that can be used in communication protocols between customers
and network operators. Those elements can also be used as input to
automated control and configuration applications.

The authors addressed my comments on version -05 of the document.
I have not further comments on this version of the draft.

Regards.
 Rifaat



From nobody Mon Nov 27 15:12:42 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 521FB127419 for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 15:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYIlDvcuhrqd for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 15:12:38 -0800 (PST)
Received: from mr11p00im-asmtp004.me.com (mr11p00im-asmtp004.me.com [17.110.69.135]) (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 6FC3412704B for <ietf@ietf.org>; Mon, 27 Nov 2017 15:12:38 -0800 (PST)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp004.me.com by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0P0300500MM90D00@mr11p00im-asmtp004.me.com> for ietf@ietf.org; Mon, 27 Nov 2017 23:12:34 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1511824354; bh=Xb/U9M/bIPob8EtCwKzscACe5Mh9aovtfmH62ngc1FE=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=orujtq804IAr/lsSHIrRkiHv3xc5yFVUDpCbSp8+uGcN1x2QJUquqDUBKW0LpCk1T WZr27P9T2Ewy0Pxayu971tKc6WFMAXQP+kUxT0Uelf8HaSVKly442LQu8OAnwaUqVt wbDOjGb0agSrgW7NhPjtWBjiF+Ac4Zw8kYc0FXNIrmi0cRjOO9804WNIpe8V/cvnvD z0bhBGsyojbbRz1ntGNquFP9I+JRYlcmgz5LP45NdEfWTSUsvB7OPyTorlya2auGj6 MkzmEFOp1UCkeqzpH3h+oyvPFVqaI1kLoFzdTKD2llWWN6QiyO19VdfkDFlC9sLZlK x6IKsrU0kyQ8A==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0P0300PWPN4V1Q20@mr11p00im-asmtp004.me.com>; Mon, 27 Nov 2017 23:12:32 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-27_12:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711270307
Date: Mon, 27 Nov 2017 15:12:31 -0800 (PST)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: Kent Watsen <kwatsen@juniper.net>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: travelling home just before thanksgiving is hard
In-reply-to: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
Message-id: <alpine.OSX.2.01.1711271506380.91054@ole-pro.local>
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tTHs6rKd9Ow0AndC0fFE4uw3tmE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 23:12:39 -0000

On Mon, 27 Nov 2017, Kent Watsen wrote:
> 
> I had an awful experience travelling home from Singapore.  What was 
> supposed to be 22-hours of travel became 40-hours.  Much of this was 
> due to my US-based connecting airport being exceptionally busy, 
> related to this most-travelled holiday of the year, causing me to 
> miss my gate and not be able to get onto either of two standbys.
> 
> Even if the travel-congestion were not an issue, there the secondary 
> issue of coming home into an already short week.  Most US companies 
> give Thursday and Friday off and many, including myself, take 
> Wednesday off as well (to travel to our Thanksgiving destinations).  
> This leads the somewhat frantic situation of trying to catch-up on 
> email from the week before while clearing the way for the week 
> ahead.
> 
> I understand that this is just an American holiday and that less 
> than half of the IETF are Americans but, if there is any discretion 
> in the matter for future meetings, I would be exceptionally happy if 
> the IETF made an effort to hold the 3rd-meeting of the year a week 
> earlier.
> 
> Thanks,
> Kent
> 

Sorry to hear that too, but looking at the actual schedule, I would 
imagine you could have left Singapore as early as Saturday morning
(or very late Friday night) which would get you to at least the West
Coast by Saturday morning (local) and that *should* at least be 
several days before chaos broke out in the US. I would agree that we
should avoid major holidays, but I'd say we mostly did in this 
particular case. Of course, as they say, "your mileage may vary."

Ole


From nobody Mon Nov 27 15:43:23 2017
Return-Path: <ddp@electric-loft.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 BCF651293EB; Mon, 27 Nov 2017 15:43:21 -0800 (PST)
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 MKsIJRCZdZWl; Mon, 27 Nov 2017 15:43:20 -0800 (PST)
Received: from Mail.Yoyodyne.COM (mail.yoyodyne.com [139.60.72.138]) by ietfa.amsl.com (Postfix) with SMTP id 14CE1124207; Mon, 27 Nov 2017 15:43:20 -0800 (PST)
Received: from [IPv6:2603:3024:170f:af00:dcd1:1d8e:7784:9f91] ([2603:3024:170f:af00:dcd1:1d8e:7784:9f91]) by Mail.Yoyodyne.COM via Internet for <secdir@ietf.org> (and others); Mon, 27 Nov 2017 15:43:18 PST
From: Derrell Piper <ddp@electric-loft.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_6A7F9CDF-0D51-49BA-98C5-0EBCB40EA87C"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: [secdir] Secdir review of draft-ietf-mboned-mtrace-v2-21
Date: Mon, 27 Nov 2017 15:43:18 -0800
References: <151181870041.30959.17144962798564184590@ietfa.amsl.com>
To: secdir@ietf.org, ietf@ietf.org, draft-ietf-mboned-mtrace-v2-21@ietf.org
In-Reply-To: <151181870041.30959.17144962798564184590@ietfa.amsl.com>
Message-Id: <C758369D-5D40-41E0-A838-F134031632EB@electric-loft.org>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yUFMmOgFyUGp1jW72S0DjrdZ5o8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 23:43:22 -0000

--Apple-Mail=_6A7F9CDF-0D51-49BA-98C5-0EBCB40EA87C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Reviewer: Derrell Piper
Review result: ready with nits

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.

This document describes a new version of tracroute designed for =
multicast.  In
the multicast environment, traceroute functions in reverse with each =
router on
the path back towards the client adding diagnostic information along the =
way.
This information can be used to diagnose a variety of network problems,
including packet loss (congestion) and configuration problems (TTL).

The security considerations section discusses a variety of requirements =
and
suggestions for multicast routers and the protocol includes an =
ADMIN_PROHIB
flag which can be used at a border router to prevent multicast =
traceroute from
being able to probe network topology or to perform traffic analysis.

This appears to be a useful diagnostic utility and the obvious security
concerns seem to have been addressed.

nits:

page 33, section 9.3 and 9.4

MAY should be capitalized in these two sections.

Derrell


--Apple-Mail=_6A7F9CDF-0D51-49BA-98C5-0EBCB40EA87C
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-----

iQIzBAEBCAAdFiEEcPdH3FAEATSMj56DLFinjYm9kMIFAlocoxYACgkQLFinjYm9
kMLHhBAAlrPxOGhY3qmuS9GyZoejjJyq2tPLTbt9nJx48+18rFtq1mDepk0Ecbo3
gRYc2HEl3t/jxS+vx/jFW1gpY2zCNqt7v1AfqHIM4K/LjCToybgt8ANsORfLS2Qi
+SNJ7Ns8EDk7wNvwZcnfRikRu6cHPvO6yYKevvyi7ZnDvJMLZrzMbUaLx6s0fbYB
i/MUAhI9wYNoa35GpnC6a96u5LxbggYGTVBuOo105TNWhG9p8TWWviZkq9kLThYa
J+9TR6xOL5E478tkdH9LVErDGZxtP3KJAPJX11GL60hvpKjep13wrGF2/FYC60m9
yShx/Z33XYekbz08xoc41w/tnIA+qljbrrZtUDLttq1q6h3GcK8QP9O0/igErOdq
V/hwl7jB721FTnrpRTrO9fN5YR9ALQIv+bdLsRLHo2Yoinqfp0RoStf4K0v12ZVH
x++iZAgA5yoqNm37mD1KAYDXl8Am0UPtdyoKSvq77WDUoFV7lJFZ30h5Wr2SsYle
Aqrz51GvLr0t3kesAkt4Pu2uCsiCBqILxQNG352fX8uTZcMh+J/qc+ausqqw1lNB
UNzspTQaIXykG2dlzZchha6CUIj/PJoYqO5jk8CLKuGXHGFoJAujsa9eo0149iGD
klsRlIXgk5stLqUFriLgfpY+zJIZNrIZKw4DSquW/6WKMfnwRUc=
=rETv
-----END PGP SIGNATURE-----

--Apple-Mail=_6A7F9CDF-0D51-49BA-98C5-0EBCB40EA87C--


From nobody Mon Nov 27 16:23:54 2017
Return-Path: <ddp@electric-loft.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 334C5128C81; Mon, 27 Nov 2017 16:23:53 -0800 (PST)
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 164PEuFnlr0N; Mon, 27 Nov 2017 16:23:52 -0800 (PST)
Received: from Mail.Yoyodyne.COM (mail.yoyodyne.com [139.60.72.138]) by ietfa.amsl.com (Postfix) with SMTP id 4C4F1128AA1; Mon, 27 Nov 2017 16:23:52 -0800 (PST)
Received: from [IPv6:2603:3024:170f:af00:dcd1:1d8e:7784:9f91] ([2603:3024:170f:af00:dcd1:1d8e:7784:9f91]) by Mail.Yoyodyne.COM via Internet for <secdir@ietf.org> (and others); Mon, 27 Nov 2017 16:23:52 PST
From: Derrell Piper <ddp@electric-loft.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_830C2323-EE52-42F8-8042-9EF19CC07CFE"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: [secdir]  Secdir review of draft-ietf-mboned-mtrace-v2-21
Date: Mon, 27 Nov 2017 16:23:51 -0800
References: <151181870041.30959.17144962798564184590@ietfa.amsl.com> <C758369D-5D40-41E0-A838-F134031632EB@electric-loft.org>
To: secdir@ietf.org, ietf@ietf.org, draft-ietf-mboned-mtrace-v2-21.all@ietf.org
In-Reply-To: <C758369D-5D40-41E0-A838-F134031632EB@electric-loft.org>
Message-Id: <DC7A8884-2B15-476B-9249-1E5C95A66859@electric-loft.org>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2aUFadd24WmRyVXORy8sUQ__s-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: Tue, 28 Nov 2017 00:23:53 -0000

--Apple-Mail=_830C2323-EE52-42F8-8042-9EF19CC07CFE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

[Apologies for the repost, hopefully this one doesn=E2=80=99t wrap.  I =
also didn=E2=80=99t
include the =E2=80=9C.all=E2=80=9D suffix on the previous email.]

Reviewer: Derrell Piper
Review result: ready with nits

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.

This document describes a new version of tracroute designed for
multicast.  In the multicast environment, traceroute functions in
reverse with each router on the path back towards the client adding
diagnostic information along the way.  This information can be used to
diagnose a variety of network problems, including packet loss
(congestion) and configuration problems (TTL).

The security considerations section discusses a variety of requirements
and suggestions for multicast routers and the protocol includes an
ADMIN_PROHIB flag which can be used at a border router to prevent
multicast traceroute from being able to probe network topology or to
perform traffic analysis.

This appears to be a useful diagnostic utility and the obvious security
concerns seem to have been addressed.

nits:

page 33, section 9.3 and 9.4

MAY should be capitalized in these two sections.

Derrell


--Apple-Mail=_830C2323-EE52-42F8-8042-9EF19CC07CFE
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-----

iQIzBAEBCAAdFiEEcPdH3FAEATSMj56DLFinjYm9kMIFAlocrJcACgkQLFinjYm9
kMIWVhAAma84dY25L7qizikoRqCC7Xc7+R8qmRkkQL0jeudwWyQ5cUENgnRF8TP1
kh7KneA/NYqAug1gUuSH0e92lhwicQaSDo/eh2BTNZENB4mXYlwcPcOEtXmPaMcr
K78gSSeMiTB/gFckNOzD8nATfMXxiDAZ6zvd1o2SQ2yuz+EURPPP6jBZSZ6jqb6S
CsTaxV/JsCsfw1+8fSYRY499cKPlxpnGVsJpKHfvjgZduaVKjYWj1LJnKP1Yiets
sVYyQkGWfkI91pPLLG2q9UFXlF/NC4IT5MHA88QVDgaOQn75+GQGasrkXD9DzCMy
jsRfzboxNdFilZEHVaUzP96gAoh2v8UmkSdFyBxnqJtnaBQUdemRR442aTHcWxdC
CWBtmBUmqW/KT06pMCgG5qkotpQ8MLUNl35S9cs/dMZqdeVOO6GV54XFkwi2v6ma
ieNk2OW/d93Ks729opkckLd71d0HdPLcFi5BH79fJF6ozHT9FYXPOAhw9p8NewVm
qgf2OQv7hauPf/4A8gzKOR6978JYS8JLwimPAAaRGCc889LdeFPMd4qpnN/g194g
gQPxeKU5dCUFCF4AdF1gVwkn/qSGS7O2GOWV9VcdH3ZDWG/FzaF5/t4uvrMnsdLu
aIpG3z+f3WzNCJAHOsWYNLvY5V0DrxCBzGFTYHNmSA58O95XaDk=
=SkTS
-----END PGP SIGNATURE-----

--Apple-Mail=_830C2323-EE52-42F8-8042-9EF19CC07CFE--


From nobody Mon Nov 27 17:58:14 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 E671E1200C1 for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 17:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShLfAhtxpOpJ for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 17:58:11 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 9F8C81205D3 for <ietf@ietf.org>; Mon, 27 Nov 2017 17:58:11 -0800 (PST)
Received: (qmail 51160 invoked from network); 28 Nov 2017 01:58:10 -0000
Received: from unknown (64.57.183.53) by gal.iecc.com with QMQP; 28 Nov 2017 01:58:10 -0000
Date: 28 Nov 2017 01:57:49 -0000
Message-ID: <20171128015749.18146.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: kwatsen@juniper.net
Subject: Re: travelling home just before thanksgiving is hard
In-Reply-To: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
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/wp-j_aS8mBC6UFJkRJciftlB1HU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 01:58:13 -0000

In article <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> you write:
>
>I had an awful experience travelling home from Singapore.  What was supposed to be 22-hours of travel
>became 40-hours.  Much of this was due to my US-based connecting airport being exceptionally busy,
>related to this most-travelled holiday of the year, causing me to miss my gate and not be able to get
>onto either of two standbys.

Also sorry to hear it, but I'm rather surprised.  I flew home on
Monday the 20th with no trouble at all.  Where did you misconnect,
and how long a layover did you have?

R's,
John



From nobody Mon Nov 27 18:19:38 2017
Return-Path: <lberger@labn.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 C7ED7128ACA for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 18:19:36 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.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 hoUboEoMRh5x for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 18:19:35 -0800 (PST)
Received: from gproxy9-pub.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) (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 0FB66128CF0 for <ietf@ietf.org>; Mon, 27 Nov 2017 18:19:33 -0800 (PST)
Received: from cmgw3 (unknown [10.0.90.84]) by gproxy9.mail.unifiedlayer.com (Postfix) with ESMTP id CC3061E07CD for <ietf@ietf.org>; Mon, 27 Nov 2017 19:19:29 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw3 with  id fEKS1w00J2SSUrH01EKV9c; Mon, 27 Nov 2017 19:19:29 -0700
X-Authority-Analysis: v=2.2 cv=H76r+6Qi c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=kj9zAlcOel0A:10 a=sC3jslCIGhcA:10 a=QLhupLqRAAAA:8 a=OUXY8nFuAAAA:8 a=Iz4LAfsWGsaIHSaK7YIA:9 a=CjuIK1q_8ugA:10 a=tar-a19HCcU9EdznJS_w:22 a=cAcMbU7R10T-QSRYIcO_:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Subject: References:In-Reply-To:Message-ID:Date:CC:To:From: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=qdFUjA9s3e1U99tW2ama7JBCTvPl6Q9DKdwRzlTurNQ=; b=B751IxKzEzKNzZIJUD5CAJfil+ AJ9Jo5M3igbg3svYJ3B7EzMye4ciihmlCa9KPvBHioigFG9cSEzGToPc4Q8/7oloaACv6J9ryp90y OAXjUCt1KXjBNLsRUDYQljzVS;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:37153 helo=[11.4.0.163]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <lberger@labn.net>) id 1eJVUc-003lip-75; Mon, 27 Nov 2017 19:19:26 -0700
From: Lou Berger <lberger@labn.net>
To: John Levine <johnl@taugh.com>, <ietf@ietf.org>
CC: <kwatsen@juniper.net>
Date: Mon, 27 Nov 2017 21:19:23 -0500
Message-ID: <160006bf3f8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
In-Reply-To: <20171128015749.18146.qmail@ary.lan>
References: <20171128015749.18146.qmail@ary.lan>
User-Agent: AquaMail/1.11.0-568 (build: 101100004)
Subject: Re: travelling home just before thanksgiving is hard
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.86.101
X-Exim-ID: 1eJVUc-003lip-75
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([11.4.0.163]) [100.15.86.101]:37153
X-Source-Auth: lberger@labn.net
X-Email-Count: 2
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n3ePL9cD46T1wAbaBEsWPj2FXkI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 02:19:37 -0000

FWIW i had a very similar experience to Kent's last year returning from Seoul.

I wonder what the conflict was that made us move from the 2nd week of 
December...

Lou


On November 27, 2017 8:58:47 PM "John Levine" <johnl@taugh.com> wrote:

> In article <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> you write:
>>
>>I had an awful experience travelling home from Singapore.  What was 
>>supposed to be 22-hours of travel
>>became 40-hours.  Much of this was due to my US-based connecting airport 
>>being exceptionally busy,
>>related to this most-travelled holiday of the year, causing me to miss my 
>>gate and not be able to get
>>onto either of two standbys.
>
> Also sorry to hear it, but I'm rather surprised.  I flew home on
> Monday the 20th with no trouble at all.  Where did you misconnect,
> and how long a layover did you have?
>
> R's,
> John
>
>
>



From nobody Mon Nov 27 18:35:20 2017
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68951292AE for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 18:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NO_DNS_FOR_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 0cQuEyja1IPc for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 18:35:17 -0800 (PST)
Received: from smtp102.ord1d.emailsrvr.com (smtp102.ord1d.emailsrvr.com [184.106.54.102]) (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 1CD35124207 for <ietf@ietf.org>; Mon, 27 Nov 2017 18:35:17 -0800 (PST)
Received: from smtp13.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp13.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 50ACCC0074; Mon, 27 Nov 2017 21:35:16 -0500 (EST)
X-Auth-ID: ogud@ogud.com
Received: by smtp13.relay.ord1d.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id BEFADC0063;  Mon, 27 Nov 2017 21:35:15 -0500 (EST)
X-Sender-Id: ogud@ogud.com
Received: from [192.0.0.4] ([UNAVAILABLE]. [172.58.200.16]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:465 (trex/5.7.12); Mon, 27 Nov 2017 21:35:16 -0500
In-Reply-To: <160006bf3f8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
References: <20171128015749.18146.qmail@ary.lan> <160006bf3f8.27d3.9b4188e636579690ba6c69f2c8a0f1fd@labn.net>
X-Referenced-Uid: 233261
Thread-Topic: Re: travelling home just before thanksgiving is hard
X-Blue-Identity: !l=315&o=96429&fo=98018&pl=205&po=0&qs=PREFIX&f=HTML&m=!%3AZDBjOGEyOWMtOTM1Ny00ODRhLTkwNjYtMGRmN2RmZWI2Yjhl%3ASU5CT1g%3D%3AMjMzMjYx%3AANSWERED&p=186&q=SHOW
User-Agent: Android
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----URDSYHGQAFV4OM1D06E1GQ20H3W7ZF"
Content-Transfer-Encoding: 7bit
Subject: Re: travelling home just before thanksgiving is hard
From: =?ISO-8859-1?Q?=D3lafur_Gu=F0mundsson?= <ogud@ogud.com>
Date: Mon, 27 Nov 2017 21:35:13 -0500
To: Lou Berger <lberger@labn.net>
CC: John Levine <johnl@taugh.com>,ietf@ietf.org, kwatsen@juniper.net
Message-ID: <a83c1c07-6bfd-453c-8e4a-329516adcc1f@ogud.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w2L4U7pcQszSZ_G-oszKyM3ZllM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 02:35:19 -0000

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

I have decided that from now on I will skip IETF meetings in November that =
are in Asia=2E The main reason is my family does not want another turkey co=
oked by a zombie like last year when Lou and I shared bad trip back=2E

Ola=
fur

=E2=81=A3Sent from Blue =E2=80=8BOn Nov 27, 2017, at 21:19, Lou Berger=
 <lberger@labn=2Enet> wrote:

FWIW i had a very similar experience to Kent'=
s last year returning from Seoul=2E

I wonder what the conflict was that ma=
de us move from the 2nd week of 
December=2E=2E=2E

Lou


On November 27, 2=
017 8:58:47 PM "John Levine" <johnl@taugh=2Ecom> wrote:

In article <9792B9=
8B-68B3-4832-A60D-3210C9401D89@juniper=2Enet> you write:


I had an awful e=
xperience travelling home from Singapore=2E What was 
supposed to be 22-hou=
rs of travel
became 40-hours=2E Much of this was due to my US-based connect=
ing airport 
being exceptionally busy,
related to this most-travelled holid=
ay of the year, causing me to miss my 
gate and not be able to get
onto eit=
her of two standbys=2E


Also sorry to hear it, but I'm rather surprised=2E=
 I flew home on
Monday the 20th with no trouble at all=2E Where did you mis=
connect,
and how long a layover did you have?

R's,
John

On Nov 27, 2017, =
21:19, at 21:19, Lou Berger <lberger@labn=2Enet> wrote:
>FWIW i had a very =
similar experience to Kent's last year returning from
>Seoul=2E
>
>I wonder=
 what the conflict was that made us move from the 2nd week of 
>December=2E=
=2E=2E
>
>Lou
>
>
>On November 27, 2017 8:58:47 PM "John Levine" <johnl@tau=
gh=2Ecom> wrote:
>
>> In article <9792B98B-68B3-4832-A60D-3210C9401D89@juni=
per=2Enet> you
>write:
>>>
>>>I had an awful experience travelling home fro=
m Singapore=2E  What was 
>>>supposed to be 22-hours of travel
>>>became 40=
-hours=2E  Much of this was due to my US-based connecting
>airport 
>>>bein=
g exceptionally busy,
>>>related to this most-travelled holiday of the year=
, causing me to
>miss my 
>>>gate and not be able to get
>>>onto either of =
two standbys=2E
>>
>> Also sorry to hear it, but I'm rather surprised=2E  I=
 flew home on
>> Monday the 20th with no trouble at all=2E  Where did you m=
isconnect,
>> and how long a layover did you have?
>>
>> R's,
>> John
>>
>>=

>>

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

<div dir=3D"auto">I have decided that from now on I will skip IETF meetings=
 in November that are in Asia=2E The main reason is my family does not want=
 another turkey cooked by a zombie like last year when Lou and I shared bad=
 trip back=2E<br><br></div>
<div dir=3D"auto">Olafur<br><br></div>
<div dir=
=3D"auto"><!-- tmjah_g_1299s -->Sent from <!-- tmjah_g_1299e --><a href=3D"=
http://www=2Ebluemail=2Eme/r?b=3D11249"><!-- tmjah_g_1299s -->Blue<!-- tmja=
h_g_1299e --></a><!-- tmjah_g_1299s --> On Nov 27, 2017, at 21:19, Lou Berg=
er &lt;<!-- tmjah_g_1299e --><a href=3D"mailto:lberger@labn=2Enet"><!-- tmj=
ah_g_1299s -->lberger@labn=2Enet<!-- tmjah_g_1299e --></a><!-- tmjah_g_1299=
s -->&gt; wrote:<!-- tmjah_g_1299e --><br><br></div>
<div dir=3D"auto"><!--=
 tmjah_g_1299s -->FWIW i had a very similar experience to Kent's last year =
returning from Seoul=2E<!-- tmjah_g_1299e --><br><br></div>
<div dir=3D"aut=
o"><!-- tmjah_g_1299s -->I wonder what the conflict was that made us move f=
rom the 2nd week of <!-- tmjah_g_1299e --><br></div>
<div dir=3D"auto"><!--=
 tmjah_g_1299s -->December=2E=2E=2E<!-- tmjah_g_1299e --><br><br></div>
<di=
v dir=3D"auto"><!-- tmjah_g_1299s -->Lou<!-- tmjah_g_1299e --><br><br><br><=
/div>
<div dir=3D"auto"><!-- tmjah_g_1299s -->On November 27, 2017 8:58:47 =
PM "John Levine" &lt;johnl@taugh=2Ecom&gt; wrote:<!-- tmjah_g_1299e --><br>=
<br></div>
<div dir=3D"auto"><!-- tmjah_g_1299s -->In article &lt;9792B98B-=
68B3-4832-A60D-3210C9401D89@juniper=2Enet&gt; you write:<!-- tmjah_g_1299e =
--><br><br><br></div>
<div dir=3D"auto"><!-- tmjah_g_1299s -->I had an awfu=
l experience travelling home from Singapore=2E What was <!-- tmjah_g_1299e =
--><br></div>
<div dir=3D"auto"><!-- tmjah_g_1299s -->supposed to be 22-hou=
rs of travel<!-- tmjah_g_1299e --><br></div>
<div dir=3D"auto"><!-- tmjah_g=
_1299s -->became 40-hours=2E Much of this was due to my US-based connecting=
 airport <!-- tmjah_g_1299e --><br></div>
<div dir=3D"auto"><!-- tmjah_g_12=
99s -->being exceptionally busy,<!-- tmjah_g_1299e --><br></div>
<div dir=
=3D"auto"><!-- tmjah_g_1299s -->related to this most-travelled holiday of t=
he year, causing me to miss my <!-- tmjah_g_1299e --><br></div>
<div dir=3D=
"auto"><!-- tmjah_g_1299s -->gate and not be able to get<!-- tmjah_g_1299e =
--><br></div>
<div dir=3D"auto"><!-- tmjah_g_1299s -->onto either of two st=
andbys=2E<!-- tmjah_g_1299e --><br><br><br></div>
<div dir=3D"auto"><!-- tm=
jah_g_1299s -->Also sorry to hear it, but I'm rather surprised=2E I flew ho=
me on<!-- tmjah_g_1299e --><br></div>
<div dir=3D"auto"><!-- tmjah_g_1299s =
-->Monday the 20th with no trouble at all=2E Where did you misconnect,<!-- =
tmjah_g_1299e --><br></div>
<div dir=3D"auto"><!-- tmjah_g_1299s -->and how=
 long a layover did you have?<!-- tmjah_g_1299e --><br><br></div>
<div dir=
=3D"auto"><!-- tmjah_g_1299s -->R's,<!-- tmjah_g_1299e --><br></div>
<div d=
ir=3D"auto"><!-- tmjah_g_1299s -->John<!-- tmjah_g_1299e --></div>

------URDSYHGQAFV4OM1D06E1GQ20H3W7ZF--


From nobody Mon Nov 27 22:51:51 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 BB751127876 for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 22:51:40 -0800 (PST)
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 vxa9gf_OpGZ6 for <ietf@ietfa.amsl.com>; Mon, 27 Nov 2017 22:51:39 -0800 (PST)
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 1150F1200E5 for <ietf@ietf.org>; Mon, 27 Nov 2017 22:51:39 -0800 (PST)
Received: by mail-oi0-x22c.google.com with SMTP id a75so21267260oib.1 for <ietf@ietf.org>; Mon, 27 Nov 2017 22:51:39 -0800 (PST)
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=HC5wKV2i5RJZPBdTwF53KrZrVAa2Y7rkB4UdRzsvi0w=; b=TWGf+Yn2FG1xlxKcqK1GZdpySFQ7PyhkAuknvItfRP3hMAC7bYfZZwRzEWcLKrRmm4 pFIfMimS9BIpSSeuoAun8+s6Rr2rae8SmXK2v8SOX5dG5dpTF6QnGVxV4ai2+3y2KYyn gd/BxlTOKcPZGR7cEhp5+3QgM+FcGnm9qnpLZIK7W+qAgw+coJkZpkoMZUQqrwK0oChX Zt+7Y8+PYrtdRf+TsBDc+JvZwrKtcgGiKobuXouWqa8nvw0DPxKrg84Eqah2gbQ24Z4h MhR4ZJrUX2MOd10DpcEyFTkZW18LaFOqcktbgu4RUurMXQW3KvXrPE7+bYbaV0iPrkGQ qoFw==
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=HC5wKV2i5RJZPBdTwF53KrZrVAa2Y7rkB4UdRzsvi0w=; b=Ra0xg/7C3d9YSn8MEY+KGS/UgEhv4/+RZq5CsV4tVQKQgfW1OK54JNCtb1Z0mdHVq+ gU4UFd4ZAaYiVGVnTiK5Q20lgeXDt9TYNegZg9ZRmf6XlvDmSLo1g76mdRlMuK2/zM+u dGSTlp3NE99NjwZPhuyP57T5c1xJqqqym2knPeEmcUacfVK2+2qEjKgJX6Y8RUpn5Yqx RTbYG6gUipMfvFwOEIQp1rWFdRYu16ndBABukfBQo4Z9Ywn6AJqzYSz5dx0H3jC0UpPS GVeHPNARwh+xOXzlYDuv5fDj4M7Ql5Y5XBwkm34z8lwiZpfRe2EVnn/pU8ZORFQkYD6k QCWQ==
X-Gm-Message-State: AJaThX7aUIFoq/C2uHLy9SwQMmSdmkQIPVuGUs4yVe7Wpd769C9oAFp0 YqAjld4ZpulS0DM0vHa3e9qHLaLbdXs/7rkgUmy2ol0T
X-Google-Smtp-Source: AGs4zMYX6UUNVE5f9qxxSbKlhrnFDMK8LyHswdTRtiPYw7AVgpjBuCEqMFljYWqOqoXXSCOuS9pxseuHuRVREkNjwiA=
X-Received: by 10.202.170.143 with SMTP id t137mr18564893oie.313.1511851898159;  Mon, 27 Nov 2017 22:51:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.8.11 with HTTP; Mon, 27 Nov 2017 22:51:37 -0800 (PST)
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 28 Nov 2017 17:51:37 +1100
Message-ID: <CABkgnnU5jd--NAodUMsnDf1Ei036hd9WPmK7qHFtNa=5=vhoYw@mail.gmail.com>
Subject: draft-mm-wg-effect-encrypt-13 Sections 6.2-6.4
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6iLwZ2noGQ92tiZQMQ0BwlTOgEI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 06:51:41 -0000

I haven't time at the moment to go through this document in detail.
But I did notice a few obvious errors in the mentioned sections.

6.2

SNI encryption has been adopted by the TLS WG, but that doesn't mean
that all future versions of TLS will include the capability - or even
be able to use it - as the text implies.  Encrypting SNI calls for
some hard trade-offs that likely mean that encryption won't be
universally deployed.  I do appreciate the effort to forewarn about
this, but it misses the point somewhat.

The point here is that SNI is being used as a proxy for identification
of content.  That it is a poor proxy is widely acknowledged (though
not in the draft), but it has been more or less accepted as adequate
for some applications of content-based discrimination.

Let's say that we accept that as implicit - rather than a cleaner
explicit statement - and continue to focus on identification of
content via SNI.  In that case, RFC 7540 defined something that should
be more of a concern: connection coalescing.  That feature is also
widely implemented in browsers.  The ORIGIN frame
(draft-ietf-httpbis-origin-frame) makes this stronger by potentially
taking DNS out of the loop.  Add the likely-to-be-adopted
draft-bishop-httpbis-http2-additional-certs and things far more
challenging for snooping than merely encrypting SNI.

This is misleading:

   It should be noted that
   HTTP/2 introduces the Alt-SVC method for upgrading the connection
   from HTTP/1 to either unencrypted or encrypted HTTP/2.  If the
   initial HTTP/1 request is unencrypted, the destination alternate
   service name can be identified before the communication is
   potentially upgraded to encrypted HTTP/2 transport.

RFC 8164 defines the use of Alt-Svc [check capitalization] for
opportunistically upgrading to an encrypted (and authenticated!)
transport.  The claim here that the service name can be identified is
perhaps correct, but also unnecessary, since the alternative is
contacted using the SNI of the original (as defined in RFC 7838).


6.3

As I mentioned in a previous review, ALPN is not encrypted in TLS 1.3.
The correct statement would be that ALPN options are available to the
network (just like SNI), but the selection by the server is not.  I'm
still not sure what use cases this datum drives though.

6.4

This mentions nothing of padding.  Padding is available in HTTP/2 and
TLS 1.3, plus many other protocols.  It at least deserves some
recognition, even if it isn't widely deployed (outside of some
relatively specialized uses, that is).  There's a whole RFC on traffic
analysis and countermeasures missing from our dialogue here, but a
mention is probably wise.


From nobody Tue Nov 28 07:30:42 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 B7AF4126D3F for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 07:30:40 -0800 (PST)
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 oJn0TSOvRFUD for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 07:30:39 -0800 (PST)
Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002: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 029661242EA for <ietf@ietf.org>; Tue, 28 Nov 2017 07:30:39 -0800 (PST)
Received: by mail-yb0-x236.google.com with SMTP id s46so81624ybi.8 for <ietf@ietf.org>; Tue, 28 Nov 2017 07:30:38 -0800 (PST)
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=OOm4d3DAjdL7im8ofDir4geLjPxW3fRiMG9re5Kg7as=; b=Pd2VPnBshwDzU5rinlqc/lMwwxRzm2DtgU31bDQUHcGIgAP3EfDCGlnkqFc/ozNjiS fKPd9ZJsRqyjwBiYGNkoW/dRf1WraEEqp1cnqX5XNJ33oXQpPDZwpi5QrrpRYiPqKdwS n99dEDhB19JilWTzsSgkoMG3HMYmYdZDlnRHRGu8tLAxn4f9V5qt761v5zl0CaDM7PHw HFpqTFz6wxuDTaJJIA9fhk01wri85EGyvjRh4sByDftdIAu+arZM8dwk2o/kTTaCDewX kqu06D8qbij42dGh9O9C9Ryfxtde9aBERP/ly2zlC/5jlUQXOufp95y0zFSpmgveepY5 GpAw==
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=OOm4d3DAjdL7im8ofDir4geLjPxW3fRiMG9re5Kg7as=; b=OxG4LMDgC458pufjbAuHQLPbA2OqMV2Pm+2Kg9uUbi6e2RNfCQGd4se5tkQaU7oSmq nmCOYmK1giMBjAQvDXKJgnRaaZnXd1H4CYJ9Le9FSaf4jFubVkWWq6iKkmOrMrgq/Onb tOn/pKQMWBvYMmA50+0wqRyItrD4sWJrSyfSJWR0MWvy6n/LL9aAbH97tFXAeZkpfVnw B/HxXQnFcnlayT+I6IhUHFhtpQHoFLM9oK7yzRSHa+zA18ann/ecEbYI5edGyTfmHjqy r7dQmw6CUbRvA5vBUjcQHhs/DxigYnrPVkwmUiKHKB/yMFZcsGbrWVHnankP17ZnHEwU 84Lg==
X-Gm-Message-State: AJaThX6IsVH9EVOUv0kK+Dr3LxFEygOL1BAXgjxal9Q0VcPSjuFe/WhT NWw1TjPXYLxooqZolxkztpJOgNg4rxge6l0zI/0=
X-Google-Smtp-Source: AGs4zMbvhGVnOa2vXQIcS3TwnfHpeFnJAH910D+IumG6xlaw0ev1t1KMQY/EZto9zXPN5VKtzoaXmdauj1K/AhAuVnY=
X-Received: by 10.37.9.76 with SMTP id u12mr26560102ybm.417.1511883037896; Tue, 28 Nov 2017 07:30:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.135.75 with HTTP; Tue, 28 Nov 2017 07:30:37 -0800 (PST)
In-Reply-To: <CABkgnnU5jd--NAodUMsnDf1Ei036hd9WPmK7qHFtNa=5=vhoYw@mail.gmail.com>
References: <CABkgnnU5jd--NAodUMsnDf1Ei036hd9WPmK7qHFtNa=5=vhoYw@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 28 Nov 2017 09:30:37 -0600
Message-ID: <CAKKJt-dmVrBke_SAGq9=XStLBUsA1eOQuhbqiuLSOeC9rC7TPw@mail.gmail.com>
Subject: Re: draft-mm-wg-effect-encrypt-13 Sections 6.2-6.4
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403043b5f386a7316055f0cb329"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Pl2i-fD3FaZrLRsEVviWbyrDk1c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 15:30:41 -0000

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

Just chiming in on Martin's last point ...

On Tue, Nov 28, 2017 at 12:51 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> 6.4
>
> This mentions nothing of padding.  Padding is available in HTTP/2 and
> TLS 1.3, plus many other protocols.  It at least deserves some
> recognition, even if it isn't widely deployed (outside of some
> relatively specialized uses, that is).  There's a whole RFC on traffic
> analysis and countermeasures missing from our dialogue here, but a
> mention is probably wise.
>

I've been talking with the IESG since at least our retreat in May, about
the need for (some value of) us to up-level our discussion so that we're
providing general guidance about privacy, and not just arguing about
privacy on every document where someone notices something (too often,
during IETF Last Call or IESG Evaluation).

If Martin's point is that we don't have an appropriate document to point to
as something like a canonical checklist, it would be great if that changed.
I don't know if a BCP is the right thing to do, but if an RFC providing
guidance already exists, it's not jumping out at me.

Mirja and I hosted Mike Perry from the Tor Project to talk about " Privacy
and Traffic Analysis Resistance for Encrypted Protocols" to TSVAREA at IETF
98, for instance, and that was very helpful, but ISTM that pointing people
to a PowerPoint presentation (Privacy and Traffic Analysis Resistance for
Encrypted Protocols) or MeetEcho recording (
https://www.youtube.com/watch?v=0tvKH_Cnvwg&list=PLC86T-6ZTP5jo6kIuqdyeYYhsKv9sUwG1&index=84,
beginning at about 1:11 from the beginning) may not be the best we could do
...

Thoughts from others?

Spencer, as TSV AD, responsible AD for QUIC, and apparently the Spin Bit AD
...

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

<div dir=3D"ltr">Just chiming in on Martin&#39;s last point ...<div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Nov 28, 2017 at 12:=
51 AM, Martin Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomso=
n@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">6.4<br>
<br>
This mentions nothing of padding.=C2=A0 Padding is available in HTTP/2 and<=
br>
TLS 1.3, plus many other protocols.=C2=A0 It at least deserves some<br>
recognition, even if it isn&#39;t widely deployed (outside of some<br>
relatively specialized uses, that is).=C2=A0 There&#39;s a whole RFC on tra=
ffic<br>
analysis and countermeasures missing from our dialogue here, but a<br>
mention is probably wise.<br></blockquote><div><br></div><div>I&#39;ve been=
 talking with the IESG since at least our retreat in May, about the need fo=
r (some value of) us to up-level our discussion so that we&#39;re providing=
 general guidance about privacy, and not just arguing about privacy on ever=
y document where someone notices something (too often, during IETF Last Cal=
l or IESG Evaluation).</div><div><br></div><div>If Martin&#39;s point is th=
at we don&#39;t have an appropriate document to point to as something like =
a canonical checklist, it would be great if that changed. I don&#39;t know =
if a BCP is the right thing to do, but if an RFC providing guidance already=
 exists, it&#39;s not jumping out at me.</div><div><br></div><div>Mirja and=
 I hosted Mike Perry from the Tor Project to talk about &quot; Privacy and =
Traffic Analysis Resistance for Encrypted Protocols&quot; to TSVAREA at IET=
F 98, for instance, and that was very helpful, but ISTM that pointing peopl=
e to a PowerPoint presentation (Privacy and Traffic Analysis Resistance
for
Encrypted Protocols) or MeetEcho recording (<a href=3D"https://www.youtube.=
com/watch?v=3D0tvKH_Cnvwg&amp;list=3DPLC86T-6ZTP5jo6kIuqdyeYYhsKv9sUwG1&amp=
;index=3D84">https://www.youtube.com/watch?v=3D0tvKH_Cnvwg&amp;list=3DPLC86=
T-6ZTP5jo6kIuqdyeYYhsKv9sUwG1&amp;index=3D84</a>, beginning at about 1:11 f=
rom the beginning) may not be the best we could do ...</div><div><br></div>=
<div>Thoughts from others?</div><div><br></div><div>Spencer, as TSV AD, res=
ponsible AD for QUIC, and apparently the Spin Bit AD ...</div></div></div><=
/div>

--f403043b5f386a7316055f0cb329--


From nobody Tue Nov 28 07:35: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 2A55F127B31 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 07:35:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IsRMg-I46vgu for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 07:35:06 -0800 (PST)
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 308C9127A91 for <ietf@ietf.org>; Tue, 28 Nov 2017 07:35:06 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id F286E2008C for <ietf@ietf.org>; Tue, 28 Nov 2017 10:37:31 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 13C1E807CC for <ietf@ietf.org>; Tue, 28 Nov 2017 10:35:05 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: travelling home just before thanksgiving is hard
In-Reply-To: <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com>
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net> <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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, 28 Nov 2017 10:35:05 -0500
Message-ID: <30894.1511883305@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vO7Pr867YU4Zg7TSKCyJMvj2jHM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 15:35:15 -0000

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


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > Also, if we have to steer clear of Thanksgiving, in fairness we'd have
    > to steer clear of Chinese New Year and other such events.

My take on this is that it's not Thanksgiving itself, but rather the travel
congestion associated with it.
Last weekend (when y'all were returning from Singapore) is apparently the 2nd
busiest travel weekends in the US.

Chinese New Year is two weeks, I think.

I also think that aside from the family issues for someone being away during
those two weeks, if someone had to travel in China in the middle of the two
weeks that there would be little travel congestion.

The Orlando 2012 week was similar: a March break weekend between the Quebec
and Ontario school breaks in Canada, and an extremely popular time to visit
Florida.  I arrived a day late, having flown an extra 3000km.

I'd like to see us work to reduce the demand for meeting time, and pull the
hackathon and other "weekend" events into a Sunday->Thursday schedule.


--
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+93Q3WUFAlodgigACgkQgItw+93Q
3WWnKAf+NZ4GoPfVDf94znXMrDpuUNpgdvHCmkcKYEn/6r3TH2+viau7LuzuD7XE
oOKk7CD94pR49kGs15HJf0/a09WuXmr6pwvA0a9dOHuR6nth5EqPiDbizRwyJjjQ
3USqGgdJc4UxxIwTzA+YEazf6MlZVCUAhiWAp/zHwGSAOwlcPla0KG4kNgzHlf+P
vpNGvUXGHi3LGl+RUW6UYUz2d7U390V6NslucRDwgitXSiZNO1fSBKKkPzxQQ4UD
Xueh/OZieWeF1nIHdJdCG6465jotxwlU7GFliQbXZLpxwBa1gCo4AbuDHGeBAO/p
Pf+iPLaYiKaQE/RdKqq2R8gH0QnPhQ==
=m6Sc
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Nov 28 07:56:37 2017
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23BFE12711D for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 07:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=me.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzlkt0_-xmFL for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 07:56:35 -0800 (PST)
Received: from mr11p00im-asmtp003.me.com (mr11p00im-asmtp003.me.com [17.110.69.254]) (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 11E96126CE8 for <ietf@ietf.org>; Tue, 28 Nov 2017 07:56:35 -0800 (PST)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp003.me.com by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) id <0P0400700WD9WI00@mr11p00im-asmtp003.me.com> for ietf@ietf.org; Tue, 28 Nov 2017 15:56:31 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=me.com; s=04042017; t=1511884591; bh=EOx0EclbzqSdHvqgeQQWXStimocF5gYNYngM1gLWQPE=; h=Date:From:To:Subject:Message-id:MIME-version:Content-type; b=nImwREO5ArkufG5G/g1bVoQqh0DPOVT9c1iqT2Ef2DpBWKFmmpmgbiC6MJ1gKL1jV iBundkStCUprRsSMtum+44mK4uCALa/+lk/LWYrKKjoxeQxtMWP3pMDwadeDxuYNvc NYxPGWz0EEQ6fQKfHNr73MqMsKFgzfXedQ+EZQ+JaRDObijCypu4uYUO8zYxPe0Z+s ZwFejKsm/U+BucyRWIuosbrfxnCnN0UJhQi3pbmhfzbgOgu/RsLJCO0f3YI17Kyvbx Hk6JCr/3uFyEdPstTZXJKnnRU0+yT8ZQPjpCTkgEBzg9lAEpwu7Zkh3phVV4jZIl1m TOIhUx7tswYfg==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp003.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun  7 2017)) with ESMTPSA id <0P04009D4XM5OC30@mr11p00im-asmtp003.me.com>; Tue, 28 Nov 2017 15:56:30 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-11-28_10:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1711280215
Date: Tue, 28 Nov 2017 07:56:28 -0800 (PST)
From: Ole Jacobsen <olejacobsen@me.com>
Reply-to: Ole Jacobsen <olejacobsen@me.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: ietf@ietf.org
Subject: Re: travelling home just before thanksgiving is hard
In-reply-to: <30894.1511883305@obiwan.sandelman.ca>
Message-id: <alpine.OSX.2.01.1711280751390.91054@ole-pro.local>
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net> <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com> <30894.1511883305@obiwan.sandelman.ca>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qs3Iz6yKuxiHNMgqMY1Db82oF-g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 15:56:36 -0000

Just keep in mind that the first and foremost requirement (assuming
other conditions are satisfied) is "availability of venue for our
published dates." We have an opportunity to adjust those dates once
we decide to publish dates beyong 2022, or (exceptionally) change
what we have published with sufficient notice and reason.

I tend to agree that early November is probably better than "week 
before Thanksgiving in the US."

Ole


Ole J. Jacobsen
Editor and Publisher
The Internet Protocol Journal
Office: +1 415-550-9433
Cell:   +1 415-370-4628
Docomo: +81 090 3337-9311
E-mail: olejacobsen@me.com
Skype: organdemo



From nobody Tue Nov 28 08:10:02 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 D22191270B4 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:10:00 -0800 (PST)
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, 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 HmzxGiSqCBEl for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:09:59 -0800 (PST)
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 42216126B72 for <ietf@ietf.org>; Tue, 28 Nov 2017 08:09:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7EAEDBEC6; Tue, 28 Nov 2017 16:09:57 +0000 (GMT)
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 DP9IEZL2rUm9; Tue, 28 Nov 2017 16:09:57 +0000 (GMT)
Received: from [134.226.62.136] (cswireless62-136.scss.tcd.ie [134.226.62.136]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 33BF7BEBE; Tue, 28 Nov 2017 16:09:57 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1511885397; bh=6LwSB7b/1x34EuaGE9S49IdVu0KgUn+aowloKkdMksI=; h=Subject:To:References:From:Date:In-Reply-To:From; b=p3lb8T0W+Riis8w47Z3EfaFMZX5DkdumOAIuD0t/eqtkSiG2ZlEYaf1WvomhPVxDr BirS4+1qSM3JHhvcLqwNaEF93md7f2AkSYe85mGEXJCL+YKXPpUc1YeGd+rzYTFOVM AylOanor6pGZF8ZSNDhK5OnocQiMk7UjIU+n1WVA=
Subject: Re: travelling home just before thanksgiving is hard
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net> <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com> <30894.1511883305@obiwan.sandelman.ca>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie>
Date: Tue, 28 Nov 2017 16:09:54 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <30894.1511883305@obiwan.sandelman.ca>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SchIaXKeAKKeixQpKV9XEkQD4qSBErVTA"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vkIouKs_S4tJP62TJjQR0G1scHs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 16:10:01 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--SchIaXKeAKKeixQpKV9XEkQD4qSBErVTA
Content-Type: multipart/mixed; boundary="HUJWrlhd1EitsavFHXgiPpW6OjFS9usX0";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
Message-ID: <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie>
Subject: Re: travelling home just before thanksgiving is hard
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
 <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net>
 <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com>
 <30894.1511883305@obiwan.sandelman.ca>
In-Reply-To: <30894.1511883305@obiwan.sandelman.ca>

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



On 28/11/17 15:35, Michael Richardson wrote:
>=20
> I'd like to see us work to reduce the demand for meeting time, and pull=
 the
> hackathon and other "weekend" events into a Sunday->Thursday schedule.

+1

S.


--HUJWrlhd1EitsavFHXgiPpW6OjFS9usX0--

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

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

iQEcBAEBCAAGBQJaHYpTAAoJEC88hzaAX42isO0IAKTVksApK9+Iv+cnTaBQRcA3
TXhTIXyLyljqGGuVs1QlHm1Loym8ABCarjRfhKA6RbMKbi7Oi5pmJuSnpAAo6aWN
tWas5MNICL537GfhjlZN9NA79Ywcu+1ZJzI1KOKn3Fg+BB7vY7ioGwfIJ0wdzvi2
S2YF4Siza60fWBfeDBupWkxylp49QzK6ac8rfJ1KLTGkelDtKqa94sAkTWRh7XAd
p573OZscgp+XvYiJJdV8ipm7noAlES9pKncNgRB9Id24REhXmoRl9g2xMqyFpl44
9UXCSINQ2yxoMl+0wNoG5yjDpK270ctoG2oCsitNAP/fnUrcQ4dnWwbLmMFjsRM=
=hdfD
-----END PGP SIGNATURE-----

--SchIaXKeAKKeixQpKV9XEkQD4qSBErVTA--


From nobody Tue Nov 28 08:14:49 2017
Return-Path: <huubatwork@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 A2B1E129405; Mon, 27 Nov 2017 14:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, 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 laVlLIHzV9wp; Mon, 27 Nov 2017 14:39:46 -0800 (PST)
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 5AD8212940F; Mon, 27 Nov 2017 14:39:46 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id r68so38320041wmr.1; Mon, 27 Nov 2017 14:39:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=reply-to:subject:to:cc:references:from:message-id :disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=51s1d/BZaUq0dqoe7v8dsdqyLXhrkJ+TqH3T9Mnzbxo=; b=uHciY8rLlWN8duUQUa6fZ5hi2vaFWt50dKr+GptuLdyOZHRTMQGBUenqOnUr4lWYhi xz4iSZqyoHB7IVBkLZTw5NEhzBMe8SLySS5/msVdXM2Z/HqB8Nmy1JKPKKGcqDY1oYnH QwG7O9HFdE8fgVC4fux3uaHk9WrGdLOixukzVmW/e3N1sSSedEvUd8/iYWjzuAU3ASGu ch33qpoUJQjBzq8zqh7Lv43hRcFNT4NoWEgxwmnvPQTeC2Ti9VpWT+VoKyvBhSeDJq8H rDlQBTZcaMFqoYx6nkh6iqGOKY6XxourdkjuiIgTQm4t8WtJtuwUj150Vku+F/gsNC3N B27A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:to:cc:references:from :message-id:disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=51s1d/BZaUq0dqoe7v8dsdqyLXhrkJ+TqH3T9Mnzbxo=; b=l32Z4s9Rjr/aw1TkwJDFKKnV6Bf47hPuFtVVIprvXdr7lAx+oId7hU84KAEPdXlzpW X3/xuoAoliRJ2mISDng+Vjcctjqos6578eLMWMKlNJaJPlHZDz71Wa3qYVlub5xwNzP9 4WV/8ZaJwqw5ajf2c6iL2tblaGkPJ3Pj00unMtxKQ2s0OMsdhNDZJk+wYBi6JHkqqzjd LOg2Gj0oiYy/HmYrSzEoS25dAlOxqlas7wYt9MoL1qsBkpNvl3yJO55QbRbXedpqO97s PQD670iqR8VX84C6Tes4vKpjEwMCHZl05GHVSZFKiky7P9a+DnZYbhnviNVYf7MscDne Exmg==
X-Gm-Message-State: AJaThX48iVIP3Faf8o0iG7ZzOpBXSiCdg3MqGGkjP60t0sEV0/lyynxt 8H8rCNyoDZDEPe6C+bU0Ue0tPQ==
X-Google-Smtp-Source: AGs4zMYsCRuKIOeF11yQb4Cg8WRFzzO3MDJ3O+pA3FY+3WPueqLdPO5RGoLr0Vj7iL5gxDijZ+qw/g==
X-Received: by 10.80.184.52 with SMTP id j49mr53894722ede.160.1511822384670; Mon, 27 Nov 2017 14:39:44 -0800 (PST)
Received: from McAsterix.local (g77189.upc-g.chello.nl. [80.57.77.189]) by smtp.gmail.com with ESMTPSA id x17sm20785220edx.9.2017.11.27.14.39.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Nov 2017 14:39:43 -0800 (PST)
Reply-To: huubatwork@gmail.com
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
To: Greg Mirsky <gregimirsky@gmail.com>, Qin Wu <bill.wu@huawei.com>, "iesg@ietf.org" <iesg@ietf.org>
Cc: Carlos Pignataro <cpignata@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, Ron Bonica <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, Benoit Claise <bclaise@cisco.com>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com>
From: Huub van Helvoort <huubatwork@gmail.com>
Message-ID: <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com>
Date: Mon, 27 Nov 2017 23:40:10 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com>
Content-Type: text/html; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vZI0w_8VCbD1G-zdPCedKGlZixY>
X-Mailman-Approved-At: Tue, 28 Nov 2017 08:14:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Nov 2017 22:39:48 -0000

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hello Greg,<br>
      <br>
      I agree with you that the current (version 18) text in section 3.3
      is very confusing.<br>
      <br>
      Authors:<br>
      <br>
      If I look at the definition of TP in section 2.2 I think a TP is
      similar<br>
      to a maintenance point as defined for Ethernet. Am I correct?<br>
      <br>
      I don't understand why there are TPs with no neighboring TPs,<br>
      where will their initiated OAM test be sent? Or where are OAM<br>
      tests they react to initiated?<br>
      <br>
      It is IMHO also possible that there are TPs with a neighboring <br>
      TP before AND a neighboring TP after the current TP.<br>
      <br>
      Please explain.<br>
      <br>
      Regards, Huub.<br>
      <br>
      ---------<br>
      <br>
    </div>
    <blockquote type="cite"
cite="mid:CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com">
      <div dir="ltr">Dear All,
        <div>I was under impression that that question of <span
            style="color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-tps</span><span
            style="color:rgb(0,0,0);font-size:13.3333px"> has been
            discussed and since authors couldn't produce technical
            rationale for this object we've agreed that it will be
            removed altogether from the </span><span
            style="color:rgb(0,0,0);font-size:13.3333px">grouping
            connectionless-oam-tps. But authors just changed name from
            level to position but had missed to synchronize descriptions
            in the model and in section 3.3. The later still refers to
            vertical layers:</span></div>
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">                     "List of related neighboring test points in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.";
</pre>
        </div>
        <div>while the model insists that it is peering relationship:</div>
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">        description
          "The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current
</pre>
        </div>
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">           test point in the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.";
</pre>
        </div>
        <div>So, what is it? Perhaps it is time to remove list <span
            style="color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-tps
            altogether also because having it s fixed size list is plain
            wrong. (Sorry for being so blunt but I commented too many
            times on the same to no avail from the authors).</span></div>
        <div><span style="color:rgb(0,0,0);font-size:13.3333px"><br>
          </span></div>
        <div><span style="color:rgb(0,0,0);font-size:13.3333px">Regards,</span></div>
        <div><span style="color:rgb(0,0,0);font-size:13.3333px">Greg</span></div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
================================================================
Always remember that you are unique...just like everyone else...</pre>
  </body>
</html>


From nobody Tue Nov 28 08:14:55 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 DB391124B17; Mon, 27 Nov 2017 23:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level: 
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 0HXNuSHyTh6v; Mon, 27 Nov 2017 23:36:39 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C5F1200E5; Mon, 27 Nov 2017 23:36:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7750; q=dns/txt; s=iport; t=1511854598; x=1513064198; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=6Fro7gb8eh228a0hIMji+sRiVIjHRUMeiMcV454I3+k=; b=MjcfhHXuT9j5QQBaRTZ+itHS3ouL7X1H1UbFIm+ujrxLCo9rCnjwq6sV 58CC/7JqmrP761nL76f6Y9rRQjAwrwtGx9dL0h3Hh1TaBMpsKs2VC0dHd CKuVnasD3sgyoN3NUlU4ZO6Io7wU+4K/myMpFv5liBL10bKmywXH/KCc6 E=;
X-IronPort-AV: E=Sophos;i="5.44,467,1505779200"; d="scan'208,217";a="521175"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Nov 2017 07:36:36 +0000
Received: from [10.61.99.179] (dhcp-10-61-99-179.cisco.com [10.61.99.179]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id vAS7aZ1F003380; Tue, 28 Nov 2017 07:36:35 GMT
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
To: huubatwork@gmail.com, Greg Mirsky <gregimirsky@gmail.com>, Qin Wu <bill.wu@huawei.com>, "iesg@ietf.org" <iesg@ietf.org>
Cc: Carlos Pignataro <cpignata@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, Ron Bonica <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com>
Date: Tue, 28 Nov 2017 08:36:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com>
Content-Type: multipart/alternative; boundary="------------EDF2D987899B3FF8EA00F902"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/54fYoCXqFklI-xPDMry76Jetrl8>
X-Mailman-Approved-At: Tue, 28 Nov 2017 08:14:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 07:36:41 -0000

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

Huub,

For your information, the document is now in the RFC editor queue, ready 
to be published.
https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/

Regards, Benoit
> Hello Greg,
>
> I agree with you that the current (version 18) text in section 3.3 is 
> very confusing.
>
> Authors:
>
> If I look at the definition of TP in section 2.2 I think a TP is similar
> to a maintenance point as defined for Ethernet. Am I correct?
>
> I don't understand why there are TPs with no neighboring TPs,
> where will their initiated OAM test be sent? Or where are OAM
> tests they react to initiated?
>
> It is IMHO also possible that there are TPs with a neighboring
> TP before AND a neighboring TP after the current TP.
>
> Please explain.
>
> Regards, Huub.
>
> ---------
>
>> Dear All,
>> I was under impression that that question of oam-neighboring-tps has 
>> been discussed and since authors couldn't produce technical rationale 
>> for this object we've agreed that it will be removed altogether from 
>> the grouping connectionless-oam-tps. But authors just changed name 
>> from level to position but had missed to synchronize descriptions in 
>> the model and in section 3.3. The later still refers to vertical layers:
>>                       "List of related neighboring test points in adjacent
>>                       layers up and down the stack for the same interface
>>                       that are related to the current test point.";
>> while the model insists that it is peering relationship:
>>          description
>>            "The relative position
>>             of neighboring test point
>>             corresponding to the current
>>             test point. Level 0 indicates no neighboring
>>             test points placed before or after the current
>>             test point in the same layer.-1 means there is
>>             a neighboring test point placed before the current
>>             test point in the same layer and +1 means there is
>>             a neighboring test point placed after the current
>>             test point in same layer.";
>> So, what is it? Perhaps it is time to remove list oam-neighboring-tps 
>> altogether also because having it s fixed size list is plain wrong. 
>> (Sorry for being so blunt but I commented too many times on the same 
>> to no avail from the authors).
>>
>> Regards,
>> Greg
>
>
> -- 
> ================================================================
> Always remember that you are unique...just like everyone else...
> . 


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Huub,<br>
      <br>
      For your information, the document is now in the RFC editor queue,
      ready to be published.<br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/">https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/</a><br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote type="cite"
      cite="mid:499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div class="moz-cite-prefix">Hello Greg,<br>
        <br>
        I agree with you that the current (version 18) text in section
        3.3 is very confusing.<br>
        <br>
        Authors:<br>
        <br>
        If I look at the definition of TP in section 2.2 I think a TP is
        similar<br>
        to a maintenance point as defined for Ethernet. Am I correct?<br>
        <br>
        I don't understand why there are TPs with no neighboring TPs,<br>
        where will their initiated OAM test be sent? Or where are OAM<br>
        tests they react to initiated?<br>
        <br>
        It is IMHO also possible that there are TPs with a neighboring <br>
        TP before AND a neighboring TP after the current TP.<br>
        <br>
        Please explain.<br>
        <br>
        Regards, Huub.<br>
        <br>
        ---------<br>
        <br>
      </div>
      <blockquote type="cite"
cite="mid:CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com">
        <div dir="ltr">Dear All,
          <div>I was under impression that that question of <span
              style="color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-tps</span><span
              style="color:rgb(0,0,0);font-size:13.3333px"> has been
              discussed and since authors couldn't produce technical
              rationale for this object we've agreed that it will be
              removed altogether from the </span><span
              style="color:rgb(0,0,0);font-size:13.3333px">grouping
              connectionless-oam-tps. But authors just changed name from
              level to position but had missed to synchronize
              descriptions in the model and in section 3.3. The later
              still refers to vertical layers:</span></div>
          <div>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">                     "List of related neighboring test points in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.";
</pre>
          </div>
          <div>while the model insists that it is peering relationship:</div>
          <div>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">        description
          "The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current
</pre>
          </div>
          <div>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">           test point in the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.";
</pre>
          </div>
          <div>So, what is it? Perhaps it is time to remove list <span
              style="color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-tps
              altogether also because having it s fixed size list is
              plain wrong. (Sorry for being so blunt but I commented too
              many times on the same to no avail from the authors).</span></div>
          <div><span style="color:rgb(0,0,0);font-size:13.3333px"><br>
            </span></div>
          <div><span style="color:rgb(0,0,0);font-size:13.3333px">Regards,</span></div>
          <div><span style="color:rgb(0,0,0);font-size:13.3333px">Greg</span></div>
        </div>
      </blockquote>
      <p><br>
      </p>
      <pre class="moz-signature" cols="72">-- 
================================================================
Always remember that you are unique...just like everyone else...</pre>
      .
    </blockquote>
    <br>
  </body>
</html>

--------------EDF2D987899B3FF8EA00F902--


From nobody Tue Nov 28 08:15:05 2017
Return-Path: <huubatwork@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 3C06C1200F3; Tue, 28 Nov 2017 02:21:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.975
X-Spam-Level: 
X-Spam-Status: No, score=-1.975 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, 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 rnpzqyRJQ6Xr; Tue, 28 Nov 2017 02:21:15 -0800 (PST)
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 0A9E0126579; Tue, 28 Nov 2017 02:21:15 -0800 (PST)
Received: by mail-wm0-x22f.google.com with SMTP id x63so683336wmf.2; Tue, 28 Nov 2017 02:21:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=reply-to:subject:to:cc:references:from:message-id :disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=jbhkSKUr1rINeFGnp0MAmXnMMrIx5cnrPuddCB78iPs=; b=lqyT2E+4vtECSwo/scmGELWCD+/2SCIUaG2jSXYi5oYEkWj5oQnnb6NYnsL1eEjrh/ ZiwT053WtLPXh6AsxX6B6ZQ6/F8dbJ3ZzrLrjO8SxZnuSCe8hpetlH5yoHIEwdWsEkqN YvsO9QGrZ7oWPnWxzBzeP3rNqLErWfaWo9NIifCWg9P1EgDnbWmLVsGbDgweLW/F/Tgd T2cs/xRKwz+adpjOIcF+lvZeE+ZC8IWE41j87lvCrB8ANDgwOxmwre3ZgGCCNcHmeOE6 GI7JR2Y/TmRSPH1Q13aZeQMBoz3aKEIyEy7e+PwvH3cLSoXTiXw1ZXPnzhbsUoAZaHQx i4fw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:to:cc:references:from :message-id:disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=jbhkSKUr1rINeFGnp0MAmXnMMrIx5cnrPuddCB78iPs=; b=fx6lLrX4PbmTFBVhQw01WASROY+oYxdd7GFF36W29BpWBk1imBT0VusZaW2xsaPuts sgx4nh+ihOjqPESWic5OXmB4FCp5iWwVMGbNPXA1O3cAAhVrSg/vo+0qvEXjk02/uWxU P0WlTz+v1G5AlCU8SUDW6KHsbksSI/43ryvWf5WAOZmAUH1MpU2rJZYjy8ZqIVqe4pre AqOJSDVFlN8DOtSmH0dbsxewIjH5KxPiQ3jn4s9r+V4Ktj160tHFTqE1uu3Iay94C7hr +uIiRabX33/EDsevulibFYUa2zDkbHluR24g72ZrpjrBF5MUbcxCEVtfrLrIPaL1V/xK 8X/w==
X-Gm-Message-State: AJaThX5IpTGTOnlnLwiN/JhbI6drqC++cd7QlW5PVq20o3hlQr9s+nEG SyfFPO+XbtxmMv2gPOkunvXdMA==
X-Google-Smtp-Source: AGs4zMZf6hNyryM4c+f54OE9TbWAWzCqyWWF6Itm7IMKcT+9hoFqRVIZ8WlxW8rP4L6d7Vo2OgmEQA==
X-Received: by 10.80.205.156 with SMTP id p28mr1941386edi.255.1511864473335; Tue, 28 Nov 2017 02:21:13 -0800 (PST)
Received: from McAsterix.local (g77189.upc-g.chello.nl. [80.57.77.189]) by smtp.gmail.com with ESMTPSA id w51sm4991500edd.84.2017.11.28.02.21.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Nov 2017 02:21:12 -0800 (PST)
Reply-To: huubatwork@gmail.com
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
To: Benoit Claise <bclaise@cisco.com>, Greg Mirsky <gregimirsky@gmail.com>, Qin Wu <bill.wu@huawei.com>, "iesg@ietf.org" <iesg@ietf.org>
Cc: Carlos Pignataro <cpignata@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, Ron Bonica <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com> <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com>
From: Huub van Helvoort <huubatwork@gmail.com>
Message-ID: <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.com>
Date: Tue, 28 Nov 2017 11:21:42 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com>
Content-Type: text/html; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nWvLfgqkawF2jfEpSoVi_zlOptA>
X-Mailman-Approved-At: Tue, 28 Nov 2017 08:14:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 10:21:17 -0000

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hello Benoit,<br>
      <br>
      You reply:<br>
    </div>
    <blockquote type="cite"
      cite="mid:0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div class="moz-cite-prefix">For your information, the document is
        now in the RFC editor queue, ready to be published.<br>
        <a class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/"
          moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/</a><br>
      </div>
    </blockquote>
    I had not seen any response from the authors to the email from Greg<br>
    (I checked the archive) so I assumed that the issue was still being<br>
    discussed. <br>
    Other on-line comments were addressed by the authors.<br>
    <br>
    I also checked for updates to version 18, but did not find any, so I<br>
    don't know how the issue has been resolved.<br>
    <br>
    So now I have to wait until the RFC is published.<br>
    <br>
    Regards, Huub.<br>
    <br>
    =========<br>
    <br>
    <blockquote type="cite"
      cite="mid:0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com">
      <blockquote type="cite"
        cite="mid:499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com">
        <meta http-equiv="Content-Type" content="text/html;
          charset=utf-8">
        <div class="moz-cite-prefix">Hello Greg,<br>
          <br>
          I agree with you that the current (version 18) text in section
          3.3 is very confusing.<br>
          <br>
          Authors:<br>
          <br>
          If I look at the definition of TP in section 2.2 I think a TP
          is similar<br>
          to a maintenance point as defined for Ethernet. Am I correct?<br>
          <br>
          I don't understand why there are TPs with no neighboring TPs,<br>
          where will their initiated OAM test be sent? Or where are OAM<br>
          tests they react to initiated?<br>
          <br>
          It is IMHO also possible that there are TPs with a neighboring
          <br>
          TP before AND a neighboring TP after the current TP.<br>
          <br>
          Please explain.<br>
          <br>
          Regards, Huub.<br>
          <br>
          ---------<br>
          <br>
        </div>
        <blockquote type="cite"
cite="mid:CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com">
          <div dir="ltr">Dear All,
            <div>I was under impression that that question of <span
                style="color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-tps</span><span
                style="color:rgb(0,0,0);font-size:13.3333px"> has been
                discussed and since authors couldn't produce technical
                rationale for this object we've agreed that it will be
                removed altogether from the </span><span
                style="color:rgb(0,0,0);font-size:13.3333px">grouping
                connectionless-oam-tps. But authors just changed name
                from level to position but had missed to synchronize
                descriptions in the model and in section 3.3. The later
                still refers to vertical layers:</span></div>
            <div>
              <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">                     "List of related neighboring test points in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.";
</pre>
            </div>
            <div>while the model insists that it is peering
              relationship:</div>
            <div>
              <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">        description
          "The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current
</pre>
            </div>
            <div>
              <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">           test point in the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.";
</pre>
            </div>
            <div>So, what is it? Perhaps it is time to remove list <span
                style="color:rgb(0,0,0);font-size:13.3333px">oam-neighboring-tps
                altogether also because having it s fixed size list is
                plain wrong. (Sorry for being so blunt but I commented
                too many times on the same to no avail from the
                authors).</span></div>
            <div><span style="color:rgb(0,0,0);font-size:13.3333px"><br>
              </span></div>
            <div><span style="color:rgb(0,0,0);font-size:13.3333px">Regards,</span></div>
            <div><span style="color:rgb(0,0,0);font-size:13.3333px">Greg</span></div>
          </div>
        </blockquote>
        <p><br>
        </p>
        <pre class="moz-signature" cols="72">-- 
================================================================
Always remember that you are unique...just like everyone else...</pre>
        . </blockquote>
      <br>
    </blockquote>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
================================================================
Always remember that you are unique...just like everyone else...</pre>
  </body>
</html>


From nobody Tue Nov 28 08:15:17 2017
Return-Path: <cpignata@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 B18D212878D; Tue, 28 Nov 2017 04:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level: 
X-Spam-Status: No, score=-14.519 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, 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 nSBIaVx56V8q; Tue, 28 Nov 2017 04:04:54 -0800 (PST)
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 5831A120725; Tue, 28 Nov 2017 04:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15706; q=dns/txt; s=iport; t=1511870694; x=1513080294; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=9BUxHzr9siSRy1xN9BDxPAmXk61xh4K+WvCr78F2gWw=; b=Lka7aqaRaTOCamS05OVPcb8Z3PAF8T0PdzwZ4CeDupfNQ2WHctsBLK1q Y4bbBvZrowf7SfHc1xPD0kryPKi2KP0GWLpWtT/nr7NS8M0sFoc2Tag8h GF/cow4hJP0/b6xKVr8CLVbwmiBwOnrHsrOf3FG3+54rkh3re8aJGuv7M w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CnAACdUB1a/4MNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJKRC5mbicHg3iKII8WgVeJDohAhUoQggEKJ4UUAhqEZz8YAQE?= =?us-ascii?q?BAQEBAQEBax0LhSAGI08HEAIBCDsEAwICAh8RFBECBA4FiT5MAxUQA6dQgicmh?= =?us-ascii?q?wwNgz8BAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYM8ggmBVYFpKQuCd4JrRhiBHgU?= =?us-ascii?q?BEgEHgy0xgjIFkXmHMIhjPQKHcYghhHmCFoYNiyyMdzuIYAIRGQGBOQEfOWFbF?= =?us-ascii?q?W8VOioBgX6CUhwZgU53iCyBJIEUAQEB?=
X-IronPort-AV: E=Sophos; i="5.44,468,1505779200"; d="scan'208,217"; a="36824987"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Nov 2017 12:04:53 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id vASC4rRN003632 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 Nov 2017 12:04:53 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 28 Nov 2017 07:04:52 -0500
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1320.000; Tue, 28 Nov 2017 07:04:52 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "huubatwork@gmail.com" <huubatwork@gmail.com>
CC: "Benoit Claise (bclaise)" <bclaise@cisco.com>, Greg Mirsky <gregimirsky@gmail.com>, Qin Wu <bill.wu@huawei.com>, The IESG <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Ronald P. Bonica" <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
Thread-Topic: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
Thread-Index: AQHTQpaR7crx2zDS7kC2rAOW6lNAlKLrJSkAgAHYPQCABB9KAIACV92AgADF4YCAAKRDAIAA0fcAgBuah4CAGCTSAIAAld+AgAAuIgCAABzRAA==
Date: Tue, 28 Nov 2017 12:04:52 +0000
Message-ID: <646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com> <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com> <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.com>
In-Reply-To: <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.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.118.116.133]
Content-Type: multipart/alternative; boundary="_000_646B91602BBF45469163D6504A47C7D7ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lBjsUW7jpdlxCEnp4JRLfUTu2Wk>
X-Mailman-Approved-At: Tue, 28 Nov 2017 08:14:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 12:05:03 -0000

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

SGVsbG8sIEh1dWIsDQoNCkFkZGl0aW9uYWxseSwgcGxlYXNlIHNlZSBodHRwczovL3d3dy5pZXRm
Lm9yZy9yZmNkaWZmP3VybDE9ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2Ft
LTE3JnVybDI9ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2FtLTE4LCB3aGlj
aCBzaG93cyB0aGUgY2hhbmdlcyByZWxldmFudCB0byB0aGF0IHNwZWNpZmljIGNvbW1lbnQuDQoN
CkkgYmVsaWV2ZSB0aGUgYXV0aG9ycyBhcmUgdXNpbmcgdGV4dCBzdWdnZXN0ZWQgYnkgR3JlZy4N
Cg0KTGlrZSBCZW5vaXQgc2FpZCwgdGhlIGRvY3VtZW50IGlzIGFwcHJvdmVkIGFuZCBpbiB0aGUg
UkZDIEVkaXRvciBxdWV1ZToNCmh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cv
bGltZS9xeWhLd0ZrRTRWQjlIQTBTMDR0T1dQREZLOVENCg0KQmVzdCwNCg0K4oCUDQpDYXJsb3Mg
UGlnbmF0YXJvLCBjYXJsb3NAY2lzY28uY29tPG1haWx0bzpjYXJsb3NAY2lzY28uY29tPg0KDQri
gJxTb21ldGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQgSSBkbyBub3QgZnVsbHkgdW5kZXJzdGFu
ZCwgdG8gbWFrZSBteXNlbGYgc291bmQgbW9yZSBwaG90b3N5bnRoZXNpcy4iDQoNCk9uIE5vdiAy
OCwgMjAxNywgYXQgNToyMSBBTSwgSHV1YiB2YW4gSGVsdm9vcnQgPGh1dWJhdHdvcmtAZ21haWwu
Y29tPG1haWx0bzpodXViYXR3b3JrQGdtYWlsLmNvbT4+IHdyb3RlOg0KDQpIZWxsbyBCZW5vaXQs
DQoNCllvdSByZXBseToNCkZvciB5b3VyIGluZm9ybWF0aW9uLCB0aGUgZG9jdW1lbnQgaXMgbm93
IGluIHRoZSBSRkMgZWRpdG9yIHF1ZXVlLCByZWFkeSB0byBiZSBwdWJsaXNoZWQuDQpodHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWxpbWUteWFuZy1jb25uZWN0aW9u
bGVzcy1vYW0vDQpJIGhhZCBub3Qgc2VlbiBhbnkgcmVzcG9uc2UgZnJvbSB0aGUgYXV0aG9ycyB0
byB0aGUgZW1haWwgZnJvbSBHcmVnDQooSSBjaGVja2VkIHRoZSBhcmNoaXZlKSBzbyBJIGFzc3Vt
ZWQgdGhhdCB0aGUgaXNzdWUgd2FzIHN0aWxsIGJlaW5nDQpkaXNjdXNzZWQuDQpPdGhlciBvbi1s
aW5lIGNvbW1lbnRzIHdlcmUgYWRkcmVzc2VkIGJ5IHRoZSBhdXRob3JzLg0KDQpJIGFsc28gY2hl
Y2tlZCBmb3IgdXBkYXRlcyB0byB2ZXJzaW9uIDE4LCBidXQgZGlkIG5vdCBmaW5kIGFueSwgc28g
SQ0KZG9uJ3Qga25vdyBob3cgdGhlIGlzc3VlIGhhcyBiZWVuIHJlc29sdmVkLg0KDQpTbyBub3cg
SSBoYXZlIHRvIHdhaXQgdW50aWwgdGhlIFJGQyBpcyBwdWJsaXNoZWQuDQoNClJlZ2FyZHMsIEh1
dWIuDQoNCj09PT09PT09PQ0KDQpIZWxsbyBHcmVnLA0KDQpJIGFncmVlIHdpdGggeW91IHRoYXQg
dGhlIGN1cnJlbnQgKHZlcnNpb24gMTgpIHRleHQgaW4gc2VjdGlvbiAzLjMgaXMgdmVyeSBjb25m
dXNpbmcuDQoNCkF1dGhvcnM6DQoNCklmIEkgbG9vayBhdCB0aGUgZGVmaW5pdGlvbiBvZiBUUCBp
biBzZWN0aW9uIDIuMiBJIHRoaW5rIGEgVFAgaXMgc2ltaWxhcg0KdG8gYSBtYWludGVuYW5jZSBw
b2ludCBhcyBkZWZpbmVkIGZvciBFdGhlcm5ldC4gQW0gSSBjb3JyZWN0Pw0KDQpJIGRvbid0IHVu
ZGVyc3RhbmQgd2h5IHRoZXJlIGFyZSBUUHMgd2l0aCBubyBuZWlnaGJvcmluZyBUUHMsDQp3aGVy
ZSB3aWxsIHRoZWlyIGluaXRpYXRlZCBPQU0gdGVzdCBiZSBzZW50PyBPciB3aGVyZSBhcmUgT0FN
DQp0ZXN0cyB0aGV5IHJlYWN0IHRvIGluaXRpYXRlZD8NCg0KSXQgaXMgSU1ITyBhbHNvIHBvc3Np
YmxlIHRoYXQgdGhlcmUgYXJlIFRQcyB3aXRoIGEgbmVpZ2hib3JpbmcNClRQIGJlZm9yZSBBTkQg
YSBuZWlnaGJvcmluZyBUUCBhZnRlciB0aGUgY3VycmVudCBUUC4NCg0KUGxlYXNlIGV4cGxhaW4u
DQoNClJlZ2FyZHMsIEh1dWIuDQoNCi0tLS0tLS0tLQ0KDQpEZWFyIEFsbCwNCkkgd2FzIHVuZGVy
IGltcHJlc3Npb24gdGhhdCB0aGF0IHF1ZXN0aW9uIG9mIG9hbS1uZWlnaGJvcmluZy10cHMgaGFz
IGJlZW4gZGlzY3Vzc2VkIGFuZCBzaW5jZSBhdXRob3JzIGNvdWxkbid0IHByb2R1Y2UgdGVjaG5p
Y2FsIHJhdGlvbmFsZSBmb3IgdGhpcyBvYmplY3Qgd2UndmUgYWdyZWVkIHRoYXQgaXQgd2lsbCBi
ZSByZW1vdmVkIGFsdG9nZXRoZXIgZnJvbSB0aGUgZ3JvdXBpbmcgY29ubmVjdGlvbmxlc3Mtb2Ft
LXRwcy4gQnV0IGF1dGhvcnMganVzdCBjaGFuZ2VkIG5hbWUgZnJvbSBsZXZlbCB0byBwb3NpdGlv
biBidXQgaGFkIG1pc3NlZCB0byBzeW5jaHJvbml6ZSBkZXNjcmlwdGlvbnMgaW4gdGhlIG1vZGVs
IGFuZCBpbiBzZWN0aW9uIDMuMy4gVGhlIGxhdGVyIHN0aWxsIHJlZmVycyB0byB2ZXJ0aWNhbCBs
YXllcnM6DQoNCiAgICAgICAgICAgICAgICAgICAgICJMaXN0IG9mIHJlbGF0ZWQgbmVpZ2hib3Jp
bmcgdGVzdCBwb2ludHMgaW4gYWRqYWNlbnQNCiAgICAgICAgICAgICAgICAgICAgIGxheWVycyB1
cCBhbmQgZG93biB0aGUgc3RhY2sgZm9yIHRoZSBzYW1lIGludGVyZmFjZQ0KICAgICAgICAgICAg
ICAgICAgICAgdGhhdCBhcmUgcmVsYXRlZCB0byB0aGUgY3VycmVudCB0ZXN0IHBvaW50LiI7DQoN
Cg0Kd2hpbGUgdGhlIG1vZGVsIGluc2lzdHMgdGhhdCBpdCBpcyBwZWVyaW5nIHJlbGF0aW9uc2hp
cDoNCg0KICAgICAgICBkZXNjcmlwdGlvbg0KICAgICAgICAgICJUaGUgcmVsYXRpdmUgcG9zaXRp
b24NCiAgICAgICAgICAgb2YgbmVpZ2hib3JpbmcgdGVzdCBwb2ludA0KICAgICAgICAgICBjb3Jy
ZXNwb25kaW5nIHRvIHRoZSBjdXJyZW50DQogICAgICAgICAgIHRlc3QgcG9pbnQuIExldmVsIDAg
aW5kaWNhdGVzIG5vIG5laWdoYm9yaW5nDQogICAgICAgICAgIHRlc3QgcG9pbnRzIHBsYWNlZCBi
ZWZvcmUgb3IgYWZ0ZXIgdGhlIGN1cnJlbnQNCg0KDQogICAgICAgICAgIHRlc3QgcG9pbnQgaW4g
dGhlIHNhbWUgbGF5ZXIuLTEgbWVhbnMgdGhlcmUgaXMNCiAgICAgICAgICAgYSBuZWlnaGJvcmlu
ZyB0ZXN0IHBvaW50IHBsYWNlZCBiZWZvcmUgdGhlIGN1cnJlbnQNCiAgICAgICAgICAgdGVzdCBw
b2ludCBpbiB0aGUgc2FtZSBsYXllciBhbmQgKzEgbWVhbnMgdGhlcmUgaXMNCiAgICAgICAgICAg
YSBuZWlnaGJvcmluZyB0ZXN0IHBvaW50IHBsYWNlZCBhZnRlciB0aGUgY3VycmVudA0KICAgICAg
ICAgICB0ZXN0IHBvaW50IGluIHNhbWUgbGF5ZXIuIjsNCg0KDQpTbywgd2hhdCBpcyBpdD8gUGVy
aGFwcyBpdCBpcyB0aW1lIHRvIHJlbW92ZSBsaXN0IG9hbS1uZWlnaGJvcmluZy10cHMgYWx0b2dl
dGhlciBhbHNvIGJlY2F1c2UgaGF2aW5nIGl0IHMgZml4ZWQgc2l6ZSBsaXN0IGlzIHBsYWluIHdy
b25nLiAoU29ycnkgZm9yIGJlaW5nIHNvIGJsdW50IGJ1dCBJIGNvbW1lbnRlZCB0b28gbWFueSB0
aW1lcyBvbiB0aGUgc2FtZSB0byBubyBhdmFpbCBmcm9tIHRoZSBhdXRob3JzKS4NCg0KUmVnYXJk
cywNCkdyZWcNCg0KDQotLQ0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PQ0KQWx3YXlzIHJlbWVtYmVyIHRoYXQgeW91IGFyZSB1
bmlxdWUuLi5qdXN0IGxpa2UgZXZlcnlvbmUgZWxzZS4uLg0KDQouDQoNCg0KDQotLQ0KPT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PQ0KQWx3YXlzIHJlbWVtYmVyIHRoYXQgeW91IGFyZSB1bmlxdWUuLi5qdXN0IGxpa2UgZXZlcnlv
bmUgZWxzZS4uLg0KDQo=

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

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCkhlbGxvLCBIdXViLA0KPGRpdiBjbGFzcz0iIj48
YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+QWRkaXRpb25hbGx5LCBwbGVhc2Ug
c2VlJm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwxPWRyYWZ0
LWlldGYtbGltZS15YW5nLWNvbm5lY3Rpb25sZXNzLW9hbS0xNyZhbXA7dXJsMj1kcmFmdC1pZXRm
LWxpbWUteWFuZy1jb25uZWN0aW9ubGVzcy1vYW0tMTgiIGNsYXNzPSIiPmh0dHBzOi8vd3d3Lmll
dGYub3JnL3JmY2RpZmY/dXJsMT1kcmFmdC1pZXRmLWxpbWUteWFuZy1jb25uZWN0aW9ubGVzcy1v
YW0tMTcmYW1wO3VybDI9ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2FtLTE4
PC9hPiwNCiB3aGljaCBzaG93cyB0aGUgY2hhbmdlcyByZWxldmFudCB0byB0aGF0IHNwZWNpZmlj
IGNvbW1lbnQuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRp
diBjbGFzcz0iIj5JIGJlbGlldmUgdGhlIGF1dGhvcnMgYXJlIHVzaW5nIHRleHQgc3VnZ2VzdGVk
IGJ5IEdyZWcuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRp
diBjbGFzcz0iIj5MaWtlIEJlbm9pdCBzYWlkLCB0aGUgZG9jdW1lbnQgaXMgYXBwcm92ZWQgYW5k
IGluIHRoZSBSRkMgRWRpdG9yIHF1ZXVlOjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YSBocmVmPSJo
dHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2xpbWUvcXloS3dGa0U0VkI5SEEw
UzA0dE9XUERGSzlRIiBjbGFzcz0iIj5odHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gv
bXNnL2xpbWUvcXloS3dGa0U0VkI5SEEwUzA0dE9XUERGSzlRPC9hPjwvZGl2Pg0KPGRpdiBjbGFz
cz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+QmVzdCw8L2Rpdj4NCjxk
aXYgY2xhc3M9IiI+Jm5ic3A7PGJyIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgc3R5
bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7IGxldHRlci1zcGFjaW5nOiBub3JtYWw7IHRleHQtYWxp
Z246IHN0YXJ0OyB0ZXh0LWluZGVudDogMHB4OyB0ZXh0LXRyYW5zZm9ybTogbm9uZTsgd2hpdGUt
c3BhY2U6IG5vcm1hbDsgd29yZC1zcGFjaW5nOiAwcHg7IC13ZWJraXQtdGV4dC1zdHJva2Utd2lk
dGg6IDBweDsgd29yZC13cmFwOiBicmVhay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7
IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCuKAlDxi
ciBjbGFzcz0iIj4NCkNhcmxvcyBQaWduYXRhcm8sJm5ic3A7PGEgaHJlZj0ibWFpbHRvOmNhcmxv
c0BjaXNjby5jb20iIGNsYXNzPSIiPmNhcmxvc0BjaXNjby5jb208L2E+PGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KPGkgY2xhc3M9IiI+4oCcU29tZXRpbWVzIEkgdXNlIGJpZyB3b3JkcyB0
aGF0IEkgZG8gbm90IGZ1bGx5IHVuZGVyc3RhbmQsIHRvIG1ha2UgbXlzZWxmIHNvdW5kIG1vcmUg
cGhvdG9zeW50aGVzaXMuJnF1b3Q7PC9pPjwvZGl2Pg0KPC9kaXY+DQo8ZGl2PjxiciBjbGFzcz0i
Ij4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj5PbiBO
b3YgMjgsIDIwMTcsIGF0IDU6MjEgQU0sIEh1dWIgdmFuIEhlbHZvb3J0ICZsdDs8YSBocmVmPSJt
YWlsdG86aHV1YmF0d29ya0BnbWFpbC5jb20iIGNsYXNzPSIiPmh1dWJhdHdvcmtAZ21haWwuY29t
PC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIgY2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5ld2xp
bmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYgdGV4dD0iIzAwMDAwMCIgYmdjb2xvcj0iI0ZGRkZG
RiIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSJtb3otY2l0ZS1wcmVmaXgiPkhlbGxvIEJlbm9pdCw8
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpZb3UgcmVwbHk6PGJyIGNsYXNzPSIiPg0KPC9k
aXY+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIiBjaXRlPSJtaWQ6MDg4OGUyZDYtZjM5Zi0xNjgz
LWIxNzQtNWUzZDE5ZGYxZWFlQGNpc2NvLmNvbSIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSJtb3ot
Y2l0ZS1wcmVmaXgiPkZvciB5b3VyIGluZm9ybWF0aW9uLCB0aGUgZG9jdW1lbnQgaXMgbm93IGlu
IHRoZSBSRkMgZWRpdG9yIHF1ZXVlLCByZWFkeSB0byBiZSBwdWJsaXNoZWQuPGJyIGNsYXNzPSIi
Pg0KPGEgY2xhc3M9Im1vei10eHQtbGluay1mcmVldGV4dCIgaHJlZj0iaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2Ft
LyIgbW96LWRvLW5vdC1zZW5kPSJ0cnVlIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1pZXRmLWxpbWUteWFuZy1jb25uZWN0aW9ubGVzcy1vYW0vPC9hPjxiciBjbGFzcz0i
Ij4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KSSBoYWQgbm90IHNlZW4gYW55IHJlc3BvbnNlIGZy
b20gdGhlIGF1dGhvcnMgdG8gdGhlIGVtYWlsIGZyb20gR3JlZzxiciBjbGFzcz0iIj4NCihJIGNo
ZWNrZWQgdGhlIGFyY2hpdmUpIHNvIEkgYXNzdW1lZCB0aGF0IHRoZSBpc3N1ZSB3YXMgc3RpbGwg
YmVpbmc8YnIgY2xhc3M9IiI+DQpkaXNjdXNzZWQuIDxiciBjbGFzcz0iIj4NCk90aGVyIG9uLWxp
bmUgY29tbWVudHMgd2VyZSBhZGRyZXNzZWQgYnkgdGhlIGF1dGhvcnMuPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KSSBhbHNvIGNoZWNrZWQgZm9yIHVwZGF0ZXMgdG8gdmVyc2lvbiAxOCwg
YnV0IGRpZCBub3QgZmluZCBhbnksIHNvIEk8YnIgY2xhc3M9IiI+DQpkb24ndCBrbm93IGhvdyB0
aGUgaXNzdWUgaGFzIGJlZW4gcmVzb2x2ZWQuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0K
U28gbm93IEkgaGF2ZSB0byB3YWl0IHVudGlsIHRoZSBSRkMgaXMgcHVibGlzaGVkLjxiciBjbGFz
cz0iIj4NCjxiciBjbGFzcz0iIj4NClJlZ2FyZHMsIEh1dWIuPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KPT09PT09PT09PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KPGJsb2NrcXVv
dGUgdHlwZT0iY2l0ZSIgY2l0ZT0ibWlkOjA4ODhlMmQ2LWYzOWYtMTY4My1iMTc0LTVlM2QxOWRm
MWVhZUBjaXNjby5jb20iIGNsYXNzPSIiPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2l0ZT0i
bWlkOjQ5OWU4ZGMwLWZjYWMtYTNhOS1lM2FlLTYzMDY5MWI3MGJjNEBnbWFpbC5jb20iIGNsYXNz
PSIiPg0KPGRpdiBjbGFzcz0ibW96LWNpdGUtcHJlZml4Ij5IZWxsbyBHcmVnLDxiciBjbGFzcz0i
Ij4NCjxiciBjbGFzcz0iIj4NCkkgYWdyZWUgd2l0aCB5b3UgdGhhdCB0aGUgY3VycmVudCAodmVy
c2lvbiAxOCkgdGV4dCBpbiBzZWN0aW9uIDMuMyBpcyB2ZXJ5IGNvbmZ1c2luZy48YnIgY2xhc3M9
IiI+DQo8YnIgY2xhc3M9IiI+DQpBdXRob3JzOjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
CklmIEkgbG9vayBhdCB0aGUgZGVmaW5pdGlvbiBvZiBUUCBpbiBzZWN0aW9uIDIuMiBJIHRoaW5r
IGEgVFAgaXMgc2ltaWxhcjxiciBjbGFzcz0iIj4NCnRvIGEgbWFpbnRlbmFuY2UgcG9pbnQgYXMg
ZGVmaW5lZCBmb3IgRXRoZXJuZXQuIEFtIEkgY29ycmVjdD88YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQpJIGRvbid0IHVuZGVyc3RhbmQgd2h5IHRoZXJlIGFyZSBUUHMgd2l0aCBubyBuZWln
aGJvcmluZyBUUHMsPGJyIGNsYXNzPSIiPg0Kd2hlcmUgd2lsbCB0aGVpciBpbml0aWF0ZWQgT0FN
IHRlc3QgYmUgc2VudD8gT3Igd2hlcmUgYXJlIE9BTTxiciBjbGFzcz0iIj4NCnRlc3RzIHRoZXkg
cmVhY3QgdG8gaW5pdGlhdGVkPzxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkl0IGlzIElN
SE8gYWxzbyBwb3NzaWJsZSB0aGF0IHRoZXJlIGFyZSBUUHMgd2l0aCBhIG5laWdoYm9yaW5nIDxi
ciBjbGFzcz0iIj4NClRQIGJlZm9yZSBBTkQgYSBuZWlnaGJvcmluZyBUUCBhZnRlciB0aGUgY3Vy
cmVudCBUUC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpQbGVhc2UgZXhwbGFpbi48YnIg
Y2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpSZWdhcmRzLCBIdXViLjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCi0tLS0tLS0tLTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjwvZGl2
Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2l0ZT0ibWlkOkNBJiM0MztSeUJtWHNFNldIRVdC
YjRSZVlOM082enROVEZaNG5HLVlPQnZ4alF2Y2t4Yz1YSFFAbWFpbC5nbWFpbC5jb20iIGNsYXNz
PSIiPg0KPGRpdiBkaXI9Imx0ciIgY2xhc3M9IiI+RGVhciBBbGwsDQo8ZGl2IGNsYXNzPSIiPkkg
d2FzIHVuZGVyIGltcHJlc3Npb24gdGhhdCB0aGF0IHF1ZXN0aW9uIG9mJm5ic3A7PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTogMTMuMzMzM3B4OyIgY2xhc3M9IiI+b2FtLW5laWdoYm9yaW5nLXRwczwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMy4zMzMzcHg7IiBjbGFzcz0iIj4mbmJzcDto
YXMgYmVlbiBkaXNjdXNzZWQgYW5kIHNpbmNlIGF1dGhvcnMgY291bGRuJ3QgcHJvZHVjZSB0ZWNo
bmljYWwgcmF0aW9uYWxlIGZvciB0aGlzDQogb2JqZWN0IHdlJ3ZlIGFncmVlZCB0aGF0IGl0IHdp
bGwgYmUgcmVtb3ZlZCBhbHRvZ2V0aGVyIGZyb20gdGhlJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6IDEzLjMzMzNweDsiIGNsYXNzPSIiPmdyb3VwaW5nIGNvbm5lY3Rpb25sZXNz
LW9hbS10cHMuIEJ1dCBhdXRob3JzIGp1c3QgY2hhbmdlZCBuYW1lIGZyb20gbGV2ZWwgdG8gcG9z
aXRpb24gYnV0IGhhZCBtaXNzZWQgdG8gc3luY2hyb25pemUgZGVzY3JpcHRpb25zIGluIHRoZSBt
b2RlbA0KIGFuZCBpbiBzZWN0aW9uIDMuMy4gVGhlIGxhdGVyIHN0aWxsIHJlZmVycyB0byB2ZXJ0
aWNhbCBsYXllcnM6PC9zcGFuPjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj4NCjxwcmUgY2xhc3M9Imdt
YWlsLW5ld3BhZ2UiIHN0eWxlPSJmb250LXNpemU6IDEzLjMzMzNweDsgbWFyZ2luLXRvcDogMHB4
OyBtYXJnaW4tYm90dG9tOiAwcHg7Ij4gICAgICAgICAgICAgICAgICAgICAmcXVvdDtMaXN0IG9m
IHJlbGF0ZWQgbmVpZ2hib3JpbmcgdGVzdCBwb2ludHMgaW4gYWRqYWNlbnQNCiAgICAgICAgICAg
ICAgICAgICAgIGxheWVycyB1cCBhbmQgZG93biB0aGUgc3RhY2sgZm9yIHRoZSBzYW1lIGludGVy
ZmFjZQ0KICAgICAgICAgICAgICAgICAgICAgdGhhdCBhcmUgcmVsYXRlZCB0byB0aGUgY3VycmVu
dCB0ZXN0IHBvaW50LiZxdW90OzsNCjwvcHJlPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPndoaWxl
IHRoZSBtb2RlbCBpbnNpc3RzIHRoYXQgaXQgaXMgcGVlcmluZyByZWxhdGlvbnNoaXA6PC9kaXY+
DQo8ZGl2IGNsYXNzPSIiPg0KPHByZSBjbGFzcz0iZ21haWwtbmV3cGFnZSIgc3R5bGU9ImZvbnQt
c2l6ZTogMTMuMzMzM3B4OyBtYXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsiPiAg
ICAgICAgZGVzY3JpcHRpb24NCiAgICAgICAgICAmcXVvdDtUaGUgcmVsYXRpdmUgcG9zaXRpb24N
CiAgICAgICAgICAgb2YgbmVpZ2hib3JpbmcgdGVzdCBwb2ludA0KICAgICAgICAgICBjb3JyZXNw
b25kaW5nIHRvIHRoZSBjdXJyZW50DQogICAgICAgICAgIHRlc3QgcG9pbnQuIExldmVsIDAgaW5k
aWNhdGVzIG5vIG5laWdoYm9yaW5nDQogICAgICAgICAgIHRlc3QgcG9pbnRzIHBsYWNlZCBiZWZv
cmUgb3IgYWZ0ZXIgdGhlIGN1cnJlbnQNCjwvcHJlPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPg0K
PHByZSBjbGFzcz0iZ21haWwtbmV3cGFnZSIgc3R5bGU9ImZvbnQtc2l6ZTogMTMuMzMzM3B4OyBt
YXJnaW4tdG9wOiAwcHg7IG1hcmdpbi1ib3R0b206IDBweDsiPiAgICAgICAgICAgdGVzdCBwb2lu
dCBpbiB0aGUgc2FtZSBsYXllci4tMSBtZWFucyB0aGVyZSBpcw0KICAgICAgICAgICBhIG5laWdo
Ym9yaW5nIHRlc3QgcG9pbnQgcGxhY2VkIGJlZm9yZSB0aGUgY3VycmVudA0KICAgICAgICAgICB0
ZXN0IHBvaW50IGluIHRoZSBzYW1lIGxheWVyIGFuZCAmIzQzOzEgbWVhbnMgdGhlcmUgaXMNCiAg
ICAgICAgICAgYSBuZWlnaGJvcmluZyB0ZXN0IHBvaW50IHBsYWNlZCBhZnRlciB0aGUgY3VycmVu
dA0KICAgICAgICAgICB0ZXN0IHBvaW50IGluIHNhbWUgbGF5ZXIuJnF1b3Q7Ow0KPC9wcmU+DQo8
L2Rpdj4NCjxkaXYgY2xhc3M9IiI+U28sIHdoYXQgaXMgaXQ/IFBlcmhhcHMgaXQgaXMgdGltZSB0
byByZW1vdmUgbGlzdCZuYnNwOzxzcGFuIHN0eWxlPSJmb250LXNpemU6IDEzLjMzMzNweDsiIGNs
YXNzPSIiPm9hbS1uZWlnaGJvcmluZy10cHMgYWx0b2dldGhlciBhbHNvIGJlY2F1c2UgaGF2aW5n
IGl0IHMgZml4ZWQgc2l6ZSBsaXN0IGlzIHBsYWluIHdyb25nLiAoU29ycnkgZm9yIGJlaW5nIHNv
IGJsdW50IGJ1dCBJIGNvbW1lbnRlZCB0b28gbWFueSB0aW1lcyBvbg0KIHRoZSBzYW1lIHRvIG5v
IGF2YWlsIGZyb20gdGhlIGF1dGhvcnMpLjwvc3Bhbj48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZTogMTMuMzMzM3B4OyIgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0K
PC9zcGFuPjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMy4z
MzMzcHg7IiBjbGFzcz0iIj5SZWdhcmRzLDwvc3Bhbj48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZTogMTMuMzMzM3B4OyIgY2xhc3M9IiI+R3JlZzwvc3Bhbj48L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9w
Pg0KPHByZSBjbGFzcz0ibW96LXNpZ25hdHVyZSIgY29scz0iNzIiPi0tIA0KPT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KQWx3
YXlzIHJlbWVtYmVyIHRoYXQgeW91IGFyZSB1bmlxdWUuLi5qdXN0IGxpa2UgZXZlcnlvbmUgZWxz
ZS4uLjwvcHJlPg0KLiA8L2Jsb2NrcXVvdGU+DQo8YnIgY2xhc3M9IiI+DQo8L2Jsb2NrcXVvdGU+
DQo8cCBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L3A+DQo8cHJlIGNsYXNzPSJtb3otc2lnbmF0
dXJlIiBjb2xzPSI3MiI+LS0gDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpBbHdheXMgcmVtZW1iZXIgdGhhdCB5b3UgYXJl
IHVuaXF1ZS4uLmp1c3QgbGlrZSBldmVyeW9uZSBlbHNlLi4uPC9wcmU+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvYm9keT4N
CjwvaHRtbD4NCg==

--_000_646B91602BBF45469163D6504A47C7D7ciscocom_--


From nobody Tue Nov 28 08:16:55 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 57857128B51 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 yb6ePD-hxApw for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:16:50 -0800 (PST)
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 3CE851286B1 for <ietf@ietf.org>; Tue, 28 Nov 2017 08:16:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2410; q=dns/txt; s=iport; t=1511885803; x=1513095403; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=fIJ48f3p4Grv4FdFsqrvdCnAymd6yrk9/ObXnWPDxHA=; b=ck9yT/ZghCuK26+wP1JA2SuMljt+si0B2oYtm/8EPqfM0DiymzARSxN4 /FwlirA7QXFwi1gPfwfaPoELOo1VU+l5x5t786aDx1unrUaKBwqLgGc1l 89gafAFKNYkuHc3qyvPRfTtNgGw2R0gO/ArAIpK+Rm6iwR1v7oZ+Hf13U Q=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BxAQCSih1a/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYUQhCaLFJAglnKCEQcDhTsChUcWAQEBAQEBAQEBayiFIAEFIwR?= =?us-ascii?q?iCxgqAgJXBgEMCAEBih6nbYFtOop+AQEBAQEBAQMBAQEBAQEBEg+DPIVwgwKIN?= =?us-ascii?q?IJjBaJJhEmCKY4bgX2KCYdJlj+BOiUBMoFRMhoIGxWCZIRVQIsaAQEB?=
X-IronPort-AV: E=Sophos;i="5.44,468,1505779200"; d="asc'?scan'208";a="478200"
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; 28 Nov 2017 16:16:41 +0000
Received: from [10.61.205.15] ([10.61.205.15]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id vASGGfZN000486; Tue, 28 Nov 2017 16:16:41 GMT
Subject: Re: travelling home just before thanksgiving is hard
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net> <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com> <30894.1511883305@obiwan.sandelman.ca> <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie>
From: Eliot Lear <lear@cisco.com>
Message-ID: <ddfb8561-932a-3c7a-1bb5-89ee58a00a18@cisco.com>
Date: Tue, 28 Nov 2017 17:15:19 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="O9nrwfTxEqlWw0nWG2K90va35mVuCU2nT"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-bQeCkD_58PlYtGTo_KeJpKtnOs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 16:16:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--O9nrwfTxEqlWw0nWG2K90va35mVuCU2nT
Content-Type: multipart/mixed; boundary="8hoV5grFj3DEuUGtwTdTDXDgtsO9Dm6Ms";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>,
 Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
Message-ID: <ddfb8561-932a-3c7a-1bb5-89ee58a00a18@cisco.com>
Subject: Re: travelling home just before thanksgiving is hard
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net>
 <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net>
 <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com>
 <30894.1511883305@obiwan.sandelman.ca>
 <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie>
In-Reply-To: <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie>

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



On 11/28/17 5:09 PM, Stephen Farrell wrote:
>
> On 28/11/17 15:35, Michael Richardson wrote:
>> I'd like to see us work to reduce the demand for meeting time, and pul=
l the
>> hackathon and other "weekend" events into a Sunday->Thursday schedule.=

> +1
>

I'd go further: I'd like to see us work toward a 2 meeting per year
plenary schedule with mandatory virtual WG meetings at the other quarter
slots.=C2=A0 My logic is that there are many who really cannot afford to =
go
to all of these meetings, who nevertheless would like to participate.=C2=A0=

Some of them do virtually today, but always at a disadvantage to those
who can pay to play.

Eliot


--8hoV5grFj3DEuUGtwTdTDXDgtsO9Dm6Ms--

--O9nrwfTxEqlWw0nWG2K90va35mVuCU2nT
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

iQEcBAEBCAAGBQJaHYuXAAoJEIe2a0bZ0nozHCgH/1fZz5l4fOPrfUocXzky+XpV
UhwKEwduse6FLBPLSPVsxlGF3uAEqgmQTQrWnuugWyLWIkWE55lx3uzXQqCZl1Zw
qUkIfmG3GGFV8LLaghPfQqsaPyKnYzhmIQq9whyDTzsyjYYg+1LplM4DMYzSLt9T
M2A7DdyyQEYnhGLUPB7pCnp7rBiq7Gx1M00Ou/ZlyLv1SoNXJ2j7BQuFKF3rGhlf
qBO7IhalTzKHjc358/x6kHz4+hjScSCdZF3Dmg9Q9jWEXZ06kgFjz8D8wSURuOSr
cWn2p2veWpd++EpA+qVjMk+sg3lrfG2FYz/Kid2l5Z0SeRghD4VjiyABQfX1NrY=
=oP6Z
-----END PGP SIGNATURE-----

--O9nrwfTxEqlWw0nWG2K90va35mVuCU2nT--


From nobody Tue Nov 28 08:18:39 2017
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E27127517 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:18:38 -0800 (PST)
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, 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=lucidvision.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3AZkmvGy4O3U for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:18:37 -0800 (PST)
Received: from lucidvision.com (lucidab1.miniserver.com [78.31.106.147]) (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 A1E61126B72 for <ietf@ietf.org>; Tue, 28 Nov 2017 08:18:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucidvision.com; s=default; t=1511885766; bh=BV81ZhJH+1D0cR4lG2EL9WLVFVSSI6ANZKE4pu4oV7E=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=P6kVLoBtK3MSlG8TU1gUpQ8I8visiY9xD0hzX85WZOWp5JplU3qpSstyRIcwZvFpX b0BJRMgouYu0JjEJHqWnuSD+LHjMJBu4MYHPEsfCPIsS3+gdVAd0vZ//i60TA2vj6r 7RrTPju3cYe3Uh08RJbfJLI3PL6y7dpcYfyqbhyc=
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.255.148.181; 
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: travelling home just before thanksgiving is hard
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <ddfb8561-932a-3c7a-1bb5-89ee58a00a18@cisco.com>
Date: Tue, 28 Nov 2017 11:18:26 -0500
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <131EF8A8-4D7B-402A-A373-BB4C39618B38@lucidvision.com>
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net> <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com> <30894.1511883305@obiwan.sandelman.ca> <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie> <ddfb8561-932a-3c7a-1bb5-89ee58a00a18@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3445.4.7)
X-Authenticated-User: tnadeau@lucidvision.com 
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=0 Stars=0 Good=0 Friend=2 Surbl=0 Catch=0 r=0 ip=50.255.148.181
X-IP-stats: Notspam Incoming Last 0, First 928, in=7345, out=0, spam=0 Known=true ip=50.255.148.181
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/17gWYy3ZVmeujU5t7HGzNBJFxI0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 16:18:38 -0000

A big +1 to that.

> On Nov 28, 2017, at 11:15 AM, Eliot Lear <lear@cisco.com> wrote:
>=20
>=20
>=20
> On 11/28/17 5:09 PM, Stephen Farrell wrote:
>>=20
>> On 28/11/17 15:35, Michael Richardson wrote:
>>> I'd like to see us work to reduce the demand for meeting time, and =
pull the
>>> hackathon and other "weekend" events into a Sunday->Thursday =
schedule.
>> +1
>>=20
>=20
> I'd go further: I'd like to see us work toward a 2 meeting per year
> plenary schedule with mandatory virtual WG meetings at the other =
quarter
> slots.  My logic is that there are many who really cannot afford to go
> to all of these meetings, who nevertheless would like to participate.=20=

> Some of them do virtually today, but always at a disadvantage to those
> who can pay to play.
>=20
> Eliot
>=20


From nobody Tue Nov 28 08:21:15 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 AE0FC127B73 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:21:13 -0800 (PST)
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=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 u7ElFwwFwfZB for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:21:07 -0800 (PST)
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 27B671286B1 for <ietf@ietf.org>; Tue, 28 Nov 2017 08:21:07 -0800 (PST)
Received: from resomta-po-11v.sys.comcast.net ([96.114.154.235]) by resqmta-po-06v.sys.comcast.net with ESMTP id JicNeHnqoOB2XJid8eRjIJ; Tue, 28 Nov 2017 16:21:06 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1511886066; bh=XVlnFZUgabG/vtZJJHh20L8S93NZFxjHb8p2TfH0TWk=; h=Received:Received:To:From:Subject:Message-ID:Date:MIME-Version: Content-Type; b=V9vh9CbhwOFIRyRliU9fS9Rhp2NjGVdTBwt4C9bmkvXoD7r8/kFpSDawtQiQP8VvZ C6eQ+Z0ytYr0yyXtDEsC6sxTmqnQXdot0btIt0cpH/KomYux2hkTWuJNKyaNqtn4Lj pJISA8qtSOLCm/Ne1iSQXJEvn1RQKl/Gq9v/px9E4Cvm+eehqFqJ2qPK8euvvLcAPU jKQOledI66GnK/WbMcnCca70XKuSn8HHp3vJKlfrkvRerkU5l5vd6T9HEKTC8josvu a9H0O4Wso5BUT9OhICZsRZURrmqJzasyTOjM12EkXQJUrcxIZMx5+VCwl6BvaaQkGr LgrvEbccnXJVw==
Received: from [IPv6:2601:152:4400:720f::1005] ([IPv6:2601:152:4400:720f::1005]) by resomta-po-11v.sys.comcast.net with SMTP id Jid7eJ5GPsmO3Jid8eexs7; Tue, 28 Nov 2017 16:21:06 +0000
To: ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: ISOC Charity EMail
Message-ID: <b3d18909-af61-928f-0be7-8174ec6b7085@comcast.net>
Date: Tue, 28 Nov 2017 11:21:06 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfEg0gGnWlC6tkZn1pP1nxsDtAuWDOOsgeoCzoTu17FcvOhuNhzPXg8D7iqrPwjqLL1y2hjOCzadRnWKXV5Yi2avCv8b52LY6TPBSvWwp0OmZzJp/8qxd +tDqyKNRUDjxDKCiTCf7N9saYZ6ZKL8GG09FeHFuZ0wbke52lmGjvKb+
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_a2Y075Zh6QXbFRz9A15SKUCO5o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 16:21:14 -0000

Hi -

This morning I received a donation solicitation from ISOC entitled "Help 
connect the world".  What was interesting about it - from an IETF point 
of view - was that we were nowhere mentioned.  I got curious and clicked 
through (after checking the URL) to the donation page.  There we were 
mentioned in two words - "smart standards" in the FAQ about how the 
money will be spent.

AFAICT, I'm on the solicitation mailing list because of my donation to 
the IETF trust a while back.  If that's the case, I'm somewhat bothered 
that that list has been co-opted to be used as an ISOC source of 
potential donors.  I wouldn't mind so much if the IETF were prominently 
mentioned, or if the donations could be designated for the IETF but 
neither of these seem to be the case.

We've got another thread on the ISOC mission statement where the lack of 
a specific mention of the IETF in said mission statement has been noted.

These are disturbing trends.

Mike



From nobody Tue Nov 28 08:53:46 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 222741287A3 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJQJ8HJImFkt for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 08:53:37 -0800 (PST)
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 BE83C126DED for <ietf@ietf.org>; Tue, 28 Nov 2017 08:53:37 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eJj8W-0008Cc-71; Tue, 28 Nov 2017 11:53:32 -0500
Date: Tue, 28 Nov 2017 11:53:26 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>,  Michael Richardson <mcr+ietf@sandelman.ca>, ietf@ietf.org
Subject: Re: travelling home just before thanksgiving is hard
Message-ID: <AA3DF4A0EE474B4209F27ACF@PSB>
In-Reply-To: <ddfb8561-932a-3c7a-1bb5-89ee58a00a18@cisco.com>
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <cf7c7428-bd0b-7c02-c79b-f561afa93263@comcast.net> <499f2f93-628e-c494-1ea3-3197dc911f08@gmail.com> <30894.1511883305@obiwan.sandelman.ca> <cefbe298-56ee-e4f6-008f-03e75387f240@cs.tcd.ie> <ddfb8561-932a-3c7a-1bb5-89ee58a00a18@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
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/jV-X8WzaEJ4HvbDZcFKdvnHC5tk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 16:53:45 -0000

--On Tuesday, November 28, 2017 17:15 +0100 Eliot Lear
<lear@cisco.com> wrote:

> I'd go further: I'd like to see us work toward a 2 meeting per
> year plenary schedule with mandatory virtual WG meetings at
> the other quarter slots.=C2=A0 My logic is that there are many =
who
> really cannot afford to go to all of these meetings, who
> nevertheless would like to participate.=C2=A0 Some of them do
> virtually today, but always at a disadvantage to those who can
> pay to play.

I question "mandatory" -- a WG that is able to make adequate
progress by email should be able to do that, just as such as WG
can avoid meeting at the main IETF gatherings now -- but,
otherwise, as our remoote participation facilities get batter
and better (Thank you Meetecho and the Secretariat), that
definitely sounds to me like the right direction in which to go.

It is also not just about the money -- as things seem to be
becoming more and more specialized, it gets harder to justify
spending a week away from the "day job" in order to attend a
small number of WG sessions, a plenary (which could be sent out
remotely), a Thursday talk (ditto), and gather around assorted
real or virtual bars and water fountains.  Twice a year might be
enough for those things too.

best,
   john




From nobody Tue Nov 28 10:06:50 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 66CF4124239 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 10:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmktSio9jLe1 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 10:06:47 -0800 (PST)
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 2A7EF12420B for <ietf@ietf.org>; Tue, 28 Nov 2017 10:06:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by aws.hosed.org (Postfix) with ESMTP id 2654D8001B; Tue, 28 Nov 2017 13:06:46 -0500 (EST)
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 AvFhLZmFXKgk; Tue, 28 Nov 2017 13:06:46 -0500 (EST)
Received: from [10.200.134.147] (unknown [63.194.187.130]) by aws.hosed.org (Postfix) with ESMTPSA id AF8DF8001A; Tue, 28 Nov 2017 13:06:45 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: travelling home just before thanksgiving is hard
From: Sarah B <sbanks@encrypted.net>
In-Reply-To: <alpine.OSX.2.01.1711271506380.91054@ole-pro.local>
Date: Tue, 28 Nov 2017 10:06:38 -0800
Cc: Kent Watsen <kwatsen@juniper.net>, "ietf@ietf.org" <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E4123D9-C1A7-4FB7-BCC2-2A4FF25E3708@encrypted.net>
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <alpine.OSX.2.01.1711271506380.91054@ole-pro.local>
To: Ole Jacobsen <olejacobsen@me.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o8SGsKKjWLjekOYXdiygqPOHHF8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 18:06:48 -0000

I agree. The busiest days of the Thanksgiving week didn't start until =
the week days after; SFO was looking good when I flew in on Saturday at =
2pm. I connected through LAX and it too was no busier than normal; I =
didn't experience any "Thanksgiving rush" delays coming into the West =
Coast. (I DID have to get my morning cardio in, running from terminal 6 =
to 7, to connect, but that was a United fault, leaving Singapore an hour =
late). Perhaps looking at the schedule and leaving Thursday night, =
Friday afternoon, or late Friday night would help you for the last =
meetings of the year when they're that close to Thanksgiving, moving =
forward, or giving yourself more time to connect in the US?

/S

> On Nov 27, 2017, at 3:12 PM, Ole Jacobsen <olejacobsen@me.com> wrote:
>=20
>=20
> On Mon, 27 Nov 2017, Kent Watsen wrote:
>>=20
>> I had an awful experience travelling home from Singapore.  What was=20=

>> supposed to be 22-hours of travel became 40-hours.  Much of this was=20=

>> due to my US-based connecting airport being exceptionally busy,=20
>> related to this most-travelled holiday of the year, causing me to=20
>> miss my gate and not be able to get onto either of two standbys.
>>=20
>> Even if the travel-congestion were not an issue, there the secondary=20=

>> issue of coming home into an already short week.  Most US companies=20=

>> give Thursday and Friday off and many, including myself, take=20
>> Wednesday off as well (to travel to our Thanksgiving destinations). =20=

>> This leads the somewhat frantic situation of trying to catch-up on=20
>> email from the week before while clearing the way for the week=20
>> ahead.
>>=20
>> I understand that this is just an American holiday and that less=20
>> than half of the IETF are Americans but, if there is any discretion=20=

>> in the matter for future meetings, I would be exceptionally happy if=20=

>> the IETF made an effort to hold the 3rd-meeting of the year a week=20
>> earlier.
>>=20
>> Thanks,
>> Kent
>>=20
>=20
> Sorry to hear that too, but looking at the actual schedule, I would=20
> imagine you could have left Singapore as early as Saturday morning
> (or very late Friday night) which would get you to at least the West
> Coast by Saturday morning (local) and that *should* at least be=20
> several days before chaos broke out in the US. I would agree that we
> should avoid major holidays, but I'd say we mostly did in this=20
> particular case. Of course, as they say, "your mileage may vary."
>=20
> Ole


From nobody Tue Nov 28 10:29:02 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 A1AFC128B37; Tue, 28 Nov 2017 10:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 imMGTzqdrk_e; Tue, 28 Nov 2017 10:28:58 -0800 (PST)
Received: from sjc-alcoop-8816.cisco.com (unknown [128.107.241.191]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 0A33A128CFF; Tue, 28 Nov 2017 10:28:57 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F1A66DBD-34B9-41FD-8E3D-0BE7D2A7A7AF"
Subject: Call for feedback for the IAOC appointment by the IESG
Date: Tue, 28 Nov 2017 13:28:56 -0500
Message-Id: <4CE9FD91-CA89-4AC4-BD4D-7767D8EC21E1@ietf.org>
Cc: IETF Discussion <ietf@ietf.org>
To: IETF Announcement List <ietf-announce@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/wBb61q2djunkT2xIFUyQ0wHBFgI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 18:28:59 -0000

--Apple-Mail=_F1A66DBD-34B9-41FD-8E3D-0BE7D2A7A7AF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The IESG is responsible for filling one seat in the IAOC every other =
year.  Tobias Gondrom is the IAOC member that was appointed by the IESG, =
and his two-year term is up in March.  The IESG is in the process to =
fill this seat in March 2018, with the term ending in March 2020.

A call for nominations has been sent out.  The following candidates have =
accepted nominations:

o  Glenn Deen
o  Kathleen Moriarty
o  Michael Richardson

Kathleen Moriarty has been recused from the IESG=E2=80=99s deliberations =
on this since she is a nominee.

Please send feedback about the candidates to chair at ietf.org =
<http://ietf.org/>.  This feedback will be held in confidence by the =
IESG.  We thank you in advance for your help.  Please provide the =
feedback by December 12, 2017.

Best regards,
Alissa Cooper
IETF Chair=

--Apple-Mail=_F1A66DBD-34B9-41FD-8E3D-0BE7D2A7A7AF
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"">The IESG is responsible for filling one seat in the IAOC =
every other year. &nbsp;Tobias Gondrom is the IAOC member that was =
appointed by the IESG, and his two-year term is up in March. &nbsp;The =
IESG is in the process to fill this seat in March 2018, with the term =
ending in March 2020.<br class=3D""><br class=3D"">A call for =
nominations has been sent out. &nbsp;The following candidates have =
accepted nominations:<br class=3D""><br class=3D"">o &nbsp;Glenn Deen<br =
class=3D""><div class=3D"">o &nbsp;Kathleen Moriarty<br class=3D""><div =
class=3D"">o &nbsp;Michael Richardson<br class=3D""><br =
class=3D"">Kathleen Moriarty has been recused from the IESG=E2=80=99s =
deliberations on this since she is a nominee.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Please send feedback about the =
candidates to chair at&nbsp;<a href=3D"http://ietf.org" =
class=3D"">ietf.org</a>. &nbsp;This feedback will be held in confidence =
by the IESG. &nbsp;We thank you in advance for your help. &nbsp;Please =
provide the feedback by December 12, 2017.<br class=3D""><br =
class=3D"">Best regards,<br class=3D"">Alissa Cooper<br class=3D"">IETF =
Chair</div></div></body></html>=

--Apple-Mail=_F1A66DBD-34B9-41FD-8E3D-0BE7D2A7A7AF--


From nobody Tue Nov 28 10:54:32 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 A6173128B37 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 10:54:30 -0800 (PST)
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=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 mpPJk57TtiBG for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 10:54:29 -0800 (PST)
Received: from resqmta-po-12v.sys.comcast.net (resqmta-po-12v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:171]) (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 2492F1286CA for <ietf@ietf.org>; Tue, 28 Nov 2017 10:54:29 -0800 (PST)
Received: from resomta-po-13v.sys.comcast.net ([96.114.154.237]) by resqmta-po-12v.sys.comcast.net with ESMTP id Jl11e9q6d1SdmJl1YeC66J; Tue, 28 Nov 2017 18:54:28 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1511895268; bh=d3EqRyntagQUoTWECAIPXZ9fk82iBSKlfZ/PyPbjH30=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=JGtu6FAf1tv1oCEgKRS5Tv5DexQw/3ZOaafIJzURZ5ogD5CRoOdig0PK0noHn/i9v JZ5jpDGdvMzdAe5GTpV8R0pbQOuq1yQRMmrcJByFeA/gN52zXLZfl/BRxygZc0id9X Ivpz5GrYpnfIhY2DW8oQZL5kUOnaGfX02wjD3Cea0/cpOEIjXCQ3L8ezocggQE+rWM D3f6EfUXbUoTclz5fLGD9aHge6LTMhfWVg8nLWai5p1yhQOp2NsiP0nTObbHeXfG6h JzuhMSLeL49EkaxcZgdj9RPTAthN8Tx06wtegwjXC6gqrcpYL05BAuEr5Yg/g7wC+m 1+EazUotbVfkw==
Received: from [IPv6:2601:152:4400:720f::1005] ([IPv6:2601:152:4400:720f::1005]) by resomta-po-13v.sys.comcast.net with SMTP id Jl1Xe7y76q4RuJl1Ye33z4; Tue, 28 Nov 2017 18:54:28 +0000
Subject: Re: travelling home just before thanksgiving is hard
To: ietf@ietf.org
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <alpine.OSX.2.01.1711271506380.91054@ole-pro.local> <7E4123D9-C1A7-4FB7-BCC2-2A4FF25E3708@encrypted.net>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <52f237e0-d4da-f360-aca9-1c73a0fe0533@comcast.net>
Date: Tue, 28 Nov 2017 13:54:28 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <7E4123D9-C1A7-4FB7-BCC2-2A4FF25E3708@encrypted.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfDnxA0RLu4xGB9RbV8cKMXFircNwCH5oav6C5qGw/bKIXkBjW6zIhX2BovTa5Clu7funvP6yIswp+b/RPo0P7AKh6f5dphgMw/q5qaVHsFYcOq+GI0JR GjTj5r6NUfI6aqsgUirihup4r+G6CRbmVCQALsvgGAoLmMkj1XByFv6C
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z3TCNbMmiVp6HWvM2eecGtt7aLA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 18:54:31 -0000

On 11/28/2017 1:06 PM, Sarah B wrote:
> I agree. The busiest days of the Thanksgiving week didn't start until the week days after; SFO was looking good when I flew in on Saturday at 2pm. I connected through LAX and it too was no busier than normal; I didn't experience any "Thanksgiving rush" delays coming into the West Coast. (I DID have to get my morning cardio in, running from terminal 6 to 7, to connect, but that was a United fault, leaving Singapore an hour late). Perhaps looking at the schedule and leaving Thursday night, Friday afternoon, or late Friday night would help you for the last meetings of the year when they're that close to Thanksgiving, moving forward, or giving yourself more time to connect in the US?

I had that exact same flight and pretty close to the same cardio workout.

One of the things I noted about this trip was the extreme cost of 
flights on the return leg.  In my case, it was a return leg 2-3x the 
price of the outbound trip - so bad that I ended up using miles instead 
- and that was buying 3-4 months in advance.  For someone else, they 
ended up traveling on Monday for a $5000 reduction in a business class 
ticket over Thursday-Sunday prices.

I'm not sure how much of this was tied to US thanksgiving and a flood of 
ex-pats coming back into the country but I'm suspicious!

Mike

>
> /S
>
>> On Nov 27, 2017, at 3:12 PM, Ole Jacobsen <olejacobsen@me.com> wrote:
>>
>>
>> On Mon, 27 Nov 2017, Kent Watsen wrote:
>>> I had an awful experience travelling home from Singapore.  What was
>>> supposed to be 22-hours of travel became 40-hours.  Much of this was
>>> due to my US-based connecting airport being exceptionally busy,
>>> related to this most-travelled holiday of the year, causing me to
>>> miss my gate and not be able to get onto either of two standbys.
>>>
>>> Even if the travel-congestion were not an issue, there the secondary
>>> issue of coming home into an already short week.  Most US companies
>>> give Thursday and Friday off and many, including myself, take
>>> Wednesday off as well (to travel to our Thanksgiving destinations).
>>> This leads the somewhat frantic situation of trying to catch-up on
>>> email from the week before while clearing the way for the week
>>> ahead.
>>>
>>> I understand that this is just an American holiday and that less
>>> than half of the IETF are Americans but, if there is any discretion
>>> in the matter for future meetings, I would be exceptionally happy if
>>> the IETF made an effort to hold the 3rd-meeting of the year a week
>>> earlier.
>>>
>>> Thanks,
>>> Kent
>>>
>> Sorry to hear that too, but looking at the actual schedule, I would
>> imagine you could have left Singapore as early as Saturday morning
>> (or very late Friday night) which would get you to at least the West
>> Coast by Saturday morning (local) and that *should* at least be
>> several days before chaos broke out in the US. I would agree that we
>> should avoid major holidays, but I'd say we mostly did in this
>> particular case. Of course, as they say, "your mileage may vary."
>>
>> Ole



From nobody Tue Nov 28 10:59:51 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 D8522128CD5 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 10:59:49 -0800 (PST)
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=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 B0-xpMJx9vPt for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 10:59:48 -0800 (PST)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE7E4128B4E for <ietf@ietf.org>; Tue, 28 Nov 2017 10:59:48 -0800 (PST)
Received: from resomta-po-12v.sys.comcast.net ([96.114.154.236]) by resqmta-po-03v.sys.comcast.net with ESMTP id Jl6SelWLNVwMvJl6ieFQHN; Tue, 28 Nov 2017 18:59:48 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1511895588; bh=bTG7nf/Hs1nh15x+4VmisNtO+2vAKYjWp48YvxXz4h8=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=DSqoUBlmZ1z+IvtvzwKp5d9PWtsx6DFG9p+8fqxNESvK1UEDbW4ZdPjl2A3p/lkeN RcwpyN7izsfHufu0PY8vTlnkbkKfiNgSKK97NbpSdJ/0yCR6pSb2phzlmAaqNTwWGd WJ/SLCSLGnNUhemb0OqFO7TPUZ65mRRtUGlQeBafmHczwL42Ri1YakDuebs858zPsY bVEZ6nj14oPPXKOgvozRpr2759SG7PJCCnpBQ5VVhjBXLwAJ15HC2rvAm4fmw9UmwP 3yOKuMtht9O5hpWaWXm6CKjguAGBVXkK/j9en+rqAbVFruPMWBE9QzBZBeS/CbULDP UBICbprkiFxmw==
Received: from [IPv6:2601:152:4400:720f::1005] ([IPv6:2601:152:4400:720f::1005]) by resomta-po-12v.sys.comcast.net with SMTP id Jl6heweYXWFyCJl6ievPCc; Tue, 28 Nov 2017 18:59:48 +0000
Subject: Re: travelling home just before thanksgiving is hard
To: ietf@ietf.org
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <alpine.OSX.2.01.1711271506380.91054@ole-pro.local> <7E4123D9-C1A7-4FB7-BCC2-2A4FF25E3708@encrypted.net> <52f237e0-d4da-f360-aca9-1c73a0fe0533@comcast.net>
From: Michael StJohns <mstjohns@comcast.net>
Message-ID: <3168c57e-eab9-52f7-7bc8-add5c069014d@comcast.net>
Date: Tue, 28 Nov 2017 13:59:48 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <52f237e0-d4da-f360-aca9-1c73a0fe0533@comcast.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-CMAE-Envelope: MS4wfHkHpTK+VGaGmfRW4pjCDMtRkwiNv6fEjYN5gqZ/P26e7TQSluSWXq1h1iEtsZ33bdhYKUX7YNT0upkeogOecfATWIhX9LP0CBO/KTdklCNh4LM9J0HM btSpBEZta2F3pGnrWz7aGYmyYgBCByVBElULpd2LhAutLC9P3KMivKKI
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eqcJ4IawCY4WwZh5Y8v7M9lcYC4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 18:59:50 -0000

On 11/28/2017 1:54 PM, Michael StJohns wrote:
> On 11/28/2017 1:06 PM, Sarah B wrote:
>> I agree. The busiest days of the Thanksgiving week didn't start until 
>> the week days after; SFO was looking good when I flew in on Saturday 
>> at 2pm. I connected through LAX and it too was no busier than normal; 
>> I didn't experience any "Thanksgiving rush" delays coming into the 
>> West Coast. (I DID have to get my morning cardio in, running from 
>> terminal 6 to 7, to connect, but that was a United fault, leaving 
>> Singapore an hour late). Perhaps looking at the schedule and leaving 
>> Thursday night, Friday afternoon, or late Friday night would help you 
>> for the last meetings of the year when they're that close to 
>> Thanksgiving, moving forward, or giving yourself more time to connect 
>> in the US?
>
> I had that exact same flight and pretty close to the same cardio workout.
>
>
Oops - wrong flight.  But my saturday flight was late by 1 hour 20 
minutes leading to mostly the same scramble from one terminal to another.

Mike



From nobody Tue Nov 28 12:59:35 2017
Return-Path: <dbg@scs.stanford.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 B76CF128AB0; Tue, 28 Nov 2017 12:59:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ao09mGRcG8be; Tue, 28 Nov 2017 12:59:32 -0800 (PST)
Received: from market.scs.stanford.edu (www.scs.stanford.edu [IPv6:2001:470:806d:1::9]) (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 DC72412773A; Tue, 28 Nov 2017 12:59:32 -0800 (PST)
Received: from market.scs.stanford.edu (localhost [127.0.0.1]) by market.scs.stanford.edu (8.15.2/8.15.2) with ESMTP id vASKxSGQ032494; Tue, 28 Nov 2017 12:59:28 -0800 (PST)
Received: (from dbg@localhost) by market.scs.stanford.edu (8.15.2/8.15.2/Submit) id vASKxS2P032555; Tue, 28 Nov 2017 12:59:28 -0800 (PST)
Date: Tue, 28 Nov 2017 12:59:28 -0800
From: Daniel B Giffin <dbg@scs.stanford.edu>
To: Dale Worley <worley@ariadne.com>
Cc: gen-art@ietf.org, draft-ietf-tcpinc-tcpcrypt.all@ietf.org, tcpinc@ietf.org, ietf@ietf.org
Subject: Re: [tcpinc] Genart telechat review of draft-ietf-tcpinc-tcpcrypt-10
Message-ID: <20171128205928.GC42654@scs.stanford.edu>
References: <151173726115.30946.6601859817056753241@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <151173726115.30946.6601859817056753241@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UIwHKN8TKn7KoayOrGnG6la-QKE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 20:59:35 -0000

Hi Dale,

As described below, I've addressed these nits with a few
changes that will appear in the next draft (probably today).

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 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://wiki.tools.ietf.org/area/gen/wiki/GenArtfaq>.
> 
> Document:  review-draft-ietf-tcpinc-tcpcrypt-10
> Reviewer:  Dale R. Worley
> Review Date:  2017-11-26
> IETF LC End Date:  2017-10-19
> IESG Telechat date:  2017-11-30
> 
> Summary:
> 
>     This draft is basically ready for publication, but has nits
>     that should be considered before publication.
> 
> I'm rather impressed that the authors have gone through three
> revisions in little more than a month after LC.
> 
> The text prefixed by ">" is extracted from Daniel B Giffin's reply of
> 21 Oct 2017 to my Gen-Art review of draft-ietf-tcpinc-tcpcrypt-07.
> 
>     [in my review of draft-ietf-tcpinc-tcpcrypt-07:]
>     6. It might be worth adjusting the rules for how the A and B roles are
>     carried forward during session resumption.  Of course, each host
>     should compute the resumption identifier that it expects to receive
>     based on the role it had in the previous session.  But it's not clear
>     to me why a host that used k_ab for encryption (i.e., had the A role)
>     in the previous session must also use k_ab for encryption in the
>     resumed session, since the two sequences of k_ab/k_ba are generated
>     from the different session keys of the two sessions.  If you made the
>     choice of k_ab/k_ba be dependent on the A/B roles established by
>     TCP-ENO for *this* session, it seems like the specification of the
>     protocol would be a bit simpler.
> 
>     > I'll explain this design choice under separate cover, when I
>     > have a moment ...
> 
> I can't find the discussion of this design choice.

Sorry about that ...

This choice (determining which encryption keys to use by the
host's role in the *original* session, not the current one)
is mostly arbitrary.  I agree it is not the most intuitive
choice, but there is a sliver of purpose to justify it:

If some weakness in a TCP-ENO implementation allowed
attackers to cause two connecting tcpcrypt hosts to play the
same role when resuming, and keys were dependent on the
roles in this resumed session, they would then go ahead to
encrypt using the same keys.  That would be quite dangerous.
And each instance of session resumption would be an
opportunity to perpetrate this role-confusion attack.

Using the original session's role to choose the keys means
such an attack would have to succeed against the original
key exchange, where a confusion of roles should cause an
abort due to the asymmetrical Init1/Init2 messages (and if
not, would result in unrelated encryption keys and
non-matching session IDs).

>     > Yes, underscores are used to mark terms that are being
>     > introduced for the first time and defined.
> 
> Contra this statement, _..._ is used in two places as an emphatic:
> 
> 3.2.  Protocol Negotiation
> 
>    If a passive opener receives an ENO option including tcpcrypt TEPs it
>    supports, it MAY then attach an ENO option to its SYN-ACK segment,
>    including _solely_ the TEP it wishes to enable.
> 
> 3.5.  Session Resumption
> 
>    If an active opener sends a resumption suboption with a particular
>    TEP and the appropriate half of a resumption identifier and then, in
>    the same TCP handshake, receives a resumption suboption with the same
>    TEP and an identifier-half that does _not_ match that resumption
>    identifier, it MUST ignore that suboption.

Indeed.  I've simply removed the emphasis in those two
cases, as it doesn't seem necessary to comprehension.

> --
> 
> 3.5.  Session Resumption
> 
>    Implementations that cache session secrets MUST provide a means for
>    applications to control that caching.  In particular, when an
>    application requests a new TCP connection, it must be able to specify
>    that during the connection no session secrets will be cached and all
>    resumption requests will be ignored in favor of fresh key exchange.
>    And for an established connection, an application must be able to
>    cause any cache state that was used in or resulted from establishing
>    the connection to be flushed.  A companion document
>    [I-D.ietf-tcpinc-api] describes recommended interfaces for this
>    purpose.
> 
> The phrase "all resumption requests will be ignored in favor of fresh
> key exchange" doesn't seem to carry quite the right meaning to me,
> although what it must mean in this context is clear.  That phrase
> seems to have some implication that it operates when a fresh key
> exchange is provided along with a resumption request as an
> alternative... which is implicitly what the situation is, but not
> explicitly.  I would prefer "all resumption requests will be ignored
> and a fresh key exchange will be required".

Okay.  I've gone a bit further in order to be very clear:

   Implementations that cache session secrets MUST provide a means for
   applications to control that caching.  In particular, when an
   application requests a new TCP connection, it must be able to specify
   two policies for the duration of the connection: 1) that resumption
   requests will be ignored, and thus fresh key exchange will be
   required; and 2) that no session secrets will be cached.  (These
   policies may be specified independently or as a unit.)  And for an
   established connection, an application must be able to cause any
   cache state that was used in or resulted from establishing the
   connection to be flushed.  A companion document [I-D.ietf-tcpinc-api]
   describes recommended interfaces for this purpose.


> 
> 3.6.  Data Encryption and Authentication
> 
>    ...
>    as above, and provides these and the ciphertext value to the the AEAD
>    ...
> 
> s/the the/the/

Thanks.

> 
>     > I've gone through and used something like "negotiated TEP"
>     > in a couple places where the document said that a parameter
>     > depended on the "negotiated key-agreement scheme", and also
>     > added various phrases to make clear that the TEP dictates
>     > all the parameters.
> 
> Note that the current sections 4.3 and 5 show that the *lengths* are
> determined by TEP, but the *constants* are fixed by tcpcrypt itself.

Yes.  I suppose having the constants be parameterized by the
TEP would be the ultimate in flexibility, but I can't think
of a good enough reason to add this slight complexity to
implementations.

> 
> 3.3.  Key exchange
> 
>    o  "PK_A", "PK_B": ephemeral public keys for hosts A and B,
>       respectively.
> 
>     [in my review of draft-ietf-tcpinc-tcpcrypt-07:]
>     The use of "PK" for a public key seems to be poorly mnemonic, as it is
>     also the acronym of "private key".  There ought to be standard (and
>     distinct!) abbreviations for these phrases, but I can't find any...
> 
>     > Yeah ... at least in this document we don't name private
>     > keys, as they are never transmitted.
> 
> How about "Pub_A" and "Pub_B"?  (This suggests "Prv_A" and "Prv_B"
> (which wouldn't be used in this document.))

Good enough; I've made this change.

> 
> [END]
> 
> 
> _______________________________________________
> Tcpinc mailing list
> Tcpinc@ietf.org
> https://www.ietf.org/mailman/listinfo/tcpinc

Thanks for these comments!

daniel


From nobody Tue Nov 28 16:52:43 2017
Return-Path: <joelja@bogus.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 215C9128B93; Tue, 28 Nov 2017 16:52:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Jaeggli <joelja@bogus.com>
To: <ops-dir@ietf.org>
Cc: ipsec@ietf.org, ietf@ietf.org, draft-ietf-ipsecme-eddsa.all@ietf.org
Subject: Opsdir last call review of draft-ietf-ipsecme-eddsa-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151191675007.8090.17913891042195155302@ietfa.amsl.com>
Date: Tue, 28 Nov 2017 16:52:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZONvh0gchK0nTaginJ79EOAtUlI>
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, 29 Nov 2017 00:52:30 -0000

Reviewer: Joel Jaeggli
Review result: Ready

I reviewed  draft-ietf-ipsecme-eddsa on behalf of the opsdir during it's IETF
Last call.

This standards track draft introduces an importance change in the IKE
negotiation in that the sender can indicate that it hash algorithms which do
not require prehashing and can instead operate on arbitrary length data.

It also goes on to make a more strong requirement then RFC 8032 (which is
informational) that:

" The pre-hashed versions of Ed25519 and Ed448 (Ed25519ph and Ed448ph
   respectively) MUST NOT be used in IKE."

Changes to IKE negotiation require careful review, but I am satisfied that this
explicit signal improves the handling of support for the edwards curves.


From nobody Tue Nov 28 17:31:25 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45B2E129329 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 17:31:14 -0800 (PST)
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_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFZs3mfnhBI4 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 17:31:13 -0800 (PST)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::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 F00DF126DFE for <ietf@ietf.org>; Tue, 28 Nov 2017 17:31:11 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id a71so2449522qkc.9 for <ietf@ietf.org>; Tue, 28 Nov 2017 17:31:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZQmmI/HaEG4LBw5c2EZ9N7QCokzHNK9PJH8Eonwc9eg=; b=MRWFfNPvgXBZ0TO2CrkOXWqezm5e1+V3KLuVF0lb7k/rmejd/nzs1kswdof9Ibw6Fe gqSdxd7p+cf0dm+VwcqVcx5B0FjTWOqT2EWb8Q5pc2QYgLWQ9PAnwp96/N4XSXwHMMbM V6ShQdqWBHXM6F5bHoYIGR/k2SGOX4n2vRNig=
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=ZQmmI/HaEG4LBw5c2EZ9N7QCokzHNK9PJH8Eonwc9eg=; b=OLTn3W6+kBqwTKeabHgZjblJwu6VD2VK0e/pLyKVWfWya3vXrqwv/3IrUbGHkvtw1D er3kK17EliFc609kE1hNMwEkgls8ZlNzM6JakJlRf5Rqkgk4V4oxAY/8diaR5R/7ukXY 3HmQmGeTFzTX96HCa5b/7qxBpXQnNDXqVRwwXc4i7MTovnq9QXWhF9w2dltFc3dTAHEu dqNH6awC6rdnfRHmpUk9yJ0WU40m1QAPa3Ac5FWK9OsskbvVAWBx6nvPK0X9STMrtRty KsflCtXg39h95aVwniUokxgdl+Gt+5jaLc75KPzHTqvkaBFt2yqJcNswHRjEB8dy3ZM8 0Sew==
X-Gm-Message-State: AJaThX5VH6uGtIpUHhsMCFnzGRMRYJ5UkjX9mvG9atzo7OjqxLTXIOKU Pb3e9JdhGQUnfCNpTTnbogmp0A==
X-Google-Smtp-Source: AGs4zMYJBll677Ps5y5bNMToK6MmpnBpr2eoyGedGmVpVf7PeaTq3n69uGSUHidaQrYzlnD/8uKozw==
X-Received: by 10.55.8.4 with SMTP id 4mr1913327qki.249.1511919071167; Tue, 28 Nov 2017 17:31:11 -0800 (PST)
Received: from [172.16.0.18] ([96.231.220.27]) by smtp.gmail.com with ESMTPSA id v129sm408771qkd.42.2017.11.28.17.31.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Nov 2017 17:31:10 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: Opsdir last call review of draft-ietf-stir-certificates-15
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <151176783194.30763.7883112843929238883@ietfa.amsl.com>
Date: Tue, 28 Nov 2017 20:31:09 -0500
Cc: ops-dir@ietf.org, draft-ietf-stir-certificates.all@ietf.org, stir@ietf.org, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <CCA456BE-C9D3-48F0-A536-09FF663BC93B@sn3rd.com>
References: <151176783194.30763.7883112843929238883@ietfa.amsl.com>
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pSGJ9H3FIc9O_oaTYYpvj7ATBM0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 01:31:14 -0000

> On Nov 27, 2017, at 02:30, Sheng Jiang <jiangsheng@huawei.com> wrote:
>=20
> RFC 8017, RFC 8224 and RFC 8225 are NOT the registered downref.  They =
are
> normative reference to Informational RFCs.

RFCs 8224 and 8225 are standards track and will be published once this =
draft pops out of the queue.

RFC8017 obsoletes RFC 3447, which was what we referred to until after =
the original IETF LC. RFC 3447 was in the DOWNREF registry but was still =
called out in the original IETF LC for this draft.  Note that since =
we=E2=80=99re referring to RSASSA-PKCS1-v1_5 which was in RFC 3447 and =
didn=E2=80=99t change in RFC8017 I=E2=80=99m hoping that this is a =
non-issue.

spt=


From nobody Tue Nov 28 17:35: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 9B47B1293D9 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 17:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4locALCLHF06 for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 17:35:26 -0800 (PST)
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 DCE61126DFE for <ietf@ietf.org>; Tue, 28 Nov 2017 17:35:26 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1eJrHY-0002ua-DR; Wed, 29 Nov 2017 01:35:24 +0000
Date: Wed, 29 Nov 2017 10:35:23 +0900
Message-ID: <m2bmjluask.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Michael StJohns <mstjohns@comcast.net>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: travelling home just before thanksgiving is hard
In-Reply-To: <52f237e0-d4da-f360-aca9-1c73a0fe0533@comcast.net>
References: <9792B98B-68B3-4832-A60D-3210C9401D89@juniper.net> <alpine.OSX.2.01.1711271506380.91054@ole-pro.local> <7E4123D9-C1A7-4FB7-BCC2-2A4FF25E3708@encrypted.net> <52f237e0-d4da-f360-aca9-1c73a0fe0533@comcast.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/25.3 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/bUnbShPNtIWPaAIaRcUY5gNyZNQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 01:35:28 -0000

> One of the things I noted about this trip was the extreme cost of
> flights on the return leg.

this is a new airline online booking trick.  the outbound is very
inexpensive; plan to walk home.

randy


From nobody Wed Nov 29 01:16:25 2017
Return-Path: <jiangsheng@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 45A541270A7; Wed, 29 Nov 2017 01:16:19 -0800 (PST)
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 PEqXnhV7Tkmt; Wed, 29 Nov 2017 01:16:18 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 1442B124B17; Wed, 29 Nov 2017 01:16:18 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id E9376985A02AF; Wed, 29 Nov 2017 09:16:13 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 29 Nov 2017 09:16:15 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0361.001; Wed, 29 Nov 2017 17:16:11 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Sean Turner <sean@sn3rd.com>
CC: "ops-dir@ietf.org" <ops-dir@ietf.org>, "draft-ietf-stir-certificates.all@ietf.org" <draft-ietf-stir-certificates.all@ietf.org>, "stir@ietf.org" <stir@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Opsdir last call review of draft-ietf-stir-certificates-15
Thread-Topic: Opsdir last call review of draft-ietf-stir-certificates-15
Thread-Index: AQHTZ1Gv7ycsjmCAHUijym6pSaR+UaMqDreAgAEHyWA=
Date: Wed, 29 Nov 2017 09:16:10 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B92817B41BD@NKGEML515-MBX.china.huawei.com>
References: <151176783194.30763.7883112843929238883@ietfa.amsl.com> <CCA456BE-C9D3-48F0-A536-09FF663BC93B@sn3rd.com>
In-Reply-To: <CCA456BE-C9D3-48F0-A536-09FF663BC93B@sn3rd.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.89.150]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SxkQ8d9byGWbFCvftI5nPRXktkY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 09:16:19 -0000

SGksIFNlYW4sDQoNClRoYW5rcyBmb3IgeW91ciByZXBseS4gSXQgbWFrZXMgc2Vuc2UgdG8gbWUu
DQoNCkNoZWVycywNCg0KU2hlbmcNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IFNlYW4gVHVybmVyIFttYWlsdG86c2VhbkBzbjNyZC5jb21dIA0KU2VudDogV2VkbmVzZGF5LCBO
b3ZlbWJlciAyOSwgMjAxNyA5OjMxIEFNDQpUbzogU2hlbmcgSmlhbmcgPGppYW5nc2hlbmdAaHVh
d2VpLmNvbT4NCkNjOiBvcHMtZGlyQGlldGYub3JnOyBkcmFmdC1pZXRmLXN0aXItY2VydGlmaWNh
dGVzLmFsbEBpZXRmLm9yZzsgc3RpckBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDog
UmU6IE9wc2RpciBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtc3Rpci1jZXJ0aWZpY2F0
ZXMtMTUNCg0KDQoNCj4gT24gTm92IDI3LCAyMDE3LCBhdCAwMjozMCwgU2hlbmcgSmlhbmcgPGpp
YW5nc2hlbmdAaHVhd2VpLmNvbT4gd3JvdGU6DQo+IA0KPiBSRkMgODAxNywgUkZDIDgyMjQgYW5k
IFJGQyA4MjI1IGFyZSBOT1QgdGhlIHJlZ2lzdGVyZWQgZG93bnJlZi4gIFRoZXkgDQo+IGFyZSBu
b3JtYXRpdmUgcmVmZXJlbmNlIHRvIEluZm9ybWF0aW9uYWwgUkZDcy4NCg0KUkZDcyA4MjI0IGFu
ZCA4MjI1IGFyZSBzdGFuZGFyZHMgdHJhY2sgYW5kIHdpbGwgYmUgcHVibGlzaGVkIG9uY2UgdGhp
cyBkcmFmdCBwb3BzIG91dCBvZiB0aGUgcXVldWUuDQoNClJGQzgwMTcgb2Jzb2xldGVzIFJGQyAz
NDQ3LCB3aGljaCB3YXMgd2hhdCB3ZSByZWZlcnJlZCB0byB1bnRpbCBhZnRlciB0aGUgb3JpZ2lu
YWwgSUVURiBMQy4gUkZDIDM0NDcgd2FzIGluIHRoZSBET1dOUkVGIHJlZ2lzdHJ5IGJ1dCB3YXMg
c3RpbGwgY2FsbGVkIG91dCBpbiB0aGUgb3JpZ2luYWwgSUVURiBMQyBmb3IgdGhpcyBkcmFmdC4g
IE5vdGUgdGhhdCBzaW5jZSB3ZeKAmXJlIHJlZmVycmluZyB0byBSU0FTU0EtUEtDUzEtdjFfNSB3
aGljaCB3YXMgaW4gUkZDIDM0NDcgYW5kIGRpZG7igJl0IGNoYW5nZSBpbiBSRkM4MDE3IEnigJlt
IGhvcGluZyB0aGF0IHRoaXMgaXMgYSBub24taXNzdWUuDQoNCnNwdA0K


From nobody Wed Nov 29 07:31:19 2017
Return-Path: <jclarke@cisco.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 D68881200FC; Wed, 29 Nov 2017 07:31:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joe Clarke <jclarke@cisco.com>
To: <ops-dir@ietf.org>
Cc: draft-mm-wg-effect-encrypt.all@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-mm-wg-effect-encrypt-13
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151196946679.7944.3160175486224623517@ietfa.amsl.com>
Date: Wed, 29 Nov 2017 07:31:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SBASOmw9xLPUN8Ai6RPPfmBy5Go>
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, 29 Nov 2017 15:31:07 -0000

Reviewer: Joe Clarke
Review result: Has Nits

I have been requested to review draft-mm-wg-effect-encrypt for the ops
directorate.  This document describes the effects of pervasive encryption on
operators.  The document sets out a rather comprehensive list of network data
(in motion and at rest) use cases and explains how encryption will effect each
of them.  Overall, I feel this document is ready.  As someone that has
supported networks from a troubleshooting perspective for years, I was
especially pleased with the numerous callouts to troubleshooting impacts as
well as deficiencies in application logging.

To that end, it might be useful to specifically point out where vendors have a
role to fill in some of these areas to allow for transit encryption while
providing the necessary hooks for operators to manage and troubleshoot their
network.  Specifically, in many of the troubleshooting scenarios, operators
won't be able to provide truly useful tools to their end users unless the
vendors provide the right level of visibility.

On to some nits.

In section 1.1 you use "end user's" where I think you mean "end users'".

===

Section 2.  Today, Snowden is fairly well-known.  But as this document lives,
maybe the specifics of what he's done may get fuzzy.  Perhaps this could do
with a reference.

===

Sections 5.3 and 6.2: you reference the abbreviation SNI before formally
defining it.  It's more obvious in Section 6.2.



From nobody Wed Nov 29 08:22:14 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 39DF9127871; Wed, 29 Nov 2017 08:22:06 -0800 (PST)
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 VEEuuxVbwkqi; Wed, 29 Nov 2017 08:22:05 -0800 (PST)
Received: from mail-pl0-x233.google.com (mail-pl0-x233.google.com [IPv6:2607:f8b0:400e:c01::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 F291A127B57; Wed, 29 Nov 2017 08:22:04 -0800 (PST)
Received: by mail-pl0-x233.google.com with SMTP id b12so2373829plm.3; Wed, 29 Nov 2017 08:22:04 -0800 (PST)
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=PWHBhAq6e15AdBqZYucZHunX7TDVAlbxuVmWgI6CsGQ=; b=NU1FN6iwVPxrCvAX77j56zzhMRugAqlWkz1O9mhUdWna8Jpibk0i8ZwEkqM3Sfuf6Q J9o5KC+1myLpPEy5/zn/XVzBbicef4qzrUg92g9u0jjVH3RJa/9lwowh6gwXOfUodJe9 b7sslnXjRvtQrgOvjuPnZK0DEdMX8hYNIoxs/2FmQlXew/y04MXpLpOABYftXOYEWQcH XRq5qSinKfYdmOmZ5LCSa/frCcN5wYZA5JBYl1L4Z7fPn5/MfnPXFp/q2useG1ZKrDbk dFWmeRdYUNb9MWPv43IxjECRMLPifL06ELfRy50jy2cdZr/JLQqxR82jj7TZ8wPb+4KE /GrQ==
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=PWHBhAq6e15AdBqZYucZHunX7TDVAlbxuVmWgI6CsGQ=; b=rZV4OHPkGgBkGR44ZyXwk+CN0rgU8A16EIeCrFjM3dBDV1FMHJR4hRLAW98tepbhQ3 yLJsFybdTEduPPLP8hEt0BZvLfUw8LCyXwaEExtDnyVl9LE0V0TBSsRuNs9j+po2At0J lFoZLnbchOaROiC6IqSS7cLxk/4Z4bgIB6WukC228Pwcqf4tDxG8Cauypp2WM8brx2Sn 8FVZAYP0S4p3ckup7pR0Wvyp9Rf0dK5IgaQCQbCYWy9S6CaP+Gho79RjGQ14M1XZM5wP oBvDPoF/9whbZKpIfZgXpi0XWMGn0ngKztD/RZOVOBeUO/rdC9Xg5xX0+Z/a7Erl2oJ1 0Z0g==
X-Gm-Message-State: AJaThX5w3TnsqqcLshscPOK0GZxoAvwoPsGPIN++87UYfirkh3mpigE8 TWqnK1X/ohP5qv0SMbFw6AhXs9RdDmt/OVvVGIQ=
X-Google-Smtp-Source: AGs4zMaY3ayz3F0f3L+7XfZj+19jUQI0CH3rZRoexUnrkJwNFCX8i9h77USGTemXBV/CKgAL/COOYFxahZhOVPDW8kU=
X-Received: by 10.84.172.195 with SMTP id n61mr3363663plb.78.1511972524546; Wed, 29 Nov 2017 08:22:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.186.208 with HTTP; Wed, 29 Nov 2017 08:21:24 -0800 (PST)
In-Reply-To: <151196946679.7944.3160175486224623517@ietfa.amsl.com>
References: <151196946679.7944.3160175486224623517@ietfa.amsl.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Wed, 29 Nov 2017 11:21:24 -0500
Message-ID: <CAHbuEH4wanQoMrDZj+kvZjkv+jBUUVfvnsAx2iS+9tFQk4N8iA@mail.gmail.com>
Subject: Re: Opsdir last call review of draft-mm-wg-effect-encrypt-13
To: Joe Clarke <jclarke@cisco.com>
Cc: ops-dir@ietf.org, draft-mm-wg-effect-encrypt.all@ietf.org,  IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MPzDdjfMcbOBfwQ82_a1pgCNW6s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 16:22:06 -0000

Hello Joe,

First, thank you for your helpful review.

On Wed, Nov 29, 2017 at 10:31 AM, Joe Clarke <jclarke@cisco.com> wrote:
> Reviewer: Joe Clarke
> Review result: Has Nits
>
> I have been requested to review draft-mm-wg-effect-encrypt for the ops
> directorate.  This document describes the effects of pervasive encryption on
> operators.  The document sets out a rather comprehensive list of network data
> (in motion and at rest) use cases and explains how encryption will effect each
> of them.  Overall, I feel this document is ready.  As someone that has
> supported networks from a troubleshooting perspective for years, I was
> especially pleased with the numerous callouts to troubleshooting impacts as
> well as deficiencies in application logging.
>
> To that end, it might be useful to specifically point out where vendors have a
> role to fill in some of these areas to allow for transit encryption while
> providing the necessary hooks for operators to manage and troubleshoot their
> network.  Specifically, in many of the troubleshooting scenarios, operators
> won't be able to provide truly useful tools to their end users unless the
> vendors provide the right level of visibility.

Do you have suggested text that we could add to address this gap from
your experience?

>
> On to some nits.
>
> In section 1.1 you use "end user's" where I think you mean "end users'".
>
> ===
>
> Section 2.  Today, Snowden is fairly well-known.  But as this document lives,
> maybe the specifics of what he's done may get fuzzy.  Perhaps this could do
> with a reference.
>
> ===
>
> Sections 5.3 and 6.2: you reference the abbreviation SNI before formally
> defining it.  It's more obvious in Section 6.2.
>

Thanks for catching the nits, we will address them.

Best regards,
Kathleen

>



-- 

Best regards,
Kathleen


From nobody Wed Nov 29 08:49:20 2017
Return-Path: <rrahman@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 D6DE81293EE; Wed, 29 Nov 2017 08:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, 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 x_s2VY_VzZYk; Wed, 29 Nov 2017 08:49:10 -0800 (PST)
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 F1F63128BB7; Wed, 29 Nov 2017 08:49:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2707; q=dns/txt; s=iport; t=1511974150; x=1513183750; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=EshTLC7sLWcEqAG6UyjobkRz3UT5cVDWnDUSUiReECU=; b=OOPZqnbGl0FhVnb/dYtt1cp1rzOxXIgItUqO4gYe2QHawErFyqDmKOo2 bdpwoj8kyFZPrn1/6C4SGoLtNWsSELHcMrHjPCRFALdM8DqXd0lIVnJqF /Hlt/U2JnGYEgfYBlUE9N19tiVRSlMUwyTmb4k8nK3a5F7E670XZGtrxQ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CwAAB55B5a/4QNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM8Zm4nB4ZEh1SOcIF9hDwBApI1ghEKGAuFGAKFFD8YAQEBAQE?= =?us-ascii?q?BAQEBax0LhR8BAQEBAwEBbAsQAgEIEQEDAQEKGgsPGAsUAwYIAgQOBYoiEKlbi?= =?us-ascii?q?mcBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYNBggmBVoFpgyuFIIV4BZJGkAcCh3K?= =?us-ascii?q?NGoIWhg+LLIx5iRwCERkBgTkBHzkmgStvFTqCGQEPgweBTneIYwGBEwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.45,338,1508803200"; d="scan'208";a="320267499"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Nov 2017 16:49:09 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id vATGn9ln010498 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Nov 2017 16:49:09 GMT
Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 29 Nov 2017 10:49:08 -0600
Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1320.000; Wed, 29 Nov 2017 10:49:08 -0600
From: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
CC: "draft-ietf-rtgwg-yang-rip@ietf.org" <draft-ietf-rtgwg-yang-rip@ietf.org>,  "rtgwg@ietf.org" <rtgwg@ietf.org>, "rtgwg-chairs@ietf.org" <rtgwg-chairs@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: Last Call: <draft-ietf-rtgwg-yang-rip-06.txt> (A YANG Data Model for Routing Information Protocol (RIP)) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-rtgwg-yang-rip-06.txt> (A YANG Data Model for Routing Information Protocol (RIP)) to Proposed Standard
Thread-Index: AQHTaGZS/FASCGkfL0avLhCKeTP3ZKMrkk9F
Date: Wed, 29 Nov 2017 16:49:08 +0000
Message-ID: <1511974182521.58987@cisco.com>
References: <151188659372.12435.1451903543359435950.idtracker@ietfa.amsl.com>
In-Reply-To: <151188659372.12435.1451903543359435950.idtracker@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: [161.44.212.187]
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/1gntLZnSjANMzNa2GoGyuWQ6Jbc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 16:49:19 -0000

Hi,=0A=
=0A=
The RIP YANG model uses bfd-grouping-base-cfg-parms from BFD YANG. That gro=
uping does not exist in latest revision (it has been renamed). Also, as per=
 discussions we had with OSPF/ISIS YANG authors, the grouping which should =
be used from BFD is client-cfg-parms.=0A=
=0A=
Regards,=0A=
Reshad.=0A=
________________________________________=0A=
From: rtgwg <rtgwg-bounces@ietf.org> on behalf of The IESG <iesg-secretary@=
ietf.org>=0A=
Sent: Tuesday, November 28, 2017 11:29 AM=0A=
To: IETF-Announce=0A=
Cc: draft-ietf-rtgwg-yang-rip@ietf.org; rtgwg@ietf.org; rtgwg-chairs@ietf.o=
rg=0A=
Subject: Last Call: <draft-ietf-rtgwg-yang-rip-06.txt> (A YANG Data Model f=
or Routing Information Protocol (RIP)) to Proposed Standard=0A=
=0A=
The IESG has received a request from the Routing Area Working Group WG=0A=
(rtgwg) to consider the following document: - 'A YANG Data Model for Routin=
g=0A=
Information Protocol (RIP)'=0A=
  <draft-ietf-rtgwg-yang-rip-06.txt> as Proposed Standard=0A=
=0A=
The IESG plans to make a decision in the next few weeks, and solicits final=
=0A=
comments on this action. Please send substantive comments to the=0A=
ietf@ietf.org mailing lists by 2017-12-12. Exceptionally, comments may be=
=0A=
sent to iesg@ietf.org instead. In either case, please retain the beginning =
of=0A=
the Subject line to allow automated sorting.=0A=
=0A=
Abstract=0A=
=0A=
=0A=
   This document describes a data model for the Routing Information=0A=
   Protocol (RIP).  Both RIP version 2 and RIPng are covered.=0A=
=0A=
=0A=
=0A=
=0A=
The file can be obtained via=0A=
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-rip/=0A=
=0A=
IESG discussion can be tracked via=0A=
https://datatracker.ietf.org/doc/draft-ietf-rtgwg-yang-rip/ballot/=0A=
=0A=
=0A=
No IPR declarations have been submitted directly on this I-D.=0A=
=0A=
=0A=
The document contains these normative downward references.=0A=
See RFC 3967 for additional information:=0A=
    draft-bjorklund-netmod-rfc7223bis: A YANG Data Model for Interface Mana=
gement (None - IETF stream)=0A=
    draft-ietf-netmod-revised-datastores: Network Management Datastore Arch=
itecture (None - IETF stream)=0A=
    draft-acee-netmod-rfc8022bis: A YANG Data Model for Routing Management =
(NDMA Version) (None - )=0A=
    draft-bjorklund-netmod-rfc7277bis: A YANG Data Model for IP Management =
(None - IETF stream)=0A=
    draft-ietf-ospf-yang: Yang Data Model for OSPF Protocol (None - IETF st=
ream)=0A=
=0A=
=0A=
=0A=
_______________________________________________=0A=
rtgwg mailing list=0A=
rtgwg@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/rtgwg=0A=


From nobody Wed Nov 29 11:18:54 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 263DE126C22 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:18:52 -0800 (PST)
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 2GXRAfKm9J6g for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:18:50 -0800 (PST)
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 AD90812420B for <ietf@ietf.org>; Wed, 29 Nov 2017 11:18:50 -0800 (PST)
Received: by mail-pg0-x22b.google.com with SMTP id y6so1920791pgp.4 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:18:50 -0800 (PST)
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-language:content-transfer-encoding; bh=6aVjQaMBTW9FdC1ecvtfkfCR5hTXQGqeA7h1VHBJcyk=; b=UxWvJJ5wjUug6NXEPvxO5yv+vXUuvOjFgJRWvCTOLX2lyk8VgVkv/HYP8BePj5Xja7 MHSrUyRC0hKExpGS+tjrw3Udtd5/oqUiDlophkhLIw/5FrcLqVOxbEi+FyGCJsxd8H7X YjqPqOULHGCebP1wckP06yuLtgoNoWsmNB+xIJ3mjwYmem4HQnXXNyBUMO+C/39fUrov mc+l+YiaOw7iL6sAqNfO+njK9PP4h6ED+yIQhh9moF7VyWgMSKGM9myu6bmoHLgI6X+o 0YZULoW8QJEypfGf4Mbs89i0efVIkISQ9r2Re0ayDlgzV5oNSgJ7TYTZel+zhZbsl36R fbkw==
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-language:content-transfer-encoding; bh=6aVjQaMBTW9FdC1ecvtfkfCR5hTXQGqeA7h1VHBJcyk=; b=oHpUGq3TNSdtnokmEnzKrVYQiFw908qqjZNl6hUg2Lr/oDg1sZFqCOOzJxbRXCdEFw QmZOsGQLXwiO4XzwRiNxo7PMbeMqcQ+hpQH2D9Q8XnW8iBe1IBfsG4qYzdnWxqGsqPni jo73JD2Jm8xXUGNLf93YTKnd1/DCrGMfjBcvJcDvxRpG9BDkrbZABPF/fjZFcAI6IHwL hqdK1uKnu8kfeEOUvmqVgHLli9H1gLJc08Blp5Adwy/U3ph6XVs50jnl4n/7R1lx0BJK bgwC+DYO92UoXISkCIV2e4U0DTRi6X6hLu/bo0y8NXRMh0teoM+EwcdRT5/qZ5803Yql zSPw==
X-Gm-Message-State: AJaThX6z9oHz/oEl9h811+nvuO8r+jcKhMVtlBX7jwbyW1TV/BsNahI5 zm0G9ooZpgHnOsteMrzQHZoojw==
X-Google-Smtp-Source: AGs4zMa5SOBnnwk2zjt+2En/YJlWdrVCUSRhYkNU3hBL9bDAxeqPd+RkchmdAOqXey6FEHBObrIfrQ==
X-Received: by 10.101.75.142 with SMTP id t14mr3788226pgq.122.1511983129738; Wed, 29 Nov 2017 11:18:49 -0800 (PST)
Received: from ?IPv6:2406:e007:6f17:1:28cc:dc4c:9703:6781? ([2406:e007:6f17:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id b184sm3732371pga.90.2017.11.29.11.18.47 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 11:18:48 -0800 (PST)
To: IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: 20 versions in 31 minutes?
Organization: University of Auckland
Message-ID: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com>
Date: Thu, 30 Nov 2017 08:18:52 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N6JOA9dyOlHc6DboAkFdtRTplx4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 19:18:52 -0000

I realise that (D)TLS1.3 is controversial, but 20 versions of the draft
within 31 minutes seems a bit excessive. I'm curious about the mechanics
of how this happened, especially the confirmation process.

(The -03 version had some actual changes. The only changes in versions
-04 to -22 are the version numbers. A robot at play?)

Subject: I-D Action: draft-ietf-tls-dtls13-03.txt
Date: Wed, 29 Nov 2017 08:05:09 -0800
From: internet-drafts@ietf.org
...

Subject: I-D Action: draft-ietf-tls-dtls13-22.txt
Date: Wed, 29 Nov 2017 08:36:01 -0800
From: internet-drafts@ietf.org

Regards
   Brian Carpenter



From nobody Wed Nov 29 11:20:43 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 053F5126C22 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:20:42 -0800 (PST)
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, 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=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 Rfl5aPyTaGDh for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:20:40 -0800 (PST)
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 0F44912420B for <ietf@ietf.org>; Wed, 29 Nov 2017 11:20:40 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id d66so5892280qkg.1 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:20:40 -0800 (PST)
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=rO/qGzRWRoBU0J+O6WOpAvCNGRkbMN6B40Gqu5dDvzI=; b=Tz/FaPcONbVLehhXacpz6LOYeHlNAiJ8FNilwAFZnTqAJeqaOMG9H3FKlMyXxKy2+8 jFaglb5ipF8nUgIND2hsZcX4JIbkoouBpG/qddON1se5sLXZsEnHZG5ojcxLxTyvU58N TI+i+4m/QjLx43Jq3a8WlvDy3PaOTF3e7ntkjyBWv2WqbWLMcz5Nvcvdcwty7OxPVhd8 mrg5U2BduJP1ad5CNZphzgk1Am/EHiSqsjb1ustM0pFRVBo98ALn1CIkTuDzJKYuaUHf qIU0gcW+VkJGpil5S5aGg+dwlF5GVBy7ih1EduOMa+WACALiqmS1P0Zk+f5TMeUyIhxY 04Ag==
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=rO/qGzRWRoBU0J+O6WOpAvCNGRkbMN6B40Gqu5dDvzI=; b=gVgBq2il+X5ySSI12sfWTRRN1GK9FWgJSO3/NldEpsdXan/deLOjlSxzfuP+CuefOB A9pnDpzItZn9bMLgpUeptJjuWZpVvt85A5DJMoNXhrBOR67wAT9Jubezh3fWywzx0KJ2 GTar8KqoWPlfIt2s7BUgo4pZCO6fTEtMPBBtjzMsOHO8Nmy7hfFK0L/99ykhl148wjwQ E4iZ8kB0u3AdPNnVaj7B2cOvjma0SWzpTaKkfGOW9zG7GpXXowM2Zhs/n3LOwawRkx/f kLv5WVeIhAk50Pnm9vhHkpniBOWHjasl2E3s4epSkTWnmT/dyEZLzoPYCZDmvrzdfP1h sd0Q==
X-Gm-Message-State: AJaThX4uUWMT+jLX+WrGs25jBr8aUVY+s74/KWBc0RouqDpFu8vpDaBz U4LitH/JoThKXF72KjHBOcPv3XvWtfo=
X-Google-Smtp-Source: AGs4zMZiPl/QceMyMjD8gbF+p1piEdr0cRPu+aVB7XJ0WOEb+61AuTgpcNOoTVc40tFG0rG2E3FVdQ==
X-Received: by 10.55.221.80 with SMTP id n77mr6180122qki.279.1511983239181; Wed, 29 Nov 2017 11:20:39 -0800 (PST)
Received: from [192.168.43.27] (mobile-107-107-60-252.mycingular.net. [107.107.60.252]) by smtp.gmail.com with ESMTPSA id 26sm1794909qtm.3.2017.11.29.11.20.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 11:20:38 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_558E1608-13CD-416C-9F5D-95548DECEA07"
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: 20 versions in 31 minutes?
Date: Wed, 29 Nov 2017 14:20:36 -0500
In-Reply-To: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RVskvwN0GijlMVbdHysvJd4fhB8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 19:20:42 -0000

--Apple-Mail=_558E1608-13CD-416C-9F5D-95548DECEA07
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 29, 2017, at 2:18 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> I realise that (D)TLS1.3 is controversial, but 20 versions of the =
draft
> within 31 minutes seems a bit excessive. I'm curious about the =
mechanics
> of how this happened, especially the confirmation process.

Apparently the goal was to sync the dtls and tls draft versions.  I'm =
sure there is a reason why this was important.   I am however at a loss =
to actually say why.   :)



--Apple-Mail=_558E1608-13CD-416C-9F5D-95548DECEA07
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; line-break: after-white-space;" class=3D"">On =
Nov 29, 2017, at 2:18 PM, Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com" =
class=3D"">brian.e.carpenter@gmail.com</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"">I realise that (D)TLS1.3 is =
controversial, but 20 versions of the draft</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""><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"">within 31 minutes seems a bit excessive. I'm =
curious about the mechanics</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""><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"">of how this =
happened, especially the confirmation process.</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><br class=3D""></div><div>Apparently the =
goal was to sync the dtls and tls draft versions. &nbsp;I'm sure there =
is a reason why this was important. &nbsp; I am however at a loss to =
actually say why. &nbsp; :)</div><div><br class=3D""></div><br =
class=3D""></body></html>=

--Apple-Mail=_558E1608-13CD-416C-9F5D-95548DECEA07--


From nobody Wed Nov 29 11:47:33 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 C742B128D19 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:47:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=SIAEHOgl; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LEnP+Bxv
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id up7RynFAf_sd for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:47:27 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18186128DF3 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:47:15 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 42D8020BA3; Wed, 29 Nov 2017 14:47:14 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 29 Nov 2017 14:47:14 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=NT3Nd9Bc9fAdOQvV0W/FAXIgiL1Ty df9CHl2itZTHoc=; b=SIAEHOglkeb809t4s/X6FKbGbjUjoEMoAGKF6ZcqLc9UL PB6WDLMpRDoh1itru+Txr3hP9xjaBw1vGNLLqL49GlP5rvGhLwY7DxXpjiaVox98 ieGXv+Q3oB4QZCm7sve6yraIB0d9woukX+1Ob4anxV2+jL1UDZDYTuPq9p+GVw3W VrbjMNpyUwrJYAOni7NB5u9dY236LTDD3UEXmrPuUE8ZZgczV1cA2l5zQQsd9mH+ otzVRGQftm8ELOseXfIO7MNOpLy3X6R42wConMeu9vFtp+oq+7K3x/7c1GKijrHU Fc3mCDOVLcoQzoD1SPpx/yKYZlVhXAqPRs5/ZbxdA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=NT3Nd9 Bc9fAdOQvV0W/FAXIgiL1Tydf9CHl2itZTHoc=; b=LEnP+BxvejN4bZhkMXJ18e VvtahYIj77yT4Ezm5xZLzha4lKmVFeountFo/WzeqKIDHbVfm6uoearqNFD5pu7B 9K/zjNXLnJMpgqhC44YPfd+Bc0pC4dwLagbzD0gPM8ub+rl82WxFssxpgmmWdEkI Qm/zfdIFoG4KMrh462tsRNvk/IKjfavzyyQwGkJb4aos56dRT5aiCgMJKFkJPD0l kUNUWkUQiVM+DLnJP+vViQZfOPY5+dO2giFMyt9qp4MiU1HxEEmlzCqpki5obzZm LhGx3HjakqMIBLvI8LsVLVyqDhuyaObXn54QexGNSQKtA0WO60NoPto3CHhliIiA ==
X-ME-Sender: <xms:wg4fWkuwwNt2e7oEWgpMwtijgY8muZ33gOYPP-y56cjlHyVzPjDNlw>
Received: from [192.168.1.14] (cpe-144-136-175-28.sa.bigpond.net.au [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 1732C24751; Wed, 29 Nov 2017 14:47:12 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: 20 versions in 31 minutes?
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com>
Date: Thu, 30 Nov 2017 06:47:09 +1100
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net>
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com> <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dbQMJ3tCb0jw_Qqh6hne13gJxVk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 19:47:32 -0000

I'm assuming it's because when implementers do interop work, they talk =
about what draft they're using, and if the numbers are out of sync, this =
can be confusing.


> On 30 Nov 2017, at 6:20 am, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Nov 29, 2017, at 2:18 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>> I realise that (D)TLS1.3 is controversial, but 20 versions of the =
draft
>> within 31 minutes seems a bit excessive. I'm curious about the =
mechanics
>> of how this happened, especially the confirmation process.
>=20
> Apparently the goal was to sync the dtls and tls draft versions.  I'm =
sure there is a reason why this was important.   I am however at a loss =
to actually say why.   :)
>=20
>=20

--
Mark Nottingham   https://www.mnot.net/



From nobody Wed Nov 29 11:51:26 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A92C126C83 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:51:25 -0800 (PST)
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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPW9XUs53Gju for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:51:23 -0800 (PST)
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 25C4B1289B5 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:51:23 -0800 (PST)
Received: by mail-qk0-x22c.google.com with SMTP id 63so6013160qke.0 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:51:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=GOaFvqayRomPWWqgs4Y/oaSKZz1HiENYQYNZheI7/pQ=; b=Xg7Yxb+9U3E7WFLVhoKbiB4w4Omzo17eiIr9Wc7edcbjQw6xvd3AwC8Sq9wLx3J4Bq /GV0qufi4ytGIK704xBGP8q/aeJP1Eislbrxmx7LnmXAZLq/pSM0L1A254wASvMqn/1V +XSti7/kmYyBJHikpfz/+sUFUnCzCzdVGbyAA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=GOaFvqayRomPWWqgs4Y/oaSKZz1HiENYQYNZheI7/pQ=; b=OJgm25yvabGDVQ/GudoTrE/XKD29Z8zDAiPzxas+/IXA5ybrsrBvZcmrmeGNz7FJWD c2pU9B640iySli3cNfDvvffUzwzqK7xkNw0F4vzCUJfzeRNVjtW1JkOFg1i+UkrMoDHl Jm8fAkqbZftgMNwnLkbSU4bwGP5B1jbnp7R/nJAPkGtMUysO7MvjeeNDrEu/gn4gmiCg 0Vz2JYeWAq2jsb2b4/n57J0yXLbNmyNfH97go/jSAPJ9kWd37AasyGIPc0NpSrxagCKn YPhJt2eQYrpZsaHNC5xHuKO3pjJlqSdd/BONy0+XODCUBbit5VDIEcMg0J8y37VsNXEV liYw==
X-Gm-Message-State: AKGB3mIhinXyb3r7KG0Ee4/XnmIbPerOhFnSdgUgCm2AVy5Ek4LD5U7F JgzmQcrQMYPUiiHSC7zG5poFcgMIwtE=
X-Google-Smtp-Source: AGs4zMYMjQib7Yj2dflmUMEZOLV4eQyXe7K3kxm6Y7his3IYP2dIoB0vf2qL3scSx0UB35bRUUkDag==
X-Received: by 10.55.78.136 with SMTP id c130mr31169qkb.156.1511985082167; Wed, 29 Nov 2017 11:51:22 -0800 (PST)
Received: from [172.16.0.18] ([96.231.220.27]) by smtp.gmail.com with ESMTPSA id m5sm1813061qkh.90.2017.11.29.11.51.20 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 11:51:20 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: 20 versions in 31 minutes?
Date: Wed, 29 Nov 2017 14:51:19 -0500
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com> <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com> <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net>
Message-Id: <DF5B71C2-88B7-4758-9909-BE5A63922E42@sn3rd.com>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zC0xoUeF48RnWXLU2wK3zafHkKg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 19:51:25 -0000

Note the PSA:
https://mailarchive.ietf.org/arch/msg/tls/p9sQ_srqEaA-gYBAP1Iwib6P1fE


From nobody Wed Nov 29 11:55:42 2017
Return-Path: <warren@kumari.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 29008126C83 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:55:41 -0800 (PST)
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=kumari-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 0SMcF9PmMHv2 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:55:39 -0800 (PST)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::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 BC8BE128B37 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:55:37 -0800 (PST)
Received: by mail-wr0-x229.google.com with SMTP id x49so4485983wrb.13 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:55:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cn+rrAPYeDDPxBfQ4gh/MNnGDJvXS/EIkndLtKxc5cc=; b=iXPYTZG5trgZOj+3FRdny8oTAQ5izR8Kfe32x8DLOcdL6yQLLKHNg8B/pjw0QG9oHK 8McOAT7jDzuFfaV7Sb5IPU5EWCbjy1czeN/I4m8LxyR3qJHoJlSz5WBByarckgrvs/qd 3BtY3Hy873XIGmol5C5YJjDYeHNeGi/hNsy52smXTolkHHezh3c9UqhOqMuB+Whdi5gb Om3Whz+LYZcZsyV/pRfBO7NU/5hwyFVVvWtF0TobuIgnBGAkWiDz86t/+mPJMQuWk5fc OFhmm5uoT9DtPkwK8DQO8SrNRbhVdqCzsOELW9jhylRruZl6EgZtxgVjOw4hXiRS2T20 cFpQ==
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=cn+rrAPYeDDPxBfQ4gh/MNnGDJvXS/EIkndLtKxc5cc=; b=sbab37gCa92Za2JtZYefzEot6RJVWJcE5gBcHq1WZEJrx70GAeasoQGtOmYTYeYrPE yLBbATSCGA1YAeEY6StK3aa+qDqTh+JjjJCYf0R3U9KY3qvHNzfACbMuVZ/lQbN77TwU 0fQGtKKYSvd/1BUZvdVqWg/GEC8H40Mt+G78XsO6LURAPHWoAK3vijeEHpkPoToZgICq rBBrx8ZxKcwE6/Mf/wjtm0FhBdmQeeYv+zrkji9+1mID7A7Xx76IjMypBSGlFxWRUUCi gWMT/hfA4z6/q/LIsjROiPrvCefDrpWOa5QPTICQziAHTyoRERmO9P3ieFXMaN9CIviI LdCQ==
X-Gm-Message-State: AJaThX4zo1rycIjdNSkyyTRU5mWn+duYEYimrfqkyTrrq5l1iWSavdWl Ob3+YCl72FWxcIlxjPz66dXZNcJsTufDIi518Qi5Pg==
X-Google-Smtp-Source: AGs4zMYnF1cxGBKlUYmYwvLa3yo/5lqpgHz1O84Q++VaOxB3i6+/q5yI4qsfxZrslHVCIUGcU5YTYD/j9B0PNeGkayU=
X-Received: by 10.223.149.6 with SMTP id 6mr27916wrs.112.1511985336041; Wed, 29 Nov 2017 11:55:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.160.149 with HTTP; Wed, 29 Nov 2017 11:54:55 -0800 (PST)
In-Reply-To: <DF5B71C2-88B7-4758-9909-BE5A63922E42@sn3rd.com>
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com> <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com> <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net> <DF5B71C2-88B7-4758-9909-BE5A63922E42@sn3rd.com>
From: Warren Kumari <warren@kumari.net>
Date: Wed, 29 Nov 2017 14:54:55 -0500
Message-ID: <CAHw9_iL69BQQ=xM+tiU19O-Gcwb+bufht8gEQ9OCEWWBwEbR-Q@mail.gmail.com>
Subject: Re: 20 versions in 31 minutes?
To: Sean Turner <sean@sn3rd.com>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/meoHSAbZbiFq1xLpZ1lVrAZiH3w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 19:55:41 -0000

On Wed, Nov 29, 2017 at 2:51 PM, Sean Turner <sean@sn3rd.com> wrote:
> Note the PSA:
> https://mailarchive.ietf.org/arch/msg/tls/p9sQ_srqEaA-gYBAP1Iwib6P1fE
>

Ugh. I'm sympathetic to wanting the have the numbers in sync, but I
really think it would have been polite to include a note in versions
04-21 explaining what is happening. The current Appendix A. History
would have been a fine place for this.

W

-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf


From nobody Wed Nov 29 11:57:54 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F708128C9C for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:57:53 -0800 (PST)
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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CaahT3NQKe3m for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 11:57:51 -0800 (PST)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d: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 5D3FE1241F3 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:57:51 -0800 (PST)
Received: by mail-qk0-x235.google.com with SMTP id 63so6038475qke.0 for <ietf@ietf.org>; Wed, 29 Nov 2017 11:57:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=wnsvqUXU+/UWvTW4wYhxae9DnSAoK00YrPdZnfXmY18=; b=d4PvA32mNIsR/6IU0o/JAdLQ8t2GwS+yIigtNfsPzf0jLv0qhnL3eTiLr+J2kPBld7 v3or3pwudI5AW2GhQCYmEg/KEL8RV3ll+ivqPhvle7lm5KP53rzE19ze9oYeQozGyj4T WcZZZ5/WgzseyI2G3rZC1b46/D6o0xJ/EsKRw=
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=wnsvqUXU+/UWvTW4wYhxae9DnSAoK00YrPdZnfXmY18=; b=eIywn5ZL1rfeSvHkApcz8JioXYzKXVO45jdR9x9s6pvQqIq/wPrL3y6jUtGJqeReHq Zdjueb0oVveoaGioHNsgmkq5J2/+8ZyWvSJUn/IesGizRYkkIYSXMwci4X7peEaCzBks KJofcCH8owf5AkQcgyKztz+gHcYtBPrny54KZM55qWZ3tTq4UOS/CEyzC0KLu+zpq2Tg BrGW4FCF0nsadx8L/tjzkuufaqShkFStQb/RK7LKXoMTXY26vLxBhp/KzWU/xYA9dpcB t5IIVwLxsStEovSAeVJeW8ZKbXbwZP5/WBag50qAe6yXytyiSFPEIEFBZvQDUnJLonAr MVpw==
X-Gm-Message-State: AKGB3mLqkHSnR75wRY3ybhY3p3R6e7VbOi8yeOKvasltbTBKDJkp2O7k pVRad7cyLr88/+tm/vkqCkjJX/3Gnzw=
X-Google-Smtp-Source: AGs4zMaEHxhXJ0epHgCF6shEqu/Y8hcck59PCekXsyGCJHmsvYVuCNTqYXz6qfKNtqButAyUhfj8JA==
X-Received: by 10.55.74.144 with SMTP id x138mr7371qka.239.1511985470600; Wed, 29 Nov 2017 11:57:50 -0800 (PST)
Received: from [172.16.0.18] ([96.231.220.27]) by smtp.gmail.com with ESMTPSA id a17sm1730859qth.17.2017.11.29.11.57.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 11:57:49 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.1 \(3445.4.7\))
Subject: Re: 20 versions in 31 minutes?
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CAHw9_iL69BQQ=xM+tiU19O-Gcwb+bufht8gEQ9OCEWWBwEbR-Q@mail.gmail.com>
Date: Wed, 29 Nov 2017 14:57:48 -0500
Cc: IETF discussion list <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <0679674E-E6E5-48C8-B4DC-AB983787E422@sn3rd.com>
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com> <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com> <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net> <DF5B71C2-88B7-4758-9909-BE5A63922E42@sn3rd.com> <CAHw9_iL69BQQ=xM+tiU19O-Gcwb+bufht8gEQ9OCEWWBwEbR-Q@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.3445.4.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ux6ikqZDv6ctrjLWD5wRGGDhdKE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 19:57:53 -0000

> On Nov 29, 2017, at 14:54, Warren Kumari <warren@kumari.net> wrote:
> 
> On Wed, Nov 29, 2017 at 2:51 PM, Sean Turner <sean@sn3rd.com> wrote:
>> Note the PSA:
>> https://mailarchive.ietf.org/arch/msg/tls/p9sQ_srqEaA-gYBAP1Iwib6P1fE
>> 
> 
> Ugh. I'm sympathetic to wanting the have the numbers in sync, but I
> really think it would have been polite to include a note in versions
> 04-21 explaining what is happening. The current Appendix A. History
> would have been a fine place for this.
> 
> W

That can be arranged ;)

spt


From nobody Wed Nov 29 12:11:04 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 1873312426E for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 12:11:04 -0800 (PST)
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 J0mhs2ekb-u8 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 12:11:02 -0800 (PST)
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 49A52128D0D for <ietf@ietf.org>; Wed, 29 Nov 2017 12:10:53 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1eK8h0-000AMo-6n; Wed, 29 Nov 2017 15:10:50 -0500
Date: Wed, 29 Nov 2017 15:10:43 -0500
From: John C Klensin <john-ietf@jck.com>
To: Warren Kumari <warren@kumari.net>, Sean Turner <sean@sn3rd.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: 20 versions in 31 minutes?
Message-ID: <D374A0B5C2365190A14D81AA@PSB>
In-Reply-To: <CAHw9_iL69BQQ=xM+tiU19O-Gcwb+bufht8gEQ9OCEWWBwEbR-Q@mail.gmail.com>
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com> <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com> <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net> <DF5B71C2-88B7-4758-9909-BE5A63922E42@sn3rd.com> <CAHw9_iL69BQQ=xM+tiU19O-Gcwb+bufht8gEQ9OCEWWBwEbR-Q@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.10
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/R66zLv3ni4nmhRaBCZmIK7L_I3A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 20:11:04 -0000

--On Wednesday, November 29, 2017 14:54 -0500 Warren Kumari
<warren@kumari.net> wrote:

> On Wed, Nov 29, 2017 at 2:51 PM, Sean Turner <sean@sn3rd.com>
> wrote:
>> Note the PSA:
>> https://mailarchive.ietf.org/arch/msg/tls/p9sQ_srqEaA-gYBAP1I
>> wib6P1fE
>> 
> 
> Ugh. I'm sympathetic to wanting the have the numbers in sync,
> but I really think it would have been polite to include a note
> in versions 04-21 explaining what is happening. The current
> Appendix A. History would have been a fine place for this.

Unless we have gotten so tangled up by our tools as to make
doing sensible things entirely impossible, I would assume that a
simple explanation and requiest to the Secretariat would have
permitted posting an I-D with a chosen non-consecutive sequence
number as long as sequence numbers remained monotone increasing.
If the Secretariat were being suitably cautious, I imagine they
might ask for some AD to sign off, but I assume it wouldn't be
too hard to find one of those :-(

   john





From nobody Wed Nov 29 12:17:28 2017
Return-Path: <glen@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76E66126CF9 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 12:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.7
X-Spam-Level: 
X-Spam-Status: No, score=-3.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Djw3qA_Y81dJ for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 12:17:15 -0800 (PST)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F0CC1293DF for <ietf@ietf.org>; Wed, 29 Nov 2017 12:17:02 -0800 (PST)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id 435CE324CC for <ietf@ietf.org>; Wed, 29 Nov 2017 12:16:46 -0800 (PST)
Received: from mail-it0-f43.google.com (mail-it0-f43.google.com [209.85.214.43]) by c8a.amsl.com (Postfix) with ESMTPSA id 1F86B324C9 for <ietf@ietf.org>; Wed, 29 Nov 2017 12:16:46 -0800 (PST)
Received: by mail-it0-f43.google.com with SMTP id o130so27359538itg.0 for <ietf@ietf.org>; Wed, 29 Nov 2017 12:17:01 -0800 (PST)
X-Gm-Message-State: AJaThX7jXAe+Pe+6/LcQHTnHcrFvx8KLXN+cuIrTSEpQW+WnV953pM6G tc4JcRvb1NOv25Kfv4Nw9lRGDWIFUtZ+uvO0Dpk=
X-Google-Smtp-Source: AGs4zMbZqouJirbN+q+Wms3OJH1V74Bi4iUg85y1danOPRfL0RwTc7synK9w0V27Vf8klroKkSFi+6MqgJynCKTwO/8=
X-Received: by 10.36.110.14 with SMTP id w14mr45617itc.100.1511986621324; Wed, 29 Nov 2017 12:17:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.67.10 with HTTP; Wed, 29 Nov 2017 12:16:40 -0800 (PST)
In-Reply-To: <D374A0B5C2365190A14D81AA@PSB>
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com> <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com> <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net> <DF5B71C2-88B7-4758-9909-BE5A63922E42@sn3rd.com> <CAHw9_iL69BQQ=xM+tiU19O-Gcwb+bufht8gEQ9OCEWWBwEbR-Q@mail.gmail.com> <D374A0B5C2365190A14D81AA@PSB>
From: Glen <glen@amsl.com>
Date: Wed, 29 Nov 2017 12:16:40 -0800
X-Gmail-Original-Message-ID: <CABL0ig7USETJMhSmwmwLE5WGx-u=h06TfTmDoEA2bbtVnUP=KA@mail.gmail.com>
Message-ID: <CABL0ig7USETJMhSmwmwLE5WGx-u=h06TfTmDoEA2bbtVnUP=KA@mail.gmail.com>
Subject: Re: 20 versions in 31 minutes?
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114aad78782476055f24d1ba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cofXxRqKjz_hmR4b02ajaxVSTe4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 20:17:27 -0000

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

On Wed, Nov 29, 2017 at 12:10 PM, John C Klensin <john-ietf@jck.com> wrote:
> Unless we have gotten so tangled up by our tools as to make
> doing sensible things entirely impossible, I would assume that a
> simple explanation and requiest to the Secretariat would have
> permitted posting an I-D with a chosen non-consecutive sequence
> number as long as sequence numbers remained monotone increasing.

Under the old ID submit tools that might have been possible, but we use the
same tools to post drafts now that the community does, and I am given to
understand (and told the original requestor, when their original ticket got
escalated to me) that we did not have that ability.

Even were I to modify the database by hand, I assume that such a
modification would break the Datatracker in glorious ways.

(And, moreover, I'm sure that the community would have noticed the gap, and
mentioned it, just as they noticed the many duplicates.)

I referred them to the Tools Team to discuss this as a possible enhancement.

I agree there should be a good way to handle this.

Glen

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

<div dir=3D"ltr"><div><div><div><div><div>On Wed, Nov 29, 2017 at 12:10 PM,=
 John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com<=
/a>&gt; wrote:<br>&gt; Unless we have gotten so tangled up by our tools as =
to make<br>&gt; doing sensible things entirely impossible, I would assume t=
hat a<br>&gt; simple explanation and requiest to the Secretariat would have=
<br>&gt; permitted posting an I-D with a chosen non-consecutive sequence<br=
>&gt; number as long as sequence numbers remained monotone increasing.<br><=
br></div>Under the old ID submit tools that might have been possible, but w=
e use the same tools to post drafts now that the community does, and I am g=
iven to understand (and told the original requestor, when their original ti=
cket got escalated to me) that we did not have that ability.<br><br></div>E=
ven were I to modify the database by hand, I assume that such a modificatio=
n would break the Datatracker in glorious ways.<br></div><div><br></div><di=
v>(And, moreover, I&#39;m sure that the community would have noticed the ga=
p, and mentioned it, just as they noticed the many duplicates.)<br></div><d=
iv><br></div>I referred them to the Tools Team to discuss this as a possibl=
e enhancement.<br><br></div>I agree there should be a good way to handle th=
is.<br><br></div>Glen<br><br></div>

--001a114aad78782476055f24d1ba--


From nobody Wed Nov 29 12:27:35 2017
Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BA2126BF6 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 12:27:33 -0800 (PST)
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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 citlvzE4K-Zw for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 12:27:31 -0800 (PST)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002: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 7114B12426E for <ietf@ietf.org>; Wed, 29 Nov 2017 12:27:31 -0800 (PST)
Received: by mail-yb0-x22f.google.com with SMTP id b188so1838362ybg.11 for <ietf@ietf.org>; Wed, 29 Nov 2017 12:27:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0FVbJ6vg69leuYtW5lgUL6ptANsCDfsV81tGB54NiS8=; b=ix2i2pItPbkgTm/PiS6pSvZ092frwXQ3H5c/lYO1YPkxqGvTtPx2ne2RR+wW4/uzCT 2jta7E5CCYjvliIoxVkq8/7BFPlbsK5kQC2JZkOe7w0GocNA5tdY/Cv2dVr7Y6sxSqWT lrQOlz7C0716ZOlT9nFB/QOKsxOSAzTB/XEyyrs19ShceVl5tIFfahGf6KRXPzW1Xv7P h8bMrH0COz1gnZqDW6v5R+1Rt51nC0ip5YK6CnmoJRLhqbUGNlmtxslxTMzCIW27SD/+ 2ufo9vbE6MXIrDQVjTORdyLgTP3g5YTnvwa+CpWEmfB7pIyFCHKQO67gpnAiARETEaVI qU9A==
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=0FVbJ6vg69leuYtW5lgUL6ptANsCDfsV81tGB54NiS8=; b=PiKHsdBch7bxsyq+HPmudPrzzVbf5eOUWmPBIMO/5FIstSIi7gI/nTQEPZe+LbHqYd e682ykFCboIh1ZIyd/uYUKuGemX6jQTFHg5nGHkhzzLDWq5b4/q3XaBSz7q6j32LvRmL He8POwglDO4+jfve4uL7T13GyijZmoE5k94SbjNDkLmfOPkBBnkeI17bNhybZG7hwZB4 NsaXENS6qydXautUulugv1gJblVxpW1m4nKFAkfcSNzQz4ZD7BhzrrP5GQI1/IG6YRdz GRMAX3ILtQQFZQKl1KisJDe+3H9iuzodxDr6Oj2RWjaTkSeS5cHJG9wzaF78c0SETvsZ eAkg==
X-Gm-Message-State: AJaThX7OHIKoZmMoTof20P19Kctb+ijiMAj7nqJYMY/ciIcpc+SqnigP VT7jpN0LNm43AyIKvAxk3JUfFedJHy4f/blP8ZuiM1qw
X-Google-Smtp-Source: AGs4zMZ/XD3XyonsR48HbFFOj8p/FJFbhNwVM7oChglYT6cBfRFYElVFrszG1b1K5JdKSYGirkcEHTM1+o6Uf5G7iig=
X-Received: by 10.37.16.134 with SMTP id 128mr79598ybq.474.1511987250477; Wed, 29 Nov 2017 12:27:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.123.132 with HTTP; Wed, 29 Nov 2017 12:26:50 -0800 (PST)
In-Reply-To: <D374A0B5C2365190A14D81AA@PSB>
References: <c4eae268-9ed9-fa81-1263-4331352f56ac@gmail.com> <002CFF17-3981-468A-B8AD-0568D2D26659@fugue.com> <515FA491-B3EE-4736-AE16-0388F1AFE126@mnot.net> <DF5B71C2-88B7-4758-9909-BE5A63922E42@sn3rd.com> <CAHw9_iL69BQQ=xM+tiU19O-Gcwb+bufht8gEQ9OCEWWBwEbR-Q@mail.gmail.com> <D374A0B5C2365190A14D81AA@PSB>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 29 Nov 2017 12:26:50 -0800
Message-ID: <CABcZeBO56E9dN4J2daLeOBfyGgFRqh9ZnuCWMRV6ju86Lot8OQ@mail.gmail.com>
Subject: Re: 20 versions in 31 minutes?
To: John C Klensin <john-ietf@jck.com>
Cc: Warren Kumari <warren@kumari.net>, Sean Turner <sean@sn3rd.com>,  IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11c0125af85268055f24f661"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O1f2MOYrFfJx-mcWkW3TbcbBb9o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 20:27:34 -0000

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

On Wed, Nov 29, 2017 at 12:10 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Wednesday, November 29, 2017 14:54 -0500 Warren Kumari
> <warren@kumari.net> wrote:
>
> > On Wed, Nov 29, 2017 at 2:51 PM, Sean Turner <sean@sn3rd.com>
> > wrote:
> >> Note the PSA:
> >> https://mailarchive.ietf.org/arch/msg/tls/p9sQ_srqEaA-gYBAP1I
> >> wib6P1fE
> >>
> >
> > Ugh. I'm sympathetic to wanting the have the numbers in sync,
> > but I really think it would have been polite to include a note
> > in versions 04-21 explaining what is happening. The current
> > Appendix A. History would have been a fine place for this.
>
> Unless we have gotten so tangled up by our tools as to make
> doing sensible things entirely impossible, I would assume that a
> simple explanation and requiest to the Secretariat would have
> permitted posting an I-D with a chosen non-consecutive sequence
> number as long as sequence numbers remained monotone increasing.
>

I was told this was impossible with the current tools, so I opted for this.

-Ekr


> If the Secretariat were being suitably cautious, I imagine they
> might ask for some AD to sign off, but I assume it wouldn't be
> too hard to find one of those :-(
>
>    john
>
>
>
>
>

--001a11c0125af85268055f24f661
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 Wed, Nov 29, 2017 at 12:10 PM, John C Klensin <span dir=3D"ltr">&lt;=
<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@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"><br>
<br>
--On Wednesday, November 29, 2017 14:54 -0500 Warren Kumari<br>
<span class=3D"">&lt;<a href=3D"mailto:warren@kumari.net">warren@kumari.net=
</a>&gt; wrote:<br>
<br>
&gt; On Wed, Nov 29, 2017 at 2:51 PM, Sean Turner &lt;<a href=3D"mailto:sea=
n@sn3rd.com">sean@sn3rd.com</a>&gt;<br>
&gt; wrote:<br>
&gt;&gt; Note the PSA:<br>
&gt;&gt; <a href=3D"https://mailarchive.ietf.org/arch/msg/tls/p9sQ_srqEaA-g=
YBAP1I" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.org/<=
wbr>arch/msg/tls/p9sQ_srqEaA-<wbr>gYBAP1I</a><br>
&gt;&gt; wib6P1fE<br>
&gt;&gt;<br>
&gt;<br>
&gt; Ugh. I&#39;m sympathetic to wanting the have the numbers in sync,<br>
&gt; but I really think it would have been polite to include a note<br>
&gt; in versions 04-21 explaining what is happening. The current<br>
&gt; Appendix A. History would have been a fine place for this.<br>
<br>
</span>Unless we have gotten so tangled up by our tools as to make<br>
doing sensible things entirely impossible, I would assume that a<br>
simple explanation and requiest to the Secretariat would have<br>
permitted posting an I-D with a chosen non-consecutive sequence<br>
number as long as sequence numbers remained monotone increasing.<br></block=
quote><div><br></div><div>I was told this was impossible with the current t=
ools, so I opted for this.</div><div><br></div><div>-Ekr</div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
If the Secretariat were being suitably cautious, I imagine they<br>
might ask for some AD to sign off, but I assume it wouldn&#39;t be<br>
too hard to find one of those :-(<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=C2=A0 =C2=A0john<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a11c0125af85268055f24f661--


From nobody Wed Nov 29 13:43:11 2017
Return-Path: <linda.dunbar@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 08AB9126CD6; Wed, 29 Nov 2017 13:43:03 -0800 (PST)
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, 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] 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 Yopy1VK0UPKN; Wed, 29 Nov 2017 13:43:00 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 205AA124239; Wed, 29 Nov 2017 13:43:00 -0800 (PST)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id ED0AEAC3A1BFB; Wed, 29 Nov 2017 21:42:55 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 29 Nov 2017 21:42:57 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.170]) by SJCEML701-CHM.china.huawei.com ([169.254.3.207]) with mapi id 14.03.0361.001;  Wed, 29 Nov 2017 13:42:55 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Dino Farinacci <farinacci@gmail.com>, The IESG <iesg@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Effort & difficulty in linking ONUG work with IETF
Thread-Topic: Effort & difficulty in linking ONUG work with IETF
Thread-Index: AdNpVMX2Yb9VgYs0T7Sj4zw74q6p0w==
Date: Wed, 29 Nov 2017 21:42:55 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66AFDDBC0@sjceml521-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.137.123]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F66AFDDBC0sjceml521mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FpDMnNU2enfgtO9_LHxK8pCr4_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: Wed, 29 Nov 2017 21:43:03 -0000

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

At IETF100 plenary, Dino Farinacci brought up the subject of linking ONUG i=
nitiatives with IETF work. Since I've been actively contributing to both IE=
TF and ONUG work, I want to share my experience in trying to link the two w=
orlds.
ONUG (Open Network User Group) currently has 4 Working Groups:

-        OSE: Open SD-WAN Exchange

-        SDSS: Software Defined Security Services

-        HC: Hybrid Cloud

-        M&A: Monitoring & Analytics.

One practice by ONUG might be worth learning for IETF: ONUG only let User C=
ommunity (excluding vendors) to vote for their desired use cases. ONUG WGs =
are created for the use cases with the highest votes (by users).
ONUG's Software Defined Security Services WG is closely aligned with IETF's=
 I2NSF WG. The use cases & requirements specified by ONUG SDSS have been in=
corporated to I2NSF's draft-ietf-i2nsf-problem-and-use-cases [RFC8192].

ONUG doesn't do standard, therefore interoperability is not their priority.=
 Instead, ONUG is to let many large enterprises collectively show their com=
mon use cases, requirement, and problems they face. This year, most of the =
use cases and problems being discussed are centered on how to enable enterp=
rises to move their workloads to many available public clouds.

One interesting event of the 2017 ONUG Fall is a "Right Stuff Innovation" P=
oC demo which, per Nick Lippis (ONUG Founder), is meant to show the Beacon =
of the Light of vendors' innovative solutions for highly desired use cases =
(i.e. facilitating enterprise embracing digital transformation). I led a te=
am participated in the competition and got the award (http://www.pressrelea=
sepoint.com/huaweis-sd-wan-wins-onug-right-stuff-innovation-award).

We have been trying to bring the problems/use cases being discussed in ONUG=
 to IETF. Here are some preliminary drafts describing the problems and the =
gaps.

https://datatracker.ietf.org/doc/draft-dm-vpn-ext-to-cloud-dc-problem-state=
ment/

https://datatracker.ietf.org/doc/draft-dm-vpn-ext-to-cloud-dc-gap-analysis/


The drafts will need more work to be accepted by IETF community. We need he=
lp. If anyone is interested in working together in this domain, please cont=
act us.

Thanks, Linda Dunbar

--_000_4A95BA014132FF49AE685FAB4B9F17F66AFDDBC0sjceml521mbschi_
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* 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;}
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:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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:984549511;
	mso-list-type:hybrid;
	mso-list-template-ids:-192220704 226280496 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:7;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:SimSun;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">At IETF100 plenary, Dino Farinacci brought up the su=
bject of linking ONUG initiatives with IETF work. Since I&#8217;ve been act=
ively contributing to both IETF and ONUG work, I want to share my experienc=
e in trying to link the two worlds.
<o:p></o:p></p>
<p class=3D"MsoNormal">ONUG (Open Network User Group) currently has 4 Worki=
ng Groups:
<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span></span><![endif]>OSE: Open SD-WAN Exchange<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span></span><![endif]>SDSS: Software Defined Security Services<o:p></o:p>=
</p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span></span><![endif]>HC: Hybrid Cloud<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
</span></span><![endif]>M&amp;A: Monitoring &amp; Analytics. <o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">One practice by ONUG might be worth learning for IET=
F: ONUG only let User Community (excluding vendors) to vote for their desir=
ed use cases. ONUG WGs are created for the use cases with the highest votes=
 (by users).
<o:p></o:p></p>
<p class=3D"MsoNormal">ONUG&#8217;s Software Defined Security Services WG i=
s closely aligned with IETF&#8217;s I2NSF WG. The use cases &amp; requireme=
nts specified by ONUG SDSS have been incorporated to I2NSF&#8217;s
<i>draft-ietf-i2nsf-problem-and-use-cases [RFC8192]. </i><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">ONUG doesn&#8217;t do standard, therefore interopera=
bility is not their priority. Instead, ONUG is to let many large enterprise=
s collectively show their common use cases, requirement, and problems they =
face. This year, most of the use cases and
 problems being discussed are centered on how to enable enterprises to move=
 their workloads to many available public clouds.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">One interesting event of the 2017 ONUG Fall is a &#8=
220;Right Stuff Innovation&#8221; PoC demo which, per Nick Lippis (ONUG Fou=
nder), is meant to show the Beacon of the Light of vendors&#8217; innovativ=
e solutions for highly desired use cases (i.e. facilitating
 enterprise embracing digital transformation). I led a team participated in=
 the competition and got the award (<a href=3D"http://www.pressreleasepoint=
.com/huaweis-sd-wan-wins-onug-right-stuff-innovation-award">http://www.pres=
sreleasepoint.com/huaweis-sd-wan-wins-onug-right-stuff-innovation-award</a>=
).
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We have been trying to bring the problems/use cases =
being discussed in ONUG to IETF. Here are some preliminary drafts describin=
g the problems and the gaps.
<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-dm=
-vpn-ext-to-cloud-dc-problem-statement/">https://datatracker.ietf.org/doc/d=
raft-dm-vpn-ext-to-cloud-dc-problem-statement/</a><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-dm=
-vpn-ext-to-cloud-dc-gap-analysis/">https://datatracker.ietf.org/doc/draft-=
dm-vpn-ext-to-cloud-dc-gap-analysis/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The drafts will need more work to be accepted by IET=
F community. We need help. If anyone is interested in working together in t=
his domain, please contact us.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks, Linda Dunbar<o:p></o:p></p>
</div>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F66AFDDBC0sjceml521mbschi_--


From nobody Wed Nov 29 14:02:57 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 DA0AA126B6D for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 14:02:55 -0800 (PST)
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 ESd8gC_N0qnn for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 14:02:53 -0800 (PST)
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 9485E124BE8 for <ietf@ietf.org>; Wed, 29 Nov 2017 14:02:53 -0800 (PST)
Received: by mail-pg0-x22e.google.com with SMTP id q20so2108138pgv.2 for <ietf@ietf.org>; Wed, 29 Nov 2017 14:02:53 -0800 (PST)
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-language:content-transfer-encoding; bh=dabsxhmpsoHpclQpHV18bcv8v3UhBYL+poDPSJjt+K8=; b=IDsceJy7IaGrw0d26YYF6zJGp3fvLRqGKmqPIc8KjfkDK32p5uolWLR3g3PKEWA3m1 uBGeAhVkQHDlqkyUXVFZqPp5Qkl8udG64/VRes4QgHapHvL0X/Mj837ObK3xkdTvNt3f daR7+2vZKWrqWa4cKO/75hzyjyIhSSHsolb6iJ6pTPeL65ciGD+Wpyal6KyMm8wLC1XU clafA5hGYQ0HwXAuG32Xc6vAQjMVXdqAL7JJ/BeizRoRuuLNIWIb3N2FCiP9mJdBd2R4 vVkkPe63JxqL5oG0mVNP2ad5ZitvNMkoLP4HhV6L6rUBd5RFINPK3sL9BnjUMeBM4tLP 7e9w==
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-language:content-transfer-encoding; bh=dabsxhmpsoHpclQpHV18bcv8v3UhBYL+poDPSJjt+K8=; b=YS3DQKxdnV3QjHoxTHos4aTAxi+1pUAe4y91ZyMr6YwggLxlfMTda9b9lZ5qEJQS24 ttPyu3g+ZpTIYs1zHKEvJ609yjZC37YwKixP4tM6+JiGuhZjihIyaVfQpzL0ScILDc7R WJf9tHiNGKdgLx+bmXJ5lUpSLX5eqRYkasjDv1VgHHWV4bwWrKOPs9arIHRDI/Ip0vT3 iLOHV2MuRi72GyQh3h+fHApIUq2Ho4yJEpsnZVnqbkvuCjEaUm9KaIemqRi79hsrmwMw 5njFsnbT9GNspy7QPmGmrMamy02iBkaMAxRK8L9hUtYEfxJ76p0KWwTRdKP7YZC1iObI OCiA==
X-Gm-Message-State: AJaThX759PsHJgEpXYSbfVALISw4UP+OJ+aA6nuJlkJ6qUD8AEgYRMcC tI2ZjujXTbqdO4oF6dO+0NtfGQ==
X-Google-Smtp-Source: AGs4zMYWtqd9oxW2r+OPMTLm3C5ftCnBaoFPwyHdYQeOUGuT12OXPQdFZfOAsiV9V7B/uAlT6scBmw==
X-Received: by 10.101.68.65 with SMTP id e1mr326735pgq.282.1511992972547; Wed, 29 Nov 2017 14:02:52 -0800 (PST)
Received: from ?IPv6:2406:e007:6f17:1:28cc:dc4c:9703:6781? ([2406:e007:6f17:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id t4sm5452818pfj.56.2017.11.29.14.02.50 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 14:02:51 -0800 (PST)
To: IETF discussion list <ietf@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: IAOC role
Organization: University of Auckland
Message-ID: <514edc7c-43ad-44d9-2488-17261381cd84@gmail.com>
Date: Thu, 30 Nov 2017 11:02:56 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BGCeVhfDckPO41pKvxFVIGxmp_0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 22:02:56 -0000

Hi,

The IASA 2.0 effort is discussing the *future* of IASA and the IAOC.
That isn't my concern here, and there's a mailing list for it
(https://www.ietf.org/mailman/listinfo/iasa20).

What I'm concerned about is that fact that a couple of *current* IAOC
slots are up for appointment shortly (by NomCom and IESG respectively),
with several fine candidates in each case.

All I'm asking is that in their considerations, the appointing bodies
keep in mind the definition of the IAOC's role:

   The IAOC's role is to provide appropriate direction to the IAD, to
   review the IAD's regular reports, and to oversee IASA functions to
   ensure that the administrative needs of the IETF community are being
   properly met.  The IAOC's mission is not to be engaged in the day-
   to-day administrative work of the IASA, but rather to provide
   appropriate direction, oversight, and approval.
   (https://tools.ietf.org/html/rfc4071#section-3.2)
 
Regards
   Brian Carpenter


From nobody Wed Nov 29 21:19:12 2017
Return-Path: <linda.dunbar@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 545B0127863 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 21:19:10 -0800 (PST)
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 1-oy6mhoUf3v for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 21:19:09 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 355B0124207 for <ietf@ietf.org>; Wed, 29 Nov 2017 21:19:09 -0800 (PST)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 932B361C46E55 for <ietf@ietf.org>; Thu, 30 Nov 2017 05:19:05 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 30 Nov 2017 05:19:06 +0000
Received: from SJCEML521-MBS.china.huawei.com ([169.254.2.170]) by SJCEML703-CHM.china.huawei.com ([169.254.5.4]) with mapi id 14.03.0361.001; Wed, 29 Nov 2017 21:18:55 -0800
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: what does "politicize Internet" mean? (RE: Technical Plenary Panel at IETF100: The Internet, a look forward: social, political, and technical perspectives
Thread-Topic: what does "politicize Internet" mean? (RE: Technical Plenary Panel at IETF100: The Internet, a look forward: social, political, and technical perspectives
Thread-Index: AdNpmjsr6T37kY4ERWehBYD5zkEO7g==
Date: Thu, 30 Nov 2017 05:18:54 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F66AFDE1E8@sjceml521-mbs.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.47.136.188]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BKzujXaPjFmGLoDNC5-rJbR_MCM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 05:19:10 -0000

QnJpYW4sIA0KDQpUaGUgcGFuZWxpc3RzIHlvdSBoYXZlIGFycmFuZ2VkIHNhaWQgbXVsdGlwbGUg
dGltZXMgb24gImRvbid0IHBvbGl0aWNpemUgaW50ZXJuZXQiLiBXaGF0IGRvZXMgaXQgbWVhbj8g
DQpJIHdhcyB0b28gZW1iYXJyYXNzZWQgdG8gYXNrIGF0IHRoZSBJRVRGMTAwIFBsZW5hcnkuIFRo
ZW4gSSBsZWFybmVkIHRoYXQgSSBhbSBub3QgdGhlIG9ubHkgb25lIHdobyBkb2Vzbid0IHVuZGVy
c3RhbmQuIA0KDQpMaW5kYSBEdW5iYXINCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IGlldGYgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBCcmlh
biBUcmFtbWVsbCAoSUVURikNClNlbnQ6IFdlZG5lc2RheSwgTm92ZW1iZXIgMDgsIDIwMTcgOTo1
OCBBTQ0KVG86IElFVEYgRGlzY3Vzc2lvbiBNYWlsaW5nIExpc3QgPGlldGZAaWV0Zi5vcmc+DQpT
dWJqZWN0OiBUZWNobmljYWwgUGxlbmFyeSBQYW5lbCBhdCBJRVRGMTAwOiBUaGUgSW50ZXJuZXQs
IGEgbG9vayBmb3J3YXJkOiBzb2NpYWwsIHBvbGl0aWNhbCwgYW5kIHRlY2huaWNhbCBwZXJzcGVj
dGl2ZXMNCg0KR3JlZXRpbmdzLCBhbGwsDQoNClRoZSBQbGVuYXJ5IFNlc3Npb24gYXQgSUVURiAx
MDAgaW4gU2luZ2Fwb3JlICAoV2VkbmVzZGF5LCAxNSBOb3ZlbWJlciAyMDE3LCAxNzoxMC0xOTo0
MCBTaW5nYXBvcmUgdGltZSAoVVRDICsgOCkpIGluY2x1ZGVzIGEgcGFuZWwgZGlzY3Vzc2lvbiwg
ZW50aXRsZWQ6DQoNClRoZSBJbnRlcm5ldCwgYSBsb29rIGZvcndhcmQ6IFNvY2lhbCwgcG9saXRp
Y2FsLCBhbmQgdGVjaG5pY2FsIHBlcnNwZWN0aXZlcw0KDQpBZGRpbmcgYSBkaWdpdCB0byBjb3Vu
dCBJRVRGIG1lZXRpbmdzIGludml0ZXMgaW50cm9zcGVjdGlvbiBhbmQgcHJvZ25vc3RpY2F0aW9u
LiBGb3IgdGhlIElFVEYxMDAgUGxlbmFyeSwgdGhyZWUgcHJvbWluZW50IHN0cmF0ZWdpc3RzIHdp
bGwgc2hhcmUgdGhlaXIgdW5pcXVlIHBlcnNwZWN0aXZlcyBvbiB3aGF0IHRoZSBJbnRlcm5ldCB3
aWxsIGxvb2sgbGlrZSBpbiB0aGlydHkgeWVhcnMuIFRoZXkgd2lsbCBjb25zaWRlciBob3cgdGhl
IEludGVybmV04oCZcyBpbmZsdWVuY2Ugb24gb3VyIGxpdmVzIGFuZCBzb2NpYWwgc3lzdGVtcyB3
aWxsIGNoYW5nZSwgYW5kIGhvdyBvdXIgaW5mbHVlbmNlIG9uIHRoZSBJbnRlcm5ldCB3aWxsIGFs
c28gY2hhbmdlLCBzb2NpYWxseSwgcG9saXRpY2FsbHksIGFuZCB0ZWNobmljYWxseS4NCg0KSSds
bCBtb2RlcmF0ZSB0aGUgcGFuZWw7IHRoZSBwYW5lbGlzdHMgaW5jbHVkZToNCg0KLSBNb25pcXVl
IE1vcnJvdywgUHJlc2lkZW50IGFuZCBDby1Gb3VuZGVyIG9mIHRoZSBIdW1hbml6ZWQgSW50ZXJu
ZXQsIGEgbm9uLXByb2ZpdCBvcmdhbml6YXRpb24gZm9jdXNlZCBvbiBwcm92aWRpbmcgZGlnaXRh
bCBpZGVudGl0eSBmb3IgdGhvc2UgaW5kaXZpZHVhbHMgbW9zdCB1bmRlci1zZXJ2ZWQNCg0KLSBK
dW4gTXVyYWksIFByb2Zlc3NvciBhdCBLZWlvIFVuaXZlcnNpdHkgd2l0aCBhIHJlc2VhcmNoIGZv
Y3VzIGluIGdsb2JhbCBjb21wdXRlciBuZXR3b3JraW5nIGFuZCBjb21tdW5pY2F0aW9uLCBhbmQg
a25vd24gYXMgdGhlICJGYXRoZXIgb2YgSmFwYW7igJlzIEludGVybmV0Ig0KDQotIEhlbm5pbmcg
U2NodWx6cmlubmUsIFByb2Zlc3NvciBpbiB0aGUgRGVwYXJ0bWVudCBvZiBFbGVjdHJpY2FsIEVu
Z2luZWVyaW5nIGFuZCBjaGFpciBvZiB0aGUgRGVwYXJ0bWVudCBvZiBDb21wdXRlciBTY2llbmNl
IGF0IENvbHVtYmlhIFVuaXZlcnNpdHksIE5ldyBZb3JrDQoNClRoZSBwbGVuYXJ5IHdpbGwgYWxz
byBpbmNsdWRlIHByZXNlbnRhdGlvbiBvZiB0aGUgSW50ZXJuZXQgU29jaWV0eSBKb25hdGhhbiBC
LiBQb3N0ZWwgU2VydmljZSBBd2FyZC4NCg0KQ2hlZXJzLA0KDQpCcmlhbiAoZm9yIHRoZSBJQUIg
YW5kIHRoZSBUZWNobmljYWwgUGxlbmFyeSBQbGFubmluZyBQcm9ncmFtKQ0K


From nobody Wed Nov 29 23:50:19 2017
Return-Path: <gonzalo.camarillo@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 7161C1279E5 for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 23:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.11
X-Spam-Level: 
X-Spam-Status: No, score=-4.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ericsson.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 gVR3o7xMnK3t for <ietf@ietfa.amsl.com>; Wed, 29 Nov 2017 23:50:16 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 17CD1128DE5 for <ietf@ietf.org>; Wed, 29 Nov 2017 23:50:15 -0800 (PST)
X-AuditID: c1b4fb3a-039e19c000004c48-ec-5a1fb83536c0
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id A2.04.19528.538BF1A5; Thu, 30 Nov 2017 08:50:14 +0100 (CET)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.60) with Microsoft SMTP Server (TLS) id 14.3.352.0; Thu, 30 Nov 2017 08:49:48 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=N6KGvCYq6HoYd5+W8yOECoHHs9ixQWga+9enytSpMUA=; b=NUjKS0DPCF2UGIT08MjNUUer8Pd8/mMCq4hZlSKu8DgX5qwaloQWWeuCasUuCTgWTp4RkmW4J6I6Mivd+u9bzRviAwVbBpkxJMd1igFiD8Z8rZ/Dw20sxQUpKPJLipq5xHPohiiLEhomPIxKr27Ehe04yHlRphyhaLNufBiKfoc=
Received: from [192.168.1.5] (178.55.231.58) by AM2PR07MB0626.eurprd07.prod.outlook.com (2a01:111:e400:840d::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.282.3; Thu, 30 Nov 2017 07:49:47 +0000
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
Subject: CEO Succession at ISOC
To: <ietf@ietf.org>
Message-ID: <81735ceb-6d84-918d-30d8-dbdca64e3398@ericsson.com>
Date: Thu, 30 Nov 2017 09:47:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [178.55.231.58]
X-ClientProxiedBy: HE1PR09CA0051.eurprd09.prod.outlook.com (2603:10a6:7:3c::19) To AM2PR07MB0626.eurprd07.prod.outlook.com (2a01:111:e400:840d::25)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: a025e854-55df-4f8b-22d0-08d537c6ee11
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(5600026)(4604075)(2017052603282); SRVR:AM2PR07MB0626; 
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0626; 3:GhOPzS9RzRkhfUqK+7kzBqjHPPMMWl/NyItGbYn5FPqOTJeqFXPAtTL50RGNWgcxn9p00Ock2lfjWoSuqhDRXg7eVSMC77S5UZZ4Fjxxp7RMJTsU+/uVf5EPEgumb4XuHVGroiSRLVE26wu3XkT3fcQRPbI0a+k4fG4XYema7PH2iInZFLwZpl1lYDIRKMzGB/E60Y5YNjMNU4+VqtVwWkU/hWQams4Iq7m6yAB/hsvqiStPcEm6PugSDgjE75Fx; 25:b/UIL2rXeMgksOqiwMGBByNdahwdULpFa+PXWvzEXquoNE6LtKcwxOGc65on7qx1vUEK7R/9JyEdmIu+vNgE65k9v25AdUf4n6cWUOTFyWzn9Om83EbhgHLNRtm4XA+P/sDJMXsgsR9Kxook//MXs+1nHiKGhhEgknEq0v2S7LccsyLwGe4frULGm0+iJu84mK3DjbHg6aKpo97p4X0zeCa1Xq3jzucyk8pxeL7AOrwWgzJPUgmicrfetMwABb+AKylSRJM4jJsGHpz5BeM+/OW6aI0xLpLqAKmvBP53Q4v/2YGg+nnC5dk2zVw12j6kjFHj/JUX33EZANAEmoYH9ahfNgMdDcC+xnPETT9ewYw=; 31:INaR/v/wiwLhPTYbUzprnfPbHHP5vXi03uhkycU/9mmz7hKpC8ZAPzAvpfub6O2omVBMipMyLQg1LgRipDw5jBbawBsqoadlukWXF29lfhjWaulxa7a4Ou7gGSE98siZeWJazUPt+zbxJ0EQf/pQwwzw9No2NpMIx7X7z15JDD0wRJJ8F3nMsRi/YIFNvmaNEnxZgSs/PT7sWFETolgk/uZHTo0yLGSCAbvcat+TumY=
X-MS-TrafficTypeDiagnostic: AM2PR07MB0626:
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=gonzalo.camarillo@ericsson.com; 
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0626; 20:hPgr/aKMulC+xJmrYFT1WwpD3p6KFhb3+MMmt2mN6ExLPc6VpL5Y4r6XBFwmUO1JgAQdioqxbnHxg4LMS+Q2F/H3bvYLKUhSHIDeqdz4nZcgycshR1nGZC/gIVkWnw6XKSkrw8vEXrf+6sjWojthShHc9qnPoy0GyBacDIxM9v3h+n08nvN7sZryBaM2mZn2da2CK9iAP9GMkOOwtWmBdGn9/uk4sohlhBF3zeQc4d56xBnjbNW8ZqRhvYzUcTAOzoMxVL9pOA7EhP7Nv707tyMmJo++mhjXzd0gB7hsjeAMMtLM3qmKIpHEB+oRiKsf4Iwfe7RafmHyaA3Mxa7mwTcm6xMWvxuRLl8s3+xpa46+X9pv27jvHmAcOvtAUWLKEvLl8+XcOrZcuIOJqYEOFOiCZR05PEZGU6Cb30+bsZp9LoOrANHbMOFHDOvg1FhDFrwhE+Bs+ABFWUsczzZHTSuWtw0VyOIqPwsAKk6Vf1BzrWW2IsHiav99nXj5Pgb4; 4:sbG7TE9WkXSnpvgjTh4G/bASmapVTNb4ZjDk2Zsv5ljBvb1sN6PNntHDchE1KP1vbubWv1/lX/3PXpZxhZZE7lqL0XGryDMY1xkxsagWlkBE3lVMHtJCuZ/XKRKPrAmoJyiSykxwEJYwo/v3QtOgougtYU3cDE5p95SyM+7tx940UuUUjwuyYobKBDGDbDnz3q8SQgGzCYpZ9W0rehjBUi3fADDn6GiZqODWwKkiYLWRYqqDLunnYIR1jV+OANq9wscVQ51fSdJ76/+BzFA+Dw==
X-Microsoft-Antispam-PRVS: <AM2PR07MB06268BC458DCB8E911D35E1B83380@AM2PR07MB0626.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(2401047)(5005006)(8121501046)(3231022)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123560025)(20161123558100)(6072148)(201708071742011); SRVR:AM2PR07MB0626; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:AM2PR07MB0626; 
X-Forefront-PRVS: 05079D8470
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(6009001)(39860400002)(376002)(366004)(346002)(199003)(189002)(81166006)(8936002)(81156014)(3846002)(101416001)(189998001)(2361001)(6116002)(106356001)(33646002)(36756003)(25786009)(2351001)(97736004)(66066001)(50466002)(65956001)(58126008)(31686004)(230700001)(53936002)(305945005)(117156002)(77096006)(6486002)(65826007)(2906002)(105586002)(8676002)(65806001)(68736007)(23676004)(47776003)(7736002)(316002)(16576012)(6666003)(16526018)(31696002)(478600001)(52116002)(83506002)(52146003)(6916009)(3480700004)(64126003)(5660300001)(2486003)(50986010)(54356010)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0626; H:[192.168.1.5]; FPR:; SPF:None;  PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTJQUjA3TUIwNjI2OzIzOkNISDcwVlhHSTUzWW8yMW93YTNQRjI5K0hN?= =?utf-8?B?RDY4LzFPSmxxZ3dydFRiU1llWGRLaERqYW1Oa2JmRHd5R1JkN3JqWXMvRGNy?= =?utf-8?B?eUNaem5yR1djdkU0M3VvdTZ4a3J6VjJZWnNVRjI2Zk92Z2htVEEzdW5tNVA4?= =?utf-8?B?MEdXZTBPVFFhcUR4VUpWM1BSaHBUM0hvNWsyaW9JY0pMNDIwakwrY0NzdURV?= =?utf-8?B?OGlTdnE5N2Y0T2x1UWRCMTQyTXBuT2taaHFpaDEydk9VbFBlVGJjUXV5bW5X?= =?utf-8?B?ekVHTDJmWlVaQUVFM0srcjlHdmVCVEVjeUliUGxjeGNIUGVaK2JraklGaGdy?= =?utf-8?B?VjY3amNZemozMEc2clpJdkpvVDVON3lYNFZjQ29JOFlobnROUEpFemFWSFdr?= =?utf-8?B?dW16QklWMUNEVWZiVlFoWVg4M0h0aGprcVV2bE9aSkk1NEVMemV0WW42aUE0?= =?utf-8?B?TEJUcnlkZ042TlJhUFNFS2ZqbmNxMWVrcTRRMnY3U2RGY1VHVzA5cmljd2p3?= =?utf-8?B?QkgvODgrMmg3ajBFR2RPT2oraUF2cDJMOUJLK2xYNFhCRnoxUjl3UG9pVkdw?= =?utf-8?B?WFlidCtVcEhWY29wc2g0aXV1M291djM1cXpzUUN4VXNZTmJsejBZc0JEQm5L?= =?utf-8?B?WWcwQXF3QXJIdnRjc2Y5cUg5blFlRFhMaTRkUXo4dEF3YWo5QUxHei9wWDBq?= =?utf-8?B?ajVDU2g4dDZxazNpUkVnQ3BET2lwQnBDc0pFdnZVODlVTGVicEt6Qm5tRnVP?= =?utf-8?B?MzBWUXpXQlY2NUd6dEFFQk1WclB0STJrdTBqMExHTnlVYVF2Z2hCREM0a3JO?= =?utf-8?B?bysyNTZXRkFYWnBhem1mb0liQ01PL09zM1J3c3J4dHF0UzQ3V3ByRXhZYmM3?= =?utf-8?B?NXNPVncrYUF5b1l6cUVzTjJ1S0h3VXNZNThLKzR6OFlUYUZKVWI5QWJTQVRT?= =?utf-8?B?QXN2YTFOUzRiNFRhQS9ZSmh5Y3RRTVVnYms4ajE4TXY2bFBOcUhLK0pyK24z?= =?utf-8?B?bVJTcTlhREZtNGlyWWRUY0lheURUUmZBQmhmN1VMaFdpTjVoZnJNMkx0WTVD?= =?utf-8?B?dTZaeE0vTHF4T2w4cVNEQXgvWnBDZ3NOSDBUZXM5ZHVFeFJtS0VncWx5RWZo?= =?utf-8?B?d0xmYTRaQkVpc0xkTFJaZzROcXNramRXakpBeUgybFc4bkl0WFY2TWtuY2xJ?= =?utf-8?B?bnp6ZTA3MWpIWk5UaitMeTB2ajkrbi9FN3E0SEl1bXRtMUViV0swZWhoY3kw?= =?utf-8?B?NllnRENiTmRuYWE3NXpESll1Y3NQcEQyYWloY2tQVjQ1ZkhJR0k3RHl3aG44?= =?utf-8?B?dTlZMGJTbXZMQlpmUW9VRmFJcWcxcFM4bkwxN0czMTYxUlFVeEdrem41NS9q?= =?utf-8?B?cThEaExFVkgyRm1jQ2NWazhEN2YwUjdaQlJKTXlDbjE5ZGo5bTdFY2lsTExI?= =?utf-8?B?djNyT2xVYVdDQllmckZMUmh1Znk0N3lFcDlIWDBXbHpGMmxHQkpmV1l4MlZV?= =?utf-8?B?eFd3OWcyZ2xNSmdYc2doT2Qzb3FOYUNIMW12SXJleDhnamR4T056RHlIWDV5?= =?utf-8?B?RHkrbHNwNFkxeUhmOTdlTTFrVXg1d3VWVHdvSk04dnlycHpDTlplSkkrRGc5?= =?utf-8?B?R21yWkZNMjJCV1hNZWp6L1lROUlYMldLK1I0T1k4R3RINVhWSnZNVlkxNnM5?= =?utf-8?B?Um1wWXJUZUdMNUp4aG9MSDhKQXJFbXF3ZlRzQjFNUFdLT1VVaWRPZ0plU0Vj?= =?utf-8?B?N0VqYXp5alhaTlBvRjJNZGdscmxZMDJweHhrWjU0VTRyWVJXWXd4SlFxTGJJ?= =?utf-8?B?c2pNUmhoRElEMlZFanVGRG1sL2FnUDZ0aDZ6S0dMNER2eXc9PQ==?=
X-Microsoft-Exchange-Diagnostics: 1; AM2PR07MB0626; 6:4dyzCICtr32YgQDCIACcM2F3YpEDuQhTdCovPG7x58rjtIaUW+xMd/W75z9TvmdAngVfGBs4o6IfVMyabpfj8rse2dHO1WAvHXh88aklIzWi3ALjnpcHAiBSZ3ASMZITNoF3+9/0SR/BwCfHqkmmg405HeY3XBQDYhOaYv+yjTgY4Grs2jGycIjMcRWJx9VPYmqNKVcKFb4zSMp1MtGGjPllah3usDNAMOnpJvNk5pFILZ1FBma6m1iigyDomGy617CTdNMrq9wDdPkLOnKDdo+M2GwJc4bd2cFYjkVvET27sh0zKgoBnTFi9dWldjwjsSelu7cM2rZvNxlNW77xb/v/MojQY8YD3Op3EeF5o9Q=; 5:OvgNSnSL/84hEmcIUB7afqBt84VD9siJkNqjZQKZtVPhiWoLmEA+WL/XI/4PTES+kiFv32aKDiZnD7QZRKblz5dC+LOTBBXPROS/rDB5o538/9CwUyKybCFpT8/UfPlgYaiJE4fYm2qTWKNKhMOoUUeyceG4yUjgVbri+u0slxg=; 24:qzmRXso9ZgHokhfys6naRaO52HIjA6Rw2Ghv6dnFUOZZZOWBJy4rwXJHKmU7sotbhaDmh6ZQARIWyJZzXHnxbS5h7CVTFMQpFucI2OflghI=; 7:XPWdceX5cZ3YYXG02ywzbXJYJ0JUwnfQXhjCjWfiZmntNyr7U0CFy52Yv7U+jPcXD316FLuVu1/ad0jZSE+HTlRgZM+rGNSslOjn9c8WbWLU/7hJ9S8KgZMYhPGKXg9oQUBYP6qBtKszmOLp9qnMlKoxG7BUuHBQC+SJ3XMY5Ai22mhokfK+zC4nDoOZOBQGWLU7Qd6Pzo7S4q8tr5MSXAqDsdtZVwKdeRZXBxgQ3V7S0peLKxo/99nNJt8ShyjX
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 30 Nov 2017 07:49:47.7758 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: a025e854-55df-4f8b-22d0-08d537c6ee11
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0626
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDIsWRmVeSWpSXmKPExsUyM2K7ja7ZDvkogzP/uS2ebZzP4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujE03prIU/BOpaNr0nLGB8bNAFyMnh4SAicTK98tYuhi5OIQE DjNKHN58kxXCOcEocWHnC3YQh0Wgl1li6+avTBCZdiaJRROusoL0swlYSGy5dZ8FxBYWkJc4 P+0pM4gtIiAsceTRP3YQm1fAXqL3+nmwGhYBVYlTH1eC1YgKxEhMfHCREaJGUOLkzCdANRwc zAKaEut36YOEmQXEJW49mc8EYctLbH87hxnibEWJ+WsmgN0jITCdUWJj73Kwe4QEtCWWP2th gSiSlTh6dg7YTAkBX4nX/1Mg6pcwSpw9eJIdomYKu8SMXkMIW0vi+1GIXxgFEiX+3nvLBtFw gU3iVPcuRoiibInP6z8wwjSsu/qRGaJoAbPE7C/zoRIyEssXvYNKPGaVmL9pNhPEeakSW260 QI1dIwSU+Mo8gVFzFlIQzEIEwSykIJiFFAQLGFlWMYoWpxYX56YbGemlFmUmFxfn5+nlpZZs YgSmiYNbflvtYDz43PEQowAHoxIP78sV8lFCrIllxZW5hxglOJiVRHgDK4FCvCmJlVWpRfnx RaU5qcWHGKU5WJTEeU968kYJCaQnlqRmp6YWpBbBZJk4OKUaGI0NY/+/i15cqbw6oa3Cfb/E guWsoo2r01085BJqPz8qMXJaI7pxfwL/6sCjpse8v60vEjjlte5NaT4v91nuHbdCJ+h//yHU EVChrCb0Ucf/rmOEk3iZkPmDP4e4ihk2Pli4/ZR7UdExEZV1J9wWCLXeUNq3dtaRb5q7Jp1R 3CnCWfeKZbHeYSWW4oxEQy3mouJEADtNQcQPAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ubw0sRvzdRsPHYQ9Z97jy9_v5Co>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 07:50:18 -0000

Hi,

you will by now have heard that Kathy Brown, ISOC's CEO, has informed
the board that she will not seek another extension of her contract,
which will end at the end of 2018.

Before I discuss the search and selection process ahead of us, on
behalf of the whole board I want to express our gratitude to Kathy for
the strong leadership and commitment she has shown in taking ISOC
forward. Kathy has worked tirelessly in the interests of the
organization, always putting her job before herself. The changes she
has brought about have been both deep and wide-ranging, and she has
succeeded in readying the organization for the many challenges and
opportunities that lie ahead.

While the board would have been happy for Kathy to continue as CEO for
a further term, we also understand and respect the decision that she
has taken to dedicate time to her family. When the time comes, I hope
you will all join me in wishing Kathy the very best in her life after
ISOC.

During the process of searching for and selecting a new CEO,
operational continuity in the organization will be a key priority. The
board has just approved the 2018 Action Plan, which provides clear
direction for ISOC for the coming year. The organization will focus on
the execution of the plan during the whole CEO succession process.
Kathy will remain fully engaged and committed to that work until the
conclusion of the process.

As background, we will not be starting the CEO succession process from
scratch.  Last year, the board decided that ISOC needed to have a CEO
Succession Plan in place at all times.  Developing such a plan was one
of the focus areas for the board this year. The material we developed
in that context will naturally be used in the current succession
process.  In addition, Kathy has always taken the development of her
staff very seriously. Since Kathy has worked with her staff to improve
their leadership skills and competences, the board will consider both
external and internal candidates for the CEO position.

The next step for the board is to form a CEO Search Committee.  Based
on the CEO Succession Plan material mentioned earlier, the committee
will develop a time plan, job description, channels to distribute the
call, a process to short-list candidates, all leading to selection of
an excellent new CEO who can take over as Kathy departs. In the mean
time, if you have any input, please let us know by sending an email
to:

  ceo-succession@elists.isoc.org

Emails sent to the address above will be treated as confidential
within the ISOC board.

Cheers,

Gonzalo Camarillo (for the board)
Chair - ISOC Board of Trustees


From nobody Thu Nov 30 03:10:27 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 7B86F129443; Thu, 30 Nov 2017 03:10:25 -0800 (PST)
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-atarius-dispatch-meid-urn.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-atarius-dispatch-meid-urn-13
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151204022540.4861.7280220395105881628@ietfa.amsl.com>
Date: Thu, 30 Nov 2017 03:10:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FJ0tvKvNdVAlH9xc9GcuJVqtDTU>
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, 30 Nov 2017 11:10:25 -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 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-atarius-dispatch-meid-urn-??
Reviewer: Roni Even
Review Date: 2017-11-30
IETF LC End Date: 2017-12-08
IESG Telechat date: Not scheduled for a telechat

Summary: The document is ready for publication as an Informational RFC.

Major issues:

Minor issues:

Nits/editorial comments:
This document defines a URN namespace for the 3GPP2 and a Namespace Specific 
String (NSS) for the Mobile Equipment Identity (MEID). As such I did not see
and issues with the registration.



From nobody Thu Nov 30 08:45:21 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 56BCA1200FC for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 08:45:20 -0800 (PST)
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 HfJBDqsxK_nh for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 08:45:19 -0800 (PST)
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 1DE84127876 for <ietf@ietf.org>; Thu, 30 Nov 2017 08:45:19 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5446120008; Thu, 30 Nov 2017 11:47:52 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6A17F80683; Thu, 30 Nov 2017 11:45:18 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: IAOC role
In-Reply-To: <514edc7c-43ad-44d9-2488-17261381cd84@gmail.com>
References: <514edc7c-43ad-44d9-2488-17261381cd84@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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: Thu, 30 Nov 2017 11:45:18 -0500
Message-ID: <27314.1512060318@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cepOS7cKsiuMinpxYdFo-b62MQI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 16:45:20 -0000

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


Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    > The IASA 2.0 effort is discussing the *future* of IASA and the IAOC.
    > That isn't my concern here, and there's a mailing list for it
    > (https://www.ietf.org/mailman/listinfo/iasa20).

    > What I'm concerned about is that fact that a couple of *current* IAOC
    > slots are up for appointment shortly (by NomCom and IESG respectively),
    > with several fine candidates in each case.

    > All I'm asking is that in their considerations, the appointing bodies
    > keep in mind the definition of the IAOC's role:

    > The IAOC's role is to provide appropriate direction to the IAD, to
    > review the IAD's regular reports, and to oversee IASA functions to

1) do you believe that IAOC cmte have unreasonably expanded their scope?

2) despite this definition, a bunch of new things have shown up for the IAOC,
   and that now includes:
     * IETF Trust supervision
     * Tools cmte: managing contractors
     * something else I forgot.

Reading the reports from the IAD is still a major part; but some things have
devolved elsewhere.  Also the IAD doesn't necessarily have the right skill
set to figure out technical issues that come from contractors.
Also, financial repors, while puck-handled by the IAD have been provided by
an ISOC resource until September, and now are done by AMSL under contract.

So your advice that to pay attention to the IAD oversight misses the other
kinds of oversight that now also occurs.

{me: non-voting member of finance subcmte, nominee for IESG member.
Note: I've told the IESG that I won't be IAOC chair, and to pick someone else
if they need an IAOC chair}

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


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

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

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlogNZ4ACgkQgItw+93Q
3WW3Awf6AnQnknPiuzLX/2TYRiqSJCAUuETWUc1sPrwRCojlfSb/JLW9Sushk+bs
wtnyZfj9eWi6l2I+vUWMKd6X244A9O0IdxPYkD3BFVn8EWMHPPmcDDJTc20J0GBO
OS0cZVWABZxZYBnhQaUJKREi74bft48YVq5pgXxfPJQ6+rWY4heJEQHuqYx8Jqw3
VzDkjL1tbRRIfRVdgcziBSs7TL1vvCtzbDx1WEdmcPzKH6cl+Pk59hks4Opcky+p
ZMYCmyOd4cpj2VOmWK6MK5pd4pUPA2md+x+2RjwdvtwLUGe4rnjM+mhbFEAUA7pI
zcEjAmSbXJ1G2POPxX+quxmz7EPzoQ==
=2+IZ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Nov 30 08:50:44 2017
Return-Path: <jclarke@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 C6ED21200B9; Thu, 30 Nov 2017 08:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, 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 EI1swbBJsFGl; Thu, 30 Nov 2017 08:50:36 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33DFC1279EB; Thu, 30 Nov 2017 08:50:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1273; q=dns/txt; s=iport; t=1512060635; x=1513270235; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=RaVBbHmcei1FlC+3QWcAIcitg3E8wMasq45uUbGeFW4=; b=T5+0j3PdncnmRxR4HJrnCaiidSeXAs3e3U6JPI1E5WaU8LBEslB0thOm wJw14Aedf3EgWPJxTM3A+1D/4kQvUk+WsszPNmWtEhR9ZQu0Rc5YMUWgm aWQraEk9E5fPJ848/YcnB2Jan4tVF5QMDBhR+tgKIeh4KQJ6/o1+Z//mc U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D5AQB1NiBa/5FdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM8gVSEJpkTgX2WdoIRCoU7AoUhQRYBAQEBAQEBAQFrKIUgAQU?= =?us-ascii?q?jDwFGEAsYAgImAgJXBg0IAQGKHqYfgieKZgEBAQEBAQEBAQEBAQEBAQEBIYEPg?= =?us-ascii?q?jKBZwEhgVaCEoMCiDWCYwWTFI9Hi1+JMowJh0qWRYE6Jg0lgVFMIxWCZIRyI4o?= =?us-ascii?q?6AQEB?=
X-IronPort-AV: E=Sophos;i="5.45,341,1508803200"; d="scan'208";a="37981175"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Nov 2017 16:50:34 +0000
Received: from [10.118.87.88] (rtp-jclarke-nitro7.cisco.com [10.118.87.88]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id vAUGoXgf021698; Thu, 30 Nov 2017 16:50:34 GMT
Subject: Re: Opsdir last call review of draft-mm-wg-effect-encrypt-13
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: ops-dir@ietf.org, draft-mm-wg-effect-encrypt.all@ietf.org, IETF <ietf@ietf.org>
References: <151196946679.7944.3160175486224623517@ietfa.amsl.com> <CAHbuEH4wanQoMrDZj+kvZjkv+jBUUVfvnsAx2iS+9tFQk4N8iA@mail.gmail.com>
From: Joe Clarke <jclarke@cisco.com>
Organization: Cisco
Message-ID: <45c14d90-8d3e-c165-54ea-f72dfb282c29@cisco.com>
Date: Thu, 30 Nov 2017 11:50:33 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAHbuEH4wanQoMrDZj+kvZjkv+jBUUVfvnsAx2iS+9tFQk4N8iA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xGZYtcUQ_YLGT-04vpd_4WvFphM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 16:50:38 -0000

On 11/29/17 11:21, Kathleen Moriarty wrote:
>> To that end, it might be useful to specifically point out where vendors have a
>> role to fill in some of these areas to allow for transit encryption while
>> providing the necessary hooks for operators to manage and troubleshoot their
>> network.  Specifically, in many of the troubleshooting scenarios, operators
>> won't be able to provide truly useful tools to their end users unless the
>> vendors provide the right level of visibility.
> 
> Do you have suggested text that we could add to address this gap from
> your experience?

Maybe something along the lines of the following in Section 2.1.2 (or
maybe in a section of its own):

"Vendors must be aware that in order for operators to better
troubleshoot and manage networks with increasing amounts of encrypted
traffic, built-in diagnostics and serviceability must be enhanced to
provide detailed logging and debugging capabilities that, when possible,
can reveal cleartext network parameters.  In addition to traditional
logging and debugging methods, packet tracing and inspection along the
service path will provide operators the necessary visibility to continue
to diagnose problems reported both internally and by their customers."

Joe


From nobody Thu Nov 30 08:55:26 2017
Return-Path: <lberger@labn.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 099501293DA for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 08:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=labn.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 V5wJjMnSfJvJ for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 08:55:22 -0800 (PST)
Received: from outbound-ss-1812.hostmonster.com (gproxy1-pub.mail.unifiedlayer.com [69.89.25.95]) (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 75EA912714F for <ietf@ietf.org>; Thu, 30 Nov 2017 08:55:22 -0800 (PST)
Received: from cmgw2 (cmgw3 [10.0.90.83]) by gproxy1.mail.unifiedlayer.com (Postfix) with ESMTP id 1CDB8175D84 for <ietf@ietf.org>; Thu, 30 Nov 2017 09:55:22 -0700 (MST)
Received: from box313.bluehost.com ([69.89.31.113]) by cmgw2 with  id gGvJ1w00b2SSUrH01GvMnW; Thu, 30 Nov 2017 09:55:22 -0700
X-Authority-Analysis: v=2.2 cv=dZfw5Tfe c=1 sm=1 tr=0 a=h1BC+oY+fLhyFmnTBx92Jg==:117 a=h1BC+oY+fLhyFmnTBx92Jg==:17 a=IkcTkHD0fZMA:10 a=xqWC_Br6kY4A:10 a=sC3jslCIGhcA:10 a=48vgC7mUAAAA:8 a=SEEZGfWK5IIqbRLzb9AA:9 a=QEXdDO2ut3YA:10 a=Sbs7aBm93X4A:10 a=w1C3t2QeGrPiZgrLijVG:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc: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=3V0kSSU0OR1wPyQW5HBJ45YZV+WLSw2WkgLIj56fczs=; b=2jdVzNpdKuOGwiqZdeFmAiAOow JFbXpXznUTyynBGIBfbQNMNJv8ZbxNCQ/lPWb6OCyhdmhm7NpKtvWvG5LRmaGVgdcnB80Ygo+OGjo vMfYutUuNUZxOer2LXB/gmPgW;
Received: from pool-100-15-86-101.washdc.fios.verizon.net ([100.15.86.101]:44044 helo=[IPv6:::1]) by box313.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from <lberger@labn.net>) id 1eKS7K-003S4y-MW; Thu, 30 Nov 2017 09:55:18 -0700
Subject: Re: IAOC role
To: Michael Richardson <mcr@sandelman.ca>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF discussion list <ietf@ietf.org>
References: <514edc7c-43ad-44d9-2488-17261381cd84@gmail.com> <27314.1512060318@obiwan.sandelman.ca>
From: Lou Berger <lberger@labn.net>
Message-ID: <c51962c7-6db6-777c-7b9a-260422894db8@labn.net>
Date: Thu, 30 Nov 2017 11:55:17 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <27314.1512060318@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box313.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-BWhitelist: no
X-Source-IP: 100.15.86.101
X-Exim-ID: 1eKS7K-003S4y-MW
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: pool-100-15-86-101.washdc.fios.verizon.net ([IPv6:::1]) [100.15.86.101]:44044
X-Source-Auth: lberger@labn.net
X-Email-Count: 5
X-Source-Cap: bGFibm1vYmk7bGFibm1vYmk7Ym94MzEzLmJsdWVob3N0LmNvbQ==
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ne47Zf9dDGDzCOpuMPfzm4fHE4s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 16:55:24 -0000

On 11/30/2017 11:45 AM, Michael Richardson wrote:
>      * Tools cmte: managing contractors
FWIW the tools committee is an activity of the IESG not IAOC -- this was
clarified sometime in the last year or two. The Technology Management
Committee (https://iaoc.ietf.org/committees.html#TMC) is the IAOC sub
committee that manages the admin/contract side for the tools committee.

Lou



From nobody Thu Nov 30 09:15:33 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 B4CF4126D85; Thu, 30 Nov 2017 09:15:25 -0800 (PST)
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 E7QiZUIkqKSZ; Thu, 30 Nov 2017 09:15:23 -0800 (PST)
Received: from mail-pl0-x230.google.com (mail-pl0-x230.google.com [IPv6:2607:f8b0:400e:c01::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 7669B12762F; Thu, 30 Nov 2017 09:15:23 -0800 (PST)
Received: by mail-pl0-x230.google.com with SMTP id q7so4637130plk.0; Thu, 30 Nov 2017 09:15:23 -0800 (PST)
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=yP2VWiCvO5eGB0JQ8kuNm0NrxeEjq+wfMB+YpaCnQww=; b=ErY5QqtcjS7H70L0WYlbcbpumVit4A2hXfEFihg1nzIEaURIVCADR/fy9GOT+eGYs2 xYFrhE7kMW6zpoLSfW1MGNHcHHfNHPOyxa0rLWloZ8gjsUaFDSdVU7uL7S8+2MqAhMDr 8hEU6LvfQ8RsqS14bOjT3kKDN+WfdpHyunoZ7IJG/SwZLr7LUPJ7BdYLdSngpgphzY7d t3PNmqvhy96kzT+yyJ/sK21Pq2008Xt2/Ulf0dRyB9Q7bw7DydkwZb3BNORaWcmDLhdn AmoIYj34MIwrg7PYd48hTzlbq2SMv2Hvk39XxczGfqZjoONTJEuXmCDLJV0SnufypAb1 MgEw==
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=yP2VWiCvO5eGB0JQ8kuNm0NrxeEjq+wfMB+YpaCnQww=; b=At4wpehpSNGs0hGShGkkQrbPSb308BrmWKRH9nW7vxSjnSqbRuPIMf+QeSYlgCFIvm jLRv6dNDYx/xYhCT7bXWTd+6/9CpuI24wR+mNmx8HBgnLixLai5bdujEIu9KClWPlMWW R/0QAgLwllRchLYXLvE00NxuGyceKOvhsPzzrR/BZJFDplRodfzjCbvJgG3PDtycoi+P 5K0iF03QP3Ewih3L4lWhtNP/f89f4Jkmw5fqquvgIH29/tP1QZMOXd3LW4etfMe1Q61E HXGWFALZQ/HJX9r6UPeT/T0fS6imFAoGahBX9e7aiEvEr9a3UlgigApCNthl2zpjFOvu T66g==
X-Gm-Message-State: AJaThX4lxkMNbqttxnxw3ctlKhMZKcN9mf0m3/mv+yIfFVS982zJogHE 6Ftip9KZ8CKQ5H3xFgTbPCPoyseUhrFEyIRDUrc=
X-Google-Smtp-Source: AGs4zMbNQIYWMIUlNg/+KM4jqI7LP18FeYmE6Tv6ypGYxsKHMzPOf7g2S/iaSjoYV5evyCId/0SankHWM9nJaYfsvek=
X-Received: by 10.159.197.5 with SMTP id bj5mr3353135plb.219.1512062122816; Thu, 30 Nov 2017 09:15:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.100.186.208 with HTTP; Thu, 30 Nov 2017 09:14:42 -0800 (PST)
In-Reply-To: <45c14d90-8d3e-c165-54ea-f72dfb282c29@cisco.com>
References: <151196946679.7944.3160175486224623517@ietfa.amsl.com> <CAHbuEH4wanQoMrDZj+kvZjkv+jBUUVfvnsAx2iS+9tFQk4N8iA@mail.gmail.com> <45c14d90-8d3e-c165-54ea-f72dfb282c29@cisco.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 30 Nov 2017 12:14:42 -0500
Message-ID: <CAHbuEH6C8+HgUskSwndj4TK3jdu5cUy7YB+5AAubVust0vzWXA@mail.gmail.com>
Subject: Re: Opsdir last call review of draft-mm-wg-effect-encrypt-13
To: Joe Clarke <jclarke@cisco.com>
Cc: ops-dir@ietf.org, draft-mm-wg-effect-encrypt.all@ietf.org,  IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jEbyJZw_JU9f6EoyLQExXKGqVbg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 17:15:26 -0000

On Thu, Nov 30, 2017 at 11:50 AM, Joe Clarke <jclarke@cisco.com> wrote:
> On 11/29/17 11:21, Kathleen Moriarty wrote:
>>> To that end, it might be useful to specifically point out where vendors have a
>>> role to fill in some of these areas to allow for transit encryption while
>>> providing the necessary hooks for operators to manage and troubleshoot their
>>> network.  Specifically, in many of the troubleshooting scenarios, operators
>>> won't be able to provide truly useful tools to their end users unless the
>>> vendors provide the right level of visibility.
>>
>> Do you have suggested text that we could add to address this gap from
>> your experience?
>
> Maybe something along the lines of the following in Section 2.1.2 (or
> maybe in a section of its own):
>
> "Vendors must be aware that in order for operators to better
> troubleshoot and manage networks with increasing amounts of encrypted
> traffic, built-in diagnostics and serviceability must be enhanced to
> provide detailed logging and debugging capabilities that, when possible,
> can reveal cleartext network parameters.  In addition to traditional
> logging and debugging methods, packet tracing and inspection along the
> service path will provide operators the necessary visibility to continue
> to diagnose problems reported both internally and by their customers."

Thank you, Joe!

>
> Joe



-- 

Best regards,
Kathleen


From nobody Thu Nov 30 10:04:12 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 48BA51286AB for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 10:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFJTt5qOu8ge for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 10:04:08 -0800 (PST)
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 9F42F120726 for <ietf@ietf.org>; Thu, 30 Nov 2017 10:04:08 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 76CDC20008 for <ietf@ietf.org>; Thu, 30 Nov 2017 13:06:41 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 61F9782CCB for <ietf@ietf.org>; Thu, 30 Nov 2017 13:04:07 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: IAOC role
In-Reply-To: <c51962c7-6db6-777c-7b9a-260422894db8@labn.net>
References: <514edc7c-43ad-44d9-2488-17261381cd84@gmail.com> <27314.1512060318@obiwan.sandelman.ca> <c51962c7-6db6-777c-7b9a-260422894db8@labn.net>
X-Mailer: MH-E 8.6; nmh 1.7-RC3; 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: Thu, 30 Nov 2017 13:04:07 -0500
Message-ID: <13841.1512065047@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yZpJuze8Zv72Dos8K8EsfpjndPg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 18:04:10 -0000

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


    > On 11/30/2017 11:45 AM, Michael Richardson wrote:
    >> * Tools cmte: managing contractors

Lou Berger <lberger@labn.net> wrote:
    > FWIW the tools committee is an activity of the IESG not IAOC -- this was
    > clarified sometime in the last year or two. The Technology Management
    > Committee (https://iaoc.ietf.org/committees.html#TMC) is the IAOC sub
    > committee that manages the admin/contract side for the tools committee.

That's an important clarification, and thanks for pointing it out.
Often it's not what you don't know ("known unknowns"), but the things you
thought you knew, but it turns out you didn't that become problems

That's not what nomcoms' I was involved with before had understood, so I'm
glad that it's clearer now.

--
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+93Q3WUFAlogSBcACgkQgItw+93Q
3WUxmwf9EiNz9glyTThlPoVKcMugjIYhla3+gX++Yxnudkdzl5QDr+5mGGa6Qo1Y
ZhO1BFq3l3ji1VnI0gzEOc8k8UIKOz3PST4O5s1JAimNld4jjCHlU7Xk9ZVTFoml
/4tktAgjLYBWfmxa0QLR4CuJP8kTkixhmr/FA5fP3VtsSR5qswceQ95qD0dqHGNL
Qc1lJHkNdsEpqWU+am9q8nOvGKW/mTKBhixzYcgPYf3CCU6VkZtemBj/R4K/5nwZ
1F1KrpLPMqC1ToRRH+uBgIkfyajY80X3ja6hG6Q+89eIw3YoNEzBejvEVg6ob8Zm
0RrceOqLCRxg1OSPAYc5EWbKq0ev3w==
=86Am
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Nov 30 13:44:45 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 E87FB1294F3; Thu, 30 Nov 2017 13:44:37 -0800 (PST)
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-intarea-probe.all@ietf.org, int-area@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-ietf-intarea-probe-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151207827781.25922.11037452280009787600@ietfa.amsl.com>
Date: Thu, 30 Nov 2017 13:44:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q8-LhR0axmBhk_z2tfev78a0VRQ>
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, 30 Nov 2017 21:44:38 -0000

Reviewer: Joel Halpern
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 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-intarea-probe-07
Reviewer: Joel Halpern
Review Date: 2017-11-30
IETF LC End Date: 2017-12-13
IESG Telechat date: 2017-12-14

Summary: This document is almost ready for publication as a Proposed Standard
RFC.

Major issues:
    I can not determine from the text why two identification objects are
    sometimes allowed, or how they are to be used.  The texts seems to indicate
    that they can be somehow combined to identify a single probed interface. 
    But I can not see how.

Minor issues:
    In section 2.1 in describing the usage when the probed interface is
    identified by name or ifindex, the text refers to MIBII, RFC 2863.  I would
    expect to see it refer instead (or at least preferentially) to RFC 7223,
    the YANG model for the Interface stack.

    The E bit in the Extended ICMP Echo reply seems a bit odd.  Shall we try to
    encode all the possible interface types in this field?  Shall we try to
    distinguish Ethernet directly over fiber from Ethernet over ...?  What
    about an emulated Ethernet interface (pseudowire, etc.)  I do not
    understand why this is here, and fear it is ambiguous.

Nits/editorial comments:
    I find the description of the node containing the proxy interface as being
    "the probed node" as being somewhat odd, as it is not the node containing
    the probed interface.  I would have expected it to be called "the proxy
    node"?

    Very nitpicky: In section 4, the step reading "If the Code Field is equal
    to No Error (0) and the L-bit is clear, set the A-Bit." probably ought to
    say "otherwise, clear the A-bit."



From nobody Thu Nov 30 14:02:26 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 237841294F8; Thu, 30 Nov 2017 14:02:13 -0800 (PST)
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: i2rs@ietf.org, ietf@ietf.org, draft-ietf-i2rs-yang-network-topo.all@ietf.org
Subject: Genart last call review of draft-ietf-i2rs-yang-network-topo-18
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151207933307.11765.1286095222502008848@ietfa.amsl.com>
Date: Thu, 30 Nov 2017 14:02:13 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zpg-gIj1ZQmdPzVuNyXo6nb1mik>
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, 30 Nov 2017 22:02:13 -0000

Reviewer: Stewart Bryant
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-i2rs-yang-network-topo-18
Reviewer: Stewart Bryant
Review Date: 2017-11-30
IETF LC End Date: 2017-12-11
IESG Telechat date: 2017-12-14

Summary: This document has been significantly improved by incorporating the
feedback from the specialist reviewers and by fixing the English.

Major issues: None

Minor issues: None

Nits/editorial comments: None



From nobody Thu Nov 30 14:31:35 2017
Return-Path: <bill.wu@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 3041F127419; Wed, 29 Nov 2017 21:55:23 -0800 (PST)
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 XZeTAhFQL97U; Wed, 29 Nov 2017 21:55:20 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 26AEE1200F1; Wed, 29 Nov 2017 21:55:20 -0800 (PST)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 12FCC1DAB0134; Thu, 30 Nov 2017 05:55:17 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 30 Nov 2017 05:55:17 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.219]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0361.001; Thu, 30 Nov 2017 13:55:10 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Greg Mirsky <gregimirsky@gmail.com>, Tissa Senevirathne <tsenevir@gmail.com>
CC: "huubatwork@gmail.com" <huubatwork@gmail.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "Ronald P. Bonica" <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, The IESG <iesg@ietf.org>, "Benoit Claise (bclaise)" <bclaise@cisco.com>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
Subject: RE: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
Thread-Topic: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
Thread-Index: AQHTSLOu7WlIvr5ZZEiOwcl87rQjeKLsKAEAgASSTRCAAeTagIABSKzggAAheACAAVgBYIAbA7qAgBgk0gCAAJXfgIAALiIAgAAc0wCAAiIVAIAAIb2AgABvLICAAI9vQA==
Date: Thu, 30 Nov 2017 05:55:09 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA9ACDABAD@nkgeml513-mbx.china.huawei.com>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com> <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com> <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.com> <646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com> <1b527039-bf80-ead5-e341-c8cfeb24f855@gmail.com> <CAMdAHv-iiZ5ScQCj1OZZs6C3FZFaRZbiXbm6--ktN3KZz7b4Ag@mail.gmail.com> <CA+RyBmXLHmkQgU8eJKUabYRcpkYobDbU6D7DR++yw8X6UwGxcA@mail.gmail.com>
In-Reply-To: <CA+RyBmXLHmkQgU8eJKUabYRcpkYobDbU6D7DR++yw8X6UwGxcA@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.136.79.67]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA9ACDABADnkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HrD4BBqvRwKalQfCYH-aw_vlfLY>
X-Mailman-Approved-At: Thu, 30 Nov 2017 14:31:34 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 05:55:23 -0000

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

TmljZSB0byBoZWFyIGZyb20gVGlzc2EsIHNhbWUgd2lzaCBmb3IgeW91LiBUaGFua3MgR3JlZyBp
biBTaW5nYXBvcmUgdG8gaGVscCBhZGRyZXNzIGxhc3QgY29tbWVudCB0b2dldGhlciwgYWxzbyB0
aGFua3MgR3JlZyBhIGxvdCBvZiBpbnB1dHMgdG8gdGhpcyB3b3JrIGFsbCBhbG9uZyB0aGUgd2F5
LiBBcHByZWNpYXRlZCBhcyB3ZWxsLg0KSSBzaG91bGQgaGF2ZSBzZW50IGEgbm90ZSBvdXQgZWFy
bGllciBkdXJpbmcgYnVzeSBJRVRGIHdlZWssIHNvcnJ5IGFib3V0IHRoYXQuDQoNCi1RaW4NCuWP
keS7tuS6ujogR3JlZyBNaXJza3kgW21haWx0bzpncmVnaW1pcnNreUBnbWFpbC5jb21dDQrlj5Hp
gIHml7bpl7Q6IDIwMTflubQxMeaciDMw5pelIDEzOjE4DQrmlLbku7bkuro6IFRpc3NhIFNlbmV2
aXJhdGhuZQ0K5oqE6YCBOiBodXViYXR3b3JrQGdtYWlsLmNvbTsgQ2FybG9zIFBpZ25hdGFybyAo
Y3BpZ25hdGEpOyBpZXRmQGlldGYub3JnOyBSb25hbGQgUC4gQm9uaWNhOyBsaW1lLWNoYWlyc0Bp
ZXRmLm9yZzsgVGhlIElFU0c7IEJlbm9pdCBDbGFpc2UgKGJjbGFpc2UpOyBsaW1lQGlldGYub3Jn
OyBRaW4gV3U7IGRyYWZ0LWlldGYtbGltZS15YW5nLWNvbm5lY3Rpb25sZXNzLW9hbUBpZXRmLm9y
Zw0K5Li76aKYOiBSZTogW0xpbWVdIExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtbGltZS15YW5nLWNv
bm5lY3Rpb25sZXNzLW9hbS0xMS50eHQ+IChHZW5lcmljIFlBTkcgRGF0YSBNb2RlbCBmb3IgQ29u
bmVjdGlvbmxlc3MgT3BlcmF0aW9ucywgQWRtaW5pc3RyYXRpb24sIGFuZCBNYWludGVuYW5jZShP
QU0pIHByb3RvY29scykgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCg0KSGkgVGlzc2EsDQp0aGFuayB5
b3UgZm9yIHlvdXIga2luZCB3b3JkcywgbXVjaCBhcHByZWNpYXRlZC4gV2lzaCB5b3UgYWxsIHN1
Y2Nlc3MgaW4geW91ciBlbmRlYXZvcnMgYW5kIGhvcGUgeW91J2xsIGZpbmQgb3Bwb3J0dW5pdHkg
dG8gcmV0dXJuIHRvIElFVEYgd29yayBzb29uZXIgdGhhbiBsYXRlci4NCg0KQmVzdCByZWdhcmRz
LA0KR3JlZw0KDQpPbiBXZWQsIE5vdiAyOSwgMjAxNyBhdCAyOjQwIFBNLCBUaXNzYSBTZW5ldmly
YXRobmUgPHRzZW5ldmlyQGdtYWlsLmNvbTxtYWlsdG86dHNlbmV2aXJAZ21haWwuY29tPj4gd3Jv
dGU6DQpJIGhhdmUgYmVlbiBvdXQgb2YgSUVURiBmb3IgYSB3aGlsZSBidXQgc3RpbGwgcmVjZWl2
ZXMgTElNRSBXRyBlbWFpbHMuDQoNCkFzIHRoZSBvcmlnaW5hbCBhdXRob3Igb2YgdGhlIGNvbm5l
Y3Rpb25sZXNzIGRyYWZ0IEkgZGVsaWJlcmF0ZWx5IGF2b2lkZWQgbWFraW5nIGFueSBjb21tZW50
cyBhcyBJIGRvIG5vdCBoYXZlIGFkZXF1YXRlIHRpbWUgdG8gZG8gYSBnb29kIGpvYi4NCg0KSG93
ZXZlciwgSSBoYXZlIGJlZW4gcmVhZGluZywgd2l0aCBncmVhdCByZXNwZWN0LCB0aGUgY29tbWVu
dHMgR3JlZyBNaXJza3kgd2FzIG1ha2luZyB0byBtYWtlIHRoZXNlIGRyYWZ0cyBiZXR0ZXIgYm90
aCB0ZWNobmljYWxseSBhbmQgZWRpdG9yaWFsbHkuIEkgd2FudCB0byBleHRlbmQgYSB3ZWxsIGRl
c2VydmVkIHRoYW5rIHlvdSB0byBHcmVnLiBUaGFuayBZb3UgR3JlZy4NCg0KQWxzbyBJIGRvIG5v
dCBhZ3JlZSB3aXRoIENhcmxvcyBjb21tZW50cyBvbiBIdWJicyBvYnNlcnZhdGlvbnMsIGkuZS4g
T2ggRHJhZnQgaXMgaW4gSUVURiBlZGl0b3JzIHF1ZXVlIGFuZCBpdCBpcyB0b28gbGF0ZS4gTWF5
IGJlIHRpbWUgdG8gcHVsbCBpdCBvdXQgZnJvbSB0aGUgcXVldWUgb3IgY3JlYXRlIGVycmF0YSBp
ZiB0aGUgY2hhbmdlcyBhcmUgc2lnbmlmaWNhbnQgZW5vdWdoLg0KDQpJZiBlaXRoZXIgb2YgdGhl
c2UgaGFwcGVucyBJIGRvIGxpa2UgdG8gc3VnZ2VzdCB0d28gdGhpbmdzDQoNCjEuIEFwcG9pbnQg
YW4gZWRpdG9yIHdobyBjYW4gc2hlcGhlcmQgZWRpdHMgYW5kIHByZXNlbnRhdGlvbiBhc3BlY3Rz
IG9mIHRoZSBkcmFmdA0KMi4gUHJvdmlkZSBhZGVxdWF0ZSB0aW1lIGFuZCBiZSB0cmFuc3BhcmVu
dCB0byBzaGFyZSB3aXRoIHRoZSBXRyBvbiB3aGF0IGlzIGFncmVlZCBvciBhcHBvaW50IGEgdGVj
aG5pY2FsIHBhbmVsDQoNCg0KDQoNCk9uIFdlZCwgTm92IDI5LCAyMDE3IGF0IDEyOjM5IFBNLCBI
dXViIHZhbiBIZWx2b29ydCA8aHV1YmF0d29ya0BnbWFpbC5jb208bWFpbHRvOmh1dWJhdHdvcmtA
Z21haWwuY29tPj4gd3JvdGU6DQpIZWxsbyBDYXJsb3MsDQoNClRoYW5rIHlvdSBmb3IgdGhlIGFk
ZGl0aW9uYWwgaW5mb3JtYXRpb24uDQoNCkFzIEkgbWVudGlvbmVkIEkgYWxyZWFkeSBsb29rZWQg
YXQgdmVyc2lvbiAxOCBiZWNhdXNlIHRoYXQgd2FzIG1lbnRpb25lZA0KaW4gR3JlZ3MgcmVzcG9u
c2UuDQoNCkkgaGF2ZSB1bmRlcnN0b29kIHRoYXQgdGhpcyBkcmFmdCB3YXMgZGlzY3Vzc2VkIGlu
IFNpbmdhcG9yZS4NClVuZm9ydHVuYXRlbHkgdGhlIGFncmVlZCByZXNvbHV0aW9uIHdhcyBub3Qg
cmVwb3J0ZWQgb24gdGhlIGxpc3QuDQpUaGF0IGlzIHdoeSBJIG1pc3NlZCAocGFydCBvZikgdGhl
IGRpc2N1c3Npb24uDQoNCkkgd2lsbCBoYXZlIG5vIGZ1cnRoZXIgY29tbWVudHMuDQoNCkJlc3Qg
cmVnYXJkcywgSHV1Yi4NCg0KLS0tLS0tLS0tLS0NCkFkZGl0aW9uYWxseSwgcGxlYXNlIHNlZSBo
dHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDE9ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29u
bmVjdGlvbmxlc3Mtb2FtLTE3JnVybDI9ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxl
c3Mtb2FtLTE4LCB3aGljaCBzaG93cyB0aGUgY2hhbmdlcyByZWxldmFudCB0byB0aGF0IHNwZWNp
ZmljIGNvbW1lbnQuDQoNCkkgYmVsaWV2ZSB0aGUgYXV0aG9ycyBhcmUgdXNpbmcgdGV4dCBzdWdn
ZXN0ZWQgYnkgR3JlZy4NCg0KTGlrZSBCZW5vaXQgc2FpZCwgdGhlIGRvY3VtZW50IGlzIGFwcHJv
dmVkIGFuZCBpbiB0aGUgUkZDIEVkaXRvciBxdWV1ZToNCmh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0
Zi5vcmcvYXJjaC9tc2cvbGltZS9xeWhLd0ZrRTRWQjlIQTBTMDR0T1dQREZLOVENCg0KQmVzdCwN
Cg0K4oCUDQpDYXJsb3MgUGlnbmF0YXJvLCBjYXJsb3NAY2lzY28uY29tPG1haWx0bzpjYXJsb3NA
Y2lzY28uY29tPg0KDQrigJxTb21ldGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQgSSBkbyBub3Qg
ZnVsbHkgdW5kZXJzdGFuZCwgdG8gbWFrZSBteXNlbGYgc291bmQgbW9yZSBwaG90b3N5bnRoZXNp
cy4iDQoNCg0KT24gTm92IDI4LCAyMDE3LCBhdCA1OjIxIEFNLCBIdXViIHZhbiBIZWx2b29ydCA8
aHV1YmF0d29ya0BnbWFpbC5jb208bWFpbHRvOmh1dWJhdHdvcmtAZ21haWwuY29tPj4gd3JvdGU6
DQoNCkhlbGxvIEJlbm9pdCwNCg0KWW91IHJlcGx5Og0KRm9yIHlvdXIgaW5mb3JtYXRpb24sIHRo
ZSBkb2N1bWVudCBpcyBub3cgaW4gdGhlIFJGQyBlZGl0b3IgcXVldWUsIHJlYWR5IHRvIGJlIHB1
Ymxpc2hlZC4NCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtbGlt
ZS15YW5nLWNvbm5lY3Rpb25sZXNzLW9hbS8NCkkgaGFkIG5vdCBzZWVuIGFueSByZXNwb25zZSBm
cm9tIHRoZSBhdXRob3JzIHRvIHRoZSBlbWFpbCBmcm9tIEdyZWcNCihJIGNoZWNrZWQgdGhlIGFy
Y2hpdmUpIHNvIEkgYXNzdW1lZCB0aGF0IHRoZSBpc3N1ZSB3YXMgc3RpbGwgYmVpbmcNCmRpc2N1
c3NlZC4NCk90aGVyIG9uLWxpbmUgY29tbWVudHMgd2VyZSBhZGRyZXNzZWQgYnkgdGhlIGF1dGhv
cnMuDQoNCkkgYWxzbyBjaGVja2VkIGZvciB1cGRhdGVzIHRvIHZlcnNpb24gMTgsIGJ1dCBkaWQg
bm90IGZpbmQgYW55LCBzbyBJDQpkb24ndCBrbm93IGhvdyB0aGUgaXNzdWUgaGFzIGJlZW4gcmVz
b2x2ZWQuDQoNClNvIG5vdyBJIGhhdmUgdG8gd2FpdCB1bnRpbCB0aGUgUkZDIGlzIHB1Ymxpc2hl
ZC4NCg0KUmVnYXJkcywgSHV1Yi4NCg0KPT09PT09PT09DQoNCg0KSGVsbG8gR3JlZywNCg0KSSBh
Z3JlZSB3aXRoIHlvdSB0aGF0IHRoZSBjdXJyZW50ICh2ZXJzaW9uIDE4KSB0ZXh0IGluIHNlY3Rp
b24gMy4zIGlzIHZlcnkgY29uZnVzaW5nLg0KDQpBdXRob3JzOg0KDQpJZiBJIGxvb2sgYXQgdGhl
IGRlZmluaXRpb24gb2YgVFAgaW4gc2VjdGlvbiAyLjIgSSB0aGluayBhIFRQIGlzIHNpbWlsYXIN
CnRvIGEgbWFpbnRlbmFuY2UgcG9pbnQgYXMgZGVmaW5lZCBmb3IgRXRoZXJuZXQuIEFtIEkgY29y
cmVjdD8NCg0KSSBkb24ndCB1bmRlcnN0YW5kIHdoeSB0aGVyZSBhcmUgVFBzIHdpdGggbm8gbmVp
Z2hib3JpbmcgVFBzLA0Kd2hlcmUgd2lsbCB0aGVpciBpbml0aWF0ZWQgT0FNIHRlc3QgYmUgc2Vu
dD8gT3Igd2hlcmUgYXJlIE9BTQ0KdGVzdHMgdGhleSByZWFjdCB0byBpbml0aWF0ZWQ/DQoNCkl0
IGlzIElNSE8gYWxzbyBwb3NzaWJsZSB0aGF0IHRoZXJlIGFyZSBUUHMgd2l0aCBhIG5laWdoYm9y
aW5nDQpUUCBiZWZvcmUgQU5EIGEgbmVpZ2hib3JpbmcgVFAgYWZ0ZXIgdGhlIGN1cnJlbnQgVFAu
DQoNClBsZWFzZSBleHBsYWluLg0KDQpSZWdhcmRzLCBIdXViLg0KDQotLS0tLS0tLS0NCkRlYXIg
QWxsLA0KSSB3YXMgdW5kZXIgaW1wcmVzc2lvbiB0aGF0IHRoYXQgcXVlc3Rpb24gb2Ygb2FtLW5l
aWdoYm9yaW5nLXRwcyBoYXMgYmVlbiBkaXNjdXNzZWQgYW5kIHNpbmNlIGF1dGhvcnMgY291bGRu
J3QgcHJvZHVjZSB0ZWNobmljYWwgcmF0aW9uYWxlIGZvciB0aGlzIG9iamVjdCB3ZSd2ZSBhZ3Jl
ZWQgdGhhdCBpdCB3aWxsIGJlIHJlbW92ZWQgYWx0b2dldGhlciBmcm9tIHRoZSBncm91cGluZyBj
b25uZWN0aW9ubGVzcy1vYW0tdHBzLiBCdXQgYXV0aG9ycyBqdXN0IGNoYW5nZWQgbmFtZSBmcm9t
IGxldmVsIHRvIHBvc2l0aW9uIGJ1dCBoYWQgbWlzc2VkIHRvIHN5bmNocm9uaXplIGRlc2NyaXB0
aW9ucyBpbiB0aGUgbW9kZWwgYW5kIGluIHNlY3Rpb24gMy4zLiBUaGUgbGF0ZXIgc3RpbGwgcmVm
ZXJzIHRvIHZlcnRpY2FsIGxheWVyczoNCg0KICAgICAgICAgICAgICAgICAgICAgIkxpc3Qgb2Yg
cmVsYXRlZCBuZWlnaGJvcmluZyB0ZXN0IHBvaW50cyBpbiBhZGphY2VudA0KDQogICAgICAgICAg
ICAgICAgICAgICBsYXllcnMgdXAgYW5kIGRvd24gdGhlIHN0YWNrIGZvciB0aGUgc2FtZSBpbnRl
cmZhY2UNCg0KICAgICAgICAgICAgICAgICAgICAgdGhhdCBhcmUgcmVsYXRlZCB0byB0aGUgY3Vy
cmVudCB0ZXN0IHBvaW50LiI7DQp3aGlsZSB0aGUgbW9kZWwgaW5zaXN0cyB0aGF0IGl0IGlzIHBl
ZXJpbmcgcmVsYXRpb25zaGlwOg0KDQogICAgICAgIGRlc2NyaXB0aW9uDQoNCiAgICAgICAgICAi
VGhlIHJlbGF0aXZlIHBvc2l0aW9uDQoNCiAgICAgICAgICAgb2YgbmVpZ2hib3JpbmcgdGVzdCBw
b2ludA0KDQogICAgICAgICAgIGNvcnJlc3BvbmRpbmcgdG8gdGhlIGN1cnJlbnQNCg0KICAgICAg
ICAgICB0ZXN0IHBvaW50LiBMZXZlbCAwIGluZGljYXRlcyBubyBuZWlnaGJvcmluZw0KDQogICAg
ICAgICAgIHRlc3QgcG9pbnRzIHBsYWNlZCBiZWZvcmUgb3IgYWZ0ZXIgdGhlIGN1cnJlbnQNCg0K
ICAgICAgICAgICB0ZXN0IHBvaW50IGluIHRoZSBzYW1lIGxheWVyLi0xIG1lYW5zIHRoZXJlIGlz
DQoNCiAgICAgICAgICAgYSBuZWlnaGJvcmluZyB0ZXN0IHBvaW50IHBsYWNlZCBiZWZvcmUgdGhl
IGN1cnJlbnQNCg0KICAgICAgICAgICB0ZXN0IHBvaW50IGluIHRoZSBzYW1lIGxheWVyIGFuZCAr
MSBtZWFucyB0aGVyZSBpcw0KDQogICAgICAgICAgIGEgbmVpZ2hib3JpbmcgdGVzdCBwb2ludCBw
bGFjZWQgYWZ0ZXIgdGhlIGN1cnJlbnQNCg0KICAgICAgICAgICB0ZXN0IHBvaW50IGluIHNhbWUg
bGF5ZXIuIjsNClNvLCB3aGF0IGlzIGl0PyBQZXJoYXBzIGl0IGlzIHRpbWUgdG8gcmVtb3ZlIGxp
c3Qgb2FtLW5laWdoYm9yaW5nLXRwcyBhbHRvZ2V0aGVyIGFsc28gYmVjYXVzZSBoYXZpbmcgaXQg
cyBmaXhlZCBzaXplIGxpc3QgaXMgcGxhaW4gd3JvbmcuIChTb3JyeSBmb3IgYmVpbmcgc28gYmx1
bnQgYnV0IEkgY29tbWVudGVkIHRvbyBtYW55IHRpbWVzIG9uIHRoZSBzYW1lIHRvIG5vIGF2YWls
IGZyb20gdGhlIGF1dGhvcnMpLg0KDQpSZWdhcmRzLA0KR3JlZw0KDQoNCg0KLS0NCg0KPT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PQ0KDQpBbHdheXMgcmVtZW1iZXIgdGhhdCB5b3UgYXJlIHVuaXF1ZS4uLmp1c3QgbGlrZSBldmVy
eW9uZSBlbHNlLi4uDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQpMaW1lIG1haWxpbmcgbGlzdA0KTGltZUBpZXRmLm9yZzxtYWlsdG86TGltZUBpZXRm
Lm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbGltZQ0KDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseTrlrovkvZM7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9u
dC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEDlrovkvZMiOw0KCXBhbm9zZS0x
OjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9y
bWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4t
Ym90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7
fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
Y29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bh
bi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBjbTsN
Cgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207DQoJZm9udC1z
aXplOjEyLjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCDpooTorr7moLzlvI8gQ2hhciI7DQoJbWFy
Z2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglm
b250LWZhbWlseTrlrovkvZM7fQ0Kc3Bhbi5IVE1MQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRN
TCDpooTorr7moLzlvI8gQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHls
ZS1saW5rOiJIVE1MIOmihOiuvuagvOW8jyI7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9
DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1z
b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7fQ0KQHBhZ2UgV29yZFNl
Y3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgOTAuMHB0IDcy
LjBwdCA5MC4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQot
LT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4
dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3Rl
IG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpl
eHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+
DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJaSC1DTiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5OaWNlIHRv
IGhlYXIgZnJvbSBUaXNzYSwgc2FtZSB3aXNoIGZvciB5b3UuIFRoYW5rcyBHcmVnIGluIFNpbmdh
cG9yZSB0byBoZWxwIGFkZHJlc3MgbGFzdCBjb21tZW50IHRvZ2V0aGVyLCBhbHNvIHRoYW5rcyBH
cmVnIGEgbG90IG9mIGlucHV0cyB0bw0KIHRoaXMgd29yayBhbGwgYWxvbmcgdGhlIHdheS4gQXBw
cmVjaWF0ZWQgYXMgd2VsbC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPkkgc2hvdWxkIGhhdmUgc2VudCBhIG5vdGUgb3V0IGVhcmxpZXIgZHVyaW5nIGJ1c3kgSUVU
RiB3ZWVrLCBzb3JyeSBhYm91dCB0aGF0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj4tUWluPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20i
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQi
PuWPkeS7tuS6ujxzcGFuIGxhbmc9IkVOLVVTIj46PC9zcGFuPjwvc3Bhbj48L2I+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4gR3JlZyBNaXJza3kgW21haWx0bzpn
cmVnaW1pcnNreUBnbWFpbC5jb21dDQo8YnI+DQo8L3NwYW4+PGI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQiPuWPkemAgeaXtumXtDxzcGFuIGxhbmc9IkVOLVVTIj46PC9zcGFuPjwvc3Bh
bj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4gMjAxNzwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+5bm0PHNwYW4gbGFuZz0iRU4tVVMi
PjExPC9zcGFuPuaciDxzcGFuIGxhbmc9IkVOLVVTIj4zMDwvc3Bhbj7ml6U8c3BhbiBsYW5nPSJF
Ti1VUyI+IDEzOjE4PGJyPg0KPC9zcGFuPjxiPuaUtuS7tuS6ujxzcGFuIGxhbmc9IkVOLVVTIj46
PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IFRpc3NhIFNlbmV2aXJhdGhuZTxicj4NCjwv
c3Bhbj48Yj7mioTpgIE8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L2I+PHNwYW4gbGFuZz0i
RU4tVVMiPiBodXViYXR3b3JrQGdtYWlsLmNvbTsgQ2FybG9zIFBpZ25hdGFybyAoY3BpZ25hdGEp
OyBpZXRmQGlldGYub3JnOyBSb25hbGQgUC4gQm9uaWNhOyBsaW1lLWNoYWlyc0BpZXRmLm9yZzsg
VGhlIElFU0c7IEJlbm9pdCBDbGFpc2UgKGJjbGFpc2UpOyBsaW1lQGlldGYub3JnOyBRaW4gV3U7
IGRyYWZ0LWlldGYtbGltZS15YW5nLWNvbm5lY3Rpb25sZXNzLW9hbUBpZXRmLm9yZzxicj4NCjwv
c3Bhbj48Yj7kuLvpopg8c3BhbiBsYW5nPSJFTi1VUyI+Ojwvc3Bhbj48L2I+PHNwYW4gbGFuZz0i
RU4tVVMiPiBSZTogW0xpbWVdIExhc3QgQ2FsbDogJmx0O2RyYWZ0LWlldGYtbGltZS15YW5nLWNv
bm5lY3Rpb25sZXNzLW9hbS0xMS50eHQmZ3Q7IChHZW5lcmljIFlBTkcgRGF0YSBNb2RlbCBmb3Ig
Q29ubmVjdGlvbmxlc3MgT3BlcmF0aW9ucywgQWRtaW5pc3RyYXRpb24sIGFuZCBNYWludGVuYW5j
ZShPQU0pIHByb3RvY29scykgdG8gUHJvcG9zZWQgU3RhbmRhcmQ8bzpwPjwvbzpwPjwvc3Bhbj48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5IaSBUaXNzYSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPnRoYW5rIHlvdSBm
b3IgeW91ciBraW5kIHdvcmRzLCBtdWNoIGFwcHJlY2lhdGVkLiBXaXNoIHlvdSBhbGwgc3VjY2Vz
cyBpbiB5b3VyIGVuZGVhdm9ycyBhbmQgaG9wZSB5b3UnbGwgZmluZCBvcHBvcnR1bml0eSB0byBy
ZXR1cm4gdG8gSUVURiB3b3JrIHNvb25lciB0aGFuIGxhdGVyLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+QmVzdCByZWdhcmRzLDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj5HcmVnPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj5PbiBXZWQsIE5vdiAyOSwgMjAxNyBhdCAyOjQwIFBNLCBUaXNzYSBTZW5ldmlyYXRobmUg
Jmx0OzxhIGhyZWY9Im1haWx0bzp0c2VuZXZpckBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj50
c2VuZXZpckBnbWFpbC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkkgaGF2ZSBiZWVu
IG91dCBvZiBJRVRGIGZvciBhIHdoaWxlIGJ1dCBzdGlsbCByZWNlaXZlcyBMSU1FIFdHIGVtYWls
cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5BcyB0aGUgb3JpZ2lu
YWwgYXV0aG9yIG9mIHRoZSBjb25uZWN0aW9ubGVzcyBkcmFmdCBJIGRlbGliZXJhdGVseSBhdm9p
ZGVkIG1ha2luZyBhbnkgY29tbWVudHMgYXMgSSBkbyBub3QgaGF2ZSBhZGVxdWF0ZSB0aW1lIHRv
IGRvIGEgZ29vZCBqb2IuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIj5Ib3dldmVyLCBJIGhhdmUgYmVlbiByZWFkaW5nLCB3aXRoIGdyZWF0IHJlc3BlY3Qs
IHRoZSBjb21tZW50cyBHcmVnIE1pcnNreSB3YXMgbWFraW5nIHRvIG1ha2UgdGhlc2UgZHJhZnRz
IGJldHRlciBib3RoIHRlY2huaWNhbGx5IGFuZCBlZGl0b3JpYWxseS4gSSB3YW50IHRvIGV4dGVu
ZCBhIHdlbGwgZGVzZXJ2ZWQgdGhhbmsgeW91IHRvIEdyZWcuIFRoYW5rIFlvdSBHcmVnLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+QWxzbyBJIGRvIG5v
dCBhZ3JlZSB3aXRoIENhcmxvcyBjb21tZW50cyBvbiBIdWJicyBvYnNlcnZhdGlvbnMsIGkuZS4g
T2ggRHJhZnQgaXMgaW4gSUVURiBlZGl0b3JzIHF1ZXVlIGFuZCBpdCBpcyB0b28gbGF0ZS4gTWF5
IGJlIHRpbWUgdG8gcHVsbCBpdCBvdXQgZnJvbSB0aGUgcXVldWUgb3IgY3JlYXRlIGVycmF0YSBp
ZiB0aGUgY2hhbmdlcyBhcmUgc2lnbmlmaWNhbnQgZW5vdWdoLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+SWYgZWl0aGVyIG9mIHRoZXNlIGhhcHBlbnMg
SSBkbyBsaWtlIHRvIHN1Z2dlc3QgdHdvIHRoaW5nczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+MS4gQXBwb2ludCBhbiBlZGl0b3Igd2hvIGNhbiBzaGVw
aGVyZCBlZGl0cyBhbmQgcHJlc2VudGF0aW9uIGFzcGVjdHMgb2YgdGhlIGRyYWZ0PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiPjIuIFByb3ZpZGUgYWRlcXVhdGUgdGltZSBhbmQgYmUgdHJhbnNwYXJlbnQg
dG8gc2hhcmUgd2l0aCB0aGUgV0cgb24gd2hhdCBpcyBhZ3JlZWQgb3IgYXBwb2ludCBhIHRlY2hu
aWNhbCBwYW5lbDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5PbiBXZWQsIE5vdiAy
OSwgMjAxNyBhdCAxMjozOSBQTSwgSHV1YiB2YW4gSGVsdm9vcnQgJmx0OzxhIGhyZWY9Im1haWx0
bzpodXViYXR3b3JrQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmh1dWJhdHdvcmtAZ21haWwu
Y29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0ND
IDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2lu
LXJpZ2h0OjBjbSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkhlbGxvIENhcmxvcyw8YnI+DQo8YnI+DQpUaGFuayB5
b3UgZm9yIHRoZSBhZGRpdGlvbmFsIGluZm9ybWF0aW9uLjxicj4NCjxicj4NCkFzIEkgbWVudGlv
bmVkIEkgYWxyZWFkeSBsb29rZWQgYXQgdmVyc2lvbiAxOCBiZWNhdXNlIHRoYXQgd2FzIG1lbnRp
b25lZDxicj4NCmluIEdyZWdzIHJlc3BvbnNlLjxicj4NCjxicj4NCkkgaGF2ZSB1bmRlcnN0b29k
IHRoYXQgdGhpcyBkcmFmdCB3YXMgZGlzY3Vzc2VkIGluIFNpbmdhcG9yZS48YnI+DQpVbmZvcnR1
bmF0ZWx5IHRoZSBhZ3JlZWQgcmVzb2x1dGlvbiB3YXMgbm90IHJlcG9ydGVkIG9uIHRoZSBsaXN0
Ljxicj4NClRoYXQgaXMgd2h5IEkgbWlzc2VkIChwYXJ0IG9mKSB0aGUgZGlzY3Vzc2lvbi48YnI+
DQo8YnI+DQpJIHdpbGwgaGF2ZSBubyBmdXJ0aGVyIGNvbW1lbnRzLjxicj4NCjxicj4NCkJlc3Qg
cmVnYXJkcywgSHV1Yi48YnI+DQo8YnI+DQotLS0tLS0tLS0tLTxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1
LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIj5BZGRpdGlvbmFsbHksIHBsZWFzZSBzZWUmbmJzcDs8YSBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDE9ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlv
bmxlc3Mtb2FtLTE3JmFtcDt1cmwyPWRyYWZ0LWlldGYtbGltZS15YW5nLWNvbm5lY3Rpb25sZXNz
LW9hbS0xOCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJs
MT1kcmFmdC1pZXRmLWxpbWUteWFuZy1jb25uZWN0aW9ubGVzcy1vYW0tMTcmYW1wO3VybDI9ZHJh
ZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2FtLTE4PC9hPiwNCiB3aGljaCBzaG93
cyB0aGUgY2hhbmdlcyByZWxldmFudCB0byB0aGF0IHNwZWNpZmljIGNvbW1lbnQuIDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkkgYmVsaWV2ZSB0aGUgYXV0aG9ycyBh
cmUgdXNpbmcgdGV4dCBzdWdnZXN0ZWQgYnkgR3JlZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkxpa2UgQmVub2l0IHNhaWQsIHRoZSBkb2N1bWVudCBp
cyBhcHByb3ZlZCBhbmQgaW4gdGhlIFJGQyBFZGl0b3IgcXVldWU6PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPjxhIGhyZWY9Imh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cvbGltZS9x
eWhLd0ZrRTRWQjlIQTBTMDR0T1dQREZLOVEiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL21haWxh
cmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2xpbWUvcXloS3dGa0U0VkI5SEEwUzA0dE9XUERGSzlR
PC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+QmVz
dCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImNvbG9yOmJsYWNrIj7igJQ8YnI+DQpDYXJsb3MgUGlnbmF0YXJvLCZuYnNwOzxhIGhyZWY9Im1h
aWx0bzpjYXJsb3NAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+Y2FybG9zQGNpc2NvLmNvbTwv
YT48YnI+DQo8YnI+DQo8aT7igJxTb21ldGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQgSSBkbyBu
b3QgZnVsbHkgdW5kZXJzdGFuZCwgdG8gbWFrZSBteXNlbGYgc291bmQgbW9yZSBwaG90b3N5bnRo
ZXNpcy4mcXVvdDs8L2k+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PGJyPg0KPGJyPg0K
PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj5PbiBOb3YgMjgsIDIwMTcsIGF0IDU6MjEgQU0sIEh1dWIgdmFuIEhlbHZv
b3J0ICZsdDs8YSBocmVmPSJtYWlsdG86aHV1YmF0d29ya0BnbWFpbC5jb20iIHRhcmdldD0iX2Js
YW5rIj5odXViYXR3b3JrQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5IZWxsbyBCZW5vaXQsPGJyPg0KPGJyPg0K
WW91IHJlcGx5OjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5
bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPkZvciB5b3VyIGluZm9ybWF0aW9uLCB0
aGUgZG9jdW1lbnQgaXMgbm93IGluIHRoZSBSRkMgZWRpdG9yIHF1ZXVlLCByZWFkeSB0byBiZSBw
dWJsaXNoZWQuPGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2FtLyIgdGFyZ2V0PSJfYmxhbmsi
Pmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtbGltZS15YW5nLWNv
bm5lY3Rpb25sZXNzLW9hbS88L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+SSBoYWQg
bm90IHNlZW4gYW55IHJlc3BvbnNlIGZyb20gdGhlIGF1dGhvcnMgdG8gdGhlIGVtYWlsIGZyb20g
R3JlZzxicj4NCihJIGNoZWNrZWQgdGhlIGFyY2hpdmUpIHNvIEkgYXNzdW1lZCB0aGF0IHRoZSBp
c3N1ZSB3YXMgc3RpbGwgYmVpbmc8YnI+DQpkaXNjdXNzZWQuIDxicj4NCk90aGVyIG9uLWxpbmUg
Y29tbWVudHMgd2VyZSBhZGRyZXNzZWQgYnkgdGhlIGF1dGhvcnMuPGJyPg0KPGJyPg0KSSBhbHNv
IGNoZWNrZWQgZm9yIHVwZGF0ZXMgdG8gdmVyc2lvbiAxOCwgYnV0IGRpZCBub3QgZmluZCBhbnks
IHNvIEk8YnI+DQpkb24ndCBrbm93IGhvdyB0aGUgaXNzdWUgaGFzIGJlZW4gcmVzb2x2ZWQuPGJy
Pg0KPGJyPg0KU28gbm93IEkgaGF2ZSB0byB3YWl0IHVudGlsIHRoZSBSRkMgaXMgcHVibGlzaGVk
Ljxicj4NCjxicj4NClJlZ2FyZHMsIEh1dWIuPGJyPg0KPGJyPg0KPT09PT09PT09PGJyPg0KPGJy
Pg0KPGJyPg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdp
bi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyI+SGVs
bG8gR3JlZyw8YnI+DQo8YnI+DQpJIGFncmVlIHdpdGggeW91IHRoYXQgdGhlIGN1cnJlbnQgKHZl
cnNpb24gMTgpIHRleHQgaW4gc2VjdGlvbiAzLjMgaXMgdmVyeSBjb25mdXNpbmcuPGJyPg0KPGJy
Pg0KQXV0aG9yczo8YnI+DQo8YnI+DQpJZiBJIGxvb2sgYXQgdGhlIGRlZmluaXRpb24gb2YgVFAg
aW4gc2VjdGlvbiAyLjIgSSB0aGluayBhIFRQIGlzIHNpbWlsYXI8YnI+DQp0byBhIG1haW50ZW5h
bmNlIHBvaW50IGFzIGRlZmluZWQgZm9yIEV0aGVybmV0LiBBbSBJIGNvcnJlY3Q/PGJyPg0KPGJy
Pg0KSSBkb24ndCB1bmRlcnN0YW5kIHdoeSB0aGVyZSBhcmUgVFBzIHdpdGggbm8gbmVpZ2hib3Jp
bmcgVFBzLDxicj4NCndoZXJlIHdpbGwgdGhlaXIgaW5pdGlhdGVkIE9BTSB0ZXN0IGJlIHNlbnQ/
IE9yIHdoZXJlIGFyZSBPQU08YnI+DQp0ZXN0cyB0aGV5IHJlYWN0IHRvIGluaXRpYXRlZD88YnI+
DQo8YnI+DQpJdCBpcyBJTUhPIGFsc28gcG9zc2libGUgdGhhdCB0aGVyZSBhcmUgVFBzIHdpdGgg
YSBuZWlnaGJvcmluZyA8YnI+DQpUUCBiZWZvcmUgQU5EIGEgbmVpZ2hib3JpbmcgVFAgYWZ0ZXIg
dGhlIGN1cnJlbnQgVFAuPGJyPg0KPGJyPg0KUGxlYXNlIGV4cGxhaW4uPGJyPg0KPGJyPg0KUmVn
YXJkcywgSHV1Yi48YnI+DQo8YnI+DQotLS0tLS0tLS08bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206
NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5E
ZWFyIEFsbCwgPG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIGxhbmc9IkVOLVVTIj5JIHdhcyB1bmRlciBpbXByZXNzaW9uIHRoYXQgdGhhdCBx
dWVzdGlvbiBvZiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQiPm9hbS1uZWlnaGJvcmluZy10cHMmbmJzcDtoYXMgYmVlbiBkaXNjdXNzZWQgYW5k
IHNpbmNlIGF1dGhvcnMgY291bGRuJ3QgcHJvZHVjZSB0ZWNobmljYWwgcmF0aW9uYWxlIGZvciB0
aGlzIG9iamVjdCB3ZSd2ZSBhZ3JlZWQNCiB0aGF0IGl0IHdpbGwgYmUgcmVtb3ZlZCBhbHRvZ2V0
aGVyIGZyb20gdGhlJm5ic3A7Z3JvdXBpbmcgY29ubmVjdGlvbmxlc3Mtb2FtLXRwcy4gQnV0IGF1
dGhvcnMganVzdCBjaGFuZ2VkIG5hbWUgZnJvbSBsZXZlbCB0byBwb3NpdGlvbiBidXQgaGFkIG1p
c3NlZCB0byBzeW5jaHJvbml6ZSBkZXNjcmlwdGlvbnMgaW4gdGhlIG1vZGVsIGFuZCBpbiBzZWN0
aW9uIDMuMy4gVGhlIGxhdGVyIHN0aWxsIHJlZmVycyB0byB2ZXJ0aWNhbCBsYXllcnM6PC9zcGFu
PjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
ICZxdW90O0xpc3Qgb2YgcmVsYXRlZCBuZWlnaGJvcmluZyB0ZXN0IHBvaW50cyBpbiBhZGphY2Vu
dDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBsYXllcnMgdXAgYW5kIGRvd24gdGhlIHN0YWNrIGZv
ciB0aGUgc2FtZSBpbnRlcmZhY2U8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgdGhhdCBhcmUgcmVs
YXRlZCB0byB0aGUgY3VycmVudCB0ZXN0IHBvaW50LiZxdW90Ozs8bzpwPjwvbzpwPjwvc3Bhbj48
L3ByZT4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIj53aGlsZSB0aGUgbW9kZWwgaW5zaXN0cyB0aGF0IGl0IGlzIHBlZXJpbmcgcmVsYXRpb25z
aGlwOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwcmU+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgZGVzY3JpcHRpb248bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4N
CjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJnF1b3Q7VGhl
IHJlbGF0aXZlIHBvc2l0aW9uPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IG9mIG5laWdoYm9yaW5nIHRl
c3QgcG9pbnQ8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgY29ycmVzcG9uZGluZyB0byB0aGUgY3VycmVu
dDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0ZXN0IHBvaW50LiBMZXZlbCAwIGluZGljYXRlcyBubyBu
ZWlnaGJvcmluZzxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHByZT48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0ZXN0IHBvaW50cyBwbGFjZWQgYmVmb3Jl
IG9yIGFmdGVyIHRoZSBjdXJyZW50PG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8L2Rpdj4NCjxk
aXY+DQo8cHJlPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
IHRlc3QgcG9pbnQgaW4gdGhlIHNhbWUgbGF5ZXIuLTEgbWVhbnMgdGhlcmUgaXM8bzpwPjwvbzpw
Pjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgYSBuZWlnaGJvcmluZyB0ZXN0IHBvaW50IHBsYWNlZCBiZWZvcmUgdGhlIGN1
cnJlbnQ8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgdGVzdCBwb2ludCBpbiB0aGUgc2FtZSBsYXllciBh
bmQgJiM0MzsxIG1lYW5zIHRoZXJlIGlzPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGEgbmVpZ2hib3Jp
bmcgdGVzdCBwb2ludCBwbGFjZWQgYWZ0ZXIgdGhlIGN1cnJlbnQ8bzpwPjwvbzpwPjwvc3Bhbj48
L3ByZT4NCjxwcmU+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsgdGVzdCBwb2ludCBpbiBzYW1lIGxheWVyLiZxdW90Ozs8bzpwPjwvbzpwPjwvc3Bhbj48L3By
ZT4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
Ij5Tbywgd2hhdCBpcyBpdD8gUGVyaGFwcyBpdCBpcyB0aW1lIHRvIHJlbW92ZSBsaXN0Jm5ic3A7
PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+b2FtLW5l
aWdoYm9yaW5nLXRwcyBhbHRvZ2V0aGVyIGFsc28gYmVjYXVzZSBoYXZpbmcgaXQgcyBmaXhlZCBz
aXplIGxpc3QgaXMgcGxhaW4gd3JvbmcuIChTb3JyeSBmb3IgYmVpbmcgc28gYmx1bnQgYnV0DQog
SSBjb21tZW50ZWQgdG9vIG1hbnkgdGltZXMgb24gdGhlIHNhbWUgdG8gbm8gYXZhaWwgZnJvbSB0
aGUgYXV0aG9ycykuPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5S
ZWdhcmRzLDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTAuMHB0Ij5HcmVnPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9ibG9j
a3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8
cD48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHByZT48
c3BhbiBsYW5nPSJFTi1VUyI+LS0gPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFu
IGxhbmc9IkVOLVVTIj49PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFu
IGxhbmc9IkVOLVVTIj5BbHdheXMgcmVtZW1iZXIgdGhhdCB5b3UgYXJlIHVuaXF1ZS4uLmp1c3Qg
bGlrZSBldmVyeW9uZSBlbHNlLi4uPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiPl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KTGltZSBt
YWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86TGltZUBpZXRmLm9yZyIgdGFyZ2V0PSJf
YmxhbmsiPkxpbWVAaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9saW1lIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0
Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9saW1lPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
YmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_B8F9A780D330094D99AF023C5877DABA9ACDABADnkgeml513mbxchi_--


From nobody Thu Nov 30 14:33:13 2017
Return-Path: <prvs=1498f0a599=michael.kelly.49.ctr@us.af.mil>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DAC212711A for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 09:53:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RDNS_NONE=0.793, 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 enty2_VOBNSv for <ietf@ietfa.amsl.com>; Tue, 28 Nov 2017 09:53:27 -0800 (PST)
Received: from SCOTT-MAIL5.AFNOC.AF.MIL (unknown [131.9.253.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD7CD12420B for <ietf@ietf.org>; Tue, 28 Nov 2017 09:53:23 -0800 (PST)
Received: from us.af.mil (unknown [131.15.70.112]) by SCOTT-MAIL5.AFNOC.AF.MIL with smtp (TLS: TLSv1/SSLv3,256bits,DHE-RSA-AES256-SHA) id 659d_0d0e_fc53a858_aa2c_4d3d_9a4b_93faa70b6d35; Tue, 28 Nov 2017 17:53:21 +0000
Received: from ([131.15.68.157]) by 52tdkp-mr-006.us.af.mil with ESMTP with TLS id 1YL2FN1.226992242; Tue, 28 Nov 2017 10:20:00 -0700
Received: from 52ZHTX-D06-05E.AREA52.AFNOAPPS.USAF.MIL (131.27.55.30) by 52TDKP-D02-03B.area52.afnoapps.usaf.mil (131.15.68.157) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 28 Nov 2017 10:53:13 -0700
Received: from 52ZHTX-D05-05E.AREA52.AFNOAPPS.USAF.MIL ([169.254.5.109]) by 52ZHTX-D06-05E.area52.afnoapps.usaf.mil ([169.254.5.99]) with mapi id 14.03.0361.001; Tue, 28 Nov 2017 12:53:06 -0500
From: "KELLY, MICHAEL B CTR USAF AFMC 412 TENG/ENI" <michael.kelly.49.ctr@us.af.mil>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Questions about RFC 7252
Thread-Topic: Questions about RFC 7252
Thread-Index: AdNocPSTedFhJogkQEmo/2oeXmQDYg==
Date: Tue, 28 Nov 2017 17:53:06 +0000
Message-ID: <C100D0AB51422F48B5655B0FD58BB204281F5F@52ZHTX-D05-05E.area52.afnoapps.usaf.mil>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-dset: 0-NNZN-0
x-originating-ip: [131.27.49.6]
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/0rQcmzJlU9gQxcfkOMj4gGoPbso>
X-Mailman-Approved-At: Thu, 30 Nov 2017 14:33:11 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Nov 2017 17:53:29 -0000

Greetings,

I am searching for a place to ask questions about RFC 7252, The Constrained=
 Application Protocol (CoAP).
If this is sufficient information for you to delete this email or take some=
 action please stop here.

If you are interested details follow.

My questions begin rather early in the document.  For example, section 2.1 =
shows a transaction schematic with the text=20
CON [0x7d34]=20
and the text=20
ACK [0x7d34]

I "presume" that means a confirmable message followed by an acknowledgement=
 message.  The RFC does not provide / confirm that information.
I see the hex number 0x7d34 but do not understand its significance.  If I t=
ry to put that number into a message and examine the individual fields as s=
hown in Figure 5, I wind up with an invalid message. =20

Taking hex value 0x7D34 puts binary 01 into the Version field, that is oK. =
 Then a binary 011 into the Type field for a Reset command. =20
That leaves 0Xd or binary 1101 in the TKL field.  But lengths 9-15 (decimal=
 I presume per the RFC) are reserved so that will not work.

Additional reading leads me to presume that this might be a message ID.  Ho=
wever, the document  neither states that clearly not does it describe how t=
he message ID is created.

Obviously there are some things about this RFC that I do not understand.  W=
here might I go to post my questions such that there is a possibility that =
someone may answer them?

Thank you for your time,
M Bryan Kelly
JT3/ATAC Contractor
412 TENG/ENIE CANIS Software
661-277-7852
DSN 527-7852
Blg 1600 Block 500
300 E. Yeager Blvd
Edwards AFB, 93524



From nobody Thu Nov 30 14:33:18 2017
Return-Path: <cpignata@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 10EF01242F5; Wed, 29 Nov 2017 13:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level: 
X-Spam-Status: No, score=-14.52 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 EjosCoXlU7tg; Wed, 29 Nov 2017 13:06:53 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B74AF120227; Wed, 29 Nov 2017 13:06:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23476; q=dns/txt; s=iport; t=1511989612; x=1513199212; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=UUGup0XmZksT9Cll4hlnDu2BIwSb0JisjjHAXqgmfCQ=; b=ZKyLWhpZTgxNlwrMSvIKXpU8bSJXDcaqlMaMHWQhzO7uxpVuJna03wRz jvstXo1qFPzTKOeYHU7aMjK5W8DrA4Cgflq8VWx7nMY9LneSKT6g2ttH1 ixRIHVkT0/ZkiwSdXNRtRu2/C/oiW3qzcZ2TMH7czizPAvHH+dzbILa8d Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DUAABtIB9a/40NJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYJKRC5mbicHg3iKII5wgX2IaohAhUoQggEKJ4UUAhqEez8YAQE?= =?us-ascii?q?BAQEBAQEBax0LhR8BAQEBAyNPBxACAQgRAwECJAQDAgICHxEUCQgCBA4FiT5MA?= =?us-ascii?q?xUQA6dIgicmhw4NgyYBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYNBggmBVoFpKYM?= =?us-ascii?q?CgmtHGIEeBQESAQc4FoJfMYIyBYo6hz+HMYhmPQKHcoghhHmCFoYPhWSFSIx5O?= =?us-ascii?q?4hhAhEZAYE5AR85YVsVbxU6KgGBfoJSHBmBTneHP4EkgRQBAQE?=
X-IronPort-AV: E=Sophos; i="5.45,339,1508803200"; d="scan'208,217"; a="38090169"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Nov 2017 21:06:51 +0000
Received: from XCH-RTP-007.cisco.com (xch-rtp-007.cisco.com [64.101.220.147]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id vATL6pIn017094 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 29 Nov 2017 21:06:51 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-007.cisco.com (64.101.220.147) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 29 Nov 2017 16:06:50 -0500
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1320.000; Wed, 29 Nov 2017 16:06:50 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "huubatwork@gmail.com" <huubatwork@gmail.com>
CC: "Benoit Claise (bclaise)" <bclaise@cisco.com>, Greg Mirsky <gregimirsky@gmail.com>, Qin Wu <bill.wu@huawei.com>, The IESG <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Ronald P. Bonica" <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
Thread-Topic: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
Thread-Index: AQHTQpaR7crx2zDS7kC2rAOW6lNAlKLrJSkAgAHYPQCABB9KAIACV92AgADF4YCAAKRDAIAA0fcAgBuah4CAGCTSAIAAld+AgAAuIgCAABzRAIACIhcAgAAHroA=
Date: Wed, 29 Nov 2017 21:06:50 +0000
Message-ID: <88B5F94B-63BC-4F1B-9C8A-0544A3DA9941@cisco.com>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com> <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com> <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.com> <646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com> <1b527039-bf80-ead5-e341-c8cfeb24f855@gmail.com>
In-Reply-To: <1b527039-bf80-ead5-e341-c8cfeb24f855@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.27.0.171010
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.133]
Content-Type: multipart/alternative; boundary="_000_88B5F94B63BC4F1B9C8A0544A3DA9941ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5Chm3D-Q5hKSLCi_DV4R54M4Re8>
X-Mailman-Approved-At: Thu, 30 Nov 2017 14:33:11 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 21:06:56 -0000

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

RGVhciBIdXViLA0KDQpUaGFua3MgZm9yIHRoZSByZXNwb25zZSDigJMgZ2xhZCB0byBzZWUgdGhp
cyBsb29wIGlzIGNsb3NlZC4NCg0KQmVzdCwNCg0KLS0gQ2FybG9zLg0KDQpGcm9tOiBIdXViIHZh
biBIZWx2b29ydCA8aHV1YmF0d29ya0BnbWFpbC5jb20+DQpSZXBseS1UbzogImh1dWJhdHdvcmtA
Z21haWwuY29tIiA8aHV1YmF0d29ya0BnbWFpbC5jb20+DQpEYXRlOiBXZWRuZXNkYXksIE5vdmVt
YmVyIDI5LCAyMDE3IGF0IDM6MzggUE0NClRvOiAiQ2FybG9zIFBpZ25hdGFybyAoY3BpZ25hdGEp
IiA8Y3BpZ25hdGFAY2lzY28uY29tPg0KQ2M6IEJlbm9pdCBDbGFpc2UgPGJjbGFpc2VAY2lzY28u
Y29tPiwgR3JlZyBNaXJza3kgPGdyZWdpbWlyc2t5QGdtYWlsLmNvbT4sIFFpbiBXdSA8YmlsbC53
dUBodWF3ZWkuY29tPiwgVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+LCAiaWV0ZkBpZXRmLm9yZyIg
PGlldGZAaWV0Zi5vcmc+LCBSb25hbGQgQm9uaWNhIDxyYm9uaWNhQGp1bmlwZXIubmV0PiwgImxp
bWUtY2hhaXJzQGlldGYub3JnIiA8bGltZS1jaGFpcnNAaWV0Zi5vcmc+LCAibGltZUBpZXRmLm9y
ZyIgPGxpbWVAaWV0Zi5vcmc+LCAiZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mt
b2FtQGlldGYub3JnIiA8ZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2FtQGll
dGYub3JnPg0KU3ViamVjdDogUmU6IFtMaW1lXSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLWxpbWUt
eWFuZy1jb25uZWN0aW9ubGVzcy1vYW0tMTEudHh0PiAoR2VuZXJpYyBZQU5HIERhdGEgTW9kZWwg
Zm9yIENvbm5lY3Rpb25sZXNzIE9wZXJhdGlvbnMsIEFkbWluaXN0cmF0aW9uLCBhbmQgTWFpbnRl
bmFuY2UoT0FNKSBwcm90b2NvbHMpIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQoNCkhlbGxvIENhcmxv
cywNCg0KVGhhbmsgeW91IGZvciB0aGUgYWRkaXRpb25hbCBpbmZvcm1hdGlvbi4NCg0KQXMgSSBt
ZW50aW9uZWQgSSBhbHJlYWR5IGxvb2tlZCBhdCB2ZXJzaW9uIDE4IGJlY2F1c2UgdGhhdCB3YXMg
bWVudGlvbmVkDQppbiBHcmVncyByZXNwb25zZS4NCg0KSSBoYXZlIHVuZGVyc3Rvb2QgdGhhdCB0
aGlzIGRyYWZ0IHdhcyBkaXNjdXNzZWQgaW4gU2luZ2Fwb3JlLg0KVW5mb3J0dW5hdGVseSB0aGUg
YWdyZWVkIHJlc29sdXRpb24gd2FzIG5vdCByZXBvcnRlZCBvbiB0aGUgbGlzdC4NClRoYXQgaXMg
d2h5IEkgbWlzc2VkIChwYXJ0IG9mKSB0aGUgZGlzY3Vzc2lvbi4NCg0KSSB3aWxsIGhhdmUgbm8g
ZnVydGhlciBjb21tZW50cy4NCg0KQmVzdCByZWdhcmRzLCBIdXViLg0KDQotLS0tLS0tLS0tLQ0K
QWRkaXRpb25hbGx5LCBwbGVhc2Ugc2VlIGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJs
MT1kcmFmdC1pZXRmLWxpbWUteWFuZy1jb25uZWN0aW9ubGVzcy1vYW0tMTcmdXJsMj1kcmFmdC1p
ZXRmLWxpbWUteWFuZy1jb25uZWN0aW9ubGVzcy1vYW0tMTgsIHdoaWNoIHNob3dzIHRoZSBjaGFu
Z2VzIHJlbGV2YW50IHRvIHRoYXQgc3BlY2lmaWMgY29tbWVudC4NCg0KSSBiZWxpZXZlIHRoZSBh
dXRob3JzIGFyZSB1c2luZyB0ZXh0IHN1Z2dlc3RlZCBieSBHcmVnLg0KDQpMaWtlIEJlbm9pdCBz
YWlkLCB0aGUgZG9jdW1lbnQgaXMgYXBwcm92ZWQgYW5kIGluIHRoZSBSRkMgRWRpdG9yIHF1ZXVl
Og0KaHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL21zZy9saW1lL3F5aEt3RmtFNFZC
OUhBMFMwNHRPV1BERks5UQ0KDQpCZXN0LA0KDQrigJQNCkNhcmxvcyBQaWduYXRhcm8sIGNhcmxv
c0BjaXNjby5jb208bWFpbHRvOmNhcmxvc0BjaXNjby5jb20+DQoNCuKAnFNvbWV0aW1lcyBJIHVz
ZSBiaWcgd29yZHMgdGhhdCBJIGRvIG5vdCBmdWxseSB1bmRlcnN0YW5kLCB0byBtYWtlIG15c2Vs
ZiBzb3VuZCBtb3JlIHBob3Rvc3ludGhlc2lzLiINCg0KDQpPbiBOb3YgMjgsIDIwMTcsIGF0IDU6
MjEgQU0sIEh1dWIgdmFuIEhlbHZvb3J0IDxodXViYXR3b3JrQGdtYWlsLmNvbTxtYWlsdG86aHV1
YmF0d29ya0BnbWFpbC5jb20+PiB3cm90ZToNCg0KSGVsbG8gQmVub2l0LA0KDQpZb3UgcmVwbHk6
DQpGb3IgeW91ciBpbmZvcm1hdGlvbiwgdGhlIGRvY3VtZW50IGlzIG5vdyBpbiB0aGUgUkZDIGVk
aXRvciBxdWV1ZSwgcmVhZHkgdG8gYmUgcHVibGlzaGVkLg0KaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2FtLw0KSSBo
YWQgbm90IHNlZW4gYW55IHJlc3BvbnNlIGZyb20gdGhlIGF1dGhvcnMgdG8gdGhlIGVtYWlsIGZy
b20gR3JlZw0KKEkgY2hlY2tlZCB0aGUgYXJjaGl2ZSkgc28gSSBhc3N1bWVkIHRoYXQgdGhlIGlz
c3VlIHdhcyBzdGlsbCBiZWluZw0KZGlzY3Vzc2VkLg0KT3RoZXIgb24tbGluZSBjb21tZW50cyB3
ZXJlIGFkZHJlc3NlZCBieSB0aGUgYXV0aG9ycy4NCg0KSSBhbHNvIGNoZWNrZWQgZm9yIHVwZGF0
ZXMgdG8gdmVyc2lvbiAxOCwgYnV0IGRpZCBub3QgZmluZCBhbnksIHNvIEkNCmRvbid0IGtub3cg
aG93IHRoZSBpc3N1ZSBoYXMgYmVlbiByZXNvbHZlZC4NCg0KU28gbm93IEkgaGF2ZSB0byB3YWl0
IHVudGlsIHRoZSBSRkMgaXMgcHVibGlzaGVkLg0KDQpSZWdhcmRzLCBIdXViLg0KDQo9PT09PT09
PT0NCg0KDQpIZWxsbyBHcmVnLA0KDQpJIGFncmVlIHdpdGggeW91IHRoYXQgdGhlIGN1cnJlbnQg
KHZlcnNpb24gMTgpIHRleHQgaW4gc2VjdGlvbiAzLjMgaXMgdmVyeSBjb25mdXNpbmcuDQoNCkF1
dGhvcnM6DQoNCklmIEkgbG9vayBhdCB0aGUgZGVmaW5pdGlvbiBvZiBUUCBpbiBzZWN0aW9uIDIu
MiBJIHRoaW5rIGEgVFAgaXMgc2ltaWxhcg0KdG8gYSBtYWludGVuYW5jZSBwb2ludCBhcyBkZWZp
bmVkIGZvciBFdGhlcm5ldC4gQW0gSSBjb3JyZWN0Pw0KDQpJIGRvbid0IHVuZGVyc3RhbmQgd2h5
IHRoZXJlIGFyZSBUUHMgd2l0aCBubyBuZWlnaGJvcmluZyBUUHMsDQp3aGVyZSB3aWxsIHRoZWly
IGluaXRpYXRlZCBPQU0gdGVzdCBiZSBzZW50PyBPciB3aGVyZSBhcmUgT0FNDQp0ZXN0cyB0aGV5
IHJlYWN0IHRvIGluaXRpYXRlZD8NCg0KSXQgaXMgSU1ITyBhbHNvIHBvc3NpYmxlIHRoYXQgdGhl
cmUgYXJlIFRQcyB3aXRoIGEgbmVpZ2hib3JpbmcNClRQIGJlZm9yZSBBTkQgYSBuZWlnaGJvcmlu
ZyBUUCBhZnRlciB0aGUgY3VycmVudCBUUC4NCg0KUGxlYXNlIGV4cGxhaW4uDQoNClJlZ2FyZHMs
IEh1dWIuDQoNCi0tLS0tLS0tLQ0KRGVhciBBbGwsDQpJIHdhcyB1bmRlciBpbXByZXNzaW9uIHRo
YXQgdGhhdCBxdWVzdGlvbiBvZiBvYW0tbmVpZ2hib3JpbmctdHBzIGhhcyBiZWVuIGRpc2N1c3Nl
ZCBhbmQgc2luY2UgYXV0aG9ycyBjb3VsZG4ndCBwcm9kdWNlIHRlY2huaWNhbCByYXRpb25hbGUg
Zm9yIHRoaXMgb2JqZWN0IHdlJ3ZlIGFncmVlZCB0aGF0IGl0IHdpbGwgYmUgcmVtb3ZlZCBhbHRv
Z2V0aGVyIGZyb20gdGhlIGdyb3VwaW5nIGNvbm5lY3Rpb25sZXNzLW9hbS10cHMuIEJ1dCBhdXRo
b3JzIGp1c3QgY2hhbmdlZCBuYW1lIGZyb20gbGV2ZWwgdG8gcG9zaXRpb24gYnV0IGhhZCBtaXNz
ZWQgdG8gc3luY2hyb25pemUgZGVzY3JpcHRpb25zIGluIHRoZSBtb2RlbCBhbmQgaW4gc2VjdGlv
biAzLjMuIFRoZSBsYXRlciBzdGlsbCByZWZlcnMgdG8gdmVydGljYWwgbGF5ZXJzOg0KDQogICAg
ICAgICAgICAgICAgICAgICAiTGlzdCBvZiByZWxhdGVkIG5laWdoYm9yaW5nIHRlc3QgcG9pbnRz
IGluIGFkamFjZW50DQoNCiAgICAgICAgICAgICAgICAgICAgIGxheWVycyB1cCBhbmQgZG93biB0
aGUgc3RhY2sgZm9yIHRoZSBzYW1lIGludGVyZmFjZQ0KDQogICAgICAgICAgICAgICAgICAgICB0
aGF0IGFyZSByZWxhdGVkIHRvIHRoZSBjdXJyZW50IHRlc3QgcG9pbnQuIjsNCndoaWxlIHRoZSBt
b2RlbCBpbnNpc3RzIHRoYXQgaXQgaXMgcGVlcmluZyByZWxhdGlvbnNoaXA6DQoNCiAgICAgICAg
ZGVzY3JpcHRpb24NCg0KICAgICAgICAgICJUaGUgcmVsYXRpdmUgcG9zaXRpb24NCg0KICAgICAg
ICAgICBvZiBuZWlnaGJvcmluZyB0ZXN0IHBvaW50DQoNCiAgICAgICAgICAgY29ycmVzcG9uZGlu
ZyB0byB0aGUgY3VycmVudA0KDQogICAgICAgICAgIHRlc3QgcG9pbnQuIExldmVsIDAgaW5kaWNh
dGVzIG5vIG5laWdoYm9yaW5nDQoNCiAgICAgICAgICAgdGVzdCBwb2ludHMgcGxhY2VkIGJlZm9y
ZSBvciBhZnRlciB0aGUgY3VycmVudA0KDQogICAgICAgICAgIHRlc3QgcG9pbnQgaW4gdGhlIHNh
bWUgbGF5ZXIuLTEgbWVhbnMgdGhlcmUgaXMNCg0KICAgICAgICAgICBhIG5laWdoYm9yaW5nIHRl
c3QgcG9pbnQgcGxhY2VkIGJlZm9yZSB0aGUgY3VycmVudA0KDQogICAgICAgICAgIHRlc3QgcG9p
bnQgaW4gdGhlIHNhbWUgbGF5ZXIgYW5kICsxIG1lYW5zIHRoZXJlIGlzDQoNCiAgICAgICAgICAg
YSBuZWlnaGJvcmluZyB0ZXN0IHBvaW50IHBsYWNlZCBhZnRlciB0aGUgY3VycmVudA0KDQogICAg
ICAgICAgIHRlc3QgcG9pbnQgaW4gc2FtZSBsYXllci4iOw0KU28sIHdoYXQgaXMgaXQ/IFBlcmhh
cHMgaXQgaXMgdGltZSB0byByZW1vdmUgbGlzdCBvYW0tbmVpZ2hib3JpbmctdHBzIGFsdG9nZXRo
ZXIgYWxzbyBiZWNhdXNlIGhhdmluZyBpdCBzIGZpeGVkIHNpemUgbGlzdCBpcyBwbGFpbiB3cm9u
Zy4gKFNvcnJ5IGZvciBiZWluZyBzbyBibHVudCBidXQgSSBjb21tZW50ZWQgdG9vIG1hbnkgdGlt
ZXMgb24gdGhlIHNhbWUgdG8gbm8gYXZhaWwgZnJvbSB0aGUgYXV0aG9ycykuDQoNClJlZ2FyZHMs
DQpHcmVnDQoNCg0KDQotLQ0KDQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09DQoNCkFsd2F5cyByZW1lbWJlciB0aGF0IHlvdSBh
cmUgdW5pcXVlLi4uanVzdCBsaWtlIGV2ZXJ5b25lIGVsc2UuLi4NCg==

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

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCglwYW5vc2UtMToyIDcg
MyA5IDIgMiA1IDIgNCA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0
aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQt
ZmFtaWx5OiJZdSBNaW5jaG8iOw0KCXBhbm9zZS0xOjIgMiA0IDAgMCAwIDAgMCAwIDA7fQ0KQGZv
bnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0
IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9y
bWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJ
Y29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bh
bi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsN
Cgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1z
aXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpwcmUNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRl
ZCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyIsc2VyaWY7fQ0KcC5Nc29MaXN0
UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFwaA0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbWFyZ2luLXRvcDowaW47DQoJbWFyZ2luLXJpZ2h0OjBp
bjsNCgltYXJnaW4tYm90dG9tOjBpbjsNCgltYXJnaW4tbGVmdDouNWluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6
IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28t
c3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIixz
ZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBs
eTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0
O30NCnNwYW4ubXNvSW5zDQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCW1zby1zdHls
ZS1uYW1lOiIiOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7DQoJY29sb3I6dGVhbDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6
MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJn
aW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldv
cmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgYmdjb2xvcj0id2hpdGUi
IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9Ildv
cmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5EZWFyIEh1dWIsPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlRoYW5rcyBmb3IgdGhlIHJlc3BvbnNlIOKAkyBnbGFkIHRvIHNlZSB0aGlz
IGxvb3AgaXMgY2xvc2VkLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CZXN0LDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj4tLSBDYXJsb3MuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9y
OmJsYWNrIj5Gcm9tOiA8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2Nv
bG9yOmJsYWNrIj5IdXViIHZhbiBIZWx2b29ydCAmbHQ7aHV1YmF0d29ya0BnbWFpbC5jb20mZ3Q7
PGJyPg0KPGI+UmVwbHktVG86IDwvYj4mcXVvdDtodXViYXR3b3JrQGdtYWlsLmNvbSZxdW90OyAm
bHQ7aHV1YmF0d29ya0BnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPldlZG5lc2RheSwg
Tm92ZW1iZXIgMjksIDIwMTcgYXQgMzozOCBQTTxicj4NCjxiPlRvOiA8L2I+JnF1b3Q7Q2FybG9z
IFBpZ25hdGFybyAoY3BpZ25hdGEpJnF1b3Q7ICZsdDtjcGlnbmF0YUBjaXNjby5jb20mZ3Q7PGJy
Pg0KPGI+Q2M6IDwvYj5CZW5vaXQgQ2xhaXNlICZsdDtiY2xhaXNlQGNpc2NvLmNvbSZndDssIEdy
ZWcgTWlyc2t5ICZsdDtncmVnaW1pcnNreUBnbWFpbC5jb20mZ3Q7LCBRaW4gV3UgJmx0O2JpbGwu
d3VAaHVhd2VpLmNvbSZndDssIFRoZSBJRVNHICZsdDtpZXNnQGlldGYub3JnJmd0OywgJnF1b3Q7
aWV0ZkBpZXRmLm9yZyZxdW90OyAmbHQ7aWV0ZkBpZXRmLm9yZyZndDssIFJvbmFsZCBCb25pY2Eg
Jmx0O3Jib25pY2FAanVuaXBlci5uZXQmZ3Q7LCAmcXVvdDtsaW1lLWNoYWlyc0BpZXRmLm9yZyZx
dW90OyAmbHQ7bGltZS1jaGFpcnNAaWV0Zi5vcmcmZ3Q7LCAmcXVvdDtsaW1lQGlldGYub3JnJnF1
b3Q7DQogJmx0O2xpbWVAaWV0Zi5vcmcmZ3Q7LCAmcXVvdDtkcmFmdC1pZXRmLWxpbWUteWFuZy1j
b25uZWN0aW9ubGVzcy1vYW1AaWV0Zi5vcmcmcXVvdDsgJmx0O2RyYWZ0LWlldGYtbGltZS15YW5n
LWNvbm5lY3Rpb25sZXNzLW9hbUBpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6
IFtMaW1lXSBMYXN0IENhbGw6ICZsdDtkcmFmdC1pZXRmLWxpbWUteWFuZy1jb25uZWN0aW9ubGVz
cy1vYW0tMTEudHh0Jmd0OyAoR2VuZXJpYyBZQU5HIERhdGEgTW9kZWwgZm9yIENvbm5lY3Rpb25s
ZXNzIE9wZXJhdGlvbnMsIEFkbWluaXN0cmF0aW9uLCBhbmQgTWFpbnRlbmFuY2UoT0FNKSBwcm90
b2NvbHMpIHRvIFByb3Bvc2VkIFN0YW5kYXJkPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IZWxsbyBDYXJsb3MsPGJyPg0KPGJyPg0K
VGhhbmsgeW91IGZvciB0aGUgYWRkaXRpb25hbCBpbmZvcm1hdGlvbi48YnI+DQo8YnI+DQpBcyBJ
IG1lbnRpb25lZCBJIGFscmVhZHkgbG9va2VkIGF0IHZlcnNpb24gMTggYmVjYXVzZSB0aGF0IHdh
cyBtZW50aW9uZWQ8YnI+DQppbiBHcmVncyByZXNwb25zZS48YnI+DQo8YnI+DQpJIGhhdmUgdW5k
ZXJzdG9vZCB0aGF0IHRoaXMgZHJhZnQgd2FzIGRpc2N1c3NlZCBpbiBTaW5nYXBvcmUuPGJyPg0K
VW5mb3J0dW5hdGVseSB0aGUgYWdyZWVkIHJlc29sdXRpb24gd2FzIG5vdCByZXBvcnRlZCBvbiB0
aGUgbGlzdC48YnI+DQpUaGF0IGlzIHdoeSBJIG1pc3NlZCAocGFydCBvZikgdGhlIGRpc2N1c3Np
b24uPGJyPg0KPGJyPg0KSSB3aWxsIGhhdmUgbm8gZnVydGhlciBjb21tZW50cy48YnI+DQo8YnI+
DQpCZXN0IHJlZ2FyZHMsIEh1dWIuPGJyPg0KPGJyPg0KLS0tLS0tLS0tLS08bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJv
dHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BZGRpdGlvbmFsbHksIHBsZWFzZSBz
ZWUmbmJzcDs8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDE9ZHJhZnQt
aWV0Zi1saW1lLXlhbmctY29ubmVjdGlvbmxlc3Mtb2FtLTE3JmFtcDt1cmwyPWRyYWZ0LWlldGYt
bGltZS15YW5nLWNvbm5lY3Rpb25sZXNzLW9hbS0xOCI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvcmZj
ZGlmZj91cmwxPWRyYWZ0LWlldGYtbGltZS15YW5nLWNvbm5lY3Rpb25sZXNzLW9hbS0xNyZhbXA7
dXJsMj1kcmFmdC1pZXRmLWxpbWUteWFuZy1jb25uZWN0aW9ubGVzcy1vYW0tMTg8L2E+LA0KIHdo
aWNoIHNob3dzIHRoZSBjaGFuZ2VzIHJlbGV2YW50IHRvIHRoYXQgc3BlY2lmaWMgY29tbWVudC4g
PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGJlbGlldmUg
dGhlIGF1dGhvcnMgYXJlIHVzaW5nIHRleHQgc3VnZ2VzdGVkIGJ5IEdyZWcuPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkxpa2UgQmVub2l0IHNh
aWQsIHRoZSBkb2N1bWVudCBpcyBhcHByb3ZlZCBhbmQgaW4gdGhlIFJGQyBFZGl0b3IgcXVldWU6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBo
cmVmPSJodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2xpbWUvcXloS3dGa0U0
VkI5SEEwUzA0dE9XUERGSzlRIj5odHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNn
L2xpbWUvcXloS3dGa0U0VkI5SEEwUzA0dE9XUERGSzlRPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CZXN0LDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjpi
bGFjayI+4oCUPGJyPg0KQ2FybG9zIFBpZ25hdGFybywmbmJzcDs8YSBocmVmPSJtYWlsdG86Y2Fy
bG9zQGNpc2NvLmNvbSI+Y2FybG9zQGNpc2NvLmNvbTwvYT48YnI+DQo8YnI+DQo8aT7igJxTb21l
dGltZXMgSSB1c2UgYmlnIHdvcmRzIHRoYXQgSSBkbyBub3QgZnVsbHkgdW5kZXJzdGFuZCwgdG8g
bWFrZSBteXNlbGYgc291bmQgbW9yZSBwaG90b3N5bnRoZXNpcy4mcXVvdDs8L2k+PG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4t
dG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPk9uIE5vdiAyOCwgMjAxNywgYXQgNToyMSBBTSwgSHV1YiB2YW4gSGVsdm9vcnQgJmx0Ozxh
IGhyZWY9Im1haWx0bzpodXViYXR3b3JrQGdtYWlsLmNvbSI+aHV1YmF0d29ya0BnbWFpbC5jb208
L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5IZWxsbyBCZW5vaXQsPGJyPg0KPGJyPg0KWW91IHJlcGx5OjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4t
Ym90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Gb3IgeW91ciBpbmZv
cm1hdGlvbiwgdGhlIGRvY3VtZW50IGlzIG5vdyBpbiB0aGUgUkZDIGVkaXRvciBxdWV1ZSwgcmVh
ZHkgdG8gYmUgcHVibGlzaGVkLjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0
Zi5vcmcvZG9jL2RyYWZ0LWlldGYtbGltZS15YW5nLWNvbm5lY3Rpb25sZXNzLW9hbS8iPmh0dHBz
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtbGltZS15YW5nLWNvbm5lY3Rp
b25sZXNzLW9hbS88L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkkgaGFkIG5vdCBzZWVuIGFueSByZXNwb25zZSBmcm9tIHRoZSBh
dXRob3JzIHRvIHRoZSBlbWFpbCBmcm9tIEdyZWc8YnI+DQooSSBjaGVja2VkIHRoZSBhcmNoaXZl
KSBzbyBJIGFzc3VtZWQgdGhhdCB0aGUgaXNzdWUgd2FzIHN0aWxsIGJlaW5nPGJyPg0KZGlzY3Vz
c2VkLiA8YnI+DQpPdGhlciBvbi1saW5lIGNvbW1lbnRzIHdlcmUgYWRkcmVzc2VkIGJ5IHRoZSBh
dXRob3JzLjxicj4NCjxicj4NCkkgYWxzbyBjaGVja2VkIGZvciB1cGRhdGVzIHRvIHZlcnNpb24g
MTgsIGJ1dCBkaWQgbm90IGZpbmQgYW55LCBzbyBJPGJyPg0KZG9uJ3Qga25vdyBob3cgdGhlIGlz
c3VlIGhhcyBiZWVuIHJlc29sdmVkLjxicj4NCjxicj4NClNvIG5vdyBJIGhhdmUgdG8gd2FpdCB1
bnRpbCB0aGUgUkZDIGlzIHB1Ymxpc2hlZC48YnI+DQo8YnI+DQpSZWdhcmRzLCBIdXViLjxicj4N
Cjxicj4NCj09PT09PT09PTxicj4NCjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPGJsb2Nr
cXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkhl
bGxvIEdyZWcsPGJyPg0KPGJyPg0KSSBhZ3JlZSB3aXRoIHlvdSB0aGF0IHRoZSBjdXJyZW50ICh2
ZXJzaW9uIDE4KSB0ZXh0IGluIHNlY3Rpb24gMy4zIGlzIHZlcnkgY29uZnVzaW5nLjxicj4NCjxi
cj4NCkF1dGhvcnM6PGJyPg0KPGJyPg0KSWYgSSBsb29rIGF0IHRoZSBkZWZpbml0aW9uIG9mIFRQ
IGluIHNlY3Rpb24gMi4yIEkgdGhpbmsgYSBUUCBpcyBzaW1pbGFyPGJyPg0KdG8gYSBtYWludGVu
YW5jZSBwb2ludCBhcyBkZWZpbmVkIGZvciBFdGhlcm5ldC4gQW0gSSBjb3JyZWN0Pzxicj4NCjxi
cj4NCkkgZG9uJ3QgdW5kZXJzdGFuZCB3aHkgdGhlcmUgYXJlIFRQcyB3aXRoIG5vIG5laWdoYm9y
aW5nIFRQcyw8YnI+DQp3aGVyZSB3aWxsIHRoZWlyIGluaXRpYXRlZCBPQU0gdGVzdCBiZSBzZW50
PyBPciB3aGVyZSBhcmUgT0FNPGJyPg0KdGVzdHMgdGhleSByZWFjdCB0byBpbml0aWF0ZWQ/PGJy
Pg0KPGJyPg0KSXQgaXMgSU1ITyBhbHNvIHBvc3NpYmxlIHRoYXQgdGhlcmUgYXJlIFRQcyB3aXRo
IGEgbmVpZ2hib3JpbmcgPGJyPg0KVFAgYmVmb3JlIEFORCBhIG5laWdoYm9yaW5nIFRQIGFmdGVy
IHRoZSBjdXJyZW50IFRQLjxicj4NCjxicj4NClBsZWFzZSBleHBsYWluLjxicj4NCjxicj4NClJl
Z2FyZHMsIEh1dWIuPGJyPg0KPGJyPg0KLS0tLS0tLS0tPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQi
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlYXIgQWxsLCA8bzpwPjwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHdhcyB1bmRlciBpbXByZXNzaW9uIHRoYXQg
dGhhdCBxdWVzdGlvbiBvZiZuYnNwOzxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5vYW0t
bmVpZ2hib3JpbmctdHBzJm5ic3A7aGFzIGJlZW4gZGlzY3Vzc2VkIGFuZCBzaW5jZSBhdXRob3Jz
IGNvdWxkbid0IHByb2R1Y2UgdGVjaG5pY2FsIHJhdGlvbmFsZSBmb3IgdGhpcyBvYmplY3Qgd2Un
dmUgYWdyZWVkIHRoYXQgaXQgd2lsbCBiZSByZW1vdmVkIGFsdG9nZXRoZXIgZnJvbQ0KIHRoZSZu
YnNwO2dyb3VwaW5nIGNvbm5lY3Rpb25sZXNzLW9hbS10cHMuIEJ1dCBhdXRob3JzIGp1c3QgY2hh
bmdlZCBuYW1lIGZyb20gbGV2ZWwgdG8gcG9zaXRpb24gYnV0IGhhZCBtaXNzZWQgdG8gc3luY2hy
b25pemUgZGVzY3JpcHRpb25zIGluIHRoZSBtb2RlbCBhbmQgaW4gc2VjdGlvbiAzLjMuIFRoZSBs
YXRlciBzdGlsbCByZWZlcnMgdG8gdmVydGljYWwgbGF5ZXJzOjwvc3Bhbj48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwcmU+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZxdW90O0xpc3Qgb2YgcmVsYXRlZCBuZWln
aGJvcmluZyB0ZXN0IHBvaW50cyBpbiBhZGphY2VudDxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyBsYXllcnMgdXAgYW5kIGRvd24gdGhlIHN0YWNrIGZvciB0aGUgc2FtZSBpbnRlcmZhY2U8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgdGhhdCBhcmUgcmVsYXRlZCB0byB0aGUgY3Vy
cmVudCB0ZXN0IHBvaW50LiZxdW90Ozs8bzpwPjwvbzpwPjwvcHJlPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+d2hpbGUgdGhlIG1vZGVsIGluc2lzdHMgdGhhdCBpdCBpcyBw
ZWVyaW5nIHJlbGF0aW9uc2hpcDo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwcmU+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwO2Rlc2NyaXB0aW9uPG86
cD48L286cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZxdW90O1RoZSByZWxhdGl2ZSBwb3NpdGlvbjxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyBvZiBuZWlnaGJvcmluZyB0ZXN0IHBvaW50PG86cD48L286cD48L3By
ZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7IGNvcnJlc3BvbmRpbmcgdG8gdGhlIGN1cnJlbnQ8bzpwPjwvbzpwPjwvcHJl
Pg0KPHByZT4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgdGVzdCBwb2ludC4gTGV2ZWwgMCBpbmRpY2F0ZXMgbm8gbmVpZ2hib3Jpbmc8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgdGVzdCBwb2ludHMgcGxhY2VkIGJlZm9yZSBvciBh
ZnRlciB0aGUgY3VycmVudDxvOnA+PC9vOnA+PC9wcmU+DQo8L2Rpdj4NCjxkaXY+DQo8cHJlPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyB0ZXN0IHBvaW50IGluIHRoZSBzYW1lIGxheWVyLi0xIG1lYW5zIHRoZXJlIGlzPG86cD48L286
cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IGEgbmVpZ2hib3JpbmcgdGVzdCBwb2ludCBwbGFjZWQgYmVmb3Jl
IHRoZSBjdXJyZW50PG86cD48L286cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRlc3QgcG9pbnQgaW4gdGhl
IHNhbWUgbGF5ZXIgYW5kICYjNDM7MSBtZWFucyB0aGVyZSBpczxvOnA+PC9vOnA+PC9wcmU+DQo8
cHJlPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyBhIG5laWdoYm9yaW5nIHRlc3QgcG9pbnQgcGxhY2VkIGFmdGVyIHRoZSBjdXJyZW50
PG86cD48L286cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRlc3QgcG9pbnQgaW4gc2FtZSBsYXllci4mcXVv
dDs7PG86cD48L286cD48L3ByZT4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PlNvLCB3aGF0IGlzIGl0PyBQZXJoYXBzIGl0IGlzIHRpbWUgdG8gcmVtb3ZlIGxpc3QmbmJzcDs8
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+b2FtLW5laWdoYm9yaW5nLXRwcyBhbHRvZ2V0
aGVyIGFsc28gYmVjYXVzZSBoYXZpbmcgaXQgcyBmaXhlZCBzaXplIGxpc3QgaXMgcGxhaW4gd3Jv
bmcuIChTb3JyeSBmb3IgYmVpbmcgc28gYmx1bnQgYnV0IEkgY29tbWVudGVkIHRvbyBtYW55IHRp
bWVzIG9uIHRoZSBzYW1lDQogdG8gbm8gYXZhaWwgZnJvbSB0aGUgYXV0aG9ycykuPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+UmVnYXJkcyw8L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdCI+R3JlZzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxwPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHByZT4tLSA8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT49PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PG86cD48L286cD48L3ByZT4NCjxwcmU+QWx3YXlzIHJlbWVtYmVyIHRoYXQgeW91IGFyZSB1bmlx
dWUuLi5qdXN0IGxpa2UgZXZlcnlvbmUgZWxzZS4uLjxvOnA+PC9vOnA+PC9wcmU+DQo8L2Rpdj4N
CjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_88B5F94B63BC4F1B9C8A0544A3DA9941ciscocom_--


From nobody Thu Nov 30 14:33:28 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 1E561128D3E; Wed, 29 Nov 2017 21:18:07 -0800 (PST)
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 fHGbMvKfJQ_u; Wed, 29 Nov 2017 21:18:04 -0800 (PST)
Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::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 3AA1C124207; Wed, 29 Nov 2017 21:18:04 -0800 (PST)
Received: by mail-lf0-x230.google.com with SMTP id f20so6496245lfe.3; Wed, 29 Nov 2017 21:18:04 -0800 (PST)
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=OpraytxtahchJR8ZAxXqVjFWMxl4XkvW7CWMrtt3Vm8=; b=mb6zus4nBddJ1BT+JWxf0eT5z3c7MDV8dpTj7yYHPYIygbjrX1rfq0dr5Kck6QRDa2 96fZ1qWUOCz+Sy2F7MelIPdvxsPKkmrXnvFsJ1lezuLmSSpQLkE/yJ7xH0JQ6mEczR0Y D/Zlt92PAx0VEBvTvDfAl8wRW1D1URUW5FEjbeo428H1MrLtmamDOnBWC8e3VAHu1+U5 YY3e+n1OMiSmbcUfhdvQ2UggRNf2AGuaSok+3cRMwQjbGWLvne7Tbi2/pY27XupTNIt9 M3N5Hd+JAGpY27hADUWgsuWhmoK+/DgZRWnuCvhkrTZxQ+yTOyiFkAJyqbokUBMt4e1j YJDw==
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=OpraytxtahchJR8ZAxXqVjFWMxl4XkvW7CWMrtt3Vm8=; b=CI7bN4+d7e3tM25YwL/VVuNPP/PAHWF7RtLInsBIiW7q/ncTiIqoE7Z+uEPs9L5x36 UBKwxTRhCcvi5rWWjjNyNCKy/Zw/3emlvAdJBylHSESDtZMIDzm/FAjCf/Xahvxi9qhL wSYQahk9nGLIfyvhMcbZswak7WrUcbmWbZN4aVa/wjyxW98HX7zTEZ3uDejWHttqhRZy 66Nx5zr60IoFWFKnb9DZNkU1Vvjoodiv89ncTWOU+UZFvN31AaBe/oDWTmGTot1O2d/D qKnoXzbsWbEjOfpUGiTgT0hREl0MtXFbvDL5Bi9aHfLe2qgagA6GtNBczviRv3msDFWJ STPg==
X-Gm-Message-State: AJaThX7a3ZNgSKz7ieCmvFjFDK5iseYuFbjHfYm3D9aD8Z7GpDi2mW8t nnHbYVzN47Zow6MBKSjK2xrvTCnyUn+20umncdE=
X-Google-Smtp-Source: AGs4zMb1ZbHU8fOSIoRMNHbA6703nU9lQM6B2h+J4L1k8vxG1J344CyDluzyqSHqp3Mat7OVmzD8eP/gPhgc4UCXJ7c=
X-Received: by 10.46.64.6 with SMTP id n6mr2663308lja.129.1512019082352; Wed, 29 Nov 2017 21:18:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.46.32.136 with HTTP; Wed, 29 Nov 2017 21:18:01 -0800 (PST)
In-Reply-To: <CAMdAHv-iiZ5ScQCj1OZZs6C3FZFaRZbiXbm6--ktN3KZz7b4Ag@mail.gmail.com>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com> <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com> <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.com> <646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com> <1b527039-bf80-ead5-e341-c8cfeb24f855@gmail.com> <CAMdAHv-iiZ5ScQCj1OZZs6C3FZFaRZbiXbm6--ktN3KZz7b4Ag@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 29 Nov 2017 21:18:01 -0800
Message-ID: <CA+RyBmXLHmkQgU8eJKUabYRcpkYobDbU6D7DR++yw8X6UwGxcA@mail.gmail.com>
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
To: Tissa Senevirathne <tsenevir@gmail.com>
Cc: "huubatwork@gmail.com" <huubatwork@gmail.com>,  "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, "Ronald P. Bonica" <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, The IESG <iesg@ietf.org>,  "Benoit Claise (bclaise)" <bclaise@cisco.com>, "lime@ietf.org" <lime@ietf.org>, Qin Wu <bill.wu@huawei.com>,  "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1a5e704c1daa055f2c60d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F84l-LCZzkHRZ0XkIB8Hx2WfPEw>
X-Mailman-Approved-At: Thu, 30 Nov 2017 14:33:11 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 05:18:07 -0000

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

Hi Tissa,
thank you for your kind words, much appreciated. Wish you all success in
your endeavors and hope you'll find opportunity to return to IETF work
sooner than later.

Best regards,
Greg

On Wed, Nov 29, 2017 at 2:40 PM, Tissa Senevirathne <tsenevir@gmail.com>
wrote:

> I have been out of IETF for a while but still receives LIME WG emails.
>
> As the original author of the connectionless draft I deliberately avoided
> making any comments as I do not have adequate time to do a good job.
>
> However, I have been reading, with great respect, the comments Greg Mirsk=
y
> was making to make these drafts better both technically and editorially. =
I
> want to extend a well deserved thank you to Greg. Thank You Greg.
>
> Also I do not agree with Carlos comments on Hubbs observations, i.e. Oh
> Draft is in IETF editors queue and it is too late. May be time to pull it
> out from the queue or create errata if the changes are significant enough=
.
>
> If either of these happens I do like to suggest two things
>
> 1. Appoint an editor who can shepherd edits and presentation aspects of
> the draft
> 2. Provide adequate time and be transparent to share with the WG on what
> is agreed or appoint a technical panel
>
>
>
>
> On Wed, Nov 29, 2017 at 12:39 PM, Huub van Helvoort <huubatwork@gmail.com=
>
> wrote:
>
>> Hello Carlos,
>>
>> Thank you for the additional information.
>>
>> As I mentioned I already looked at version 18 because that was mentioned
>> in Gregs response.
>>
>> I have understood that this draft was discussed in Singapore.
>> Unfortunately the agreed resolution was not reported on the list.
>> That is why I missed (part of) the discussion.
>>
>> I will have no further comments.
>>
>> Best regards, Huub.
>>
>> -----------
>>
>> Additionally, please see https://www.ietf.org/rfcdi
>> ff?url1=3Ddraft-ietf-lime-yang-connectionless-oam-17&url2=3D
>> draft-ietf-lime-yang-connectionless-oam-18, which shows the changes
>> relevant to that specific comment.
>>
>> I believe the authors are using text suggested by Greg.
>>
>> Like Benoit said, the document is approved and in the RFC Editor queue:
>> https://mailarchive.ietf.org/arch/msg/lime/qyhKwFkE4VB9HA0S04tOWPDFK9Q
>>
>> Best,
>>
>> =E2=80=94
>> Carlos Pignataro, carlos@cisco.com
>>
>> *=E2=80=9CSometimes I use big words that I do not fully understand, to m=
ake
>> myself sound more photosynthesis."*
>>
>> On Nov 28, 2017, at 5:21 AM, Huub van Helvoort <huubatwork@gmail.com>
>> wrote:
>>
>> Hello Benoit,
>>
>> You reply:
>>
>> For your information, the document is now in the RFC editor queue, ready
>> to be published.
>> https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam=
/
>>
>> I had not seen any response from the authors to the email from Greg
>> (I checked the archive) so I assumed that the issue was still being
>> discussed.
>> Other on-line comments were addressed by the authors.
>>
>> I also checked for updates to version 18, but did not find any, so I
>> don't know how the issue has been resolved.
>>
>> So now I have to wait until the RFC is published.
>>
>> Regards, Huub.
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> Hello Greg,
>>
>> I agree with you that the current (version 18) text in section 3.3 is
>> very confusing.
>>
>> Authors:
>>
>> If I look at the definition of TP in section 2.2 I think a TP is similar
>> to a maintenance point as defined for Ethernet. Am I correct?
>>
>> I don't understand why there are TPs with no neighboring TPs,
>> where will their initiated OAM test be sent? Or where are OAM
>> tests they react to initiated?
>>
>> It is IMHO also possible that there are TPs with a neighboring
>> TP before AND a neighboring TP after the current TP.
>>
>> Please explain.
>>
>> Regards, Huub.
>>
>> ---------
>>
>> Dear All,
>> I was under impression that that question of oam-neighboring-tps has
>> been discussed and since authors couldn't produce technical rationale fo=
r
>> this object we've agreed that it will be removed altogether from the gro=
uping
>> connectionless-oam-tps. But authors just changed name from level to
>> position but had missed to synchronize descriptions in the model and in
>> section 3.3. The later still refers to vertical layers:
>>
>>                      "List of related neighboring test points in adjacen=
t
>>                      layers up and down the stack for the same interface
>>                      that are related to the current test point.";
>>
>> while the model insists that it is peering relationship:
>>
>>         description
>>           "The relative position
>>            of neighboring test point
>>            corresponding to the current
>>            test point. Level 0 indicates no neighboring
>>            test points placed before or after the current
>>
>>            test point in the same layer.-1 means there is
>>            a neighboring test point placed before the current
>>            test point in the same layer and +1 means there is
>>            a neighboring test point placed after the current
>>            test point in same layer.";
>>
>> So, what is it? Perhaps it is time to remove list oam-neighboring-tps
>> altogether also because having it s fixed size list is plain wrong. (Sor=
ry
>> for being so blunt but I commented too many times on the same to no avai=
l
>> from the authors).
>>
>> Regards,
>> Greg
>>
>>
>> --
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> Always remember that you are unique...just like everyone else...
>>
>>
>> _______________________________________________
>> Lime mailing list
>> Lime@ietf.org
>> https://www.ietf.org/mailman/listinfo/lime
>>
>>
>

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

<div dir=3D"ltr">Hi Tissa,<div>thank you for your kind words, much apprecia=
ted. Wish you all success in your endeavors and hope you&#39;ll find opport=
unity to return to IETF work sooner than later.</div><div><br></div><div>Be=
st regards,</div><div>Greg</div></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Wed, Nov 29, 2017 at 2:40 PM, Tissa Senevirathne <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:tsenevir@gmail.com" target=3D"_blank"=
>tsenevir@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"ltr">I have been out of IETF for a while but still receives LI=
ME WG emails.<div><br></div><div>As the original author of the connectionle=
ss draft I deliberately avoided making any comments as I do not have adequa=
te time to do a good job.</div><div><br></div><div>However, I have been rea=
ding, with great respect, the comments Greg Mirsky was making to make these=
 drafts better both technically and editorially. I want to extend a well de=
served thank you to Greg. Thank You Greg.</div><div><br></div><div>Also I d=
o not agree with Carlos comments on Hubbs observations, i.e. Oh Draft is in=
 IETF editors queue and it is too late. May be time to pull it out from the=
 queue or create errata if the changes are significant enough.</div><div><b=
r></div><div>If either of these happens I do like to suggest two things</di=
v><div><br></div><div>1. Appoint an editor who can shepherd edits and prese=
ntation aspects of the draft</div><div>2. Provide adequate time and be tran=
sparent to share with the WG on what is agreed or appoint a technical panel=
</div><div><br></div><div><br></div><div><br></div></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote"><div><div class=3D"h5">On Wed, Nov =
29, 2017 at 12:39 PM, Huub van Helvoort <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:huubatwork@gmail.com" target=3D"_blank">huubatwork@gmail.com</a>&gt;</=
span> wrote:<br></div></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class=
=3D"h5">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"m_7063178834543132092m_-509113956322476388moz-cite-prefix=
">Hello Carlos,<br>
      <br>
      Thank you for the additional information.<br>
      <br>
      As I mentioned I already looked at version 18 because that was
      mentioned<br>
      in Gregs response.<br>
      <br>
      I have understood that this draft was discussed in Singapore.<br>
      Unfortunately the agreed resolution was not reported on the list.<br>
      That is why I missed (part of) the discussion.<br>
      <br>
      I will have no further comments.<br>
      <br>
      Best regards, Huub.<br>
      <br>
      -----------<br>
    </div><div><div class=3D"m_7063178834543132092h5">
    <blockquote type=3D"cite">
     =20
      Additionally, please see=C2=A0<a href=3D"https://www.ietf.org/rfcdiff=
?url1=3Ddraft-ietf-lime-yang-connectionless-oam-17&amp;url2=3Ddraft-ietf-li=
me-yang-connectionless-oam-18" target=3D"_blank">https://www.ietf.org/rfcdi=
<wbr>ff?url1=3Ddraft-ietf-lime-yang-<wbr>connectionless-oam-17&amp;url2=3D<=
wbr>draft-ietf-lime-yang-connectio<wbr>nless-oam-18</a>,
      which shows the changes relevant to that specific comment.
      <div><br>
      </div>
      <div>I believe the authors are using text suggested by
        Greg.</div>
      <div><br>
      </div>
      <div>Like Benoit said, the document is approved and in
        the RFC Editor queue:</div>
      <div><a href=3D"https://mailarchive.ietf.org/arch/msg/lime/qyhKwFkE4V=
B9HA0S04tOWPDFK9Q" target=3D"_blank">https://mailarchive.ietf.org/a<wbr>rch=
/msg/lime/qyhKwFkE4VB9HA0S0<wbr>4tOWPDFK9Q</a></div>
      <div><br>
      </div>
      <div>Best,</div>
      <div>=C2=A0<br>
        <div>
          <div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:s=
tart;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0p=
x;word-wrap:break-word">
            =E2=80=94<br>
            Carlos Pignataro,=C2=A0<a href=3D"mailto:carlos@cisco.com" targ=
et=3D"_blank">carlos@cisco.com</a><br>
            <br>
            <i>=E2=80=9CSometimes I use big words that I do not fully
              understand, to make myself sound more photosynthesis.&quot;</=
i></div>
        </div>
        <div><br>
          <blockquote type=3D"cite">
            <div>On Nov 28, 2017, at 5:21 AM, Huub van Helvoort
              &lt;<a href=3D"mailto:huubatwork@gmail.com" target=3D"_blank"=
>huubatwork@gmail.com</a>&gt;
              wrote:</div>
            <br class=3D"m_7063178834543132092m_-509113956322476388Apple-in=
terchange-newline">
            <div>
              <div text=3D"#000000" bgcolor=3D"#FFFFFF">
                <div class=3D"m_7063178834543132092m_-509113956322476388moz=
-cite-prefix">Hello Benoit,<br>
                  <br>
                  You reply:<br>
                </div>
                <blockquote type=3D"cite">
                  <div class=3D"m_7063178834543132092m_-509113956322476388m=
oz-cite-prefix">For your information, the
                    document is now in the RFC editor queue, ready to be
                    published.<br>
                    <a class=3D"m_7063178834543132092m_-509113956322476388m=
oz-txt-link-freetext" href=3D"https://datatracker.ietf.org/doc/draft-ietf-l=
ime-yang-connectionless-oam/" target=3D"_blank">https://datatracker.ietf.or=
g/d<wbr>oc/draft-ietf-lime-yang-connec<wbr>tionless-oam/</a><br>
                  </div>
                </blockquote>
                I had not seen any response from the authors to the
                email from Greg<br>
                (I checked the archive) so I assumed that the issue was
                still being<br>
                discussed. <br>
                Other on-line comments were addressed by the authors.<br>
                <br>
                I also checked for updates to version 18, but did not
                find any, so I<br>
                don&#39;t know how the issue has been resolved.<br>
                <br>
                So now I have to wait until the RFC is published.<br>
                <br>
                Regards, Huub.<br>
                <br>
                =3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
                <br>
                <blockquote type=3D"cite">
                  <blockquote type=3D"cite">
                    <div class=3D"m_7063178834543132092m_-50911395632247638=
8moz-cite-prefix">Hello Greg,<br>
                      <br>
                      I agree with you that the current (version 18)
                      text in section 3.3 is very confusing.<br>
                      <br>
                      Authors:<br>
                      <br>
                      If I look at the definition of TP in section 2.2 I
                      think a TP is similar<br>
                      to a maintenance point as defined for Ethernet. Am
                      I correct?<br>
                      <br>
                      I don&#39;t understand why there are TPs with no
                      neighboring TPs,<br>
                      where will their initiated OAM test be sent? Or
                      where are OAM<br>
                      tests they react to initiated?<br>
                      <br>
                      It is IMHO also possible that there are TPs with a
                      neighboring <br>
                      TP before AND a neighboring TP after the current
                      TP.<br>
                      <br>
                      Please explain.<br>
                      <br>
                      Regards, Huub.<br>
                      <br>
                      ---------<br>
                      <br>
                    </div>
                    <blockquote type=3D"cite">
                      <div dir=3D"ltr">Dear All,
                        <div>I was under impression that that
                          question of=C2=A0<span style=3D"font-size:13.3333=
px">oam-neighboring-tps</span><span style=3D"font-size:13.3333px">=C2=A0has
                            been discussed and since authors couldn&#39;t
                            produce technical rationale for this object
                            we&#39;ve agreed that it will be removed
                            altogether from the=C2=A0</span><span style=3D"=
font-size:13.3333px">grouping
                            connectionless-oam-tps. But authors just
                            changed name from level to position but had
                            missed to synchronize descriptions in the
                            model and in section 3.3. The later still
                            refers to vertical layers:</span></div>
                        <div>
                          <pre class=3D"m_7063178834543132092m_-50911395632=
2476388gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bo=
ttom:0px">                     &quot;List of related neighboring test point=
s in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.&quot;;
</pre>
                        </div>
                        <div>while the model insists that it is
                          peering relationship:</div>
                        <div>
                          <pre class=3D"m_7063178834543132092m_-50911395632=
2476388gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bo=
ttom:0px">        description
          &quot;The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current
</pre>
                        </div>
                        <div>
                          <pre class=3D"m_7063178834543132092m_-50911395632=
2476388gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bo=
ttom:0px">           test point in the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.&quot;;
</pre>
                        </div>
                        <div>So, what is it? Perhaps it is time
                          to remove list=C2=A0<span style=3D"font-size:13.3=
333px">oam-neighboring-tps
                            altogether also because having it s fixed
                            size list is plain wrong. (Sorry for being
                            so blunt but I commented too many times on
                            the same to no avail from the authors).</span><=
/div>
                        <div><span style=3D"font-size:13.3333px"><br>
                          </span></div>
                        <div><span style=3D"font-size:13.3333px">Regards,</=
span></div>
                        <div><span style=3D"font-size:13.3333px">Greg</span=
><br>
                        </div>
                      </div>
                    </blockquote>
                  </blockquote>
                </blockquote>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <pre class=3D"m_7063178834543132092m_-509113956322476388moz-signature" =
cols=3D"72">--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D
Always remember that you are unique...just like everyone else...</pre>
  </div></div></div>


<br></div></div><span class=3D"">______________________________<wbr>_______=
__________<br>
Lime mailing list<br>
<a href=3D"mailto:Lime@ietf.org" target=3D"_blank">Lime@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/lime" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/lime</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>

--94eb2c1a5e704c1daa055f2c60d8--


From nobody Thu Nov 30 14:33:43 2017
Return-Path: <tsenevir@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 6CD61126B6D; Wed, 29 Nov 2017 14:40:12 -0800 (PST)
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 r_8NwnQry4Zq; Wed, 29 Nov 2017 14:40:09 -0800 (PST)
Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::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 01EB41201FA; Wed, 29 Nov 2017 14:40:09 -0800 (PST)
Received: by mail-ot0-x233.google.com with SMTP id b54so4501109otd.8; Wed, 29 Nov 2017 14:40:08 -0800 (PST)
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=sD11PjzxMyyRaGEgjsLoYFnb3NQPkAaDdszptcSZTsg=; b=Pa3SsKBJYU+dJu8YLP1+VjYO8owVzdUugSKViXy96StO5DYygDWGeCgmShnHAOerdO KsHunjYU5qO8OebgdTfd6AD1BacOFLfYJO/SaoVoY4+tlENPgp4p5KEEWJgYhmLGa9ma wOlKCYnRQhS/kJ9DP3ITmmZTv++2WuvDN/3YQIIqOpiZY4e4tnHpxJ4kjmrxBUBkS2qN qM32GfmjIKy0dcZTh0+GNTDunWR6rZQj1bqwd+yA87hL1FOa9IgF0Zk0gUWTlFiw4FvN cQytziU+izFrlSsm+2XDSXRWnSzomUeojmwXXSFcyp914EtKM2GX4Ia1ifcVT5aFJnLm wLlw==
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=sD11PjzxMyyRaGEgjsLoYFnb3NQPkAaDdszptcSZTsg=; b=gcPaCbv+Qrr9vwfwiudVEn/CMSuHielTjGJfEYaxou6ik0Lk5lkrgfFbr5bj2IJxi/ deqRfMg5lwSumN2fohkzHx4OrL3srYtj2y/Testff+NuVZfEqVbOFT6L6ft78d9rUYkz Cw0fFYBOTf/gVYrdqOE1AVDu2avWxSFo7XR8ONV0c+o5lil2sDBnxjNhOoix6rgynwP3 LaZEkMFg4uPPZa3sR5cNkL6UgrdLlJr9FGfEdtLeFqMZC5AmMGrSKHYZ9CtvIubzXyp+ Aa4325BnSnooLAAux2MFd7oEAgCnVwFO5dcNR58Pvv1HaFXSddNklcazLhypMuiZcE0y 9l9A==
X-Gm-Message-State: AJaThX535RBbPzka+f1FQu8nF7dj3j6ZuN5/d+WTL5M5Ogx9gfTVFv3G YLvOLnfcFL1FvlYyqvThsSNst0Je+t9X2qMP3ZI=
X-Google-Smtp-Source: AGs4zMY9jx7u//Ra6OGh0UnQAWesWc4R2SHxEn9VDkG0DAnT9k0Ex7vDsOoesMFGykHnHS0RMVIogE/qyxP0Rc4CzT4=
X-Received: by 10.157.38.248 with SMTP id i53mr3343098otd.94.1511995208140; Wed, 29 Nov 2017 14:40:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.22.209 with HTTP; Wed, 29 Nov 2017 14:40:07 -0800 (PST)
In-Reply-To: <1b527039-bf80-ead5-e341-c8cfeb24f855@gmail.com>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com> <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com> <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.com> <646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com> <1b527039-bf80-ead5-e341-c8cfeb24f855@gmail.com>
From: Tissa Senevirathne <tsenevir@gmail.com>
Date: Wed, 29 Nov 2017 14:40:07 -0800
Message-ID: <CAMdAHv-iiZ5ScQCj1OZZs6C3FZFaRZbiXbm6--ktN3KZz7b4Ag@mail.gmail.com>
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
To: huubatwork@gmail.com
Cc: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Greg Mirsky <gregimirsky@gmail.com>,  "ietf@ietf.org" <ietf@ietf.org>, "Ronald P. Bonica" <rbonica@juniper.net>,  "lime-chairs@ietf.org" <lime-chairs@ietf.org>, The IESG <iesg@ietf.org>,  "Benoit Claise (bclaise)" <bclaise@cisco.com>, "lime@ietf.org" <lime@ietf.org>, Qin Wu <bill.wu@huawei.com>,  "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
Content-Type: multipart/alternative; boundary="001a113e20b6488d35055f26d129"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fdSa3Mvc6nZQ718tcytlFnPy3s8>
X-Mailman-Approved-At: Thu, 30 Nov 2017 14:33:11 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 22:40:12 -0000

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

I have been out of IETF for a while but still receives LIME WG emails.

As the original author of the connectionless draft I deliberately avoided
making any comments as I do not have adequate time to do a good job.

However, I have been reading, with great respect, the comments Greg Mirsky
was making to make these drafts better both technically and editorially. I
want to extend a well deserved thank you to Greg. Thank You Greg.

Also I do not agree with Carlos comments on Hubbs observations, i.e. Oh
Draft is in IETF editors queue and it is too late. May be time to pull it
out from the queue or create errata if the changes are significant enough.

If either of these happens I do like to suggest two things

1. Appoint an editor who can shepherd edits and presentation aspects of the
draft
2. Provide adequate time and be transparent to share with the WG on what is
agreed or appoint a technical panel




On Wed, Nov 29, 2017 at 12:39 PM, Huub van Helvoort <huubatwork@gmail.com>
wrote:

> Hello Carlos,
>
> Thank you for the additional information.
>
> As I mentioned I already looked at version 18 because that was mentioned
> in Gregs response.
>
> I have understood that this draft was discussed in Singapore.
> Unfortunately the agreed resolution was not reported on the list.
> That is why I missed (part of) the discussion.
>
> I will have no further comments.
>
> Best regards, Huub.
>
> -----------
>
> Additionally, please see https://www.ietf.org/
> rfcdiff?url1=3Ddraft-ietf-lime-yang-connectionless-oam-17&
> url2=3Ddraft-ietf-lime-yang-connectionless-oam-18, which shows the change=
s
> relevant to that specific comment.
>
> I believe the authors are using text suggested by Greg.
>
> Like Benoit said, the document is approved and in the RFC Editor queue:
> https://mailarchive.ietf.org/arch/msg/lime/qyhKwFkE4VB9HA0S04tOWPDFK9Q
>
> Best,
>
> =E2=80=94
> Carlos Pignataro, carlos@cisco.com
>
> *=E2=80=9CSometimes I use big words that I do not fully understand, to ma=
ke myself
> sound more photosynthesis."*
>
> On Nov 28, 2017, at 5:21 AM, Huub van Helvoort <huubatwork@gmail.com>
> wrote:
>
> Hello Benoit,
>
> You reply:
>
> For your information, the document is now in the RFC editor queue, ready
> to be published.
> https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/
>
> I had not seen any response from the authors to the email from Greg
> (I checked the archive) so I assumed that the issue was still being
> discussed.
> Other on-line comments were addressed by the authors.
>
> I also checked for updates to version 18, but did not find any, so I
> don't know how the issue has been resolved.
>
> So now I have to wait until the RFC is published.
>
> Regards, Huub.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Hello Greg,
>
> I agree with you that the current (version 18) text in section 3.3 is ver=
y
> confusing.
>
> Authors:
>
> If I look at the definition of TP in section 2.2 I think a TP is similar
> to a maintenance point as defined for Ethernet. Am I correct?
>
> I don't understand why there are TPs with no neighboring TPs,
> where will their initiated OAM test be sent? Or where are OAM
> tests they react to initiated?
>
> It is IMHO also possible that there are TPs with a neighboring
> TP before AND a neighboring TP after the current TP.
>
> Please explain.
>
> Regards, Huub.
>
> ---------
>
> Dear All,
> I was under impression that that question of oam-neighboring-tps has been
> discussed and since authors couldn't produce technical rationale for this
> object we've agreed that it will be removed altogether from the grouping
> connectionless-oam-tps. But authors just changed name from level to
> position but had missed to synchronize descriptions in the model and in
> section 3.3. The later still refers to vertical layers:
>
>                      "List of related neighboring test points in adjacent
>                      layers up and down the stack for the same interface
>                      that are related to the current test point.";
>
> while the model insists that it is peering relationship:
>
>         description
>           "The relative position
>            of neighboring test point
>            corresponding to the current
>            test point. Level 0 indicates no neighboring
>            test points placed before or after the current
>
>            test point in the same layer.-1 means there is
>            a neighboring test point placed before the current
>            test point in the same layer and +1 means there is
>            a neighboring test point placed after the current
>            test point in same layer.";
>
> So, what is it? Perhaps it is time to remove list oam-neighboring-tps
> altogether also because having it s fixed size list is plain wrong. (Sorr=
y
> for being so blunt but I commented too many times on the same to no avail
> from the authors).
>
> Regards,
> Greg
>
>
> --
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Always remember that you are unique...just like everyone else...
>
>
> _______________________________________________
> Lime mailing list
> Lime@ietf.org
> https://www.ietf.org/mailman/listinfo/lime
>
>

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

<div dir=3D"ltr">I have been out of IETF for a while but still receives LIM=
E WG emails.<div><br></div><div>As the original author of the connectionles=
s draft I deliberately avoided making any comments as I do not have adequat=
e time to do a good job.</div><div><br></div><div>However, I have been read=
ing, with great respect, the comments Greg Mirsky was making to make these =
drafts better both technically and editorially. I want to extend a well des=
erved thank you to Greg. Thank You Greg.</div><div><br></div><div>Also I do=
 not agree with Carlos comments on Hubbs observations, i.e. Oh Draft is in =
IETF editors queue and it is too late. May be time to pull it out from the =
queue or create errata if the changes are significant enough.</div><div><br=
></div><div>If either of these happens I do like to suggest two things</div=
><div><br></div><div>1. Appoint an editor who can shepherd edits and presen=
tation aspects of the draft</div><div>2. Provide adequate time and be trans=
parent to share with the WG on what is agreed or appoint a technical panel<=
/div><div><br></div><div><br></div><div><br></div></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Wed, Nov 29, 2017 at 12:39 PM, Hu=
ub van Helvoort <span dir=3D"ltr">&lt;<a href=3D"mailto:huubatwork@gmail.co=
m" target=3D"_blank">huubatwork@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">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"m_-509113956322476388moz-cite-prefix">Hello Carlos,<br>
      <br>
      Thank you for the additional information.<br>
      <br>
      As I mentioned I already looked at version 18 because that was
      mentioned<br>
      in Gregs response.<br>
      <br>
      I have understood that this draft was discussed in Singapore.<br>
      Unfortunately the agreed resolution was not reported on the list.<br>
      That is why I missed (part of) the discussion.<br>
      <br>
      I will have no further comments.<br>
      <br>
      Best regards, Huub.<br>
      <br>
      -----------<br>
    </div><div><div class=3D"h5">
    <blockquote type=3D"cite">
     =20
      Additionally, please see=C2=A0<a href=3D"https://www.ietf.org/rfcdiff=
?url1=3Ddraft-ietf-lime-yang-connectionless-oam-17&amp;url2=3Ddraft-ietf-li=
me-yang-connectionless-oam-18" target=3D"_blank">https://www.ietf.org/<wbr>=
rfcdiff?url1=3Ddraft-ietf-lime-<wbr>yang-connectionless-oam-17&amp;<wbr>url=
2=3Ddraft-ietf-lime-yang-<wbr>connectionless-oam-18</a>,
      which shows the changes relevant to that specific comment.
      <div><br>
      </div>
      <div>I believe the authors are using text suggested by
        Greg.</div>
      <div><br>
      </div>
      <div>Like Benoit said, the document is approved and in
        the RFC Editor queue:</div>
      <div><a href=3D"https://mailarchive.ietf.org/arch/msg/lime/qyhKwFkE4V=
B9HA0S04tOWPDFK9Q" target=3D"_blank">https://mailarchive.ietf.org/<wbr>arch=
/msg/lime/<wbr>qyhKwFkE4VB9HA0S04tOWPDFK9Q</a></div>
      <div><br>
      </div>
      <div>Best,</div>
      <div>=C2=A0<br>
        <div>
          <div style=3D"color:rgb(0,0,0);letter-spacing:normal;text-align:s=
tart;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0p=
x;word-wrap:break-word">
            =E2=80=94<br>
            Carlos Pignataro,=C2=A0<a href=3D"mailto:carlos@cisco.com" targ=
et=3D"_blank">carlos@cisco.com</a><br>
            <br>
            <i>=E2=80=9CSometimes I use big words that I do not fully
              understand, to make myself sound more photosynthesis.&quot;</=
i></div>
        </div>
        <div><br>
          <blockquote type=3D"cite">
            <div>On Nov 28, 2017, at 5:21 AM, Huub van Helvoort
              &lt;<a href=3D"mailto:huubatwork@gmail.com" target=3D"_blank"=
>huubatwork@gmail.com</a>&gt;
              wrote:</div>
            <br class=3D"m_-509113956322476388Apple-interchange-newline">
            <div>
              <div text=3D"#000000" bgcolor=3D"#FFFFFF">
                <div class=3D"m_-509113956322476388moz-cite-prefix">Hello B=
enoit,<br>
                  <br>
                  You reply:<br>
                </div>
                <blockquote type=3D"cite">
                  <div class=3D"m_-509113956322476388moz-cite-prefix">For y=
our information, the
                    document is now in the RFC editor queue, ready to be
                    published.<br>
                    <a class=3D"m_-509113956322476388moz-txt-link-freetext"=
 href=3D"https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionle=
ss-oam/" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/draft-ietf=
-lime-yang-<wbr>connectionless-oam/</a><br>
                  </div>
                </blockquote>
                I had not seen any response from the authors to the
                email from Greg<br>
                (I checked the archive) so I assumed that the issue was
                still being<br>
                discussed. <br>
                Other on-line comments were addressed by the authors.<br>
                <br>
                I also checked for updates to version 18, but did not
                find any, so I<br>
                don&#39;t know how the issue has been resolved.<br>
                <br>
                So now I have to wait until the RFC is published.<br>
                <br>
                Regards, Huub.<br>
                <br>
                =3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
                <br>
                <blockquote type=3D"cite">
                  <blockquote type=3D"cite">
                    <div class=3D"m_-509113956322476388moz-cite-prefix">Hel=
lo Greg,<br>
                      <br>
                      I agree with you that the current (version 18)
                      text in section 3.3 is very confusing.<br>
                      <br>
                      Authors:<br>
                      <br>
                      If I look at the definition of TP in section 2.2 I
                      think a TP is similar<br>
                      to a maintenance point as defined for Ethernet. Am
                      I correct?<br>
                      <br>
                      I don&#39;t understand why there are TPs with no
                      neighboring TPs,<br>
                      where will their initiated OAM test be sent? Or
                      where are OAM<br>
                      tests they react to initiated?<br>
                      <br>
                      It is IMHO also possible that there are TPs with a
                      neighboring <br>
                      TP before AND a neighboring TP after the current
                      TP.<br>
                      <br>
                      Please explain.<br>
                      <br>
                      Regards, Huub.<br>
                      <br>
                      ---------<br>
                      <br>
                    </div>
                    <blockquote type=3D"cite">
                      <div dir=3D"ltr">Dear All,
                        <div>I was under impression that that
                          question of=C2=A0<span style=3D"font-size:13.3333=
px">oam-neighboring-tps</span><span style=3D"font-size:13.3333px">=C2=A0has
                            been discussed and since authors couldn&#39;t
                            produce technical rationale for this object
                            we&#39;ve agreed that it will be removed
                            altogether from the=C2=A0</span><span style=3D"=
font-size:13.3333px">grouping
                            connectionless-oam-tps. But authors just
                            changed name from level to position but had
                            missed to synchronize descriptions in the
                            model and in section 3.3. The later still
                            refers to vertical layers:</span></div>
                        <div>
                          <pre class=3D"m_-509113956322476388gmail-newpage"=
 style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px">           =
          &quot;List of related neighboring test points in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.&quot;;
</pre>
                        </div>
                        <div>while the model insists that it is
                          peering relationship:</div>
                        <div>
                          <pre class=3D"m_-509113956322476388gmail-newpage"=
 style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px">        des=
cription
          &quot;The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current
</pre>
                        </div>
                        <div>
                          <pre class=3D"m_-509113956322476388gmail-newpage"=
 style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px">           =
test point in the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.&quot;;
</pre>
                        </div>
                        <div>So, what is it? Perhaps it is time
                          to remove list=C2=A0<span style=3D"font-size:13.3=
333px">oam-neighboring-tps
                            altogether also because having it s fixed
                            size list is plain wrong. (Sorry for being
                            so blunt but I commented too many times on
                            the same to no avail from the authors).</span><=
/div>
                        <div><span style=3D"font-size:13.3333px"><br>
                          </span></div>
                        <div><span style=3D"font-size:13.3333px">Regards,</=
span></div>
                        <div><span style=3D"font-size:13.3333px">Greg</span=
><br>
                        </div>
                      </div>
                    </blockquote>
                  </blockquote>
                </blockquote>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <pre class=3D"m_-509113956322476388moz-signature" cols=3D"72">--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D
Always remember that you are unique...just like everyone else...</pre>
  </div></div></div>


<br>______________________________<wbr>_________________<br>
Lime mailing list<br>
<a href=3D"mailto:Lime@ietf.org">Lime@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/lime" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/lime</a><br>
<br></blockquote></div><br></div>

--001a113e20b6488d35055f26d129--


From nobody Thu Nov 30 14:33:55 2017
Return-Path: <huubatwork@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 9FA15126BF6; Wed, 29 Nov 2017 12:38:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, 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 47FT5hyR3yOQ; Wed, 29 Nov 2017 12:38:50 -0800 (PST)
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 1E6381200CF; Wed, 29 Nov 2017 12:38:50 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id t8so8893531wmc.3; Wed, 29 Nov 2017 12:38:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=reply-to:subject:to:cc:references:from:message-id :disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=1De0CODwx//ZkqT+ARgriBaXv9oUj5qc8t56vGZzPK8=; b=HWcmILuuO7sLqUExuajQvhp6NJ9nzMRFBGpAx06ylLrPzNIIrKn/RHoUruWkRGDAeB pzpM7/UaohCOLCHa+XS103rSGvj5/ACpM2+PJh0OAJQHKjJR2LTg0hvPyah7EDgLUVpb sbYXtR0FEv7+I4qKyqpFMNYaEZMnnb5TfuBkDIt7gBOF+ImJ/odqipNC3m1LS/NWDEQQ 4b4BTuzLFfO3vVcPdbRQSxFwlhLEq+OZOGaO7/tCRGkDVyKp8sVFLQV9Xh9mnIbo3NK7 mMKt8riZbP/6v/Z1fWkX3xhr+QcKnjDcYeP1XddYKX4ZC/Ah04GSA9N7eM2VUHHhh+HC ZAQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:reply-to:subject:to:cc:references:from :message-id:disposition-notification-to:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=1De0CODwx//ZkqT+ARgriBaXv9oUj5qc8t56vGZzPK8=; b=ILVsvYH9sNJaadhjeU/ykEWxwzA62YeteUGl8ip6g6Cu/HnGSPNcuXuXri3TaC/V4x k3nXKpFKeKC8OoYwAw/eCdFz0IxTdWdWe/jlCMatWyQ4plWgMLbdb15bo0xxaaUuyi1M F2ERLiM/lUh8/5DBQ9tpYLaCgJwPOlHZWso1Qs/FQZl5wsr/SE+i+hX3GI7WSHs0ew6c Rs/dFaJjMngkHXymj5qjfAgzJJwge16nsLfOgbeEsjNr5d3zHXXu1KfAQOiWgRJyUd1G z2OgiFeExrraN9cKa8KvUoSAwJBtRFog7M5ZEf+6Blrrel0nRiRTFdE62QaWCFPQpqx0 WpSA==
X-Gm-Message-State: AJaThX6fWfiI3Rw7UhdHDVV15ODozYf3a96E41bFktTnYC/1+96wITw4 Azo3vgSO3Cck00HJFV+RhAb1VA==
X-Google-Smtp-Source: AGs4zMaW5UpuGzJ1s9LvX9uoJqcA61MfHj4jkieEhI+/P7TgLTqP1iSj+HHH5rJVWlUVdc5BbGdTGQ==
X-Received: by 10.80.219.69 with SMTP id b5mr9572464edl.218.1511987928053; Wed, 29 Nov 2017 12:38:48 -0800 (PST)
Received: from McAsterix.local (g77189.upc-g.chello.nl. [80.57.77.189]) by smtp.gmail.com with ESMTPSA id w13sm2187246edk.46.2017.11.29.12.38.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Nov 2017 12:38:47 -0800 (PST)
Reply-To: huubatwork@gmail.com
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: "Benoit Claise (bclaise)" <bclaise@cisco.com>, Greg Mirsky <gregimirsky@gmail.com>, Qin Wu <bill.wu@huawei.com>, The IESG <iesg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Ronald P. Bonica" <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com> <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com> <3b6c5ab3-ff5e-1d1a-313c-2dd7bdd0919d@gmail.com> <646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com>
From: Huub van Helvoort <huubatwork@gmail.com>
Message-ID: <1b527039-bf80-ead5-e341-c8cfeb24f855@gmail.com>
Date: Wed, 29 Nov 2017 21:39:22 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com>
Content-Type: text/html; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uysy2d_fnG_pntnXMI6qNoTUBwY>
X-Mailman-Approved-At: Thu, 30 Nov 2017 14:33:11 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Nov 2017 20:38:53 -0000

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hello Carlos,<br>
      <br>
      Thank you for the additional information.<br>
      <br>
      As I mentioned I already looked at version 18 because that was
      mentioned<br>
      in Gregs response.<br>
      <br>
      I have understood that this draft was discussed in Singapore.<br>
      Unfortunately the agreed resolution was not reported on the list.<br>
      That is why I missed (part of) the discussion.<br>
      <br>
      I will have no further comments.<br>
      <br>
      Best regards, Huub.<br>
      <br>
      -----------<br>
    </div>
    <blockquote type="cite"
      cite="mid:646B9160-2BBF-4546-9163-D6504A47C7D7@cisco.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      Additionally, please see <a
href="https://www.ietf.org/rfcdiff?url1=draft-ietf-lime-yang-connectionless-oam-17&amp;url2=draft-ietf-lime-yang-connectionless-oam-18"
        class="" moz-do-not-send="true">https://www.ietf.org/rfcdiff?url1=draft-ietf-lime-yang-connectionless-oam-17&amp;url2=draft-ietf-lime-yang-connectionless-oam-18</a>,
      which shows the changes relevant to that specific comment.
      <div class=""><br class="">
      </div>
      <div class="">I believe the authors are using text suggested by
        Greg.</div>
      <div class=""><br class="">
      </div>
      <div class="">Like Benoit said, the document is approved and in
        the RFC Editor queue:</div>
      <div class=""><a
href="https://mailarchive.ietf.org/arch/msg/lime/qyhKwFkE4VB9HA0S04tOWPDFK9Q"
          class="" moz-do-not-send="true">https://mailarchive.ietf.org/arch/msg/lime/qyhKwFkE4VB9HA0S04tOWPDFK9Q</a></div>
      <div class=""><br class="">
      </div>
      <div class="">Best,</div>
      <div class=""> <br class="">
        <div class="">
          <div style="color: rgb(0, 0, 0); letter-spacing: normal;
            text-align: start; text-indent: 0px; text-transform: none;
            white-space: normal; word-spacing: 0px;
            -webkit-text-stroke-width: 0px; word-wrap: break-word;
            -webkit-nbsp-mode: space; -webkit-line-break:
            after-white-space;" class="">
            —<br class="">
            Carlos Pignataro, <a href="mailto:carlos@cisco.com" class=""
              moz-do-not-send="true">carlos@cisco.com</a><br class="">
            <br class="">
            <i class="">“Sometimes I use big words that I do not fully
              understand, to make myself sound more photosynthesis."</i></div>
        </div>
        <div><br class="">
          <blockquote type="cite" class="">
            <div class="">On Nov 28, 2017, at 5:21 AM, Huub van Helvoort
              &lt;<a href="mailto:huubatwork@gmail.com" class=""
                moz-do-not-send="true">huubatwork@gmail.com</a>&gt;
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div text="#000000" bgcolor="#FFFFFF" class="">
                <div class="moz-cite-prefix">Hello Benoit,<br class="">
                  <br class="">
                  You reply:<br class="">
                </div>
                <blockquote type="cite"
                  cite="mid:0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com"
                  class="">
                  <div class="moz-cite-prefix">For your information, the
                    document is now in the RFC editor queue, ready to be
                    published.<br class="">
                    <a class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/"
                      moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/</a><br
                      class="">
                  </div>
                </blockquote>
                I had not seen any response from the authors to the
                email from Greg<br class="">
                (I checked the archive) so I assumed that the issue was
                still being<br class="">
                discussed. <br class="">
                Other on-line comments were addressed by the authors.<br
                  class="">
                <br class="">
                I also checked for updates to version 18, but did not
                find any, so I<br class="">
                don't know how the issue has been resolved.<br class="">
                <br class="">
                So now I have to wait until the RFC is published.<br
                  class="">
                <br class="">
                Regards, Huub.<br class="">
                <br class="">
                =========<br class="">
                <br class="">
                <blockquote type="cite"
                  cite="mid:0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com"
                  class="">
                  <blockquote type="cite"
                    cite="mid:499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com"
                    class="">
                    <div class="moz-cite-prefix">Hello Greg,<br class="">
                      <br class="">
                      I agree with you that the current (version 18)
                      text in section 3.3 is very confusing.<br class="">
                      <br class="">
                      Authors:<br class="">
                      <br class="">
                      If I look at the definition of TP in section 2.2 I
                      think a TP is similar<br class="">
                      to a maintenance point as defined for Ethernet. Am
                      I correct?<br class="">
                      <br class="">
                      I don't understand why there are TPs with no
                      neighboring TPs,<br class="">
                      where will their initiated OAM test be sent? Or
                      where are OAM<br class="">
                      tests they react to initiated?<br class="">
                      <br class="">
                      It is IMHO also possible that there are TPs with a
                      neighboring <br class="">
                      TP before AND a neighboring TP after the current
                      TP.<br class="">
                      <br class="">
                      Please explain.<br class="">
                      <br class="">
                      Regards, Huub.<br class="">
                      <br class="">
                      ---------<br class="">
                      <br class="">
                    </div>
                    <blockquote type="cite"
cite="mid:CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com"
                      class="">
                      <div dir="ltr" class="">Dear All,
                        <div class="">I was under impression that that
                          question of <span style="font-size:
                            13.3333px;" class="">oam-neighboring-tps</span><span
                            style="font-size: 13.3333px;" class=""> has
                            been discussed and since authors couldn't
                            produce technical rationale for this object
                            we've agreed that it will be removed
                            altogether from the </span><span
                            style="font-size: 13.3333px;" class="">grouping
                            connectionless-oam-tps. But authors just
                            changed name from level to position but had
                            missed to synchronize descriptions in the
                            model and in section 3.3. The later still
                            refers to vertical layers:</span></div>
                        <div class="">
                          <pre class="gmail-newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px;">                     "List of related neighboring test points in adjacent
                     layers up and down the stack for the same interface
                     that are related to the current test point.";
</pre>
                        </div>
                        <div class="">while the model insists that it is
                          peering relationship:</div>
                        <div class="">
                          <pre class="gmail-newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px;">        description
          "The relative position
           of neighboring test point
           corresponding to the current
           test point. Level 0 indicates no neighboring
           test points placed before or after the current
</pre>
                        </div>
                        <div class="">
                          <pre class="gmail-newpage" style="font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px;">           test point in the same layer.-1 means there is
           a neighboring test point placed before the current
           test point in the same layer and +1 means there is
           a neighboring test point placed after the current
           test point in same layer.";
</pre>
                        </div>
                        <div class="">So, what is it? Perhaps it is time
                          to remove list <span style="font-size:
                            13.3333px;" class="">oam-neighboring-tps
                            altogether also because having it s fixed
                            size list is plain wrong. (Sorry for being
                            so blunt but I commented too many times on
                            the same to no avail from the authors).</span></div>
                        <div class=""><span style="font-size:
                            13.3333px;" class=""><br class="">
                          </span></div>
                        <div class=""><span style="font-size:
                            13.3333px;" class="">Regards,</span></div>
                        <div class=""><span style="font-size:
                            13.3333px;" class="">Greg</span><br class="">
                        </div>
                      </div>
                    </blockquote>
                  </blockquote>
                </blockquote>
              </div>
            </div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <pre class="moz-signature" cols="72">-- 
================================================================
Always remember that you are unique...just like everyone else...</pre>
  </body>
</html>


From nobody Thu Nov 30 14:48:04 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 B078D129511; Thu, 30 Nov 2017 14:47:56 -0800 (PST)
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: spring@ietf.org, draft-ietf-spring-ipv6-use-cases.all@ietf.org, ietf@ietf.org
Subject: Genart telechat review of draft-ietf-spring-ipv6-use-cases-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151208207669.11941.1774085292828356059@ietfa.amsl.com>
Date: Thu, 30 Nov 2017 14:47:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0GkFd7O3xQhc9s5awBNHpZl-IYQ>
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, 30 Nov 2017 22:47:57 -0000

Reviewer: Stewart Bryant
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 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-spring-ipv6-use-cases-11
Reviewer: Stewart Bryant
Review Date: 2017-11-30
IETF LC End Date: 2017-05-04
IESG Telechat date: 2017-12-14

Summary: The document has clearly been improved by the removal of the MPLS
text. It is now quite a short draft. However a number of major issues appear to
remain.

Major issues:

The homenet section calls up an enterprise related draft, but none of the
homenet drafts. As I understand it homenet also supports source-destination
routeing. Is the use case really the home environment? If so there really needs
to be text explaining why the apparently competing solution is needed. If the
use case is the Enterprise environment perhaps the section name should be
changed.

The authors did not address my question from the previous review concerning how
the necessary routing information is provided given that the homenet WG are
using a distance vector routing protocol.

There seems to be an outstanding comment concerning the text

  "Information included in the SPRING header, whether imposed by the
   end-host itself, a customer edge router, or within the access network
   of the ISP, may be of use at the far ends of the data communication
   as well.  For example, an application running on an end-host with
   application-support in a data center can utilize the SPRING header as
   a channel to include information that affects its treatment within
   the data center itself, allowing for application-level steering and
   load-balancing without relying upon implicit application
   classification techniques at the data-center edge.  Further, as more
   and more application traffic is encrypted, the ability to extract
   (and include in the SPRING header) just enough information to enable
   the network and data center to load-balance and steer traffic
   appropriately becomes more and more important."

SB> However there is a trust issue with sharing information in this way
SB> and it was a breach of trust that caused the source routing feature
SB> to be removed from IPv6 in the first place.
SB>
SB> For this to be a valid use case I think you need to address the
SB> trust and security issues to explain why they are no longer relevant
SB> or make it clear that they need to be addressed.

I don't thing the following question was addressed from my previous review:

   The need to setup a source-based path, going through some specific
   middle/intermediate points in the network may be related to different
   requirements:

SB> There needs to be some discussion on the trust model here and
SB> attack vectors associated with this proposal.

This remains from my previous review:

An ingress node steers a packet through
   a controlled set of instructions, called segments, by prepending the
   packet with SPRING header.

SB> That is what I think it should do, but that is not the design direction
SB> of the current IPv6 proposal. The design of record modifies the
SB> IPv6 header.

As I understand the design the it does not prepend (i.e. use an encapsulation
or a tunnel) it modifies the IPv6 header and then inserts a block of data
between the header and the transport header.

I do not recall seeing an answer to this question from the previous review:

   In an environment, where each single cache system can be uniquely
   identified by its own IPv6 address, a list containing a sequence of
   the caches in a hierarchy can be built.  At each node (cache) in the
   list, the presence of the requested content if checked.  If the
   requested content is found at the cache (cache hits scenario) the
   sequence ends, even if there are more nodes in the list; otherwise
   next element in the list (next node/cache) is examined.

SB> This needs some discussion on the alternative approaches:
SB> for example service function chaining and an ICN overlay.

Minor issues: None

Nits/editorial comments: None



From nobody Thu Nov 30 15:13:59 2017
Return-Path: <kaduk@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 EDD321294F7 for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 15:13:57 -0800 (PST)
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 a7QEv9E-aqKK for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 15:13:56 -0800 (PST)
Received: from dmz-mailsec-scanner-3.mit.edu (dmz-mailsec-scanner-3.mit.edu [18.9.25.14]) (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 033DB124E15 for <ietf@ietf.org>; Thu, 30 Nov 2017 15:13:54 -0800 (PST)
X-AuditID: 1209190e-003ff7000000110b-54-5a2090b01bfa
Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id AE.C7.04363.0B0902A5; Thu, 30 Nov 2017 18:13:53 -0500 (EST)
Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id vAUNDm35023254; Thu, 30 Nov 2017 18:13:50 -0500
Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id vAUNDjSA004486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 30 Nov 2017 18:13:47 -0500
Date: Thu, 30 Nov 2017 17:13:45 -0600
From: Benjamin Kaduk <kaduk@mit.edu>
To: "KELLY, MICHAEL B CTR USAF AFMC 412 TENG/ENI" <michael.kelly.49.ctr@us.af.mil>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Questions about RFC 7252
Message-ID: <20171130231344.GL39477@kduck.kaduk.org>
References: <C100D0AB51422F48B5655B0FD58BB204281F5F@52ZHTX-D05-05E.area52.afnoapps.usaf.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C100D0AB51422F48B5655B0FD58BB204281F5F@52ZHTX-D05-05E.area52.afnoapps.usaf.mil>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLIsWRmVeSWpSXmKPExsUixG6nrrtxgkKUwY15bBbPNs5nsbj7YSWz A5PHkiU/mTz2bm9hDGCK4rJJSc3JLEst0rdL4MrYtXgPY8FLlooDU96zNjB+Yu5i5OSQEDCR uDhzMlsXIxeHkMBiJol9D7cyQzgbGSXaN19mhXCuMkmc2/+FCaSFRUBVYvuZjWDtbAIqEg3d l8FsEYEgiWf79oLVMAsoSxz9eoMdxBYGql/2ficbiM0LtG7nzfksILaQQIzEjj/H2CHighIn Zz5hgejVkrjx7yXQHA4gW1pi+T8OkDCnQKzE3Bd/wcaIAo3f23eIfQKjwCwk3bOQdM9C6F7A yLyKUTYlt0o3NzEzpzg1Wbc4OTEvL7VI11gvN7NELzWldBMjKEw5Jfl2ME5q8D7EKMDBqMTD ayGoECXEmlhWXJl7iFGSg0lJlPdSGFCILyk/pTIjsTgjvqg0J7X4EKMEB7OSCK9xKFCONyWx siq1KB8mJc3BoiTOuy1oV6SQQHpiSWp2ampBahFMVoaDQ0mCN7ofqFGwKDU9tSItM6cEIc3E wQkynAdoeARIDW9xQWJucWY6RP4UozHHjYfX/zBxPJv5uoFZiCUvPy9VSpy3AaRUAKQ0ozQP bhoo1Uhk7695xSgO9JwwLz8w8QjxANMU3LxXQKuYgFZlLpcHWVWSiJCSamBsCfuSmBP2aN82 vT7uZ5tOrKy3XPTb3zDkVlrVi1gVpsxF14IOHQtSuJmW2n2oicch9rWvKM//5I0fY6cefpNf t+rMJLkFR/dUuymFveriqfJRNX648tpL7YRzu1atLY5iiCiazrml7L2Io73Dy+SD65d5rSps ebdoQ/rWjn3KzafclZkrrh1TYinOSDTUYi4qTgQALAi5mRADAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yDza-KCk4LuIhk7a8zK9_rdr6aE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 30 Nov 2017 23:13:58 -0000

Hi Bryan,

On Tue, Nov 28, 2017 at 05:53:06PM +0000, KELLY, MICHAEL B CTR USAF AFMC 412 TENG/ENI wrote:
> Greetings,
> 
> I am searching for a place to ask questions about RFC 7252, The Constrained Application Protocol (CoAP).
> If this is sufficient information for you to delete this email or take some action please stop here.

RFC 7252 is a product of the Constrained RESTful Environments (core)
working group (https://datatracker.ietf.org/wg/core/about/).  Its
mailing list, core@ietf.org, is still active, so if you do not get
any replies to this posting, that would be a good place to try.

-Ben


From nobody Thu Nov 30 18:48:41 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 5A332127058 for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 18:48:40 -0800 (PST)
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 O0eAwEm9fOPR for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 18:48:38 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 99150126B72 for <ietf@ietf.org>; Thu, 30 Nov 2017 18:48:38 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id j28so4004943pfk.8 for <ietf@ietf.org>; Thu, 30 Nov 2017 18:48:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=d3mCaojRWvmoIg24BETJAdCnvQZ9pKlDOd7YURxJDTk=; b=YclpCnO9L1iRt62hHYVXts8SiW6qWE3zjkzq5XTDpgfLn3TquW4R/SP/+LSdkc4LOh Gvo0mVmu9BGPnve57ojDw9ZzK0C/F9Qoe6cPNvs079rxfalNl7nT3qwomQU1eEHCmiub AoIeOGLXe2NlWIh07xka75b3yC/tEquQ84XKEW9Q5Q33A70cysJLEykGloNNw8qLERG1 TuDFo6DYGwyN823eXpYnENAeFwhyX2naXbZWDS55LUgXMTr+5qLOLU5FCf4bOlggVAg4 EVGyaeg60LFFpJrLV9xv7+zugoRmY+cwn4kyF6M6ihBrxPRZBXRdEFC5EYlAyBJANadl WWCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=d3mCaojRWvmoIg24BETJAdCnvQZ9pKlDOd7YURxJDTk=; b=Vkwa3ib4e+T7ioDQPqzCGyU8c4rbuAn26GeclC+hKoW6jQcdUPAgbG76Ps/kwmR2Bz motBdRKXonAEgsS82M9gHL8aYYrIYHhfXgFc9rAOekf2pxvtNURGXgRKETFqDDp0/wpq f2wHSYRWuApOSX2g76FBZ6WZYMpsAK9ZBYPCjqo/ETQQDIgpDF/YjxAei1Nd9zw21/qt jGgfHMJMJ1gxpZnKCrjjg9C35pm0vR0d3sYXjGEHkcu7H0WJkjCec0Pm5c8IoCaGvyEB BoRgDZxKxeotNXKRH8/FBtmQpqiD/U9CSVWAH/YyLRzarFrSoc4M74Gj2rJC3q94thJR Watg==
X-Gm-Message-State: AJaThX7J4bbW0bL7jEbH80nMyIc8GwX2cpOPVU/JqnJQH0k40DD/97g+ EszyMLxzRoU8PuvnQ6ttLQjuOA==
X-Google-Smtp-Source: AGs4zMah7U2APQJc4+iWTQr8UrkooNpCFhu5TLPUa6OZzzwFajKoF/GSvTJC8uBL2kaaJtN0szJIkQ==
X-Received: by 10.99.61.66 with SMTP id k63mr4391090pga.421.1512096517827; Thu, 30 Nov 2017 18:48:37 -0800 (PST)
Received: from ?IPv6:2406:e007:6f17:1:28cc:dc4c:9703:6781? ([2406:e007:6f17:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id w73sm9286285pfd.86.2017.11.30.18.48.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Nov 2017 18:48:36 -0800 (PST)
Subject: Re: IAOC role
To: Michael Richardson <mcr@sandelman.ca>
Cc: IETF discussion list <ietf@ietf.org>
References: <514edc7c-43ad-44d9-2488-17261381cd84@gmail.com> <27314.1512060318@obiwan.sandelman.ca>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2c74ac11-fdc4-4899-eb8f-414a9155affd@gmail.com>
Date: Fri, 1 Dec 2017 15:48:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <27314.1512060318@obiwan.sandelman.ca>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_ZDyzmjoPkZGCHijue6AAB-5Ti4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Dec 2017 02:48:40 -0000

On 01/12/2017 05:45, Michael Richardson wrote:
> 
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> The IASA 2.0 effort is discussing the *future* of IASA and the
>> IAOC. That isn't my concern here, and there's a mailing list for
>> it (https://www.ietf.org/mailman/listinfo/iasa20).
> 
>> What I'm concerned about is that fact that a couple of *current*
>> IAOC slots are up for appointment shortly (by NomCom and IESG
>> respectively), with several fine candidates in each case.
> 
>> All I'm asking is that in their considerations, the appointing
>> bodies keep in mind the definition of the IAOC's role:
> 
>> The IAOC's role is to provide appropriate direction to the IAD, to 
>> review the IAD's regular reports, and to oversee IASA functions to
> 
> 1) do you believe that IAOC cmte have unreasonably expanded their
> scope?
> 
> 2) despite this definition, a bunch of new things have shown up for
> the IAOC, and that now includes: * IETF Trust supervision

Well, IETF Trust *membership*, not supervision. As an editor of RFC 4371,
I'm unlikely to forget that. But like the original IAOC role, it was
clearly intended to be a "Board" level of activity, not an executive
function. That's all I'm saying, and all I want to say on this list.

    Brian

> * Tools cmte: managing contractors * something else I forgot.
> 
> Reading the reports from the IAD is still a major part; but some
> things have devolved elsewhere.  Also the IAD doesn't necessarily
> have the right skill set to figure out technical issues that come
> from contractors. Also, financial repors, while puck-handled by the
> IAD have been provided by an ISOC resource until September, and now
> are done by AMSL under contract.
> 
> So your advice that to pay attention to the IAD oversight misses the
> other kinds of oversight that now also occurs.
> 
> {me: non-voting member of finance subcmte, nominee for IESG member. 
> Note: I've told the IESG that I won't be IAOC chair, and to pick
> someone else if they need an IAOC chair}
> 
> -- ]               Never tell me the odds!                 | ipv6
> mesh networks [ ]   Michael Richardson, Sandelman Software Works
> | network architect  [ ]     mcr@sandelman.ca
> http://www.sandelman.ca/        |   ruby on rails    [
> 


From nobody Thu Nov 30 21:53:15 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 182FF127866 for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 21:53:13 -0800 (PST)
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 RqffV_wfHRB5 for <ietf@ietfa.amsl.com>; Thu, 30 Nov 2017 21:53:10 -0800 (PST)
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 5C6BA1243F6 for <ietf@ietf.org>; Thu, 30 Nov 2017 21:53:10 -0800 (PST)
Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.21/8.16.0.21) with SMTP id vB15nKTW080665 for <ietf@ietf.org>; Fri, 1 Dec 2017 00:53:09 -0500
Received: from e11.ny.us.ibm.com (e11.ny.us.ibm.com [129.33.205.201]) by mx0b-001b2d01.pphosted.com with ESMTP id 2ejyxfc7qh-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 01 Dec 2017 00:53:09 -0500
Received: from localhost by e11.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, 1 Dec 2017 00:53:08 -0500
Received: from b01cxnp23034.gho.pok.ibm.com (9.57.198.29) by e11.ny.us.ibm.com (146.89.104.198) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 1 Dec 2017 00:53:06 -0500
Received: from b01ledav003.gho.pok.ibm.com (b01ledav003.gho.pok.ibm.com [9.57.199.108]) by b01cxnp23034.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id vB15r6oZ46071858 for <ietf@ietf.org>; Fri, 1 Dec 2017 05:53:06 GMT
Received: from b01ledav003.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 21A73B2058 for <ietf@ietf.org>; Fri,  1 Dec 2017 00:50:14 -0500 (EST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav003.gho.pok.ibm.com (Postfix) with ESMTPS id 0B531B2050 for <ietf@ietf.org>; Fri,  1 Dec 2017 00:50:14 -0500 (EST)
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 vB15r5bS008517 for <ietf@ietf.org>; Fri, 1 Dec 2017 00:53:05 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id vB15r4QS008455 for ietf@ietf.org; Fri, 1 Dec 2017 00:53:04 -0500
From: narten@us.ibm.com
Date: Fri, 01 Dec 2017 00:53:04 -0500
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: 17120105-2213-0000-0000-00000243FF3E
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00008132; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000242; SDB=6.00953720; UDB=6.00481917; IPR=6.00733795;  BA=6.00005724; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00018285; XFM=3.00000015; UTC=2017-12-01 05:53:07
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17120105-2214-0000-0000-00005850D215
Message-Id: <201712010553.vB15r4QS008455@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-12-01_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=89 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-1709140000 definitions=main-1712010070
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H2esyb6GeMdCJYNyGdZ7JCFn0kQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Dec 2017 05:53:13 -0000

Total of 101 messages in the last 7 days.
 
script run at: Fri Dec  1 00:53:03 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.92% |    8 |  7.47% |    87621 | mfidelman@meetinghouse.net
  4.95% |    5 |  7.69% |    90180 | gonzalo.camarillo@ericsson.com
  5.94% |    6 |  5.37% |    63006 | brian.e.carpenter@gmail.com
  3.96% |    4 |  3.57% |    41915 | mstjohns@comcast.net
  2.97% |    3 |  4.52% |    52979 | huubatwork@gmail.com
  3.96% |    4 |  3.21% |    37695 | olejacobsen@me.com
  1.98% |    2 |  4.77% |    55935 | cpignata@cisco.com
  2.97% |    3 |  2.32% |    27179 | sean@sn3rd.com
  2.97% |    3 |  2.31% |    27145 | john-ietf@jck.com
  1.98% |    2 |  2.51% |    29404 | linda.dunbar@huawei.com
  0.99% |    1 |  3.27% |    38411 | bill.wu@huawei.com
  1.98% |    2 |  1.99% |    23339 | sob@sobco.com
  1.98% |    2 |  1.69% |    19804 | kathleen.moriarty.ietf@gmail.com
  1.98% |    2 |  1.65% |    19343 | jmh@joelhalpern.com
  1.98% |    2 |  1.64% |    19189 | lberger@labn.net
  0.99% |    1 |  2.59% |    30375 | gregimirsky@gmail.com
  1.98% |    2 |  1.57% |    18451 | ddp@electric-loft.org
  1.98% |    2 |  1.48% |    17393 | mcr+ietf@sandelman.ca
  1.98% |    2 |  1.48% |    17360 | chair@ietf.org
  0.99% |    1 |  2.46% |    28810 | tsenevir@gmail.com
  1.98% |    2 |  1.45% |    16968 | stewart.bryant@gmail.com
  1.98% |    2 |  1.38% |    16241 | jclarke@cisco.com
  1.98% |    2 |  1.34% |    15719 | ynir.ietf@gmail.com
  1.98% |    2 |  1.29% |    15156 | jiangsheng@huawei.com
  1.98% |    2 |  1.21% |    14205 | randy@psg.com
  0.99% |    1 |  1.48% |    17366 | bclaise@cisco.com
  0.99% |    1 |  1.29% |    15110 | dbg@scs.stanford.edu
  0.99% |    1 |  1.15% |    13441 | spencerdawkins.ietf@gmail.com
  0.99% |    1 |  1.14% |    13321 | ogud@ogud.com
  0.99% |    1 |  1.12% |    13157 | kwatsen@juniper.net
  0.99% |    1 |  1.11% |    13065 | ocl@gih.com
  0.99% |    1 |  1.09% |    12774 | ekr@rtfm.com
  0.99% |    1 |  1.08% |    12722 | cdel@firsthand.net
  0.99% |    1 |  1.05% |    12296 | rrahman@cisco.com
  0.99% |    1 |  1.04% |    12176 | mellon@fugue.com
  0.99% |    1 |  1.00% |    11699 | narten@us.ibm.com
  0.99% |    1 |  0.93% |    10954 | worley@ariadne.com
  0.99% |    1 |  0.91% |    10653 | martin.thomson@gmail.com
  0.99% |    1 |  0.89% |    10491 | lear@cisco.com
  0.99% |    1 |  0.87% |    10235 | glen@amsl.com
  0.99% |    1 |  0.82% |     9645 | mcr@sandelman.ca
  0.99% |    1 |  0.82% |     9598 | mnot@mnot.net
  0.99% |    1 |  0.81% |     9512 | sbanks@encrypted.net
  0.99% |    1 |  0.81% |     9505 | linuxwolf+ietf@outer-planes.net
  0.99% |    1 |  0.81% |     9449 | kaduk@mit.edu
  0.99% |    1 |  0.80% |     9436 | stephen.farrell@cs.tcd.ie
  0.99% |    1 |  0.80% |     9399 | aaron.falk@gmail.com
  0.99% |    1 |  0.80% |     9368 | warren@kumari.net
  0.99% |    1 |  0.77% |     8988 | michael.kelly.49.ctr@us.af.mil
  0.99% |    1 |  0.76% |     8908 | gorry@erg.abdn.ac.uk
  0.99% |    1 |  0.76% |     8899 | cabo@tzi.org
  0.99% |    1 |  0.73% |     8522 | johnl@iecc.com
  0.99% |    1 |  0.71% |     8383 | tnadeau@lucidvision.com
  0.99% |    1 |  0.64% |     7518 | dburk@burkov.aha.ru
  0.99% |    1 |  0.60% |     7031 | johnl@taugh.com
  0.99% |    1 |  0.58% |     6775 | ron.even.tlv@gmail.com
  0.99% |    1 |  0.54% |     6281 | rifaat.ietf@gmail.com
  0.99% |    1 |  0.53% |     6248 | adam.w.montville@gmail.com
  0.99% |    1 |  0.53% |     6215 | joelja@bogus.com
--------+------+--------+----------+------------------------
100.00% |  101 |100.00% |  1172963 | Total


From nobody Thu Nov 30 22:56:25 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 93DBD127863; Thu, 30 Nov 2017 22:56:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jouni.nospam@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-tokbind-protocol.all@ietf.org, unbearable@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-tokbind-protocol-16
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151211137956.11945.3926284036867947678@ietfa.amsl.com>
Date: Thu, 30 Nov 2017 22:56:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A8dm3SMpp2Dmqn8oVJhpbBF_xow>
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, 01 Dec 2017 06:56:20 -0000

Reviewer: Jouni Korhonen
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-tokbind-protocol-??
Reviewer: Jouni Korhonen
Review Date: 2017-11-30
IETF LC End Date: 2017-11-27
IESG Telechat date: Not scheduled for a telechat

Summary: Ready to go. I am not an expert on this field thus my review was
rather superficial. Reading the document through did not raise any alarms.

Major issues: None spotted.

Minor issues: None.

Nits/editorial comments:  IDnist result was good (outdated references are
non-issues).


