
From nobody Wed Jul  2 01:49:25 2014
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3140B1A019D for <irtf-discuss@ietfa.amsl.com>; Wed,  2 Jul 2014 01:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.553
X-Spam-Level: 
X-Spam-Status: No, score=-7.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpnDOB4UQsvv for <irtf-discuss@ietfa.amsl.com>; Wed,  2 Jul 2014 01:49:23 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 029741A005E for <irtf-discuss@irtf.org>; Wed,  2 Jul 2014 01:49:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,587,1400050800";  d="asc'?scan'208";a="132031449"
Received: from vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) by mx11-out.netapp.com with ESMTP; 02 Jul 2014 01:49:21 -0700
Received: from HIOEXCMBX05-PRD.hq.netapp.com (10.122.105.38) by vmwexceht03-prd.hq.netapp.com (10.106.76.241) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 2 Jul 2014 01:49:21 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.847.32; Wed, 2 Jul 2014 01:49:20 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::8485:306a:80a6:ba8f%21]) with mapi id 15.00.0847.030; Wed, 2 Jul 2014 01:49:02 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: Request for IETF Mentoring Program Volunteers
Thread-Index: AQHPlX7qHa8SwjMxHkC4F86PPAKcBQ==
Date: Wed, 2 Jul 2014 08:49:02 +0000
Message-ID: <8BCA92F2-41DA-4DEC-8520-2BC8ED97CD6E@netapp.com>
References: <20140701225030.3233.40394.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.120.60.36]
Content-Type: multipart/signed; boundary="Apple-Mail=_436EC8E7-9931-4F40-887D-D2FD63EA631C"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/e1MpW2xtbIsLQG0yMN8tsjMudsU
Subject: [irtf-discuss] Fwd: Request for IETF Mentoring Program Volunteers
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
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: <http://www.irtf.org/mail-archive/web/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, 02 Jul 2014 08:49:24 -0000

--Apple-Mail=_436EC8E7-9931-4F40-887D-D2FD63EA631C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Some new participants come for IRTF RGs. It would therefore be good to =
have mentors with IRTF experience in the pool. Please volunteer.

Begin forwarded message:

> From: IETF Chair <chair@ietf.org>
> Subject: Request for IETF Mentoring Program Volunteers
> Date: July 2, 2014 at 0:50:30 GMT+2
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: <ietf@ietf.org>
> Reply-To: <ietf@ietf.org>
>=20
> Hi all,
>=20
> In Toronto we will once again be running the IETF Mentoring Program. =
We
> will be pairing IETF participants who are new or otherwise in need of
> guidance with existing IETF participants. Unlike at previous meetings,
> anyone will be able to sign up for a mentor regardless of how many
> meetings they have attended. The goal is to provide a resource for
> participants that can assist them with integrating into the IETF
> community.  Mentors and newcomers will be paired prior to IETF 90.
>=20
> We're seeking IETF participants to volunteer to be mentors. As a =
mentor,
> we would ask that you be willing to assist your mentoring participant
> before, during, and (hopefully) after IETF 90.  The actual level of
> interaction will be driven by an agreement between the mentor and the
> mentoring participant. Additionally, we would need a brief description =
of
> your areas of expertise, technical interests, and conversational =
languages.
>=20
> A description of the Mentor Program (including a FAQ describing
> how to volunteer to be a mentor) is available:
>=20
> http://www.ietf.org/resources/mentoring-program.html.
>=20
> Anyone interested in being a mentor who has not previously signed up
> should follow the sign-up instructions contained in the above URL. If =
you
> have previously signed up as a mentor, you do not need to sign up and =
you
> should have received an email requesting that you confirm whether you =
will
> be available to mentor in Toronto.
>=20
> Please consider volunteering. The more volunteers we have, the =
stronger
> the program will be!
>=20
> Regards,
> Jari Arkko
> IETF Chair
>=20


--Apple-Mail=_436EC8E7-9931-4F40-887D-D2FD63EA631C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQCVAwUBU7PHfNZcnpRveo1xAQJXDQP9FBQNpvVXCmZgnR4bC2MartbSvAN/U6RS
08F50L1G4ek8HDs4aR7Liat49xE/ju8/0nOt0w48WtTR9Cd90+H5LjbPupEn0Dhj
ye6r+qH4Ils+8lDsNdD5zUP+MYtAOd5OfaCiZn5tcNTNN4fTzkNoAecMn5vjqsvE
6zN24bgnoRA=
=ZpM7
-----END PGP SIGNATURE-----

--Apple-Mail=_436EC8E7-9931-4F40-887D-D2FD63EA631C--


