
From nobody Thu May 19 17:04:10 2016
Return-Path: <zsolt.pardi@gmail.com>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44DFB12D1D5 for <din@ietfa.amsl.com>; Thu, 19 May 2016 17:04:08 -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 atMuO4FmM9ew for <din@ietfa.amsl.com>; Thu, 19 May 2016 17:04:06 -0700 (PDT)
Received: from mail-lb0-x243.google.com (mail-lb0-x243.google.com [IPv6:2a00:1450:4010:c04::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E33812D177 for <din@irtf.org>; Thu, 19 May 2016 17:04:06 -0700 (PDT)
Received: by mail-lb0-x243.google.com with SMTP id r5so4735355lbj.3 for <din@irtf.org>; Thu, 19 May 2016 17:04:05 -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; bh=kcVIbS2NnSLZYOotNdjNERFgWcM6ZNVELY1jPluDk/c=; b=rX/t6Q6IfGD5LEpQKMo6z8aMNxtup0AMJ2cp/68JIU8oJ8sZcmhE/Y4cxmyEykVYSl b56cj/xMVpdZi7sj8aafpgZjHKuIpz+Y083espG1KeWZgT4sUdE2mWlszzsQzFkwnjwU OL11H/C/hU8dIBltkAJ9e688SVNsRnPycJKhex1/0Yop+/ifEpwYf0S8btrLlCp5+epW zg0pEJ603agbeFejEUeWKieHEbW7doKaP30wfLphKNcQYWlmPJ1zV3fhFoUIz3LimkOP mTeZKcb01AJqwQGGlPtdkn4iygqejOXxFMRMVeXPUtVTFvzZkKHvhIIPUcIsdX8WKsm9 NJFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=kcVIbS2NnSLZYOotNdjNERFgWcM6ZNVELY1jPluDk/c=; b=c8rYIRGXezPeZt9N7Bk3UW+E+TlHuaUhojIDXSLKqUIfBB6ensPcG/03bU3igSddqP GzEQ4OmtxXr1EliL3jZ4chIUf3KIE8s363HbTfpFi+QhjnKHNkeU02nrY21ptKaSzKfi Xyy5hBHY9Adv2KekFrKzbUYDn78pk5gNK972wrb4APa1LDqIRKiWwY45swlKhV0WuqHM N98gcXhNRPULA7ZUDzHuqT5m60GD6w7L5GH8tX5eaTx4dJCVuADse1Y3qor+r6HaXzTv rr1XUz/1I3PcCr0ST7tnkmc1sMjLTPP3GnmEl5f9+88fpLXNNo6Il3l8TKb2oaAMvqxT oipA==
X-Gm-Message-State: AOPr4FWjilRQId80iw3FXn1lNXfYxWWPH9axnALx+APrcGsS1AjE6OQ95D1OCdYv1Qg1n0UHjJ52KPy7vGnQYQ==
MIME-Version: 1.0
X-Received: by 10.112.205.69 with SMTP id le5mr34232lbc.138.1463702643830; Thu, 19 May 2016 17:04:03 -0700 (PDT)
Received: by 10.25.206.195 with HTTP; Thu, 19 May 2016 17:04:03 -0700 (PDT)
Date: Fri, 20 May 2016 01:04:03 +0100
Message-ID: <CAO3dM7=_nhQOF1zWzqeUK9p6PHS5OZ+9=1kZQ8U7Jit2Lt_cow@mail.gmail.com>
From: Zsolt Pardi <zsolt.pardi@gmail.com>
To: din@irtf.org
Content-Type: multipart/alternative; boundary=001a11c3c1be247a2005333ad431
Archived-At: <http://mailarchive.ietf.org/arch/msg/din/GnpCbLLk8ebZYSiE7Tmg5RoterY>
Subject: [Din] Decentralised, peer-to-peer approach
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 00:04:08 -0000

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

Hi

I just wanted to send this email to say a hello to the group as I have just
joined to the mailing list.

I have been participating at the W3C WoT Interest Group, my details are T Z
Pardi, public invited participant in the member list at
https://www.w3.org/2000/09/dbwg/details?group=75874&public=1.

I am trying to make progress in decentralised, peer-to-peer IoT and
blockchain related subjects within the group. I think there is consensus
within the industry that the decentralized approach is here to stay. Users
start to realize that decentralised computing addresses many
business/system requirements; scalability, high availability, confirming
data origin and accuracy, tracking updates, establishing true data
authority and ensuring privacy, and does this all in a relatively cost
effective manner. These are everyday problems for businesses and users. To
address scalability and high availability requirements is even more
pressuring problem for SMEs and new businesses (that need to build up their
infrastructure from scratch). I am also passionate about this technology
from software development viewpoint. I have been working with Bitcoin and
other blockchain techs for a while. I also wrote this whitepaper and it is
at http://streembit.github.io/downloads/streembit_whitepaper_v101.pdf . It
is related with a decentralized, peer-to-peer open source system I wrote
recently. I released the system 2 weeks ago, it is GNU licensed, so can be
used, copied, forked, etc. without any restriction.

I also started to work on a protocol which perhaps can grow to an IETF
standard. The industry probably will need a standard - currently, as many
large cryptocurrencies as much implementation. I thought it would be great
to create a collaboration which delivers a protocol. The protocol would
address contact discovery, transport and storage which are generic
functionalities and system components and these are not exclusive to IoT.
Currently the repo is at
https://github.com/w3c/web-of-things-framework/blob/master/documents/p2p/protocol.md.
I am not sure if anyone is interested to work on this? What would be the
repository if we work on the protocol? Would the repo stay at W3C or would
we use one of the IRTF repository?

Thanks for your time to read this and please let me know if you have any
questions.

Regards,
Tibor

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

<div dir=3D"ltr"><div>Hi</div><div><br></div><div>I just wanted to send thi=
s email to say a hello to the group as I have just joined to the mailing li=
st.</div><div><br></div><div>I have been participating at the W3C WoT Inter=
est Group, my details are T Z Pardi, public invited participant in the memb=
er list at <a href=3D"https://www.w3.org/2000/09/dbwg/details?group=3D75874=
&amp;public=3D1">https://www.w3.org/2000/09/dbwg/details?group=3D75874&amp;=
public=3D1</a>.</div><div><br></div><div>I am trying to make progress in de=
centralised, peer-to-peer IoT and blockchain related subjects within the gr=
oup. I think there is consensus within the industry that the decentralized =
approach is here to stay. Users start to realize that decentralised computi=
ng addresses many business/system requirements; scalability, high availabil=
ity, confirming data origin and accuracy, tracking updates, establishing tr=
ue data authority and ensuring privacy, and does this all in a relatively c=
ost effective manner. These are everyday problems for businesses and users.=
 To address scalability and high availability requirements is even more pre=
ssuring problem for SMEs and new businesses (that need to build up their in=
frastructure from scratch). I am also passionate about this technology from=
 software development viewpoint. I have been working with Bitcoin and other=
 blockchain techs for a while. I also wrote this whitepaper and it is at <a=
 href=3D"http://streembit.github.io/downloads/streembit_whitepaper_v101.pdf=
">http://streembit.github.io/downloads/streembit_whitepaper_v101.pdf</a> . =
It is related with a decentralized, peer-to-peer open source system I wrote=
 recently. I released the system 2 weeks ago, it is GNU licensed, so can be=
 used, copied, forked, etc. without any restriction.</div><div><br></div><d=
iv>I also started to work on a protocol which perhaps can grow to an IETF s=
tandard. The industry probably will need a standard - currently, as many la=
rge cryptocurrencies as much implementation. I thought it would be great to=
 create a collaboration which delivers a protocol. The protocol would addre=
ss contact discovery, transport and storage which are generic functionaliti=
es and system components and these are not exclusive to IoT. Currently the =
repo is at <a href=3D"https://github.com/w3c/web-of-things-framework/blob/m=
aster/documents/p2p/protocol.md">https://github.com/w3c/web-of-things-frame=
work/blob/master/documents/p2p/protocol.md</a>. I am not sure if anyone is =
interested to work on this? What would be the repository if we work on the =
protocol? Would the repo stay at W3C or would we use one of the IRTF reposi=
tory?</div><div><br></div><div>Thanks for your time to read this and please=
 let me know if you have any questions.</div><div><br></div><div>Regards,</=
div><div>Tibor</div><div><br></div></div>

--001a11c3c1be247a2005333ad431--


From nobody Fri May 20 03:46:27 2016
Return-Path: <Dirk.Kutscher@neclab.eu>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDBC212D74C; Fri, 20 May 2016 03:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.047
X-Spam-Level: 
X-Spam-Status: No, score=-4.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id slD_mqO19koi; Fri, 20 May 2016 03:46:07 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 580DC12D1B1; Fri, 20 May 2016 03:46:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id B2A671005BB; Fri, 20 May 2016 12:46:05 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRY-PEihRSNl; Fri, 20 May 2016 12:46:05 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 865581005AB; Fri, 20 May 2016 12:45:57 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.185]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.03.0210.002; Fri, 20 May 2016 12:45:36 +0200
From: Dirk Kutscher <Dirk.Kutscher@neclab.eu>
To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>
Thread-Topic: Distributed Data and Service Federation
Thread-Index: AdGygDWUU905ZLogQ8SubRrRWhlckg==
Date: Fri, 20 May 2016 10:45:35 +0000
Message-ID: <82AB329A76E2484D934BBCA77E9F5249AF307315@PALLENE.office.hd>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.7.0.197]
Content-Type: multipart/alternative; boundary="_000_82AB329A76E2484D934BBCA77E9F5249AF307315PALLENEofficehd_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/din/fpmkXlEoSwGRteTRHGrZajcXCao>
Cc: "Carsten Bormann \(cabo@tzi.org\)" <cabo@tzi.org>, "din@irtf.org" <din@irtf.org>, "Hejianfei \(Jeffrey\) \(jeffrey.he@huawei.com\)" <jeffrey.he@huawei.com>
Subject: [Din] Distributed Data and Service Federation
X-BeenThere: din@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/din>, <mailto:din-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din/>
List-Post: <mailto:din@irtf.org>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/din>, <mailto:din-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 May 2016 10:46:11 -0000
X-List-Received-Date: Fri, 20 May 2016 10:46:11 -0000

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

