
From nobody Wed Jul  5 03:56:07 2017
Return-Path: <sankalp.nitt@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03B681328FF for <irtf-discuss@ietfa.amsl.com>; Wed,  5 Jul 2017 03:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.726
X-Spam-Level: 
X-Spam-Status: No, score=-0.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, 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=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 a4690yqUKQEf for <irtf-discuss@ietfa.amsl.com>; Wed,  5 Jul 2017 03:56:04 -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 BBDAC132908 for <irtf-discuss@irtf.org>; Wed,  5 Jul 2017 03:56:04 -0700 (PDT)
Received: by mail-oi0-x236.google.com with SMTP id l130so123018306oib.1 for <irtf-discuss@irtf.org>; Wed, 05 Jul 2017 03:56:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=TurUNHm10mFkIOdWjUbgyMOTb4fk30LfhuscDmnuRVA=; b=fl2soqSEcmJFtO8WNR67wO4CoFkEvAKtmDTCw5i8gU0RGE12jmHvVGcb0H/SMTJCo3 bdf7uhzkfKJgR9Lu3scHWqfkd9uKh7T7a5eYfgE36iIH823OJJFQ2vvEo4pisJ9Mf2BC GgAMdah/MQtnDpKdWwro9T2N+mGCb9WOflKlBC9Ns8J1nYvHS7nW3rJswM28ZfsHeecV 2OD1YcK7twclzNUsn+7mcXAeI8BX8sCT73AQkGKl8n0D6mHR2AXBHfQwGZACom1uYJiM imDMkPfyRJligg6zmm303poNtq1q/Lx/5t894v1fhPLj90K0HhuECMRYPypesysRtLVp LIwQ==
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=TurUNHm10mFkIOdWjUbgyMOTb4fk30LfhuscDmnuRVA=; b=ZEKhS7ZzZbZNyJXt5cklYMVdcOf/U8xQwOzn1KcaXtyhnUbwI+cKaaGXa+TXWE2rrk MRzPIwWFhWOpR80lufJ2Vr+1/V4+hsR8xRJ9+bJbaQhrladK1Nd/9P/Vp4etpYWilc6D FRQ6Nybv+CMaWjLtDJNdU1r93/w5nwAA9cqxAbBHyYte9NJcUm1nx+y5Yj6KknZU8XKg V6O5VRrjL56NoQ2wKYgnqibekxSLgD0AqVkG3yXlOIxrckO+J97rvn+tUS444oMDjar9 6d0sTNuVEFTnL6HnVr5tXJQTTJjL1M/aGRbZdcn74KwDeZtbESo65qHQOsPlIdwCoPiZ HBaA==
X-Gm-Message-State: AKS2vOw4DCd91X7TVyZP6K0P+OXkIlMO1pKgFgq3dqfLHbyA2ERNiQoP zvFrYac5eph8XZPfMxnVlrMw0/P3Kw==
X-Received: by 10.202.199.148 with SMTP id x142mr30463055oif.185.1499252164023;  Wed, 05 Jul 2017 03:56:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.49.212 with HTTP; Wed, 5 Jul 2017 03:56:03 -0700 (PDT)
From: Sankalp Bagaria <sankalp.nitt@gmail.com>
Date: Wed, 5 Jul 2017 16:26:03 +0530
Message-ID: <CAPZZOTiHLrZHXc6ii1nYcCN+LE1anGafpZkXNv-_=vyFKfSqPQ@mail.gmail.com>
To: nmlrg-chairs@ietf.org, albert.cabellos@gmail.com, jiangsheng@huawei.com
Cc: irtf-discuss@irtf.org
Content-Type: multipart/alternative; boundary="001a1134e0b4aa5bd805538fd8c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/dVFq4Ka666tq3cBJ2u2nEMmydfA>
Subject: [irtf-discuss] Meeting at Prague IETF 99
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jul 2017 10:56:06 -0000

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

Dear Sir,

Is the Network Machine Learning group meeting during IETF 99 at Prague ?
Can it be attended remotely ? Please share the agenda, if you can.

I am also unable to join the mailing list of the group.

Thanks and Regards,
Sankalp Bagaria,
Centre for Development of Advanced Computing,
Bangalore, India.

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

<div dir=3D"ltr">Dear Sir,<div><br></div><div>Is the Network Machine Learni=
ng group meeting during IETF 99 at Prague ?</div><div>Can it be attended re=
motely ? Please share the agenda, if you can.</div><div><br></div><div>I am=
 also unable to join the mailing list of the group.</div><div><br></div><di=
v>Thanks and Regards,</div><div>Sankalp Bagaria,</div><div>Centre for Devel=
opment of Advanced Computing,</div><div>Bangalore, India.</div></div>

--001a1134e0b4aa5bd805538fd8c1--


