From nobody Thu Aug 11 06:31:10 2016 Return-Path: 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 6C23A12D0E5 for ; Thu, 11 Aug 2016 06:31:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.468 X-Spam-Level: X-Spam-Status: No, score=-2.468 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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.247, 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 GOPOgwtE6QvT for ; Thu, 11 Aug 2016 06:31:06 -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 56DFF12D581 for ; Thu, 11 Aug 2016 06:31:06 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 830D7100FAF for ; Thu, 11 Aug 2016 15:31:04 +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 t9BI8onBlfOd for ; Thu, 11 Aug 2016 15:31:04 +0200 (CEST) X-ENC: Last-Hop-TLS-encrypted X-ENC: Last-Hop-TLS-encrypted Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 61768100F64 for ; Thu, 11 Aug 2016 15:31:02 +0200 (CEST) Received: from PALLENE.office.hd ([169.254.1.198]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.03.0301.000; Thu, 11 Aug 2016 15:31:02 +0200 From: Dirk Kutscher To: "din@irtf.org" Thread-Topic: HAT project Thread-Index: AdHz1FX+2D88j+29Rmm0Fd+zbaIBqg== Date: Thu, 11 Aug 2016 13:31:01 +0000 Message-ID: <82AB329A76E2484D934BBCA77E9F5249AF445D95@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.1.2.102] Content-Type: multipart/alternative; boundary="_000_82AB329A76E2484D934BBCA77E9F5249AF445D95PALLENEofficehd_" MIME-Version: 1.0 Archived-At: Subject: [Din] HAT project 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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2016 13:31:09 -0000 --_000_82AB329A76E2484D934BBCA77E9F5249AF445D95PALLENEofficehd_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, in case you have not seen it, the HAT (Hub of all Things) project is IMO re= lated to the distributed data federation discussion we had in this context: http://www.hatdex.org/ Cheers, Dirk --_000_82AB329A76E2484D934BBCA77E9F5249AF445D95PALLENEofficehd_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

in case you have not seen it, t= he HAT (Hub of all Things) project is IMO related to the distributed data f= ederation discussion we had in this context:

 

http://www.hatdex.org/

 

Cheers,

Dirk