Hello everyone,



This a heads-up message for a side meeting we are planning on Distributed D=
ata and Service Federation at IETF-96.



The idea came out of discussions in Buenos Aires on Blockchain and Distribu=
ted Internet (see Wiki linked below).



In case you are interested,

there is a Wiki page: https://trac.tools.ietf.org/group/irtf/trac/wiki/bloc=
kchain-federation

and a mailing list: https://www.ietf.org/mailman/listinfo/din



Follow-up discussions should take place on the DIN mailing list.



We are planning for a meeting on Monday/Tuesday evening - if you'd like to =
attend, please unicast Jeffrey, Carsten and me, so that we get an idea how =
the required room size. Also, if you think you want to contribute, please l=
et us know.



Cheers,

Jeffrey, Carsten, Dirk





1) Distributed Data and Service Federation

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



Evolving network systems require resource and asset sharing beyond connecti=
vity and transit services as in today's networks. For example, in IoT scena=
rios such as Smart City, data is characterized as the "new oil" for future =
service and business development. In order to utilize data in new contexts,=
 it needs to be freed from application- or service-provider-specific silos.=
 From a user control and privacy perspective, this cannot be done with some=
 assurance on data usage policies and privacy guarantees [2]. Also, for exc=
hanging data between different business peers, for example between aggregat=
ion and application-specific processing and presentation, data ownership, u=
sage rights and authenticity needs to be assured.