From nobody Thu Jul 20 02:01:27 2017
Return-Path: <allison.mankin@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4697412ECCB for <irtf-discuss@ietfa.amsl.com>; Thu, 20 Jul 2017 02:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QyX_F4DUrQNz for <irtf-discuss@ietfa.amsl.com>; Thu, 20 Jul 2017 02:01:20 -0700 (PDT)
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 B2513129B40 for <irtf-discuss@irtf.org>; Thu, 20 Jul 2017 02:01:19 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id l81so5680663wmg.1 for <irtf-discuss@irtf.org>; Thu, 20 Jul 2017 02:01:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=lJ+ICAs6XTuzKPLfnVqPVye3y6UdJeK7aX2qosoLwWw=; b=kg9nXBltgEBBnlP9BwIBhTugvuOUy8VWja9EAJL3kluNpV5kFFTDlHS6K+8zR9PzZW swLwMTV5UXf7mxN5Sppjq46g0TG5W8xWhI957DJwf8dNlu4gxQ1dH0OZAkQLggKP/9zp n5NY68I5hUSU/1/gdG5PTlB5oC321lq4EJAYv5xW1DEZfLDL5SvEMGz4bY1Kw4UnJwlr kBAkf9ONdNIy27/jXE7eI917U5O9LlHsoeVAJ+VdzCbkA2TQ0Gpk3xMiAEgr1hJIibb6 +wjpzSZsnKxjuMZ3kgR3tqLMFvn2JJSzgsmWvNncibWcbIL4FsxJxr9E9OaMXDypv1G0 Ic7w==
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=lJ+ICAs6XTuzKPLfnVqPVye3y6UdJeK7aX2qosoLwWw=; b=q2uWFSh48rBiAmWe9SBRuhoEny50xgCXlKN5VL9FL9bWy9JcOCPsAQVACS/oN8PXIq cTfFy3U1BNSiLVEBXIkyvApan1FA+COzFJnJXfVmJw8A1crIEHBPC04UPFkXK82Opv5o 4NqrTn/iyH7FI+25I5Ig/Hn5Dc5pZm2WQ7F3njZ5mJxSBleGnMHUmV5flIbv9wyUzK8q to3fxp1MY89RTTthRfhOjr2zG8dx7raom6UrJ59kIGCXMt7wjtY2/8t8YCrWqzkpvtES mbCCG2QQErFcddKGXU4jAVByeDwQlrUvK5v4dVGJW+pa749SbVsIxYEGIzRcPrx1Hq/+ /hbA==
X-Gm-Message-State: AIVw111uIOScV+PmYmC2FxbWF63mMeXCXZzh143kaNoQqGwSxFiD56XO t9SPXNQLHzd8qxQVVymsETOnxZJ4RqenUH8=
X-Received: by 10.80.214.147 with SMTP id r19mr2428509edi.236.1500541278051; Thu, 20 Jul 2017 02:01:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.138.69 with HTTP; Thu, 20 Jul 2017 02:01:17 -0700 (PDT)
From: Allison Mankin <allison.mankin@gmail.com>
Date: Thu, 20 Jul 2017 11:01:17 +0200
Message-ID: <CAP8yD=sia5KciTHn4UuOiVtLXZmFgLoA3Bf6ZkE1VkCQXwRvdg@mail.gmail.com>
To: irtf-discuss@irtf.org
Content-Type: multipart/alternative; boundary="94eb2c1afcf0d9604e0554bbfd00"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/jUSIk4wbsISReLP_j1q5BaZQ3cA>
Subject: [irtf-discuss] Agenda for IRTFOPEN Meeting this afternoon
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 09:01:26 -0000

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

This has been uploaded.

Come and hear the ANRP Prize Winners today (Afternoon II, Karlin I/II)

IRTFOPEN 99 Agenda:

Brief update on the IRTF

- See also overview presented Saturday for EDU program


Applied Networking Research Prize Talks (45 minutes each, including
discussion):


Philipp Richter, Technische Universit=C3=A4t Berlin, DE
A Multi-perspective Analysis of Carrier-Grade NAT Deployment

Stephen Checkoway, University of Illinois Chicago, US
A Systematic Analysis of the Juniper Dual EC Incident

Discussion (Time Permitting):

Plans for the Future - What Type of Publication Stream do you need?

Open Mic

-------

See you there!

Allison

--94eb2c1afcf0d9604e0554bbfd00
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">This has been uploaded.<br><br></div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif">Come and hear t=
he ANRP Prize Winners today (Afternoon II, Karlin I/II)<br><br>IRTFOPEN 99 =
Agenda:<br><br>Brief update on the IRTF<br><br>- See also overview presente=
d Saturday for EDU program<br><br><br>Applied Networking Research Prize Tal=
ks (45 minutes each, including discussion):<br><br><br>Philipp Richter, Tec=
hnische Universit=C3=A4t Berlin, DE<br>A Multi-perspective Analysis of Carr=
ier-Grade NAT Deployment<br><br>Stephen Checkoway, University of Illinois C=
hicago, US<br>A Systematic Analysis of the Juniper Dual EC Incident<br><br>=
Discussion (Time Permitting):<br><br>Plans for the Future - What Type of Pu=
blication Stream do you need?<br><br>Open Mic<br><br></div><div class=3D"gm=
ail_default" style=3D"font-family:arial,helvetica,sans-serif">-------<br><b=
r></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif">See you there!<br><br></div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif">Allison <br></div><div class=3D=
"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br></div>=
</div>

--94eb2c1afcf0d9604e0554bbfd00--


From nobody Thu Jul 20 02:02:53 2017
Return-Path: <allison.mankin@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91F4312ECEF for <irtf-discuss@ietfa.amsl.com>; Thu, 20 Jul 2017 02:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0jrq5aIwFdK for <irtf-discuss@ietfa.amsl.com>; Thu, 20 Jul 2017 02:02:51 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 588EB127735 for <irtf-discuss@irtf.org>; Thu, 20 Jul 2017 02:02:51 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id w126so18622717wme.0 for <irtf-discuss@irtf.org>; Thu, 20 Jul 2017 02:02:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=jUejGhzxgILBSK6MxffW8vgEK5RV+ul3CofLUNDI8H4=; b=LMbc5lr/aJiOeWoR5a2tG3IUQDfHek4xL6ktfh/CtiJuBvI0nuAYSH6p1lPeTob9XT RTd22F1xMD3ykvCWCIs1MISdMh8IXABD+LHCUtUYNhRgb2b2bhQdz3zXU3v0woeNYH7A atJwx1ktrNt/7mhR/lZfDXUp59T58nwxomJxzbou86CxFX19GuFj7W1PWUHcFJ8tgfBt 9aya8UP8wsS3s464XH8iZUFkL0MYtva6HlsWXk0I/k7sTA4wmIWXdFe4xe1ptn4ZAYIj d6guWeo+lYnVRgfwLAd6fMtb9vNBGNxlbvX1iMlnZUkiw/fNAGDDkTMub+t+hAe5cnbz vbjA==
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=jUejGhzxgILBSK6MxffW8vgEK5RV+ul3CofLUNDI8H4=; b=GmDYZ5llmlCxse7iOuz7AkeiSFf0x7qoKs1QREYAjjpNoxvyYLbQIGbN5KplA8Jwzt hFj6YefmhEriX5C9RbLATgRUWzJi9HuyGkedZcORm+5x7Vf17fLvwEtBpkKleTtYfT0C xXMigYhjbJ65ARTuKWtMhQfeNcHJEVRgMGgFAnymxQ/WIBQFOkJA5PUNmmxOvD55c2Hx /+uCXy5Qx2SvBoZ3a38aTZaVpPtU1oAQvvOmkJORpaFnA3An0drOQNS9fCVjW1WtvanF zDTCyOS+hqzuxiLiZkACtFcEEsVxshrIdG4vVta7TksxdHTm3cP6Dk4PBvGGlgD8wYKp LFhw==
X-Gm-Message-State: AIVw111GjI25qL74k192oFh/Sbwsf2DqhUlJ8lmrJP7cqkcm1JkHMU2u RnMl/1kLN+c060Ufx1N1dl1szpG7vnFK
X-Received: by 10.80.170.155 with SMTP id q27mr2156989edc.208.1500541369716; Thu, 20 Jul 2017 02:02:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.138.69 with HTTP; Thu, 20 Jul 2017 02:02:49 -0700 (PDT)
From: Allison Mankin <allison.mankin@gmail.com>
Date: Thu, 20 Jul 2017 11:02:49 +0200
Message-ID: <CAP8yD=uOJaFzdoV6VuG-bNjK9K+mmY40zHhwO0F0Dx_QEaFN5A@mail.gmail.com>
To: irtf-discuss@irtf.org
Content-Type: multipart/alternative; boundary="94eb2c199cb25014bb0554bc03f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/GI6pf9hP3iEBW43V_9bkdhUZshY>
Subject: [irtf-discuss] Needed: Note taker and Jabber Scribe for IRTF Open
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 09:02:52 -0000

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