From nobody Wed Jul 16 01:26:04 2014
Return-Path: <pascal.urien@gmail.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89B641B29E4 for <irtf-discuss@ietfa.amsl.com>; Wed, 16 Jul 2014 01:26: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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fHuuUmKnECOQ for <irtf-discuss@ietfa.amsl.com>; Wed, 16 Jul 2014 01:26:02 -0700 (PDT)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7F021A0322 for <irtf-discuss@irtf.org>; Wed, 16 Jul 2014 01:26:01 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id x3so467557qcv.9 for <irtf-discuss@irtf.org>; Wed, 16 Jul 2014 01:26:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=OZp4KB6R86tp90n4Pdxx9PcfyT++aL7ZWMRxsCCAN4w=; b=Og1mKLuWp4dBj0UXLcAEfWSFX/7LC9n72Im6ZFEffRsoz+MStxGOmPRPxlUB8NJVZk woWS9Fqr9FG2ohVoVH+VFFn2+DreyaoUpWdsFA8LkgWwWp9WWxYC7o4eD9TYkOEv/w0v Hq0wTADvSZuqSrg/wB8klX+tfbmkSmlfpLiEaOz779mKMTxOwTgF5uhYfE1/8ucA4Ojp C1YDXXrgxZg6niV8/nS5u2PxVil9gxZn+k5KLTNPRgXvy98GvGdJnzjJtPrw4pBESy9m qXDBUrLorq1TNZfZEc3i4dAK+hvrV70Rkq2+TjDqeYTaywuwAVDEfQq88Xu0om3oTkF8 c/Cw==
MIME-Version: 1.0
X-Received: by 10.224.115.3 with SMTP id g3mr43758956qaq.9.1405499160981; Wed, 16 Jul 2014 01:26:00 -0700 (PDT)
Received: by 10.96.194.225 with HTTP; Wed, 16 Jul 2014 01:26:00 -0700 (PDT)
Date: Wed, 16 Jul 2014 10:26:00 +0200
Message-ID: <CAEQGKXSM3DQdMisB=y=qVG2QjSML2cHYrESaAzL_xxDy_kv6wA@mail.gmail.com>
From: Pascal Urien <pascal.urien@gmail.com>
To: irtf-discuss@irtf.org
Content-Type: multipart/alternative; boundary=047d7bdc96b038f7ae04fe4b46af
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/3JF7YIRIQhVf0W8neHO0ZJBNmsc
Cc: Pascal Urien <pascal.urien@telecom-paristech.fr>
Subject: [irtf-discuss] Secure Elements in the cloud...
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
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: <http://www.irtf.org/mail-archive/web/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, 16 Jul 2014 08:26:03 -0000

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

Dear All

During the IRTF open meeting, (IETF 90, Tuesday 22 july), i would like to
introduce the idea of trust for internet applications and internet users,
based on secure elements hosted in the cloud

This concept is illustrated by the draft
http://tools.ietf.org/html/draft-urien-cfrg-cose-00.

The main idea is to deploy over the internet secure elements, hosted by
Trusted Secure Element Servers (TSES), which could be used and managed by
human or software entities. This functional granularity is a key feature
for the proposed paradigm called CoSE (Cloud of Secure Elements).

 The CoSE is a kind of WEB for secure elements, able to deliver secure
storage or cryptographic services. Secure element are identified by a
server (TSES) name, a port and a unique identifier (SEID, the secure
element identifier), i.e Server:Port/SEID

 To be practical we work today with ISO7816 tamper resistant chips, which
are manufactured per billions and used for payments, access control and
various cryptographic purposes. These chips generally include a Java
Virtual Machine (JVM) and therefore can run various applications.
Furthermore open standards are available to manage their contents.

A first protocol named RACS see
http://tools.ietf.org/html/draft-urien-core-racs-03 is under definition and
is already tested by several implementations, which are online and can be
demonstrated

The URI associated to a secure element hosted is the cloud is consequently
RACS://Server:Port/SEID

 It should be great to share this vision with people caring with internet
trust for both users and applications.
What about a working group ?
Regards
Pascal Urien

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

<div dir=3D"ltr"><p style=3D"margin:0cm 0cm 10pt"><span lang=3D"FR"><font c=
olor=3D"#000000" face=3D"Calibri" size=3D"3">Dear All</font></span></p><fon=
t color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=3D"=
margin:0cm 0cm 10pt">

 <span><font color=3D"#000000" face=3D"Calibri" size=3D"3">During the IRTF =
open meeting, (IETF 90, Tuesday 22 july),=C2=A0i would like to introduce th=
e idea of trust for internet applications and internet users, based on secu=
re elements hosted in the cloud</font></span></p>