Similarly, future mobile network architectures are being design with the id=
ea of layering different service layers [3], each provided by a unique prov=
ider in order to provide adequate facilities for different users and vertic=
al applications of the network. For example, a base connectivity layer woul=
d be employed by an MVNO that offers a richer service, or an ICN cache-and-=
forward infrastructure would be employed by a Mobile-TV service requiring s=
calable distribution of live and video-on-demand content.



This proposal aims to investigate a decentralized federation infrastructure=
 to support such re-use of data and services at Internet scale.  Instead of=
 centralized control of independent network and application silos, we envis=
ion a general, Internet-wide infrastructure for creating, managing and stor=
ing information about data and service federations. Such federations would =
be set up dynamically, i.e., on-demand, and secured in a way that allows ea=
sy verification.





2) Motivation

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



We think that now is a right time to start thinking about data sharing and =
service layering in a distributed fashion. Base technologies such as IoT ne=
tworking and ICN are reaching sufficient maturity levels for deployments. L=
inked Data initiatives are continuing to emerge, and research efforts such =
as 5GPPP are taking the next steps towards ad-hoc service create in layered=
 frameworks. Also, policy makers are calling for decentralized architecture=
s, e.g. in EU H2020:  "Current centralized platforms for big and social dat=
a management consolidate the dominance of existing incumbent actors, stifli=
ng innovation and allowing less and less control over the data by citizens.=
 Distributed architectures and decentralized platforms have a huge potentia=