--_000_82AB329A76E2484D934BBCA77E9F5249AF445D95PALLENEofficehd_-- From nobody Wed Aug 17 05:32:03 2016 Return-Path: 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 6582F12D67C; Wed, 17 Aug 2016 05:32:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.868 X-Spam-Level: X-Spam-Status: No, score=-3.868 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.247, 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 EedDR2uBZErz; Wed, 17 Aug 2016 05:31:58 -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 0510012D670; Wed, 17 Aug 2016 05:31:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 201E0101055; Wed, 17 Aug 2016 14:31:56 +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 9XBtNWKCTn-e; Wed, 17 Aug 2016 14:31:55 +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 E701B100FB0; Wed, 17 Aug 2016 14:31:47 +0200 (CEST) Received: from PALLENE.office.hd ([169.254.1.198]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.03.0301.000; Wed, 17 Aug 2016 14:31:47 +0200 From: Dirk Kutscher To: "din@irtf.org" , Dirk Kutscher , "irtf-announce@irtf.org" Thread-Topic: Distributed Data and Service Federation Thread-Index: AdGygDWUU905ZLogQ8SubRrRWhlckgdpwjzAA2qUWFAAuje9EAEGd+GgBOu2hnA= Date: Wed, 17 Aug 2016 12:31:47 +0000 Message-ID: <82AB329A76E2484D934BBCA77E9F5249AF455BED@PALLENE.office.hd> References: <82AB329A76E2484D934BBCA77E9F5249AF307315@PALLENE.office.hd> <82AB329A76E2484D934BBCA77E9F5249AF376A9F@PALLENE.office.hd> <82AB329A76E2484D934BBCA77E9F5249AF3807AF@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.1.2.102] Content-Type: multipart/alternative; boundary="_000_82AB329A76E2484D934BBCA77E9F5249AF455BEDPALLENEofficehd_" MIME-Version: 1.0 Archived-At: Cc: "Carsten Bormann \(cabo@tzi.org\)" , "Hejianfei \(Jeffrey\) \(jeffrey.he@huawei.com\)" Subject: Re: [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" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2016 12:32:02 -0000 --_000_82AB329A76E2484D934BBCA77E9F5249AF455BEDPALLENEofficehd_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, there were some issues with storing attachments on the Trac server, so I mo= ved the presentations from Berlin to github and updated the links at https:= //trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation Cheers, Dirk From: Dirk Kutscher Sent: Samstag, 23. Juli 2016 13:51 To: 'Dirk Kutscher'; irtf-announce@irtf.org Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey) (jeff= rey.he@huawei.com) Subject: RE: Distributed Data and Service Federation Hi everyone, I hope you make it all home safely. I finally got to uploading the presenta= tions from Tuesday. https://trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation Thanks to all presented and to everyone who participated - we had pretty g= ood attendance and got good input in the discussion. I also added a link to a relevant presentation by Jon to the Wiki page. Unf= ortunately he wasn't able to make it to Berlin in the end, and we did not h= ave time to talk about this at the meeting but this is touching on some of = the points we discussed (scope, scalability). I took some notes that are on the last slide of my presentation. My personal summary: There seems to be something around decentralizing Internet infrastructure t= hat people find interesting and important. The use cases we discussed were = quite heterogeneous (decentralizing Internet infrastructure, service federa= tion, IoT etc.). There are other topics we mentioned only briefly on Tuesd= ay, i.e., the Distributed Web activities, the connection to ICN etc. As next steps, I suggest that we try to scope this to something focused eno= ugh to have constructive work/discussions in the future. One suggestion tha= t was made was to focus on decentralizing today's Internet infrastructure. = I personally think that this might be a little too limited, considering the= IoT requirements (for example). It would be great to get more opinions on that so that we frame the discuss= ion better (for example for upcoming meetings). Please discuss on din@irtf.org. Thanks, Dirk From: Din [mailto:din-bounces@irtf.org] On Behalf Of Dirk Kutscher Sent: Montag, 18. Juli 2016 08:10 To: irtf-announce@irtf.org Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey) (jeffrey.he@huawei.com) Subject: Re: [Din] Distributed Data and Service Federation Agenda update: Coordinates * Date & Time: Tuesday, July 19, 18:50 -- 20:20 * Room: Tegel Agenda * Diego Lopez: Service Federation in 5G * Carsten Bormann: Service Federation in IoT * Thomas Scheffler: A Privacy Aware Localization Service for Healthcare= Environments * Jeffrey He: Architecture Consideration for Data Sharing, and Open Que= stions * Discussion of Next Steps See you tomorrow, Dirk From: Din [mailto:din-bounces@irtf.org] On Behalf Of Dirk Kutscher Sent: Donnerstag, 14. Juli 2016 15:15 To: irtf-announce@irtf.org Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey) (jeffrey.he@huawei.com) Subject: Re: [Din] Distributed Data and Service Federation Hello, friendly reminder of the meeting next week Tuesday. You can still go to the= social afterwards. Coordinates * Date & Time: Tuesday, July 19, 18:50 -- 20:20 * Room: Tegel Draft Agenda * Diego Lopez: Service Federation in 5G * Carsten Bormann: Service Federation in IoT * Jeffrey He: Architecture Consideration for Data Sharing, and Open Que= stions * Ethereum presentation (tentative) * Dirk Kutscher: Federation in ICN * Discussion of Next Steps Best regards, Dirk Kutscher From: Dirk Kutscher Sent: Montag, 27. Juni 2016 05:58 To: 'Dirk Kutscher'; irtf-announce@irtf.org Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey) (jeffrey.he@huawei.com) Subject: RE: Distributed Data and Service Federation Hello everyone, the side meeting got scheduled for Tuesday, 18:50 - 20:20, in the Tegel roo= m. This should allow people to still get to the social afterwards. There will = be shuttle buses. The draft agenda is below and also at https://trac.tools.ietf.org/group/irt= f/trac/wiki/blockchain-federation If you are interested in attending, please add your name to the attendees l= ist on the Wiki page (or unicast to me) - the room has limited capacity... Draft Agenda * Diego Lopez: Service Federation in 5G * Carsten Bormann: Service Federation in IoT * Jeffrey He: Architecture Consideration for Data Sharing, and Open Que= stions * Jon Crowcroft: Challenges of Federating at Scale (tentative) * Ethereum presentation (tentative) * Dirk Kutscher: Federation in ICN * Discussion of Next Steps See you in Berlin! Dirk From: 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 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_82AB329A76E2484D934BBCA77E9F5249AF455BEDPALLENEofficehd_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,<= /p>

 

there w= ere some issues with storing attachments on the Trac server, so I moved the= presentations from Berlin to github and updated the links at https://trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation<= o:p>

&n= bsp;

Cheers,=

Dirk

&n= bsp;

 

Dirk = Kutscher
Sent: Samstag, 23. Juli 2016 13:51
To: 'Dirk Kutscher'; irtf-announce@irtf.org
Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey= ) (jeffrey.he@huawei.com)
Subject: RE: Distributed Data and Service Federation

 