Please volunteer and I will owe you a beer

--94eb2c199cb25014bb0554bc03f3
Content-Type: text/html; charset="UTF-8"

<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Please volunteer and I will owe you a beer<br></div></div>

--94eb2c199cb25014bb0554bc03f3--


From nobody Thu Jul 20 04:41:18 2017
Return-Path: <melinda.shore@nomountain.net>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5504131C04 for <irtf-discuss@ietfa.amsl.com>; Thu, 20 Jul 2017 04:41: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, 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=nomountain-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 oO7mUTMGhnP4 for <irtf-discuss@ietfa.amsl.com>; Thu, 20 Jul 2017 04:41:15 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D952131A86 for <irtf-discuss@irtf.org>; Thu, 20 Jul 2017 04:41:15 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id v105so39481294wrb.0 for <irtf-discuss@irtf.org>; Thu, 20 Jul 2017 04:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomountain-net.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=T69qPK1MASg2e16+ka/Vg8d3IfDxacJq1tdcoyuFc3U=; b=AiPFlMbr4YpZTuBX1VeuK5wAvsAOcCqTwDPu4+84aw590uuBG943sxg+YDdqkptZuY KiETKYkPEoJaNikoNjo6VJCiXWnkz00WMwxZsdmBSnl9AT11LmNHFGwwRfnD5N0H3vJs EPSlqe70LlKTVsBJ0DE42ZuWTgPGMpIK4azHncWYz9gkWEF1/fG4dfc1SxyyKVyu1bzK Tqexhje9FUGiLCjsZFtG79X22vfrTuV0uMd/F0dguNhsTyzKtNi1otHkeqPcGFD+m/Qd je5OI5C7jvZLAUYXWeHsPqB7ylee2mnFy+h3Q9Et+ks+hteZHFJX6bVYZ+cgRdEpUFjV AG3Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=T69qPK1MASg2e16+ka/Vg8d3IfDxacJq1tdcoyuFc3U=; b=oNbwxwcn07fVUZ2RYCQNOcLiVDG/KQbL6/Yalz4ObtX5VOh1vRtmrgpZ2/wIdU9Cpx m6+Q8pApUd3k/4XTzoeoOEQVt5BaJBRUpje4x4GdDf1ljQnqpLWNr9xG89iUEw6l18zf KXVzChqCebxuVZNa5B/FGzSIMRXQR9PVuPnNVXFKGkNaVTPcOcDFXY/6Btk7Mwa6tSc9 /BdGhorJjTCMBJBlc4QF+afarQ4q9Di3bIjkl+4L35IWF4P7DVG42AXAO5g6SXFoQzY9 QJfWkwyA4k4Be0BGXXZF+tMFbs3qagCtE6iLNzxBrQE2AE108QINjGkeD+U61DW3aqLK +sSQ==
X-Gm-Message-State: AIVw1111Pq2Ige2RuIsiHER5pxEqPqJppWKDUMVNVS0zQXwsSXKM8Qhk tNpO5l0v6otuNWXEnTlLtA==
X-Received: by 10.223.154.3 with SMTP id z3mr3078375wrb.252.1500550873639; Thu, 20 Jul 2017 04:41:13 -0700 (PDT)
Received: from dhcp-80d4.meeting.ietf.org ([2001:67c:370:128:f7:3ec1:636a:28cd]) by smtp.gmail.com with ESMTPSA id h68sm5058193wrh.32.2017.07.20.04.41.12 for <irtf-discuss@irtf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jul 2017 04:41:12 -0700 (PDT)
To: irtf-discuss@irtf.org
References: <CAP8yD=uOJaFzdoV6VuG-bNjK9K+mmY40zHhwO0F0Dx_QEaFN5A@mail.gmail.com>
From: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <521c16f8-0b1a-9fce-b6d7-5f9c99da8645@nomountain.net>
Date: Thu, 20 Jul 2017 13:41:12 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAP8yD=uOJaFzdoV6VuG-bNjK9K+mmY40zHhwO0F0Dx_QEaFN5A@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PfrCTquSwsVWtDqbSJkaM40cMt3gRJTd8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/11xlmoi-YnXPaJOYVUhLxJhnTzw>
Subject: Re: [irtf-discuss] Needed: Note taker and Jabber Scribe for IRTF Open
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jul 2017 11:41:17 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PfrCTquSwsVWtDqbSJkaM40cMt3gRJTd8
Content-Type: multipart/mixed; boundary="EgaNIiAaqM3DfWL3TIXAQ9RlHXUwsxw9U";
 protected-headers="v1"
