Hello e= veryone,

&n= bsp;

the sid= e meeting got scheduled for Tuesday, 18:50 – 20:20, in the Tegel room= .

&n= bsp;

This sh= ould allow people to still get to the social afterwards. There will be shut= tle buses.

&n= bsp;

The dra= ft agenda is below and also at https://trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation<= o:p>

&n= bsp;

If you = are interested in attending, please add your name to the attendees list on = the Wiki page (or unicast to me) – the room has limited capacity̷= 0;

&n= bsp;

Draf= t Agenda

Diego Lopez: Service Federation in 5G=
Carsten Bormann: Service Federation in IoT
Jeffrey He: Architecture Consideratio= n for Data Sharing, and Open Questions
Jon Crowcroft: Challenges of Federati= ng at Scale (tentative)
Ethereum presentation (tentative)<= /li>
Dirk Kutscher: Federation in ICN
Discussion of Next Steps

&n= bsp;

See you= in Berlin!

&n= bsp;

Dirk

&n= bsp;

Din [= mailto:din-bounces@irtf.org] On Behalf Of Dirk Kutscher
Sent: Freitag, 20. Mai 2016 12:46
To: irtf-announce@irtf.org
Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey= ) (jeffrey.he@huawei.com)
Subject: [Din] Distributed Data and Service Federation

Hello everyone,

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

The idea came out of discuss= ions in Buenos Aires on Blockchain and Distributed Internet (see Wiki linke= d below).

In case you are interested,<= o:p>

there is a Wiki page: https://trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation<= o:p>

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 meetin= g on Monday/Tuesday evening – if you’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.

Cheers,
Jeffrey, Carsten, Dirk<= /o:p>

1) Distributed Data and Serv= ice 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 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 "new oil" 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.

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.

This proposal aims to invest= igate a decentralized federation infrastructure to support such re-use of d= ata and services at Internet scale. 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.

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 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: "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"([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) l= ist of challenges and potential research topics:

-- data publishing/distribut= ion in an internet-wide federation, with protection of privacy, version con= trol;

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

-- data retrieval with secur= ity: the concept of "owner" of data, access control on data objec= ts, based on federated ID management/Authorization/Authorization, privilege= management;

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

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

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

-- information model reflect= ing the above considerations: data/metadata, owner of the data, etc.

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

Specifically, these question= s/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.pdf

[4] http://ec.europa.eu/resea= rch/participants/portal/desktop/en/opportunities/h2020/topics/5083-ict-12-2= 016.html