Hi everyone,

 

I hope = you make it all home safely. I finally got to uploading the presentations f= rom Tuesday.

&n= bsp;

https://trac.tools.ietf.org/group/irtf/trac/wiki/blockchain-federation=

&n= bsp;

Thanks = to all presented and to everyone who participated – we had  pret= ty good attendance and got good input in the discussion.<= /p>

&n= bsp;

I also = added a link to a relevant presentation by Jon to the Wiki page. Unfortunat= ely he wasn’t able to make it to Berlin in the end, and we did not ha= ve time to talk about this at the meeting but this is touching on some of the points we discussed (scope, scalability).<= o:p>

&n= bsp;

I took = some notes that are on the last slide of my presentation.=

&n= bsp;

My &nbs= p;personal summary:

&n= bsp;

There s= eems to be something around decentralizing Internet infrastructure that peo= ple find interesting and important. The use cases we discussed were quite h= eterogeneous (decentralizing Internet infrastructure, service federation, IoT etc.).  There are other topic= s we mentioned only briefly on Tuesday, i.e., the Distributed Web activitie= s, the connection to ICN etc.

&n= bsp;

As next= steps, I suggest that we try to scope this to something focused enough to = have constructive work/discussions in the future. One suggestion that was m= ade was to focus on decentralizing today’s Internet infrastructure. I personally think that this might be a little to= o limited, considering the IoT requirements (for example).

&n= bsp;

It woul= d be great to get more opinions on that so that we frame the discussion bet= ter (for example for upcoming meetings).

&n= bsp;

Please = discuss on din@irtf.org.

&n= bsp;

Thanks,=

Dirk

&n= bsp;

&n= bsp;

&n= bsp;

&n= bsp;

&n= bsp;

&n= bsp;

Din [= mailto:din-bounces@irtf.org] On Behalf Of Dirk Kutscher
Sent: Montag, 18. Juli 2016 08:10
To: irtf-announce@irtf.org=
Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey) (jeffrey.he@huawei.com)
Subject: Re: [Din] Distributed Data and Service Federation

 

Agenda update:

 

= Coordinates

  • Date & Time: Tuesday, July 19, 18:50 -- 20:20
  • Room: Tegel

Agenda

  • Diego Lopez: Service Federation in 5G
  • Carsten Bormann: Service Federation in IoT
  • Thomas Scheffler: A Privacy Aware Localization Service= for Healthcare Environments
  • Jeffrey He: Architecture Consideration for Data Sharin= g, and Open Questions
  • Discussion of Next Steps

 

See you tomorrow,=

Dirk=

 

 

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

 

Hello,

 

friendl= y reminder of the meeting next week Tuesday. You can still go to the social= afterwards.

&n= bsp;

= Coordinates

  • Date & Time: Tuesday, July 19, 18:50 -- 20:20
  • Room: Tegel

Draft Agenda<= /h3>
  • Diego Lopez: Service Federation in 5G
  • Carsten Bormann: Service Federation in IoT
  • Jeffrey He: Architecture Consideration for Data Sharin= g, and Open Questions
  • Ethereum presentation (tentative)
  • Dirk Kutscher: Federation in ICN
  • Discussion of Next Steps

&n= bsp;

&n= bsp;

Best re= gards,

Dirk Ku= tscher

&n= bsp;

&n= bsp;

Dirk = Kutscher
Sent: Montag, 27. Juni 2016 05:58
To: 'Dirk Kutscher'; irtf-= announce@irtf.org
Cc: Carsten Bormann (cabo@tzi.org); din@irtf.org; Hejianfei (Jeffrey) (jeffrey.he@huawei.com)
Subject: RE: Distributed Data and Service Federation

 

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;

&n= bsp;

&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

 

 

 

--_000_82AB329A76E2484D934BBCA77E9F5249AF455BEDPALLENEofficehd_--