From: Melinda Shore <melinda.shore@nomountain.net>
To: irtf-discuss@irtf.org
Message-ID: <521c16f8-0b1a-9fce-b6d7-5f9c99da8645@nomountain.net>
Subject: Re: [irtf-discuss] Needed: Note taker and Jabber Scribe for IRTF Open
References: <CAP8yD=uOJaFzdoV6VuG-bNjK9K+mmY40zHhwO0F0Dx_QEaFN5A@mail.gmail.com>
In-Reply-To: <CAP8yD=uOJaFzdoV6VuG-bNjK9K+mmY40zHhwO0F0Dx_QEaFN5A@mail.gmail.com>

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

I'll take minutes.

Melinda


--EgaNIiAaqM3DfWL3TIXAQ9RlHXUwsxw9U--

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

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

iQIcBAEBCgAGBQJZcJbZAAoJELiGRpM6HoEufEYQAIqtG6Zzh3O82GFjdMTDvupR
n+l4/NNm6lNs50pZGzVC+fGlFf4GImCcIj+qBz4z7ZLQXbiM/Q8VQpSD1YvRNZiP
kmZ9WDjHIMIOknQz5dtTXqX3VIVOu+TZcWLxBMJbraQvYVPkGK45+C+Aep6rIjZo
Yx0hQa6jMEwinih/dF4+22zw5Nx3fVMiEUjdwaHX9JBn4LM4rC4MRjwcl+c9aeCs
L0RoAJQus/1WRh2LskVgym5MZg3rrtT0Bt64mYDHEjwxn8ANB7aztLBYZUc/rM8V
aSs/Xff8DdVWa03X5j3fiNePFbOe9wFeV1zMODdTjKpBAkRl/VOVQ2OzNL05jIdo
6HwRqMKUf1meJkLrYj7TTYrpZfLsD7wGSxJexLfQijwwJvXXwHkg857UNBHw1T06
SC050CsZhdeRc65XleXFyH1vkHtSVHIT+UtZLuBxl965NbT6cgLaa2UkRqpY6bu+
vtcZFuAStdxy0cAGkOY+Myt0KQaFrIMdJDDpHJ2WrjxXHFLtrwmNJKcbpjH26+YV
leKkSsh8HLdOUdeU5JxegFSUu7j3PeFtE+CiOl9krI/m6fa2rlUPBEWxq16lRRst
dGUuSx1WBZQQWFS+KgHSKb5J3kccBwij31sld8HPliNj8sevwbsbrU2Kq1XvGxIl
agCSzt9ZItCMwH0sreNJ
=rZTE
-----END PGP SIGNATURE-----

--PfrCTquSwsVWtDqbSJkaM40cMt3gRJTd8--


From nobody Mon Jul 24 05:47:43 2017
Return-Path: <allison.mankin@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A804131CE1; Mon, 24 Jul 2017 05:47:41 -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, NORMAL_HTTP_TO_IP=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 aTA54io018-c; Mon, 24 Jul 2017 05:47:37 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0315B131C58; Mon, 24 Jul 2017 05:47:37 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id l81so19099234wmg.1; Mon, 24 Jul 2017 05:47:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=TaSraoFUCkGkaRG21pA3x03UDjhOM1RiqIc6CGC3/AU=; b=lRBeuyqVjcElopync5GLOA3EbdrnF4ubxhiDqEp2YVUy/IdklbyTDV2swu4v05vZdt 64c38c35mmy9zmPLen7IrrLizrAZRrz/rdeXyy3rb9fYl7MZ7EouZ0GvQxa1pTtOWNOS vIZrG505Lf1cuDjrqzpE3uF1Rp7uXdK0kH8Vd8r9oQmQAOY737rcl16pj8BC/wEkVXFd fRW80rdM5azZep6T40IhgshiVl0pUvb9NZF9S5lLTsLMPkQxar8Gjw+uxR6woeW1cQ08 nSuCgqD9hWEgNft1ny60vxN0YJTTNeXJgjs6eSfjKCEZumiGfOYRQ7r6aWJtgoqfubm5 ppeA==
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=TaSraoFUCkGkaRG21pA3x03UDjhOM1RiqIc6CGC3/AU=; b=tq+03IQmvIAIbFn68ISGJPmZxeWO7hTcfNqLwUGNkTB1ltv66cBN9uhoSARNh2nB0Y VUMfR+x5B392gM5bqWTpZPzKXB7d56oUBg5KGoRXv0LqRAvzr4+8rbxOYSowcBkcrDO6 +dSnHIS38we18y+XutxR0hmfNmmW5FOlvJfxC6dtXgPEFBcQdwuKJh8D/zcdS8dLQlGI g8ljsVB9NpSE01jzyg+PsqJO0x2bwEQ2aVwoNWKpEfrIKEGHml0ZlLgzkGEzOkXb0J6R Ttgz6kIgowtqbfUdEplRwsRwGhitDiXRdmhkH0ukmpP69jSpbnAxzG2FkIcyCv+ERcCp 7DcQ==
X-Gm-Message-State: AIVw110Ku9218WKr6POaeNZPdWU9DZSI24oBnmIL5MlSnUoz//6MmdHH ITvKLlwcD/IZawbzzpfays9xhxUcGayA
X-Received: by 10.80.215.7 with SMTP id t7mr15367595edi.19.1500900455003; Mon, 24 Jul 2017 05:47:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.138.69 with HTTP; Mon, 24 Jul 2017 05:47:34 -0700 (PDT)
From: Allison Mankin <allison.mankin@gmail.com>
Date: Mon, 24 Jul 2017 14:47:34 +0200
Message-ID: <CAP8yD=siaN+E3y2ePKsG94zGOhra-y_yKm-enHcJCiJDUuUNNQ@mail.gmail.com>
To: irtf-discuss@irtf.org,  "Internet Research Steering Group (irsg@irtf.org)" <irsg@irtf.org>
Cc: Philipp Richter <prichter@inet.tu-berlin.de>, Stephen Checkoway <sfc@uic.edu>
Content-Type: multipart/alternative; boundary="f403045dbe9476bd6205550f9e39"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/BUOhhs-ooXUFCDnQvlAgTlvdeMY>
Subject: [irtf-discuss] Draft Minutes for IRTFOPEN Meeting in Prague
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Jul 2017 12:47:41 -0000

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