<font color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=
=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" siz=
e=3D"3">This concept is illustrated by the draft </font><a href=3D"http://t=
ools.ietf.org/html/draft-urien-cfrg-cose-00" target=3D"_blank"><font color=
=3D"#0000ff" face=3D"Calibri" size=3D"3">http://tools.ietf.org/html/draft-u=
rien-cfrg-cose-00</font></a><font color=3D"#000000" face=3D"Calibri" size=
=3D"3">.</font></span></p>

<font color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=
=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" siz=
e=3D"3">The main idea is to deploy over the internet secure elements, hoste=
d by Trusted Secure Element Servers (TSES), which could be used and managed=
 by human or software entities. This functional granularity is a key featur=
e for the proposed paradigm called CoSE (Cloud of Secure Elements).</font><=
/span></p>

<font color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=
=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" siz=
e=3D"3">=C2=A0</font></span><span><font color=3D"#000000" face=3D"Calibri" =
size=3D"3">The CoSE is a kind of WEB for secure elements, able to deliver s=
ecure storage or cryptographic services. Secure element are identified by a=
 server (TSES) name, a port and a unique identifier (SEID, the secure eleme=
nt identifier), i.e Server:Port/SEID</font></span></p>

<font color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=
=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" siz=
e=3D"3">=C2=A0</font></span><span><font color=3D"#000000" face=3D"Calibri" =
size=3D"3">To be practical we work today with ISO7816 tamper resistant chip=
s, which are manufactured per billions and used for payments, access contro=
l and various cryptographic purposes. These chips generally include a Java =
Virtual Machine (JVM) and therefore can run various applications. Furthermo=
re open standards are available to manage their contents.</font></span></p>

<font color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=
=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" siz=
e=3D"3">A first protocol named RACS see </font><a href=3D"http://tools.ietf=
.org/html/draft-urien-core-racs-03" target=3D"_blank"><font color=3D"#0000f=
f" face=3D"Calibri" size=3D"3">http://tools.ietf.org/html/draft-urien-core-=
racs-03</font></a><font color=3D"#000000" face=3D"Calibri" size=3D"3"> is u=
nder definition and is already tested by several implementations, which are=
 online and can be demonstrated</font></span></p>

<font color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=
=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" siz=
e=3D"3">The URI associated to a secure element hosted is the cloud is conse=
quently RACS://Server:Port/SEID</font></span></p>

<font color=3D"#000000" face=3D"Times New Roman" size=3D"3"></font><p style=
=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" siz=
e=3D"3">=C2=A0</font></span><span><font color=3D"#000000" face=3D"Calibri" =
size=3D"3">It should be great to share this vision with people caring with =
internet trust for both users and applications. </font></span></p>

<div style=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Ca=
libri" size=3D"3">What about a working group ?</font></span></div><div styl=
e=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" si=
ze=3D"3">Regards</font></span></div>
<div style=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Ca=
libri" size=3D"3">Pascal Urien</font></span></div><div style=3D"margin:0cm =
0cm 10pt"><span><font color=3D"#000000" face=3D"Calibri" size=3D"3"></font>=
</span><br></div>
<div style=3D"margin:0cm 0cm 10pt"><span><font color=3D"#000000" face=3D"Ca=
libri" size=3D"3"></font></span><br></div></div>

--047d7bdc96b038f7ae04fe4b46af--


From nobody Wed Jul 16 01:56:49 2014
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D121B2AE5 for <irtf-discuss@ietfa.amsl.com>; Wed, 16 Jul 2014 01:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.887
X-Spam-Level: 
X-Spam-Status: No, score=-6.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHJJrka5cH5h for <irtf-discuss@ietfa.amsl.com>; Wed, 16 Jul 2014 01:56:44 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CE661B2AF6 for <irtf-discuss@irtf.org>; Wed, 16 Jul 2014 01:56:44 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,670,1400050800";  d="asc'?scan'208";a="176305543"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx12-out.netapp.com with ESMTP; 16 Jul 2014 01:56:27 -0700
Received: from HIOEXCMBX02-PRD.hq.netapp.com (10.122.105.35) by vmwexceht06-prd.hq.netapp.com (10.106.77.104) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 16 Jul 2014 01:56:26 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.913.22; Wed, 16 Jul 2014 01:56:17 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::8485:306a:80a6:ba8f%21]) with mapi id 15.00.0847.030; Wed, 16 Jul 2014 01:56:17 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Thread-Topic: Final Agenda for IRTF Open Meeting at IETF-90
Thread-Index: AQHPoNPNFaS7Ju6bm0+2TFOsPjfBSQ==
Date: Wed, 16 Jul 2014 08:56:16 +0000
Message-ID: <0BAEBE4D-22CF-4D24-A3C7-980EC7919E78@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.122.56.79]
Content-Type: multipart/signed; boundary="Apple-Mail=_A5ABFDC1-1B01-480E-A25C-1106C5549029"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/aWmDJoe01Q45RDe2Kydv6O8RdN4
Subject: [irtf-discuss] Final Agenda for IRTF Open Meeting at IETF-90
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
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: <http://www.irtf.org/mail-archive/web/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, 16 Jul 2014 08:56:47 -0000