l to enable the creation of viable alternatives to current dominant models"=
([4]).



3) Challenges, Potential Research Topics

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D



Here is a (non-exhaustive) list of challenges and potential research topics=
:



-- data publishing/distribution in an internet-wide federation, with protec=
tion of privacy, version control;

-- subscribing/searching to find the existing of the data, corresponding to=
 publishing/distribution mechanisms;

-- data retrieval with security: the concept of "owner" of data, access con=
trol on data objects, based on federated ID management/Authorization/Author=
ization, privilege management;

-- mechanisms enabling and encouraging data exchange/trade, e.g data anonym=
izing, data portability, etc. Blockchain may also be relevant here to provi=
de a distributed database for smart contract between non-trusting parties.

-- the ability to accommodate dynamic and evolving behavior, such as mobile=
 code;

-- semantic interoperability at different layers, e.g., as highlighted by [=
1]

-- information model reflecting the above considerations: data/metadata, ow=
ner of the data, etc.



At this point, we'd like to kick-off an inclusive discussion of interested =
members in the IRTF/IETF community.

Specifically, these questions/challenges may have connections to IETF ABFAB=
 WG, IRTF ICNRG, IRTF T2T RG among others.





[1] https://www.iab.org/wp-content/IAB-uploads/2016/03/formats.txt

[2] https://www.iab.org/wp-content/IAB-uploads/2016/03/draft-farrell-iotsi-=
00.txt

[3] https://5g-ppp.eu/wp-content/uploads/2015/10/5GPPP-brochure-final-web.p=
df

[4] http://ec.europa.eu/research/participants/portal/desktop/en/opportuniti=
es/h2020/topics/5083-ict-12-2016.html






--_000_82AB329A76E2484D934BBCA77E9F5249AF307315PALLENEofficehd_
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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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";
	mso-fareast-language:EN-US;}
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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@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=3D"DE" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Hello everyone,<o:p></o:p></=
span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">This a heads-up message for =
a side meeting we are planning on Distributed Data and Service Federation a=
t IETF-96.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">The idea came out of discuss=
ions in Buenos Aires on Blockchain and Distributed Internet (see Wiki linke=
d below).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">In case you are interested,<=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">there is a Wiki page: <a hre=
f=3D"https://trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation=
">
https://trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation</a><=
o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">and a mailing list: <a href=
=3D"https://www.ietf.org/mailman/listinfo/din">
https://www.ietf.org/mailman/listinfo/din</a><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Follow-up discussions should=
 take place on the DIN mailing list.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">We are planning for a meetin=
g on Monday/Tuesday evening &#8211; if you&#8217;d like to attend, please u=
nicast Jeffrey, Carsten and me, so that we get an idea how the required roo=
m size. Also, if you think you want to contribute,
 please let us know.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Cheers,<o:p></o:p></span></p=
>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Jeffrey, Carsten, Dirk<o:p><=
/o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">1) Distributed Data and Serv=
ice Federation<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Evolving network systems req=
uire resource and asset sharing beyond connectivity and transit services as=
 in today's networks. For example, in IoT scenarios such as Smart City, dat=
a is characterized as the &quot;new oil&quot;
 for future service and business development. In order to utilize data in n=
ew contexts, it needs to be freed from application- or service-provider-spe=
cific silos. From a user control and privacy perspective, this cannot be do=
ne with some assurance on data usage
 policies and privacy guarantees [2]. Also, for exchanging data between dif=