I've posted a draft of minutes for the IRTFOPEN meeting.  Thank you to
Melinda Shore for the excellent minute-taking.  If anyone has anything to
add or correct, let me know.

Congratulations and thanks again to Steve and Phillip for their excellent
ANRP papers!

Draft
-------

IRTF Open Meeting, 20 July 2017
-------------------------------
Minute-Taker: Melinda Shore

Chair=E2=80=99s Intro
IETF Note Well applies to IRTF, as does IETF harassment
policy.

Agenda bashing, time permitting will discuss what sort of
publication stream people would like.

Covered IRTF mission - longer term research issues related
to internet, organized into research groups.  These can be formed for
a year of trial before formal chartering.

Every research group met at IETF 99, as well as the new Proposed PANRG,
starting its year of trial, and and initial organizing meeting for DIN.

Applied Networking Research Workshop (IRTF/ACM/ISOC)
The 2nd annual ANRW was held on Saturday, materials at
http://irtf.org/anrw/2017/program.html

Applied Networking Research Prize (IRTF/ISOC)
ANRP papers were already published elsewhere
and nominated on the basis of exceptional quality.  Six awards are
made, and two are announced and presented at each IETF in the
award year.  The nominations process, papers published in 2017, for
awards in 2018, will begin again around November.

ANRP talk 1 -
Philipp Richter, TU Berlin.  "A Multi-perspective Analysis
of Carrier-Grade NAT Deployment" [1]
----------------------------------------------------------
Was presented at last year's IMC conference.  In 2017, 4 out
of 5 RIR IPv4 allocations exhausted, about ~1% of the IPv4
address space unallocated.  Other than using v6, ISPs can
buy addresses on address markets or use CGN.

There are no CGN deployment statistics available and not
much is known about deployed CGN configurations.

Surveyed more than 75 ISPs from all regions of the world.
38% said they'd deployed it already and about 12% said they
had plans.

Operational concerns include application problems (gaming),
traceability, addresses becoming blacklisted.  Challenges
include resource allocation, troubleshooting, and internal
address space fragmentation/shortage (RFC 1918).

Comments suggested that ISPs don't like CGN but v6
deployment is costly and complicated

Objectives: develop detection methods, develop methods to
extract properties.

Eventually found 2 methods to detect CGN presence.  First is
to detect "from the outside" via BitTorrent.  The BitTorrent
DHT can be used as vantage points.  Constructed a graph
of leaking relationships and then look at those graphs on a
per-AS basis.

They tested more than 2700 ASes with his methodology,
detecting CGN in over 250.  Benefits of this method include
broad coverage and no probing devices.  Caveats are that
BitTorrent activity is necessary, no cellular networks

Second method is from the inside, with Netalyzr from ICSI Berkeley.
Looked at more than 550,000 sessions in 1500 ASes.  Access to
device/router/public IP addresses.  Runs in both cellular
and non-cellular networks, and allows the use of customized
tests.

Caveats are partial visibility, and crowdsourced (users need
to run Netalizer).

More than 20% of the ASes use multiple internal address
ranges.  25.0.0.0/8 is mostly unrouted but in internal use
by at least 4 major networks.

Up to 20% of ASes use arbitrary pooling.  No dominant port
allocation behavior, often inconsistent within same AS.  IP
address and port allication: most ASes show non-uniform
behavior.  Some ASes allocate chunks of ports, can reason
about how many subscribers per IP.  Largest number they
could empirically detect was 512 per IP address.

STUN-based testing: symmetric NAT binding turns out to be
surprisingly common in CGNs (40% in cellular CGNs).

Conclusions:  CGN is very broadly deployed, stunning variety
of configurations across ASes, degree of resource sharing
varies widely, and NAT mappings and timeouts of some CGNs
more restrictive than CPE NAT.

Measuring end-user internet performance might be extended to
measure maximum concurrent connections and type of NAT
mappings.  CGNs reduce how much internet subscribers
receive, so there may be a need for guidelines or regulation
of resource allocation.

Question: did you compare against v6-only networks and
NAT64?  Public BitTorrent DHT v6 table is only sparsely
populated.

Question: routable addresses that you found - do you have a
published list to finer granularity than /8?

Q: how many deployments are compliant to the standards?
They don't specify all the things we measured, but they do
specify arbitrary pooling.  At least 20% violate that.
There are a large percentage that are not RFC-compliant.
Number of ports and sessions not specified

Q: you had port behaviors and restrictiveness - did you look
at correlations?  No, not yet

Q: When STUN was introduced it was discovered that some NATs
change their behavior as they reach exhaustion - did you
measure that in CGNs?  We noticed it but did not measure

Q: Why do you think reputation systems can work?  I don't
know how they can or should deal with that but I would be
very interested in talking with people who run such systems

Q: Did you go back to survey respondees to establish whether
or not there were false positives?  We did not find false
positives so far, but we found a few false negatives.

Q: regulation - Belgium is concerned about the growing use
of CGN and the difficulty it introduces for law
enforcement.  Given that you might see it starting to go
away

Q: if someone could tell us which devices they are, that
would be fascinating.  WRT reputation, there are pieces of
software with unique identifiers, and sometimes you see
hundreds or thousands behind same IP address.  Also
interesting to look at how IPv4 addresses map onto v6
addresses

ANRP talk 2 -
Stephen Checkoway, UI Chicago, "A Systematic Analysis of the
Juniper Dual EC Incident" [2]
------------------------------------------------------------
Was presented at ACM CCS 2016.

In late 2015 Juniper announced that unauthorized parties had
accessed source code and introduced backdoors, including a
decryption vulnerability

Affected Juniper's Secure Services Gateway.

Introduced hardcoded administrative access password.

The announcement was vague about the other backdoor.  HD
Moore ran strings over both affected version and fix, and
diffed them.  The first 5 of the long hex digits are P-256
parameters.  To figure out what the difference actually
meant required reverse-engineering the binary.  Turned out to
be backdooring PRNG in Dual EC, allowing attacker to recover
internal state.

[description of EC and dual EC operation, and
Shumow-Ferguson attack]

Attacker needs secret value d, and at least 28 bytes of r
sub k for some k, and some public function of "enough of the
following output.