--Apple-Mail=_A5ABFDC1-1B01-480E-A25C-1106C5549029
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

http://www.ietf.org/proceedings/90/agenda/agenda-90-irtfopen

Final Agenda
IRTF Open Meeting @ IETF-90
Toronto, Canada
TUESDAY, July 22, 2014
1420-1620 EDT  Tuesday Afternoon Session II

State of the IRTF
  Lars Eggert
  10 min

Applied Networking Prize (ANRP) Award Talk
  45 min

  *** Robert Lychev *** for studying the security benefits provided
  by partially-deployed S*BGP:

    Robert Lychev, Sharon Goldberg and Michael Schapira. BGP
    Security in Partial Deployment. Proc. ACM SIGCOMM, Hong Kong,
    China, August 2013.

    We use theoretical and experimental approach to study the security
    benefits provided by partially-deployed S*BGP, vis-a-vis those already
    provided by origin authentication. We find that S*BGP provides only
    meagre benefits over origin au- thentication when these popular policies
    are used.

  (Misbah Uddin will present at IETF-91 due to visa issues.)

Towards Quantum-Safe Cryptography
  Michele Mosca
  45 min

  Cryptographic tools, such as key establishment and signatures, are a
  fundamental part of the information security infrastructure. Quantum
  computers will eventually break most of the currently deployed public-key
  signature and key establishment tools. Are we ready? It is critical that
  robust implementations of quantum-safe alternatives to these tools are
  deployed before quantum computers break them. I will discuss the risk of
  this catastrophic event, the potential solutions, and the path to quantum-
  proofing the cryptographic infrastructure.

--Apple-Mail=_A5ABFDC1-1B01-480E-A25C-1106C5549029
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQCVAwUBU8Y+MNZcnpRveo1xAQLhXQP9EF7f4N1yFN+BIbuWZaw0q0KM6HyOJVgH
YHxVnkJkYl2l6RLSpFkw33/Ona9AgvmTMfUW/NIfbDV7rDjg8LUNrLBDJ/uDsgGr
zgXWkTw7ObP6u+VygNyIInbuEXoIC/mwh5f3KpPcCeTyuxRfXgVI2+EK2MV1/ruO
My++AEVXAPs=
=Y8Qk
-----END PGP SIGNATURE-----

--Apple-Mail=_A5ABFDC1-1B01-480E-A25C-1106C5549029--


From nobody Thu Jul 31 16:04:51 2014
Return-Path: <m.waehlisch@fu-berlin.de>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FAAE1A0252 for <irtf-discuss@ietfa.amsl.com>; Thu, 31 Jul 2014 16:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.229
X-Spam-Level: *
X-Spam-Status: No, score=1.229 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iDkdE09P6eW1 for <irtf-discuss@ietfa.amsl.com>; Thu, 31 Jul 2014 16:04:48 -0700 (PDT)
Received: from mail1.rz.htw-berlin.de (mail1.rz.htw-berlin.de [141.45.10.101]) (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 054B91A01FF for <irtf-discuss@irtf.org>; Thu, 31 Jul 2014 16:04:48 -0700 (PDT)
Envelope-to: irtf-discuss@irtf.org
Received: from g231108228.adsl.alicedsl.de ([92.231.108.228] helo=mw-PC.fritz.box) by mail1.rz.htw-berlin.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from <m.waehlisch@fu-berlin.de>) id 1XCzOw-000OIH-3z for irtf-discuss@irtf.org; Fri, 01 Aug 2014 01:04:46 +0200
Date: Fri, 1 Aug 2014 01:03:53 +0200
From: Matthias Waehlisch <m.waehlisch@fu-berlin.de>
To: irtf-discuss@irtf.org
Message-ID: <alpine.WNT.2.00.1408010103180.10500@mw-PC>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
X-X-Sender: mw@mail1.rz.htw-berlin.de
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: irtf-discuss@irtf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/5Zae_3m75iBDB5VDN6oXnxHRvZY
Subject: [irtf-discuss] Active vs. little activity RGs
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
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: <http://www.irtf.org/mail-archive/web/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, 31 Jul 2014 23:04:49 -0000