ferent business peers, for example between aggregation and application-spec=
ific processing and presentation, data ownership, usage rights and authenti=
city needs to be assured.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Similarly, future mobile net=
work architectures are being design with the idea of layering different ser=
vice layers [3], each provided by a unique provider in order to provide ade=
quate facilities for different users
 and vertical applications of the network. For example, a base connectivity=
 layer would be employed by an MVNO that offers a richer service, or an ICN=
 cache-and-forward infrastructure would be employed by a Mobile-TV service =
requiring scalable distribution
 of live and video-on-demand content.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">This proposal aims to invest=
igate a decentralized federation infrastructure to support such re-use of d=
ata and services at Internet scale.&nbsp; Instead of centralized control of=
 independent network and application silos,
 we envision a general, Internet-wide infrastructure for creating, managing=
 and storing information about data and service federations. Such federatio=
ns would be set up dynamically, i.e., on-demand, and secured in a way that =
allows easy verification.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">2) Motivation<o:p></o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">We think that now is a right=
 time to start thinking about data sharing and service layering in a distri=
buted fashion. Base technologies such as IoT networking and ICN are reachin=
g sufficient maturity levels for deployments.
 Linked Data initiatives are continuing to emerge, and research efforts suc=
h as 5GPPP are taking the next steps towards ad-hoc service create in layer=
ed frameworks. Also, policy makers are calling for decentralized architectu=
res, e.g. in EU H2020:&nbsp; &quot;Current
 centralized platforms for big and social data management consolidate the d=
ominance of existing incumbent actors, stifling innovation and allowing les=
s and less control over the data by citizens. Distributed architectures and=
 decentralized platforms have a
 huge potential to enable the creation of viable alternatives to current do=
minant models&quot;([4]).
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText">3) Challenges, Potential Research Topics<o:p></o:=
p></p>
<p class=3D"MsoPlainText">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Here is a (non-exhaustive) l=
ist of challenges and potential research topics:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-- data publishing/distribut=
ion in an internet-wide federation, with protection of privacy, version con=
trol;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-- subscribing/searching to =
find the existing of the data, corresponding to publishing/distribution mec=
hanisms;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-- data retrieval with secur=
ity: the concept of &quot;owner&quot; of data, access control on data objec=
ts, based on federated ID management/Authorization/Authorization, privilege=
 management;
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-- mechanisms enabling and e=
ncouraging data exchange/trade, e.g data anonymizing, data portability, etc=
. Blockchain may also be relevant here to provide a distributed database fo=
r smart contract between non-trusting
 parties. <o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-- the ability to accommodat=
e dynamic and evolving behavior, such as mobile code;<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-- semantic interoperability=
 at different layers, e.g., as highlighted by [1]<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">-- information model reflect=
ing the above considerations: data/metadata, owner of the data, etc.<o:p></=
o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">At this point, we'd like to =
kick-off an inclusive discussion of interested members in the IRTF/IETF com=
munity.
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Specifically, these question=
s/challenges may have connections to IETF ABFAB WG, IRTF ICNRG, IRTF T2T RG=
 among others.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">[1] </span><a href=3D"https:=
//www.iab.org/wp-content/IAB-uploads/2016/03/formats.txt"><span lang=3D"EN-=
US">https://www.iab.org/wp-content/IAB-uploads/2016/03/formats.txt</span></=
a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">[2] </span><a href=3D"https:=
//www.iab.org/wp-content/IAB-uploads/2016/03/draft-farrell-iotsi-00.txt"><s=
pan lang=3D"EN-US">https://www.iab.org/wp-content/IAB-uploads/2016/03/draft=
-farrell-iotsi-00.txt</span></a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">[3] </span><a href=3D"https:=
//5g-ppp.eu/wp-content/uploads/2015/10/5GPPP-brochure-final-web.pdf"><span =
lang=3D"EN-US">https://5g-ppp.eu/wp-content/uploads/2015/10/5GPPP-brochure-=
final-web.pdf</span></a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">[4] </span><a href=3D"http:/=
/ec.europa.eu/research/participants/portal/desktop/en/opportunities/h2020/t=
opics/5083-ict-12-2016.html"><span lang=3D"EN-US">http://ec.europa.eu/resea=
rch/participants/portal/desktop/en/opportunities/h2020/topics/5083-ict-12-2=
016.html</span></a><span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_82AB329A76E2484D934BBCA77E9F5249AF307315PALLENEofficehd_--