For example, a protocol that has a >=3D 28 byte nonce, and a
diffie-hellman public key.

In this attack, attacker substituted their own nonstandard Q
point.

Drew on a body of firmware revisions, which the speaker reversed
engineered.

Global output buffer used as both reseed temporary buffer
and outut of prng_generate.  Index var is global for some
reason.  X9.31 is never used as a result.

In this case the nonce is generated *after* exponent, so
Shumow-Ferguson attack doesn't recover x.  But, SreenOS
contains queues of pre-generated nonces and DH key pairs.
Queues filled once/second, nonces first.  So, in many cases
ideal Shumow-Ferguson attack works.

WIth IKEv1 with preshared keys, attacker needs to know key.
For PK encryption, attack failes due to encrypted nonces.
In IKEv2 key derivation independent of mode and attack just
works.

Built a proof-of-concept, created modified firmware wth
their own Q.  Attacked VPN configurations and found their
conclusions were correct.

History of ScreenOS PRNG code: changed to reseeding every
call, reseed bug exposes DualEC, and nonces were increased to
32 bytes.

Why was Dual EC added to seed X9.31?  No engineering reasons
he could think of, and no standardization reason.

Why reseed on every call?  No engineering reasons he could
think of, maybe backtracking resistence, could be a bug.

The reseed bug: both output and index become globals and are
reused by reseed procedure.  No good reason, could be a bug

Why increase in nonce size?  No engineering reason, no
(good) cryptographic reason, but at 20 bytes the
Shumow-Ferguson attack takes infeasible number of
iterations, but at 32 takes only 2^16

Why nonce pre-generation?  Dual EC is about 125 times slower
than X9.31.

First four required for passive VPN decrption, last enables
single connection decryption.

Are the versions of ScreenOS with Juniper's Q vulnerable?
Maybe.

How was their Q generated?  Impossible to say with data we
have.

Lessons learned: consider hashing output before putting it
on the wire, scrutinize any PRNG changes closely, use
separate PRNG instances for public and secret data

Don't allow nonces to vary in length or be longer than
necessary - IKE's 256-byte nonces are unnecessarily long,
variable length enables implementation fingerprinting,
long/variable length nonces privde implementations the
opportunity to expose secrets

Include even low-entropy secret into key derivation.  We
should not build exceptional access mechanisms into
protocols

Q: what public statements did Juniper make?  They eventually
decided to remove Dual EC altogether, but made no public
statements about remediation, etc.

Q: QUIC is having debates about what to leave some fields in the
clear on the wire - have you thought about whehter there are
other places in protocols where we might be exposing
randomness?  I hadn't thought about sequence numbers but if
they are not sequential, then yes, this should be considered.