Hi Lars,

  there is something that puzzles me since several IETF/IRTF meetings. 
In the IRTF report, you usually categorize RGs into "Active" and "Little 
activity". As argumentation at ICNRG is currently based on this, it 
would be very helpful to have a definition of what this means in detail.



Thanks
  matthias

-- 
Matthias Waehlisch
.  Freie Universitaet Berlin, Inst. fuer Informatik, AG CST
.  Takustr. 9, D-14195 Berlin, Germany
.. mailto:waehlisch@ieee.org .. http://www.inf.fu-berlin.de/~waehl
:. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net


From nobody Thu Jul 31 23:56:20 2014
Return-Path: <lars@netapp.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0AA31A0415 for <irtf-discuss@ietfa.amsl.com>; Thu, 31 Jul 2014 23:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level: 
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6itvsN_S0ivH for <irtf-discuss@ietfa.amsl.com>; Thu, 31 Jul 2014 23:56:14 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 474281A040F for <irtf-discuss@irtf.org>; Thu, 31 Jul 2014 23:56:14 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,778,1400050800";  d="asc'?scan'208";a="179397322"
Received: from vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) by mx12-out.netapp.com with ESMTP; 31 Jul 2014 23:56:14 -0700
Received: from HIOEXCMBX03-PRD.hq.netapp.com (10.122.105.36) by vmwexceht05-prd.hq.netapp.com (10.106.77.35) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 31 Jul 2014 23:56:14 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by hioexcmbx03-prd.hq.netapp.com (10.122.105.36) with Microsoft SMTP Server (TLS) id 15.0.913.22; Thu, 31 Jul 2014 23:56:13 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com ([::1]) by hioexcmbx07-prd.hq.netapp.com ([fe80::39bf:b832:59af:53b9%21]) with mapi id 15.00.0913.011; Thu, 31 Jul 2014 23:56:12 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Matthias Waehlisch <m.waehlisch@fu-berlin.de>
Thread-Topic: [irtf-discuss] Active vs. little activity RGs
Thread-Index: AQHPrRPYM4OqpeIMkUaFS3pU4IH4/5u7xogA
Date: Fri, 1 Aug 2014 06:56:12 +0000
Message-ID: <46B1C387-D0AF-48E6-B818-866198E6DA8F@netapp.com>
References: <alpine.WNT.2.00.1408010103180.10500@mw-PC>
In-Reply-To: <alpine.WNT.2.00.1408010103180.10500@mw-PC>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.1878.6)
x-originating-ip: [10.122.56.79]
Content-Type: multipart/signed; boundary="Apple-Mail=_FB0440B2-D44C-4065-BEE1-BF944DD21F77"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/irtf-discuss/v_Ha7dnmFRhbbiOZ8EjzkmcBvO8
Cc: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>
Subject: Re: [irtf-discuss] Active vs. little activity RGs
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.15
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: <http://www.irtf.org/mail-archive/web/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: Fri, 01 Aug 2014 06:56:18 -0000

--Apple-Mail=_FB0440B2-D44C-4065-BEE1-BF944DD21F77
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2014-8-1, at 1:03, Matthias Waehlisch <m.waehlisch@fu-berlin.de> =
wrote:
>  there is something that puzzles me since several IETF/IRTF meetings.=20=

> In the IRTF report, you usually categorize RGs into "Active" and =
"Little=20
> activity". As argumentation at ICNRG is currently based on this, it=20
> would be very helpful to have a definition of what this means in =
detail.

so that slide is highly subjective, and it does have errors sometime =
(like ICNRG in the last slide set.)

I am thinking about getting rid of it completely in my chair report, or =
maybe simplifying it to "active" and "dormant".

Lars

--Apple-Mail=_FB0440B2-D44C-4065-BEE1-BF944DD21F77
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQCVAwUBU9s6CNZcnpRveo1xAQIxNwQAj1dMmmTzjywRZ0rac2YK0Hxp2lUdid/y
fMWKmm5hRn1ymnHBwrr1fLgGxgkw36OtfoEugO3erHcdLd3/vJjYVdcy1iWLpvfJ
jRAMhjOKdjgvG6OMsm3RzELjQ/UPJ8GRzp652yhw9pz/8At70UZDS5JLSMCNANpx
jisoNKFfUU4=
=yOHT
-----END PGP SIGNATURE-----

--Apple-Mail=_FB0440B2-D44C-4065-BEE1-BF944DD21F77--