Q: Is it a biased RNG?  Yes, but it seems fairly low to me.
(I don't know why anybody would use Dual EC)

The room was extremely hot so the Chair adjourned the meeting
15 minutes early rather than take up the publication streams
discussion in the heat.  But she asked for people to look for
mail and join in discussion on the IRTF-discuss mailing list.


References
[1]
Authors:Philipp Richter and Florian Wohlfart and Narseo Vallina-Rodriguez
and Mark Allman and Randy Bush and Anja Feldmann and Christian
Kreibich and Nicholas Weaver and Vern Paxson
Title: A Multi-perspective Analysis of Carrier-Grade NAT Deployment
Conference: Proceedings of ACM IMC 2016
PDF: https://net.t-labs.tu-berlin.de/~prichter/imc176-richterA.pdf

[2]
Authors: Stephen Checkoway and Jacob Maskiewicz and Christina
Garman and Joshua Fried and Shaanan Cohney and
Matthew Green and Nadia Heninger and Ralf-Philipp
Weinmann and Eric Rescorla and Hovav Shacham
Title: A Systematic Analysis of the Juniper Dual EC Incident
Conference: Proceedings of CCS 2016
PDF: https://www2.cs.uic.edu/~s/papers/juniper2016/juniper2016.pdf

--f403045dbe9476bd6205550f9e39
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">I&#39;ve posted a draft of minutes for the IRTFOPEN mee=
ting.=C2=A0 Thank you to Melinda Shore for the excellent minute-taking.=C2=
=A0 If anyone has anything to add or correct, let me know.<br><br></div><di=
v class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">=
Congratulations and thanks again to Steve and Phillip for their excellent A=
NRP papers!<br><br></div><div class=3D"gmail_default" style=3D"font-family:=
arial,helvetica,sans-serif">Draft<br>-------<br><br>IRTF Open Meeting, 20 J=
uly 2017<br>-------------------------------<br>Minute-Taker: Melinda Shore<=
br><br>Chair=E2=80=99s Intro<br>IETF Note Well applies to IRTF, as does IET=
F harassment<br>policy.<br><br>Agenda bashing, time permitting will discuss=
 what sort of<br>publication stream people would like.<br><br>Covered IRTF =
mission - longer term research issues related<br>to internet, organized int=
o research groups.=C2=A0 These can be formed for<br></div><div class=3D"gma=
il_default" style=3D"font-family:arial,helvetica,sans-serif">a year of tria=
l before formal chartering.<br></div><div class=3D"gmail_default" style=3D"=
font-family:arial,helvetica,sans-serif"><br>Every research group met at IET=
F 99, as well as the new Proposed PANRG,<br>starting its year of trial, and=
 and initial organizing meeting for DIN.<br><br>Applied Networking Research=
 Workshop (IRTF/ACM/ISOC)<br>The 2nd annual ANRW was held on Saturday, mate=
rials at<br><a href=3D"http://irtf.org/anrw/2017/program.html">http://irtf.=
org/anrw/2017/program.html</a><br><br>Applied Networking Research Prize (IR=
TF/ISOC)<br>ANRP papers were already published elsewhere<br>and nominated o=
n the basis of exceptional quality.=C2=A0 Six awards are <br></div><div cla=
ss=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">made,=
 and two are announced and presented at each IETF in the<br></div><div clas=
s=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">award =
year.=C2=A0 The nominations process, papers published in 2017, for<br></div=
><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-ser=
if">awards in 2018, will begin again around November.<br></div><div class=
=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br>ANR=
P talk 1 -<br>Philipp Richter, TU Berlin.=C2=A0 &quot;A Multi-perspective A=
nalysis<br>of Carrier-Grade NAT Deployment&quot; [1]<br>-------------------=
---------------------------------------<br>Was presented at last year&#39;s=
 IMC conference.=C2=A0 In 2017, 4 out<br>of 5 RIR IPv4 allocations exhauste=
d, about ~1% of the IPv4<br>address space unallocated.=C2=A0 Other than usi=
ng v6, ISPs can<br>buy addresses on address markets or use CGN.<br><br>Ther=
e are no CGN deployment statistics available and not<br>much is known about=
 deployed CGN configurations.<br><br>Surveyed more than 75 ISPs from all re=
gions of the world.<br>38% said they&#39;d deployed it already and about 12=
% said they<br>had plans.<br><br>Operational concerns include application p=
roblems (gaming),<br>traceability, addresses becoming blacklisted.=C2=A0 Ch=
allenges<br>include resource allocation, troubleshooting, and internal<br>a=
ddress space fragmentation/shortage (RFC 1918).<br><br>Comments suggested t=
hat ISPs don&#39;t like CGN but v6<br>deployment is costly and complicated<=
br><br>Objectives: develop detection methods, develop methods to<br>extract=
 properties.<br><br>Eventually found 2 methods to detect CGN presence.=C2=
=A0 First is<br>to detect &quot;from the outside&quot; via BitTorrent.=C2=
=A0 The BitTorrent<br>DHT can be used as vantage points.=C2=A0 Constructed =
a graph<br>of leaking relationships and then look at those graphs on a<br>p=
er-AS basis.<br><br>They tested more than 2700 ASes with his methodology,<b=
r>detecting CGN in over 250.=C2=A0 Benefits of this method include<br>broad=
 coverage and no probing devices.=C2=A0 Caveats are that<br>BitTorrent acti=
vity is necessary, no cellular networks<br><br>Second method is from the in=
side, with Netalyzr from ICSI Berkeley.=C2=A0 <br>Looked at more than 550,0=
00 sessions in 1500 ASes.=C2=A0 Access to<br>device/router/public IP addres=
ses.=C2=A0 Runs in both cellular<br>and non-cellular networks, and allows t=
he use of customized<br>tests.<br><br>Caveats are partial visibility, and c=
rowdsourced (users need<br>to run Netalizer).<br><br>More than 20% of the A=
Ses use multiple internal address<br>ranges.=C2=A0 <a href=3D"http://25.0.0=
.0/8">25.0.0.0/8</a> is mostly unrouted but in internal use<br>by at least =
4 major networks.<br><br>Up to 20% of ASes use arbitrary pooling.=C2=A0 No =
dominant port<br>allocation behavior, often inconsistent within same AS.=C2=
=A0 IP<br>address and port allication: most ASes show non-uniform<br>behavi=
or.=C2=A0 Some ASes allocate chunks of ports, can reason<br>about how many =
subscribers per IP.=C2=A0 Largest number they<br>could empirically detect w=
as 512 per IP address.<br><br>STUN-based testing: symmetric NAT binding tur=
ns out to be<br>surprisingly common in CGNs (40% in cellular CGNs).<br><br>=
Conclusions:=C2=A0 CGN is very broadly deployed, stunning variety<br>of con=
figurations across ASes, degree of resource sharing<br>varies widely, and N=
AT mappings and timeouts of some CGNs<br>more restrictive than CPE NAT.<br>=
<br>Measuring end-user internet performance might be extended to<br>measure=
 maximum concurrent connections and type of NAT<br>mappings.=C2=A0 CGNs red=
uce how much internet subscribers<br>receive, so there may be a need for gu=
idelines or regulation<br>of resource allocation.<br><br>Question: did you =
compare against v6-only networks and<br>NAT64?=C2=A0 Public BitTorrent DHT =
v6 table is only sparsely<br>populated.<br><br>Question: routable addresses=
 that you found - do you have a<br>published list to finer granularity than=
 /8?<br><br>Q: how many deployments are compliant to the standards?<br>They=
 don&#39;t specify all the things we measured, but they do<br>specify arbit=
rary pooling.=C2=A0 At least 20% violate that.<br>There are a large percent=
age that are not RFC-compliant.<br>Number of ports and sessions not specifi=
ed<br><br>Q: you had port behaviors and restrictiveness - did you look<br>a=
t correlations?=C2=A0 No, not yet<br><br>Q: When STUN was introduced it was=
 discovered that some NATs<br>change their behavior as they reach exhaustio=
n - did you<br>measure that in CGNs?=C2=A0 We noticed it but did not measur=
e<br><br>Q: Why do you think reputation systems can work?=C2=A0 I don&#39;t=
<br>know how they can or should deal with that but I would be<br>very inter=
ested in talking with people who run such systems<br><br>Q: Did you go back=
 to survey respondees to establish whether<br>or not there were false posit=
ives?=C2=A0 We did not find false<br>positives so far, but we found a few f=
alse negatives.<br><br>Q: regulation - Belgium is concerned about the growi=
ng use<br>of CGN and the difficulty it introduces for law<br>enforcement.=
=C2=A0 Given that you might see it starting to go<br>away<br><br>Q: if some=
one could tell us which devices they are, that<br>would be fascinating.=C2=
=A0 WRT reputation, there are pieces of<br>software with unique identifiers=
, and sometimes you see<br>hundreds or thousands behind same IP address.=C2=
=A0 Also<br>interesting to look at how IPv4 addresses map onto v6<br>addres=
ses<br><br>ANRP talk 2 -<br>Stephen Checkoway, UI Chicago, &quot;A Systemat=
ic Analysis of the<br>Juniper Dual EC Incident&quot; [2]<br>---------------=
---------------------------------------------<br>Was presented at ACM CCS 2=
016.<br><br>In late 2015 Juniper announced that unauthorized parties had<br=
>accessed source code and introduced backdoors, including a<br>decryption v=
ulnerability<br><br>Affected Juniper&#39;s Secure Services Gateway.<br><br>=
Introduced hardcoded administrative access password.<br><br>The announcemen=
t was vague about the other backdoor.=C2=A0 HD<br>Moore ran strings over bo=
th affected version and fix, and<br>diffed them.=C2=A0 The first 5 of the l=
ong hex digits are P-256<br>parameters.=C2=A0 To figure out what the differ=
ence actually<br>meant required reverse-engineering the binary.=C2=A0 Turne=
d out to<br>be backdooring PRNG in Dual EC, allowing attacker to recover<br=
>internal state.<br><br>[description of EC and dual EC operation, and<br>Sh=
umow-Ferguson attack]<br><br>Attacker needs secret value d, and at least 28=
 bytes of r<br>sub k for some k, and some public function of &quot;enough o=
f the<br>following output.<br><br>For example, a protocol that has a &gt;=
=3D 28 byte nonce, and a<br>diffie-hellman public key.<br><br>In this attac=
k, attacker substituted their own nonstandard Q<br>point.<br><br>Drew on a =
body of firmware revisions, which the speaker reversed<br>engineered.<br><b=
r>Global output buffer used as both reseed temporary buffer<br>and outut of=
 prng_generate.=C2=A0 Index var is global for some<br>reason.=C2=A0 X9.31 i=
s never used as a result.<br><br>In this case the nonce is generated *after=
* exponent, so<br>Shumow-Ferguson attack doesn&#39;t recover x.=C2=A0 But, =
SreenOS<br>contains queues of pre-generated nonces and DH key pairs.<br>Que=
ues filled once/second, nonces first.=C2=A0 So, in many cases<br>ideal Shum=
ow-Ferguson attack works.<br><br>WIth IKEv1 with preshared keys, attacker n=
eeds to know key.<br>For PK encryption, attack failes due to encrypted nonc=
es.<br>In IKEv2 key derivation independent of mode and attack just<br>works=
.<br><br>Built a proof-of-concept, created modified firmware wth<br>their o=
wn Q.=C2=A0 Attacked VPN configurations and found their<br>conclusions were=
 correct.<br><br>History of ScreenOS PRNG code: changed to reseeding every<=
br>call, reseed bug exposes DualEC, and nonces were increased to<br>32 byte=
s.<br><br>Why was Dual EC added to seed X9.31?=C2=A0 No engineering reasons=
<br>he could think of, and no standardization reason.<br><br>Why reseed on =
every call?=C2=A0 No engineering reasons he could<br>think of, maybe backtr=
acking resistence, could be a bug.<br><br>The reseed bug: both output and i=
ndex become globals and are<br>reused by reseed procedure.=C2=A0 No good re=
ason, could be a bug<br><br>Why increase in nonce size?=C2=A0 No engineerin=
g reason, no<br>(good) cryptographic reason, but at 20 bytes the<br>Shumow-=
Ferguson attack takes infeasible number of<br>iterations, but at 32 takes o=
nly 2^16<br><br>Why nonce pre-generation?=C2=A0 Dual EC is about 125 times =
slower<br>than X9.31.<br><br>First four required for passive VPN decrption,=
 last enables<br>single connection decryption.<br><br>Are the versions of S=
creenOS with Juniper&#39;s Q vulnerable?<br>Maybe.<br><br>How was their Q g=
enerated?=C2=A0 Impossible to say with data we<br>have.<br><br>Lessons lear=
ned: consider hashing output before putting it<br>on the wire, scrutinize a=
ny PRNG changes closely, use<br>separate PRNG instances for public and secr=
et data<br><br>Don&#39;t allow nonces to vary in length or be longer than<b=
r>necessary - IKE&#39;s 256-byte nonces are unnecessarily long,<br>variable=
 length enables implementation fingerprinting,<br>long/variable length nonc=
es privde implementations the<br>opportunity to expose secrets<br><br>Inclu=
de even low-entropy secret into key derivation.=C2=A0 We<br>should not buil=
d exceptional access mechanisms into<br>protocols<br><br>Q: what public sta=
tements did Juniper make?=C2=A0 They eventually<br>decided to remove Dual E=
C altogether, but made no public<br>statements about remediation, etc.<br><=
br>Q: QUIC is having debates about what to leave some fields in the<br>clea=
r on the wire - have you thought about whehter there are<br>other places in=
 protocols where we might be exposing<br>randomness?=C2=A0 I hadn&#39;t tho=
ught about sequence numbers but if <br>they are not sequential, then yes, t=
his should be considered.<br><br>Q: Is it a biased RNG?=C2=A0 Yes, but it s=
eems fairly low to me.<br>(I don&#39;t know why anybody would use Dual EC)<=
br><br>The room was extremely hot so the Chair adjourned the meeting <br>15=
 minutes early rather than take up the publication streams<br>discussion in=
 the heat.=C2=A0 But she asked for people to look for <br>mail and join in =
discussion on the IRTF-discuss mailing list.<br><br><br>References<br>[1]<b=
r>Authors:Philipp Richter and Florian Wohlfart and Narseo Vallina-Rodriguez=
 <br>and Mark Allman and Randy Bush and Anja Feldmann and Christian <br>Kre=
ibich and Nicholas Weaver and Vern Paxson<br>Title: A Multi-perspective Ana=
lysis of Carrier-Grade NAT Deployment<br>Conference: Proceedings of ACM IMC=
 2016<br>PDF: <a href=3D"https://net.t-labs.tu-berlin.de/~prichter/imc176-r=
ichterA.pdf">https://net.t-labs.tu-berlin.de/~prichter/imc176-richterA.pdf<=
/a><br><br>[2]<br>Authors: Stephen Checkoway and Jacob Maskiewicz and Chris=
tina<br>Garman and Joshua Fried and Shaanan Cohney and<br>Matthew Green and=
 Nadia Heninger and Ralf-Philipp<br>Weinmann and Eric Rescorla and Hovav Sh=
acham<br>Title: A Systematic Analysis of the Juniper Dual EC Incident<br>Co=
nference: Proceedings of CCS 2016<br>PDF: <a href=3D"https://www2.cs.uic.ed=
u/~s/papers/juniper2016/juniper2016.pdf">https://www2.cs.uic.edu/~s/papers/=
juniper2016/juniper2016.pdf</a><br><br><br><br></div></div>

--f403045dbe9476bd6205550f9e39--

