deliverable d5.4 - final report on liaisons, standardization and dissemination

7/24/2019 Deliverable D5.4 - Final Report on Liaisons, Standardization and Dissemination

1/105

Version 0.1 Page 1of105 Copyright 2015, the Members of the SmartenIT Consortium

Socially-aware Management ofNew Overlay Application Traffic with

Energy Efficiency in the InternetEuropean Seventh Framework Project FP7-2012-ICT- 317846-STREP

Deliverable D5.4Final Report on Liaisons, Standardization,

and Dissemination

The SmartenIT Consortium

University of Zrich, UZH, SwitzerlandAthens University of Economics and Business - Research Center, AUEB-RC, GreeceJulius-Maximilians Universitt Wrzburg, UniWue, GermanyTechnische Universitt Darmstadt, TUD, GermanyAkademia Gorniczo-Hutnicza im. Stanislawa Staszica w Krakowie, AGH, PolandIntracom S.A. Telecom Solutions, ICOM, GreeceAlcatel Lucent Bell Labs, ALBLF, FranceInstytut Chemii Bioorganiicznej Pan, PSNC, PolandInterroute S.P.A, IRT, ItalyTelkom Deutschland Gmbh, TDG, Germany

Copyright 2015, the Members of the SmartenIT Consortium

For more information on this document or the SmartenIT project, please contact:

Prof. Dr. Burkhard StillerUniversitt Zrich, CSG@IFIBinzmhlestrasse 14CH8050 ZrichSwitzerland

Phone: +41 44 635 4331Fax: +41 44 635 6809E-mail: [email protected]


2/105

D5.4 Seventh Framework STREP No. 317846Public

Page 2of105 Version 1.0 Copyright 2015, the Members of the SmartenIT Consortium

Document Control

Title: Deliverable D5.4, Final Report on Liaisons, Standardization, andDissemination

Type: Public

Editor(s): Krzysztof Wajda, Rafal Stankiewicz (AGH)

E-mail: [email protected]

Author(s): Roman Lapacz (PSNC), Patrick Poullie (UZH), Sabine Randriamasy(ALBLF), Corinna Schmitt (UZH), Sergios Soursos (ICOM), Burkhard Stiller(UZH), Krzysztof Wajda (AGH), Manos Dramitinos (AUEB)

Doc ID: D5.4_v1.0.doc

AMENDMENT HISTORY

Version Date Author Description/Comments

V0.1_diss May 18, 2015 C. Schmitt Initial for part dissemination

V0.2_diss August 18, 2015 C. Schmitt Add Standardization Documents

V0.3_diss October 7, 2015 K. Wajda Dissemination activities outlined.

V0.4_diss October 12, 2015 C. Schmitt Added theses related to SmartenIT

V0.5_diss October 13, 2015 C. Schmitt Added theses related to SmartenIT

V0.6_diss October 20, 2015 K.Wajda Added publications and theses for Y3

V0.7_diss October 26, 2015 K.Wajda Added publications, references, informations from MARs, organizedevents, executive summary.

V0.8_diss October 27, 2015 C. Schmitt Updated on-line dissemination

V0.9_diss October 29, 2015 K.Wajda Added UniWue theses, summary table of dissemination, introduction

V0.1_stan Oct 1st C. Schmitt UZH updated on IETF activity in Y3, especially Sections 2.3.3-2.3.5

V.0.4_stan Oct 20 Manos AUEB update.Inter -cloud interface activity

V0.7_stan Oct 27 Sabine Final updates

V0.9 Oct 30 K.Wajda Consolidated version with standardization, external liaisons anddissemination.

V0.9_3 Oct 31 C. Schmitt Harmonize publications, correction of cross references

V1.0 Oct. 31, 2015 K. Wajda Final, corrections, editing.

Legal NoticesThe information in this document is subject to change without notice.The Members of the SmartenIT Consortium make no warranty of any kind with regard to this document,including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. TheMembers of the SmartenIT Consortium shall not be held liable for errors contained herein or direct, indirect,special, incidental or consequential damages in connection with the furnishing, performance, or use of thismaterial.


3/105

Seventh Framework STREP No. 317846 D5.4Public


Table of Contents

1

Executive Summary 5

2 Introduction 62.1 Purpose of the Deliverable 62.2 Deliverable Outline 6

3 Standardization 73.1 Summary of SmartenIT Achievements for Y1 73.2 Update of Initial Standardization Work of SmartenIT for Y2 9

3.2.1 Update on Survey on SmartenIT Relevant Standardization Bodies 93.2.2 SmartenIT workforce on Cloud-ISP interface 173.2.3 Main SmartenIT partner contributions to standardization bodies 18

3.3 SmartenIT Contributions to Standardization in Y3 20

3.3.1

Standardization on Cloud-ISP- Interface (Cloud-ISP IF) 213.3.2 Definition of project standardization work assessment 24

3.3.3 SmartenIT involvement in standardization bodies for Y3 253.3.4 SmartenIT standardization bodies and meeting attendance 283.3.5 Standardization documents submitted 31

4 External Liaisons 324.1 Liaisons Strategy Implementation 324.2 Main Achievements of Each External Liaison 34

4.2.1 eCousin 344.2.2 FLAMINGO 354.2.3 Lightness 364.2.4 NOVI 37

4.2.5

SAIL 374.2.6 STAR 38

4.2.7 SIGMONA 384.2.8 Fed4FIRE and FELIX 39

4.3 Per Project Achievements and Liaisons Results Based on Selection Criteria 40

5 Dissemination 455.1 Overview 455.2 Publications 46

5.2.1 Books 465.2.2 Book Chapters 465.2.3 Journals 475.2.4 Workshops and Conferences (Accepted Papers) 48

5.2.5

Whitepapers 55

5.2.6

Presentations (Demonstrators, Exhibitions) 55

5.2.7 Other un-refereed Material 565.2.8 Workshops and Conferences (Oral Presentations and Colloquia) 565.2.9 Press Releases 625.2.10 On-line Releases 625.2.11 Theses 715.2.12 Standardization 755.2.13 Patents 775.2.14 Other Issues Best Paper and Demo Awards (other Awards) 77

5.3 Events 785.3.1 Co-organized events 785.3.2 Other events 81

5.4

Project Website 88

6 Summary and Conclusions 96


4/105



7 Smart Objectives 98

8 References 99

9 Abbreviations 102

10Acknowledgements 105


5/105



1 Executive Summary

At the beginning of the project, D5.1 [1] and D5.2 [2] were produced in order to introducethe full set of four WP5 working fields (exploitation, standardization, external liaisons, and

dissemination). Deliverable D5.4 reports the SmartenIT project's achievements during its3-year lifetime done within the scope of external liaisons, standardization and disse-mination. This deliverable, considered jointly with D5.3 [3], reporting both industrial andacademic partners exploitation measures, they give final and concise vision of differentkinds of already published and exploited results.

This document thoroughly overviews:

Involvement of partners in standardization institutions and forums alongside withdetailed reporting of achieved results;

External liaisons - with 9 external projects were established. The following 6projects were selected initially in preliminary Phase 1 of the external liaisons plan:

o eCousin (enhanced COntent distribUtion with Social Information);

o FLAMINGO (Management of the Future Internet);

o Lightness (Low latency and high throughput dynamic network infrastructuresfor high performance datacenter interconnects);

o Novi (Networking Innovation Over Virtualized Infrastructures);

o SAIL (Scalable and Adaptive Internet Solutions);

o STAR (SwiTching And tRansmission);

External liaisons with 3 more projects established during project's runtime:o SIGMONA (SDN Concept in Generalized Mobile Network Architectures);

o Fed4FIRE: Fed4FIRE is an Integrating Project under the European UnionsSeventh Framework Programme (FP7) addressing the work programmetopic Future Internet Research and Experimentation (2012-2016);

o FELIX (FEderated Test-beds for Large-scale Infrastructure eXperiments);

All considered dissemination categories with detailed information about achieve-ments, The project has used different types of dissemination channels: starting fromtypical papers submitted to conferences (with presentations) and journals, with book

chapter and books, to online reporting done by dedicated SmartenIT web page. Theproject compiled also white papers in order to share general visions of assumptionsand solutions for chosen, specified and implemented TM solutions.

Reported achievements of different kinds allow to draw the conclusions that SmartenITproject was very successful in disseminating results via different channels and also insetting up strong and long lasting external liaisons allowing mutual exchange ofknowledge, software and many other assets with external consortia.


6/105



2 Introduction

Deliverable D5.4 Final Report on Liaisons, Standardizations and Dissemination"summarizes all dissemination and standardization activities undertaken by the SmartenIT

consortium together with external liaisons supported to promote project's results and getfeedback from the industry, EU bodies, and public institutions.

As such, this deliverable proves that SmartenIT presented:

analytical works dealing with clouds, cloud-based services, Online Social Networks,

proposals of new TM mechanisms,

representative scenarios and use-cases,

documented novel architecture,

implementation issues and prove-of-concept reports,

for external projects and wide audience.

The project used many communication channels to distribute results.

2.1 Purpose of the Deliverable

This deliverable reports all achievements for SmartenIT activities in the three areas of

(1) Standardzation activities in terms of contributed documents, also with patents andparticipation in standardization meetings;

(2) Dissemination results in terms of contributions to books, jurnal papers, conferences,

workshops, FIA events, concertation meetings, and cluster meetings, additionallyalso Eng., M.Sc. and Ph.D theses are reported;

(3) External liaisons achieved for interactions with other EC D1 projects, Challenge 1projects, and other projects.

This document presents an overall picture of what the project has produced and what isthe impact of our results, both to the ICT market and to the society. This deliverableaddresses the smart-objectives O5, as stated in the DoW.

2.2 Deliverable Outline

The remainder of the deliverable is organized as follows.Section 3 summarizes the identified projects results for standardization and drawsconclusions for the future contributions,

Section 4 reports on external liaisons and provides detailed data about assets exchangedamong SmartenIT and external projects.

Section 5 provides data about dissemination during the project's lifetime, split into manycategories.

Section 6 summarizes the deliverable and section 7 recalls Smart objectives related toaspects covered by this deliverable.


7/105



3 Standardization

This section briefly presents the achievements of SmartenIT task T5.2 Standardization forY1 (sec. 3.1), documents standardization activities of project partners in Y2 (Section 3.2

and finally summarizes standardization work done during year 3 (Section 3.3).

3.1 Summary of SmartenIT Achievements for Y1

The achievements of T5.2 in Y1 are contributions to standardization bodies anda standardization survey. The latter has been reported in Deliverable D5.2, see [2]. Thisdeliverable describes the relationship between SmartenIT project and standardizationbodies. SmartenIT highlights modern use cases that stress the need to impact bodiesrelated to overlay traffic management and optimization, security and robustness intransmission paths, reliable performance measurements and socioeconomic aspects.

Table 1 lists the partner involvement type and contributions for the T5.2 focused bodiescarried in Year 1.

Table 1 Summary of SmartenIT partner involvement and contributions in Year 1,

Standardization

Body

Involvedpartner

Type of involvement

ICOM Follow-up

Previously contributed to Internet Draft on ALTOFeedback-Based Client Protocol.

AGH Follow up

Previously presented draft-dulinski-alto-inter-problem-statement-01 [20]

ALTO

ALBLF Contribution

Base Protocol draft reviews

Individual drafts review

Previously presented: draft-randriamasy-alto-multi-cost[15] and draft-randriamasy-alto-cost-schedule (now draft-randriamasy-alto-cost-calendar) [16], both drafts being still

aliveDrafts submitted to the WG:

- "ALTO Cost Value Name", S. Randriamasy, IETF draft-randriamasy-alto-cost-value-name-00, July 16 2013,[18][18]

- "ALTO Traffic Engineering Cost Metrics", Q. Wu, Y.Lee, D. Dhody (Huawei), S. Randriamasy (Alcatel-Lucent), IETF draft-wu-alto-te-metrics-00, October 212013, presented at 88thIETF meeting, [19]


8/105



CDNi AGH,ALBLF

Follow up

IRTF-ICN ICOM Contribution

Previously contributed to the Information-centricNetworking: Evaluation Methodology, draft-irtf-icnrg-methodology-00 [14], providing content related to trafficand system metrics.

IRTF-SDN AGH,ALBLF

Follow up

MIF TDG Follow up

MPTCP TDG Follow up

RMCAT TDG Follow up

LMAP TDG Follow up

ITU-T SG13,Q16

UZH Contribution

The development of the Y.FNsocioeconomic documentbegan within Q21/13 in 2011 and was adopted by ITU-TsQ16/13 in February 2013 due to UZH efforts. It was finallypublished as ITU-T Recommendation Y.3013 in August2014 [4].

ITU-T RevCom UZH Contribution

Based on the success of Tussle Analysis inRecommendation Y.3013, a submission to RevCom wasdone in January 2014 to integrate Tussle Analysis as abasic requirement for upcoming recommendations in ITU-T

IETF CoRE/ACE UZH Contribution

Published draft titled DTLS-based Security with two-wayAuthentication for IoT as version 00 (draft-schmitt-two-way-authentication-for-iot-00>) [7], after three iterationsand shifting to working group ACE renaming to Two-wayAuthentication for IoT as version 00 (draft-schmitt-ace-

twowayauth-for-iot-00) [22].Published draft entitled X.509 Public Key InfrastructureCertificates for the Constrained Application Protocol asversion 00 (CoAP), IETF Internet Draft, Standards Track,ACE, draft-porambage-core-ace-x509-00, [12].

NML PSNC Contribution

Published the final standard document GFD.206 NetworkMarkup Language Base Schema Version 1 [17].

NSI PSNC Follow-up


9/105



3.2 Update of Initial Standardization Work of SmartenIT for Y2

The work performed in Year 2 of SmartenIT with respect to standardization is described interms of a focused update of the survey on the SmartenIT-relevant standardization bodies.This update contains a list only, and the detailed summaries of standardization workperformed in terms of meetings attended and discussion lead. This section has threeparts: part 1 provides follow-up results in terms of updates and meeting attendancereporting; part 2 outlines the SmartenIT T5.2 work initiated on the Cloud-ISP interface andpart 3 provides updates on SmartenIT partner contribution to standardization bodies.

3.2.1 Update on Survey on SmartenIT Relevant Standardization Bodies

This section focuses on standardization bodies where SmartenIT partners are activeaccording to the plans of T5.2. During project time standardization activities by partnermight shift or expand.

The attendance of SmartenIT personnel at standardization meetings had been docu-mented in Meeting Attendance Reports (MAR), for which the public summaries areavailable on the SmartenIT Website (http://www.smartenit.eu). To provide this informationto the Y2 review, all MARs have been made available online underhttp://reviewer.smartenit.eu in the publications section. Additional information on detaileddiscussions, contributions, and outcomes are available to the project internally.

The bodies considered in the following are ITU-T (SG13 and ITU-T RevCom), IETFCORE, IETF ACE, and IETF ALTO WG.

3.2.1.1 ITU Telecommunication Standardization Sector

Updates on ITU-T SG13 and RevCom are provided through the following MARs.Additionally, a MAR is included about the ITU-Activity presented at the SwissTelecommunication Association (ASUT).

MAR of ITU-T SG13 Q16 Meeting, February 2013On February 25 and 27, 2013, members of the UZH delegation (coordinator of SmartenIT)attended the ITU-T SG13 meeting in Geneva, Switzerland, to contribute to thedevelopment of ITU recommendation Y.FNsocioeconomic, which is aimed at the Socio-economic Aware Design of Future Network Technology. The development of thisdocument stems from efforts of the SESERV project [7], which initiated the development ofthe document within ITU-Ts Q21/13 in 2011. The study period during which thedevelopment of the document was started, recently ended, wherefore a new Question to

develop the document in, became necessary. Thus, the first proposal of SmartenITattendants was to continue the development of the document within an ITU-Ts Q16/13that addresses Environmental and socio-economic sustainability in future networks andearly realization of FN and is therefore considered a perfect match for the furtherdevelopment of the document. Secondly, editorial and structural changes were proposed.Third, the addition of a section that explains to ITU members how to best integrate thesocio-economic analysis (by the means of tussle analysis) proposed withinY.FNsocioeconomic in the standardization of Future Networks was suggested. All threeproposals were well received by the meeting participants. However, the valuable feedbackgiven during the meeting led to agree on significant extensions and adaptions of thedocument, as discussed subsequently.

ITU recommendation Y.3001 [8] identified objectives and design goals for future networks,two of which were "social and economic awareness" (objective) and "economic incentives"


10/105



(design goal). Y.FNsocioeconomic was started to develop a methodology to better achievethese two criteria. As pointed out by meeting participants, the objective of social andeconomic awareness implies the design goal service universalization (besides"economic incentives"), which was hitherto not addressed by Y.FNsocioeconomic. Since

the document attracted meeting participants, these volunteered to provide content for suchan additional section until the next Study Group meeting. To further improve consistencywith Y.3001, the scope of the document will be adapted and the title was changed toSocial and Economic Awareness of Future Networks (cf. Y.3001 Section 7.4 [8]).The next editorial iteration for Y.FNsocioecomic will happen during SG13 Rapporteurmeeting in June 17-28, 2013, and during SG13 meeting in November 4-15, 2013. TheUZH delegation will provide contributions to these iterations that are to be developed in theframework of SmartenITs socio-economic research facet and evaluates potential tochannel technical SmartenIT research to ITU-T recommendations as well.

MAR: ITU-T SG13 Q16 Rapporteur Meeting, June 2013On June 18 and 21, 2013, members of the UZH delegation (coordinator of SmartenIT)attended the ITU-T SG13 Rapporteur meeting in Geneva, Switzerland, to contribute to thedevelopment of ITU recommendation Y.FNsocioeconomic, which is aimed at EconomicIncentives of Future Networks. The development of this document stems from efforts ofthe SESERV project, which initiated the development of the document within ITU-TsQ21/13 in 2011. The document that is now development within ITU-Ts Q16/13 addressesEnvironmental and socio-economic sustainability in future networks and early realizationof FN.In the ITU-T SG13 study group meeting in February it was decided to add a section toY.FNsocioeconomic that explains to ITU members how to best integrate the socio-economic analysis (by the means of tussle analysis) proposed within Y.FNsocioeconomicin the standardization of Future Networks. A main output of the current meeting was togeneralize this section to explain how the proposed socio-economic analysis can bedeployed by standardization bodies in general.The section on service universalization which was added in the February meeting toY.FNsocioeconomic, in order to better comply with ITU recommendation Y.3001 wasmoved to a separate document during the current meeting, to clearly focus Y.FNsocio-economic on economic incentives. The now-removed section on service universalizationwas added to Y.FNsocioeconomic in February, since Y.FNsocioeconomic was started todevelop a methodology to better achieve the objective of social and economicawareness, which, as pointed out in February, implies, according to Y.3001, not only thedesign goal of "economic incentives" but also the design goal of service universalization.

Besides this removal also informative content was removed or moved to the appendix.The next editorial iteration for Y.FNsocioecomic will happen during SG13 Rapporteurmeeting in November 4-15, 2013. The UZH delegation will provide contributions to thisiteration that are to be developed in the framework of SmartenITs socio-economicresearch facet and evaluate potential to channel technical SmartenIT research to ITU-Trecommendations as well.

MAR: ITU-T SG13 Meeting, November 2013A member of the UZH delegation (coordinator of SmartenIT) attended the ITU-T SG13meeting in Kampala, Uganda to contribute to the development of ITU recommendationY.FNsocioeconomic, which is aimed at Socio-economic Assessment of Future Networksby Tussle Analysis. The development of this document stems from efforts of the SESERVproject, which initiated the development of the document within ITU-Ts Q21/13 in 2011.


11/105



The document that is now developed within ITU-Ts Q16/13 addresses Environmental andsocio-economic sustainability in future networks and early realization of FN.The version of Y.FNsocioeconomic that was contributed by UZH to the meeting, sawincreased comprehensibility achieved by condensing of text. The proposed changes,

which also included definitions and references, were well received by the meetingparticipants. In the course of the meeting, key parts of the document, such as title andscope, were improved. Due to these valuable changes, which were applied before andduring the meeting, the document is expected to reach consensus mid of next year.The next editorial iteration for Y.FNsocioecomic will happen during the SG13 Rapporteurmeeting in February 2013. The UZH delegation will provide contributions to this iterationthat are to be developed in the framework of SmartenITs socio-economic research facetand evaluate potential to channel technical SmartenIT research to ITU-Trecommendations as well.

MAR: ITU-T Rapporteur Meeting, February 2014The ITU-T SG13 rapporteur meeting in Geneva, Switzerland, was attended by twoSmartenIT members to contribute to the development of ITU recommendationY.FNsocioeconomic, which is aimed at Socio-economic Assessment of Future Networksby Tussle Analysis and developed within ITU-Ts Q16/13. The documents developmentwas initiated within ITU-Ts Q21/13 in 2011 by the SESERV project to raise the awarenessfor socio-economic factors in the Future Internet landscape and to standardize tussleanalysis as a tool to deal with these factors.SmartenITs contribution to the meeting finalized document changes that were requestedin the Study Group 13 meeting held in November 2013 in Kampala, Uganda, and enrichedthe document by text from SmartenITs contribution to ITU-Ts RevCom meeting held inJanuary, 2014. Since the document is already very mature the changes were mostly ofeditorial nature. During the meeting, terminology was again improved just as text furthercondensed. Due to the overall agreement of meeting participants the document will beannounced for consensus in June 2014. UZH will therefore participate in this meeting tosupport the last steps of the documents development and agreement.The outlined activities happen in the framework of SmartenITs socio-economic researchfacet where it is also evaluated whether technical SmartenIT research can be channeled toITU-T recommendations. The development of the document is highly relevant forSmartenIT, as the project puts emphasis on socio-economic aspects of networktechnology in order to enable the development of traffic management mechanisms that arenot only of high technical quality but also withstand inevitable socio-economic interactionsof stakeholders. Since Y.FNsocioeconomic is the first document within ITU-T that

addresses socio-economic aspects of network technology, SmartenITs activity in thedevelopment of this document establishes contact with other experts in this area andallows for the exchange of ideas on this topic. This allows for highly elaborateddiscussions of socio-economic aspects of traffic management within the project.Furthermore, the document itself, although not released yet, does already serve as avaluable guideline for SmartenITs socio-economic discussions. Vice-versa, also ITU-Tprofits from this document as the need for consideration of socio-economic aspects isrecognized within the organization but a suitable tool to address these in thestandardization process is missing. This gap became visible in the discussions onSmartenITs contribution to ITU-Ts RevCom meeting, where SmartenIT proposed tointegrate tussle analysis into ITU-Ts standardization process; a proposal that was well

received but postponed due to organizational considerations.


12/105



Therefore, SmartenITs efforts regarding the development of Y.FNsocioeconomic will notonly increase the socio-economic qualities of SmartenITs traffic managementmechanisms and increase SmartenITs visibility within one of the worlds leadingstandardization bodies but also eventually enrich the standardization bodys work by a

socio-economic perspective and increase the overall awareness for socio-economicaspects of the Internet.

MAR: ITU-T Study Group Meeting, July 2014Today, ITU-T Study Group 13 (SG13) finally consented RecommendationY.FNsocioeconomic during its closing plenary. The document reached consent of SG13sWorking Party 3 (WP3) already yesterday during WP3s closing plenary. Last week thedocument was refined through changes by the Question 16/13 chairman and a SmartenITmember, who attended SG13s July meeting (7th-18th of July) in Geneva, Switzerland,several times to ensure the consenting of the document. With the reached consent thedocument can now undergo ITU-Ts approval process during which ITU-T members mayrequest last changes to the document. The document is expected to have passed thisprocess in two months from now upon which it will finally be released.Y.FNsocioeconomic is aimed at the Socio-economic Assessment of Future Networks byTussle Analysis and was developed within ITU-Ts Q16/13. The documents developmentwas initiated within ITU-Ts Q21/13 in 2011 by the SESERV project to raise the awarenessfor socio-economic factors in the Future Internet landscape and to standardize tussleanalysis as a tool to deal with these factors.The outlined activities are conducted in the framework of SmartenITs socio-economicresearch facet. Because SmartenIT puts emphasis on socio-economic aspects of networktechnology in order to enable the development of traffic management mechanisms that arenot only of high technical quality but also withstand inevitable socio-economic interactionsof stakeholders, the development of Y.FNsocioeconomic is highly relevant for SmartenIT.Since Y.FNsocioeconomic is the first document within ITU-T that addresses socio-economic aspects of network technology, SmartenITs activity in the development of thisdocument establishes contact with other experts in this area and allows for the exchangeof ideas on this topic and allows for highly elaborated discussions of socio-economicaspects of traffic management within the project. Furthermore, the document itself,although not released yet, does already serve as a valuable guideline for SmartenITssocio-economic discussions.The need for consideration of socio-economic aspects is recognized by ITU-T but asuitable tool to address these in the standardization process is missing. This gap becamevisible in the discussions on UZHs contribution to ITU-Ts RevCom meeting, which

proposed to integrate tussle analysis into ITU-Ts standardization process. This proposalwas delayed, because tussle analysis is specified in Y.FNsocioeconomic, which was stillunder development. However, as of today Y.FNsocioeconomic can be expected to bereleased in the near future, also UZHs efforts within RevCom are planned to be resumed.

MAR: ITU-T RevCom Meeting, January 2014A member of the UZH delegation (coordinator of SmartenIT) attended the ITU-T RevCommeeting in Geneva, Switzerland on January 16, 2014, to initiate the integration of tussleanalysis into ITU-Ts standardization process. Tussle analysis is aimed at the socio-economic assessment of Future Networks and was developed by the SESERV project.SESERV also initiated the development of document Y.FNsocioeconomic within ITU-TSG13 in 2011, which specifies tussle analysis and is now further developed by SmartenIT.The document, which was contributed by UZH to the RevCom meeting, described aspecialized version of tussle analysis tailored to ITU-Ts standardization process and


13/105



purposes. The contribution was received with great interest as also ITU-T recognizes theneed to account for socio-economic considerations in technology development beyond thetraditionally/technical engineering goals (effectiveness, efficiency, modularity, andsecurity). Since the meeting revealed great interest in tussle analysis within ITU-T and

brought it to the attention to members of all Study Groups, the contribution to this RevCommeeting not only identified an application area for tussle analysis, which will allow tofurther refine it, but it will also greatly aid the development of Y.FNsocioeconomic inreaching consensus.The next editorial iteration for Y.FNsocioecomic will happen during the SG13 Rapporteurmeeting in February 2013. The UZH delegation will provide contributions to this iterationthat are to be developed in the framework of SmartenITs socio-economic research facetand evaluate potential to channel technical SmartenIT research to ITU-T recom-mendations as well.

MAR: ASUT CS4 Meeting, September 2014The Swiss Telecommunication Association (ASUT) invited UZH to their CS4-Meeting topresent the UZH activity within ITU-T, especially to present the approved recommendationY.3013 - Socio-economic Assessment of Future Networks by Tussle Analysis. Themeeting took place in Bern, Switzerland and representatives of Swisscom, ASUT, ETSI,ITU-T, and BAKOM were present.The invitation of UZH to this meeting was indicated by Leo Lehmann (Vice-Chair WorkingGroup 3, ITU-T, and representative of BAKOM). He was invited to present his involvementin the standardization body ITU-T. Due to the fact that Leo Lehmann supported UZH inrecommendation activity throughout the last four years resulting in the first Swissacademic recommendation Y.3013 he asked UZH to present the recommendation at theCS4-Meeting. The presentation included ITU-T activity by UZH itself from starting point in2011 until today with special focus on recommendation Y.3013 development and detailsabout the content Tussle Analysis.The meeting participants were very interesting in Tussle Analysis itself and forced tointegrate it into ASUT activities and upcoming standardization processes. As a result of theCS4 Meeting UZH was invited in the Multi-Stakeholder-Platform (MSP) meetingafterwards. The MSP group focuses at the moment on the use-case eHealth and tries togain an overview of standardization activities around this topic. They recognized that thisuse-case could gain advantages by applying Tussle Analysis in order to identify Tusslesand possible spillovers. Thus, UZH was asked to participate actively in the MSP groupbased on the involvement and experience in ITU-T and IETF.

3.2.1.2 Internet Engineering Task Force (IETF)The Internet Engineering Task Force (IETF) is a large open international community ofnetwork designers, operators, vendors, and researchers concerned with the evolution ofthe Internet architecture and the smooth operation of the Internet. It is open to anyinterested individual. The IETF Mission Statement is documented in RFC 3935.

The actual technical work of the IETF is done in its Working Groups (WG), which areorganized by topic into several areas (e.g., routing, transport, security). Much of the workis handled via mailing lists. The IETF holds meetings three times per year. During the IETFmeetings, researchers from industry and academics meet in order to present newstandardization approaches, discuss and process them to turn them into a RFC. Due to

the development in the Internet and the technical standards, more and more topics comeinto focus and become an aim for standardization. Thus, different Birds of a Feather


14/105



("BoF") meetings take place in conjunction with each IETF. The next paragraphs focus onparticular WG meetings with MAR digests.

Within IETF SmartenIT members are active in the WGs CORE, ACE and ALTO. Theyregularly participate in IETF and interim meetings as reported in the following.

MAR: Internet Engineering Task Force (IETF) 87, July/August 2013The 87th Internet Engineering Task Force (IETF) event was held in Berlin, Germany, on28th, 29th, 30th, 31st July and 1st, 2nd August with 1500 pre-registered participants fromindustry and academics. All presentations and meeting minutes are available under thelink: https://datatracker.ietf.org/meeting/87/materials.htmlSummarizing the relevant impact of IETF 87 for the project SmartenITit will be importantfor external liaisons in WP5 between UZH and FLAMINGO. One part of the externalliaisons looks on standardization process for securing data exchange betweencommunication partners and the involved access control mechanisms. Therefore, UZHsubmitted a draft to the BOF of DTLS In Constrained Environments (DICE) dealing with

questions on authentication and authorization. Based on the submission good discussionstook place showing the importance of this topic, which might be interesting for furthercooperation to industry (e.g., Sensinode, Ericsson) and academic (e.g., University ofBremen TZI, University of Oulu - Finland).

MAR: Internet Engineering Task Force (IETF) 88, November 2013The 88th Internet Engineering Task Force (IETF) event was held in Vancouver, BC,Canada, on Nov 3-8, 2013 with a pre-meeting for Authorization & Authentication (AA)group within WG CoRE on Nov 2, 2013. IETF 88 had 1500 pre-registered participants fromindustry and academia. All presentations and meeting minutes are available under the link:https://datatracker.ietf.org/meeting/88/materials.htmlSummarizing the relevant impact of IETF 88 for the project SmartenITit will be importantfor external liaisons in WP5 between UZH and FLAMINGO. One part of the externalliaisons looks on standardization process for securing data exchange betweencommunication partners and the involved access control mechanisms. Therefore, UZHsubmitted an updated version of the draft draft-schmitt-two-way-authentication-for-iot-01dealing with questions on authentication and authorization. The updated version includesuse-case description, hardware requirements, as well as modification within the solutionsection. Corinna Schmitt presented the current status within the pre-meeting of AA-groupand receiving very positive feedback and support for ongoing improvements. Discussionstook place with industry (e.g., Huawei, Ericsson) and academic (e.g., University of Bremen- TZI, University of Oulu - Finland) in order to integrate the draft in right position within the

upcoming work in the AA group. UZH will be involved in work dealing with use-cases andrequirement specification, as well as in transport issues.

MAR: Internet Engineering Task Force (IETF) 89, March 2014The 89th Internet Engineering Task Force (IETF) event was held in London, England,United Kingdom, on March 2-7, 2014 with pre-workshops on the first day. 1300 pre-registered participants from industry and academics were counted for IETF 89 in London.All presentations and meeting minutes are online available under the following link:https://datatracker.ietf.org/meeting/89/materials.htmlSummarizing the relevant impact of IETF 89 for the project SmartenIT it will be importantfor external liaisons in WP5 between UZH and FLAMINGO. One part of the externalliaisons looks on standardization process for securing data exchange betweencommunication partners and the involved access control mechanisms. Therefore, UZHsubmitted an updated version of the draft draft-schmitt-two-way-authentication-for-iot-02


15/105



dealing with questions on authentication and authorization. The updated version includeshandshake description and certificate creation details, as well as modification within thearchitecture description section. Corinna Schmitt joined the BOF of the new working groupAuthentication and Authorization for Constrained Environments (ACE) where the current

draft is associated. The BOF itself was very successful and waits now for approval as aworking group under IETF after charter update. Parallel to discussions during the BOF,different individual meetings took place with industry (e.g., Huawei, Ericsson) andacademic (e.g., University of Bremen - TZI, University of Oulu Finland) in order tointegrate the draft in right position within the upcoming work in the ACE group. Next to theaforementioned draft UZH is involved in a second draft within ACE named draft-porambage-core-ace-x509-00 dealing with the usage of X.509 certificate in networks withconstraint devices.The main outcome of IETF 89 is that different groups are interesting in the ongoing two-way authentication and certification creation process in constraint environments. Allsolutions are standard based and, therefore, can be applied to different network setups as

assumed in SmartenIT.MAR: Internet Engineering Task Force (IETF) 90, July 2014The 90th Internet Engineering Task Force (IETF) event was held in Toronto, Ontario,Canada, on July 20-25, 2014 with pre-workshops and interim meetings by differentworking groups on the first day. Around 1300 pre-registered participants from industry andacademics were counted for IETF 90 in Toronto. All presentations and meeting minutesare online available under the link: https://datatracker.ietf.org/meeting/90/materials.htmlSummarizing the relevant impact of IETF 90 for the project SmartenIT it will be importantfor external liaisons in WP5 between UZH and FLAMINGO. One part of the externalliaisons looks on standardization process for securing data exchange betweencommunication partners and the involved access control mechanisms. Therefore, UZHsubmitted an updated version of the draft draft-schmitt-two-way-authentication-for-iot-02dealing with questions on authentication and authorization. Due to the approval of theworking group Authentication and Authorization for Constrained Environments (ACE) adraft renaming was essential to draft-schmitt-ace-twowayauth-for-iot-00 [11], resulting inthe replacement of the old version and receiving an I-D by IETF. The updated versionincludes a generalization of requirements to class devices and preparation for upcominginput for class 1 devices using Elliptic Curve Crypto (ECC) for two-way authentication.Corinna Schmitt joined ACE working group meeting where the current draft is associated.The meeting had its first formal meeting at IETF 90 and, therefore, focused on presentingbasic problem statements, use-cases, and design considerations to the community.

Corinna Schmitt including also aspects from the current draft did the latter presentationand let the discussion. Discussion resulted in hinting where to look on, what to put out ofscope at the moment, and finding supporters for draft improvements. Parallel todiscussions during the WG meeting different individual meetings took place with industry(e.g., Microsoft, Cisco) and academic (e.g., University of Oslo) in order to integrate thedraft in right position within the upcoming work in the ACE group and possibilities for newviews. Next to the aforementioned draft UZH was asked to update an expired draft,entitled Compressed IPFIX for Smart Meters in Constrained Networks, dealing withefficient data format based on the IP Flow Information Export (IPFIX) Protocol and amediator. After discussions with Nevil Brownlee, the Independent Submissions Editor(ISE), a submission for the ISE publication way is intended.


16/105



The main outcome of IETF 90 is that UZH is linked with its current draft about two-wayauthentication to the WG ACE. All solutions are standard based and, therefore, can beapplied to different network setups as assumed in SmartenIT.

IETF ALTO WG updates

The IETF WG ALTO (for Application Layer Traffic Optimization) is standardizing a protocolthat specifies transport means providing applications with abstracted information on theunderlying network topology. ALTO provides guidance to applications w.r.t. networktopology so that they choose their endpoints with an awareness of the underlying ISPtopology and related transport costs. This awareness is materialized by informationreflecting the ISP-centric view of the Internet expressed by an abstract human-readabledescription of the network topology partitioned in ISP defined network regions (PIDs), e2ecosts among PIDs and possibly amongst Endpoints.

The IETF ALTO protocol is a candidate to fulfill the SmartenITgoal to produce incentivecompatible network management mechanisms for users, overlay service providers and

network providers. In particular, it is integrated in the SmartenIT architecture and in one ofthe SmartenIT Traffic Management mechanisms that optimizes application path selectionjointly w.r.t ISP and application user preferences. Sabine Randriamasy, the leader of taskT5.2 Standardization in SmartenIT has attended the ALTO WG session at the 89 thIETF inLondon, as a contributor the ALTO WG and its re-chartering inputs. She was also a minutetaker of this session for the ALTO WG.

MAR digest: ALTO WG re-charter preparation meeting at IETF89 LondonThe ALTO WG meeting at IETF89 was held on Tuesday March 6 th. This meeting was ofutmost importance to the ALTO WG as it prepared the re-chartering of the WG anddiscussed the pre-defined future agenda items with the WG and chairs of other WGs, inparticular CDNi and I2RS. In the agenda, 10 minutes were devoted to WG item progressand 60 minutes for re-charter items discussion. The chairs would like to hear whether theroom thinks that the proposed milestones are achievable in reasonable time. A detailedMAR, is available on the SmartenIT project BSCW.

The adoption of the ALTO Protocol draft as a proposed standard by the IESG had beenconfirmed this same morning. The main objective of this ALTO WG meeting was todiscuss the proposed re-charter items. Four re-charter topics were identified and can besummarized as: (i) Protocol optimization extensions (ii) Server discovery extensions (iii)Endpoint property and e2e cost extensions: for the Data Center and CDN use cases, todetermine not only where to connect but also when (iv) Graph representationextensions allowing deeper representation of e2e paths by adding nodes between PIDs.

The current charter items are now to be seen on http://datatracker.ietf.org/wg/alto/charter/.The 4 re-chartering items were discussed. The WG chairs noted the requests for re-formulation expressed by the attendance, in particular the Area Director and chairs of theCDNi and I2RS WG. They concluded that will gather discussion outcomes and get back tothe list and AD for the next steps.

ALBLF contributes since 2010 with protocol extension proposals presented and discussedat most of the ALTO WG meetings. One extension called Multi-Cost ALTO optimizes theALTO transactions by conveying jointly multiple costs and supporting constraints com-bining AND and OR operators and besides proposes new ALTO costs abstracting QoEimpacting metrics. Multi-Cost ALTO has been integrated in the design of a solution called

MUCAPS and proposed as a TM solution to the WP2 of SmartenIT. Another extensioncalled ALTO Cost Schedule provides time-based cost values helping to decide both


17/105



whereand when to connect and this concept has been integrated in re-charter item (iii).ALBLF also co-authors an extension proposing ALTO costs based on TE metrics collectedvia routing protocols. These three extension proposals relate to and motivated the re-charter item (iii).

Latest ALTO updatesSince the IETF89 meeting reported in the former paragraph, the base ALTO protocol nowRFC 7285. Its publication was announced on September 5th 2014 and is available onlink: https://www.rfc-editor.org/rfc/rfc7285.txt. In this RFC, the Alcatel-Lucent Bell Labs(BL) have been acknowledged for their contribution to the RFC edition (BL Murray Hill -US), WG lead (NP), and the protocol design (ALBLF Villarceaux and BL Stuttgart). BL(Naperville US) is also co-chairing the ALTO WG.

Two IETF ALTO WG meetings were held respectively at IETF90 and IETF 91 to discussand refine candidate protocol extension proposals relating to the new charter.

The next steps for the ALTO WG are mainly:

Decide whether to adopt or not the proposed protocol extensions

Execute new charter milestones published on Aug 19th 2014: 8 submissions are duebetween November 2014 and July 2015

Prepare an Interoperation event with RFC7285 compliant ALTO Clients and Servers,likely to happen at IETF92@dallas March 2015.

3.2.2 SmartenIT workforce on Cloud-ISP interface

This topic has been defined in June 14 2014 during a side-meeting of the SmartenITgeneral meeting at Vrachati. The partners attending the meeting were: ALBLF, AUEB,ICOM, PSNC and TDG. A face to face discussion of T5.2 partners was held with a focuson the Cloud-ISP interaction perspectives. The meeting has produced a kick-off draftdocument on problem definition, optimization potential, applicable scenarios andstandardization requirements, edited by TDG. It was identified that there is a need for acooperative interaction between the two parties. Indeed: cloud services are addressing alarge user population via ISP networks on the application layer. Without coordination, onlya best effort type service is possible where the cloud provider has no knowledge about thelocation and transport path to the users. The ISP could improve the service on thenetwork/transport layer, but has no knowledge about the application demands.Consequently, separated management of the cloud and the ISP network is suboptimalregarding overall resource usage and QoS.

Cloud ISP interfaces can help to optimize the traffic management and the QoS supportover the resources of both, the cloud provider and ISP. Resources are mainlyserver/cache/data center and transport capacities. Similarly to CDNs, the need tostandardize interfaces between heterogeneous CDNs has lead to the IETF WG CDNi(CDN interconnection). Likewise, interfaces between ISPs and Clouds would benefit fromstandardization.

Two domains needing standardization are identified currently:

Bilateral cloud - ISP interrelations: these relate to CDNi

Best effort type services involving replicated resources: these relate to ALTO


18/105



This discussion and first thoughts on Cloud-ISP Interface (CLISP-IF) are the initial steps toa more thorough study together with the identification and promotion of contributions tostandardization bodies needed to support CLISP-IF and that will be further described inthe SmartenIT T5.2 Y3 reporting on this topic, defined in Section 3.3.1.

3.2.3 Main SmartenIT partner contributions to standardization bodies

The SmartenIT T5.2 achievements in terms of contributions to standardization bodiesinvolved in the Y3 reporting can be outlined as follows.

ITU-T SG13: UZH has proposed a development of Recommendation Y.3013: Socio-economic Assessment of Future Networks by Tussle Analysis (approved Aug. 29, 2014).This proposal was consented during July meeting by Working Party 3. It is aimed at theSocio-economic Assessment of Future Networks by Tussle Analysis and was initiatedwithin ITU-Ts Q21/13 in 2011 by the SESERV project in order to raise the awareness forsocio-economic factors in the Future Internet landscape and standardize tussle analysis as

a tool to deal with these factors.ITU-T RevCom: UZH also contributed to RevCom. The core objective of the ReviewCommittee (RevCom) is to review the structure and working methods of ITUsTelecommunication Standardization Sector (ITU-T) to ensure that ITU-T continuesmeeting the standardization needs of an evolving business environment. Here UZH plansto continue its work on including the tussle analysis (recommended in ITU-T Y.3013 [4]) toupcoming standards. This means that each upcoming recommendation has to applyTussle Analysis before going for approval.

IETF ALTO WG: ALBLF contributed to the base protocol final design. The protocolextension proposals Multi-Cost ALTO and ALTO Cost Calendar (new name for ALTO

Cost Schedule) were presented by ALBLF at IETF90 in Vancouver, and a revision ALTOCost Calendar was presented at IETF91 in Honolulu. Multi-Cost ALTO is integrated indesign of the MUCAPS solution, proposed to WP2 as a TM mechanism.

IETF CORE WG - now shifted to IETF ACE WG: UZH contributed on two-wayauthentication for IoT and about usage of X.509 certificates. The proposed solution iscandidate for use-case in Inter-cloud scenario in WP2.

3.2.3.1 Standardization documents submitted

During Year 2, SmartenIT T5.2 contributors have submitted the following documents tovarious bodies:

IETF CORE WG

C. Schmitt, B. Stiller, DTLS-based Security with two-way Authentication for IoT, draft-schmitt-two-way-authentication-for-iot-02, IETF Internet Draft, Feb. 2014

P. Porambage, C. Schmitt, A. Gurtov, S. Gerdes, X.509 Public Key InfrastructureCertificates for the Constrained Application Protocol (CoAP), draft-porambage-core-ace-x509-00, IETF Internet Draft, Feb. 2014

Definition and relation to SmartenIT: UZH contributed several draft visions for two-wayauthentication possibilities for constraint devices (e.g., sensor nodes). The first versionfocused on a DTLS-based solution including X.509 certificates. The usage of X.509

certificates and the included information was specified in the second mentioned draft. Bothdrafts were presented at IETF meetings during project time and on intermediate meetings.


19/105



IETF ACE WG

C. Schmitt, B. Stiller: Two-way Authentication for IoT (Version 00); IETF, online,Fremont, California, U.S.A., June 25, 2014, URL: http://tools.ietf.org/pdf/draft-schmitt-ace-twowayauth-for-iot-00.pdf, replaces earlier IETF contributions

Definition and relation to SmartenIT: ACE is the follow up working group of CORE asindicated before in the MARs with focus on authorization and authentication. Thus, thedraft by UZH was shifted to this group and had to be renamed. The content stayed thesame as before. The proposed solution is standard-based and can be applied to everykind of network independent of the inclusion of sensor networks. Thus, it is interesting forSmartenIT WP2 use-cases.

ITU-T, SG 13, Q16 and RevCom

M. Waldburger, P. Poullie, C. Schmitt, B. Stiller (Eds.): Y.3013: Socio-economicAssessment of Future Networks by Tussle Analysis; in: ITU-T Recommendation,

Geneva, Switzerland, Aug. 2014, URL: http://www.itu.int/rec/T-REC-Y.3013-201408-I Submission to RevCom by P. Poullie, C. Schmitt, and B. Stiller in January 2014 (not

publicly available due to ITU restrictions)

Definition and relation to SmartenIT: The development of an ITU recommendationaiming at the socio-economic aware design of future network technology will constitute achannel to promote Tussle Analysis developed within SmartenIT to ITU-Trecommendations. Indeed, the core objective of the Review Committee (RevCom) is toreview the structure and working methods of ITUs Telecommunication StandardizationSector (ITU-T) to ensure that ITU-T continues meeting the standardization needs of anevolving business environment. Here UZH plans to continue its work on including the

tussle analysis (recommended in ITU-T Y.3013) to upcoming standards. This means thateach upcoming recommendation has to apply tussle analysis before going for approval.Besides, the ITU-T Recommendation Y.3013 has been identified by project partners as acandidate Use Case for the Dynamic Traffic Management (DTM) mechanism and itsapplicability is being studied in Task 2.2 (Definition of Use-cases, Parameters, andMetrics) of WP2.

IETF ALTO WG

Multi-Cost ALTO, S. Randriamasy (editor) and W. Roome(ALBLF) and N. Schwan(Thales), IETF draft draft-randriamasy-alto-multi-cost-08, July 4th 2014, Presented atthe 90thIETF, draft-randriamasy-alto-multi-cost-09, October 2014

Definition: This extension proposal optimizes the ALTO transactions by conveyingjointly multiple costs and supporting constraints combining AND and OR operators andbesides proposes new ALTO costs abstracting QoE impacting metrics. Multi-CostALTO has been integrated in the design of a solution called MUCAPS and proposed asa TM solution to the WP2 of SmartenIT.

ALTO Cost Calendar, S. Randriamasy (editor) (ALBLF), R. Yang (Yale), Q. Wu(Huawei), L. Deng (China Mobile), N. Schwan (Thales), IETF draft draft-randriamasy-alto-cost-calendar-01, July 4th 2014, Presented at the 90th IETF, draft-randriamasy-alto-cost-calendar-02, October 2014, Presented at the 91thIETF


20/105



Definition: this draft extension proposal provides time-based cost values helping todecide both where and when to connect and this concept has been integrated newALTO charter as item (iii).

"ALTO Traffic Engineering Cost Metrics", Q. Wu (Huawei), Y. Yang (Yale), Y. Lee

(Huawei), D. Dhody (Huawei), S. Randriamasy (Alcatel-Lucent), IETF draft-wu-alto-te-metrics-00, October 2013, presented at the 88th IETF, draft-wu-alto-te-metrics-01,February 2014, input to 89thIETF meeting re-chartering presentation with ALTO CostCalendar features, IETF draft-wu-alto-te-metrics-04, July 22nd2014, Presented at the90thIETF, draft-wu-alto-te-metrics-05, October 2014.

Definition: this extension proposal defines ALTO cost metrics based on TE metricscollected via routing protocols, in particular to support the inter-Data Centercommunication use case.

Relation to SmartenIT: The IETF ALTO protocol is a candidate to fill the SmartenIT goalto produce incentive compatible network management mechanisms for users, overlay

service providers and network providers. ALTO is used, together with its Multi-Cost in thedefinition of a Traffic Management mechanism called MUCAPS, proposed in WP2 tooptimize cloud traffic with transport network topology awareness and that could beadvantageously combined with other WP2 TM solutions providing social and energyawareness. The ALTO Calendar extensions providing time-based network information andthe ALTO TE-based metrics highly useful for bulk data transfers, are natural candidates forfuture extensions of MUCAPS.

3.3 SmartenIT Contributions to Standardization in Y3

This section outlines the SmartenIT T5.2 standardization achievements for the projectYear 3. The initial plans are listed below and related results will be detailed in theremainder of this section.

Identification and defense of standardization items for the Cloud-ISP interface,including:

o Problem statement and requirements definition for:

Best Effort transport

Transport with QoS-support by the ISP

Assess the standardization work produced within SmartenIT

o As a project outcome while most of the contributions stem from individualpartners that have various motivations

o Given the timeline of standardization proposals adoption and body specificprocesses.

Permanent contributions to relevant standardization bodies

o IETF ACE, IETF ALTO, ITU,IRTF ICN,

o ITU-T RevCom and perhaps other areas within ITU-T (currently unclear)

Permanent follow-up of other relevant bodies listed in Table 1.


21/105



3.3.1 Standardization on Cloud-ISP- Interface (Cloud-ISP IF)

3.3.1.1 Purpose and problem definition

A face to face discussion of T5.2 partners was held, with a focus on the Cloud-ISP

interaction perspectives, during the SmartenIT project meeting in Vrachati in June 2014 asindicated in section 3.2.2. It was identified that there is a need for a cooperative interactionbetween the two parties. Indeed: cloud services are addressing a large user population viaISP networks on the application layer. Without coordination, only a best effort type serviceis possible where the cloud provider has no knowledge about the location and transportpath to the users. The ISP could improve the service on the network/transport layer, buthas no knowledge about the application demands. Consequently, separated managementof the cloud and the ISP network is suboptimal regarding overall resource usage and QoS.

Cloud ISP interfaces can help to optimize the traffic management and the QoS supportover the resources of both, the cloud provider and ISP. Resources are mainlyserver/cache/data center and transport capacities.

Similarly to CDNs, the need to standardize interfaces between heterogeneous CDNs haslead to the IETF WG CDNi (CDN interconnection). Likewise, interfaces between ISPs andClouds would benefit from standardization. This requires the following steps:

1. Define the problem statement for Cloud-ISP IF standardization: this includes definingthe Optimization goals for cloud and network management and identifying the involvedparties

2. Select and specify options for Cloud - ISP interaction

3. Identify the requirements for standardization:

a. This implies identifying a number of considered interaction modes such as besteffort and QoS support

b. For each interaction mode, the appropriate standardization actions need to beidentified, together with the relevant standardization body.

4. Identify the applicability of Cloud-ISP IF standards

3.3.1.2 Results

Several actions were taken to address the Cloud-ISP IF challenge. as identified for theoptimization of Best Effort traffic via a Cloud-ISP IF. It consists in using the IETF ALTOprotocol to support the provision of ISP information to Clouds in order to optimize the traffic

paths. This may be possible by leveraging the currently proposed ALTO extensions intime-dependent information to:

Propose protocol extensions supporting anticipatedALTO requests

Motivate this by use-case of a Cloud-ISP interface to get anticipated ISP networkinformation so as to better schedule its flows w.r.t. the ISP network state.

Clouds may get this information via ALTO requests for applications that can anticipatetheir needs for both network resources and ALTO information on these resources and theircosts.

TDG who formulated the problem definition for the QoS aware and Best Effort cases also

worked on cloud federation together with an EU COST ACROSS activity, seehttp://www.cost-across.nl. They contributed to a white paper of the ACROSS cloud


22/105



federation task force led by W. Burakowski of the Warsaw University. TDG provided whitepaper sections on architectures, service scenarios, modeling of resource sharing, taskscheduling, Virtual Network Infrastructure. This paper was presented at an ACROSSworkshop in Sept. on the ITC 2015, see [23].

AUEB worked on use-cases and discussed possible ALTO protocol extensions withALBLF. They came to the following proposal:

The taskforce has produced an internal document on use cases and requirements tohighlight the importance of the Cloud-ISP interface and its impact on the market. TheCloud-ISP interface can result in tangible benefits for both the ISP (new market ofservices) and Digital Service Providers (monetization of their services, infrastructuregains), including Content Providers, Application Providers of streaming, telepresence,augmented reality services, CDNs, Cloud Service Providers and datacenters.

We propose to create a menu/catalogue of cost metrics for (future) time intervals. Inparticular, also in accordance with the ALTO approach, these cost metrics will be abstract

weights/costs of the expected network load for specific paths and time intervals, defined bythe ISP. This information would be of high value also for the emerging federations ofclouds and datacenters that need advanced (flexible, scalable, elastic, possibly assured-quality) inter-domain network services suitable for various demands (various applications).Use of those services should be dynamic which means federation may replace networkservices from time to time. For a wide variety of use cases interconnection assisted by theCloud-ISP interface can bring the required results, while respecting the administrativeboundaries of the individual cloud providers. An indicative list follows:

Independent clouds/datacenters transfers: Inter-cloud communication performed toacquire data or services (VM migration) over specific time intervals is needed to support

applications such as weather forecasts, scientific compute, stock market forecast, etc. Allthose applications must be run at a specific instance in time (e.g. for stock marketprediction after the close of the stock markets) and must be completed up to a specifictime, while acquiring data from multiple sources results in significant transfers.

Cloud Federation operations: Federations of clouds/datacenters allow the on-demandelastic scaling of resources over multiple geographical regions (e.g. cities) so as to acquireresources as close to the end users consuming the respective services as possible. Thisrequires periodic transfer of data over specific future time intervals to support e.g. cloudfederation data replication bulk data transfers, security back ups.

Web back-office traffic (including CDNs): The so-called back-office Web traffic is a

large portion of the Internet inter-domain traffic, being up to 30% and occasionally 40-50%of the total traffic of popular Internet links. The main sources contributing to this traffic areWeb proxies/intermediaries, CDN servers, ad exchanges and Web crawlers. The majorityof the data transfers (e.g. CDN cache synchronization) involved are scheduled datatransfers (e.g. pushing news, video and content in general at the end of each day from USto Europe caches back and forth to make it globally available), hence having someknowledge of the underlying network cost over the respective network paths and timeintervals would be highly beneficial.

Tele-presence and video-conferencing: A service that by definition is planned aheadand will be instantiated in a future time interval.

Virtual office environments - Multi-party collaboration:Multiple potential locations forcollaboration over the Internet to take place over specific time intervals.


23/105



Live streaming: Streaming of major live events also occur in well-known fixed timeintervals in the future. Thus, having some knowledge of the underlying network cost overthe respective network paths and time intervals would be highly beneficial in order toproperly plan how content should be delivered efficiently to the service subscribers taking

into account the underlying network constraints. Gaming: including multi-party on-linegame tournaments, E-health, E-learning comprise additional similar use cases with highlatency and QoS constraints over specific network paths and time frames.

Note that this Cloud-ISP interface futures costs menu proposition is technology-agnosticand applicable to both Best Effort and QoS-enabled paths, both intra- and inter-domain.Regarding implementation, we envision an approach similar to that used in energymarkets, in the sense that a standardized menu a la future markets (information per nextmonth, week, day, hour) would be published over the interface so as to optimize RESTreq-response. The granularity and time scales could be defined by ISP according to hisand his business customers needs (and what info can be disseminated) but standard timescales would greatly contribute to market liquidity and applications monetization potential.

ALBLF proposed to leverage their protocol extension proposal ALTO Cost Calendar. Itsdesign facilitates the introduction of attributes such as timeFromand timeTo proposed byAUEB and that would delimit the time scope of the requested calendars cost information.Besides, a possible exploitation of these attributes could be done via papers on use casesusing these features once the Calendar draft is adopted.

The input parameters to anticipated ALTO Calendar requests could include the fieldsmarked in bold:

{

timeFrom : long (timestamp of the start of time interval)

timeTo : long (timestamp of the end of time interval)

src : a network point (e.g. IP), the start of the path

dest : a network point (e.g. IP), the end of the path

cost-type-name : the ALTO network cost

}

timeFrom: can be a filtering parameter on the ALTO Calendar start-time attribute

timeTo: could be another filtering parameter if encoded in terms of ALTO Calendar nb-intervals attribute.

An integration of these fields in the ALTO WG protocol extension would require:

The timely acceptance by the ALTO WG of the ALTO Cost Calendar proposal as awork item,

The ALTO WG acceptance on such extension proposal, which in turn requires theactive participation of all involved SmartenIT individuals to the ALTO mailing listdiscussions in order to promote such features,

To ensure that these parameters are complaint with a RESTful architecture.


24/105



3.3.2 Definition of project standardization work assessment

3.3.2.1 Purpose

The results of the SmartenIT task T5.2 Standardization can be evaluated w.r.t. its

relevance to the SmartenIT goals and should examine the following questions: How do the outcome of the standardization bodies, to which the T5.2 partners

contribute, help to improve the SmartenIT mechanisms?

How can the SmartenIT research on novel applications and network behavior providenew use cases for standards or for proposed standard extensions?

Use cases are highly important, because they generally motivate the proposed extensions.A reliable assessment of the T5.2 outcomes needs to consider the following aspects:

The timeline of standardization proposals adoption is in many bodies way beyond athree years project duration. Thus, the work will be continued after SmartenIT runtime.

The standardization process is body-specific. For example:

o Bodies such as IETF accept contributions authored by individuals highlighting,thus, the name of an author, who also contributes to the project. They alsoaccept project names to be mentioned in the contributions at variable degrees.Everybody can post a contribution that sometimes is accepted for presentation.But the WG adoption decision may take several years and often happens afterthe project end. The datatracker tool of IETF helps to follow the contributionprocess.

o Bodies such as 3GPP only accept company contributions that are adopted as

standard items often within a year.Examples of standardization time lines:

Multi-Cost ALTO: first presented in Nov. 2010, became an IETF draft in May 2015

Inter-ALTO: first presented in Aug 2011. Was re-presented in March 2015

Calendar: first presented in in Nov 2011: expected acceptance 2015

3.3.2.2 Results

T5.2 produces three types of results:

Contributions in standardization bodies to new protocols or their extensions,

Definition of use cases: use cases are at least as important as protocols or theirextensions,

Follow-up of relevant bodies: this provides also knowledge advancements to theproject. Follow-up is crucial to detect which standard items can be used in SmartenITand which body should be targeted by the project to propose contributions.

A formal assessment method will be specified in T5.2, based on aspects of theStandardization Survey deliverable produced in the end of Y1.

The definition of the standardization work assessment method requires further discussionamong the T5.2 partners and will elaborate on the following items. Up to now, the followingmethodology elements have been identified:


25/105



Definition and specification of 3 levels of relevance for T5.2 results

o For example: loose, medium, high

Classification of T5.2 results w.r.t. these levels

Number of partner contributions issued by T5.2 partners Level of progress of contribution to standardization bodies

o For instance: posted, presented, adopted

o To be assessed w.r.t. the processes of the standardization body.

3.3.3 SmartenIT involvement in standardization bodies for Y3

Given the outcomes related to their submitted material in Y2 and the evolution of theproject, the T5.2 contributors were involved in the following bodies:

ITU-T IETF ACE

IETF ALTO

This section provides the SmartenIT achievements for each of these bodies.

3.3.3.1 Contributions on social-economic awareness at ITU-T

Due to the success of UZH within ITU-T and the positive feedback from industry, researchcommunity and academia UZH continued its work within ITU-T. Based on the first Swissacademic Recommendation Y.3013 [9] UZH pushed the integration of the Tussle Analysisas a standard method for upcoming recommendations. Therefore, UZH became activewithin the ITU-T RevCom and will participate in upcoming meetings at ITU-T. The UZHactivity is distributed as follows:

Study Group 17 looking at security issues (UZH)o April 24, 2015: Tussles for Edge Network Caching presented at ITU-T Workshop

(http://www.smartenit.eu/news/tusslesforedgenetworkcachingpresentedatitu-tworkshop)

o Tussle Analysis: of interest to the Y2 SmartenIT reviewers, intensive consortiumdiscussion since the Darmstadt-15 meeting.

SmartenIT: external liaision with EU project FLAMINGO

o Tussle Analysis: of interest to the Y2 reviewers3.3.3.2 Contributions on security issues at ITU-T

Based on meetings at the ITU-T premesis in November 2013 and standardization activityin IETF in the area of security, UZH was invited by the SG 17 chair to give a tutorial in April2015. The tutorial entitled Two-way Authentication for Tiny Devices covers a briefoverview about the research, the application area, developed solutions TinyDTLS andTinyTO, and lessons learned. The audience acknowledged these standard-basedsolutions, which allow for the support of a two-way authentication on constraint devices,like sensor nodes (e.g., TelosB or OPAL). The audience was pleased to learn that not onlytheoretical ideas were presented, but existing solutions and successfully running code.

The following discussions raised the question of what can be a common definition forconstraint devices. This seems to be a dedicated need for the ITU, since no formal


26/105



definition is in place. Furthermore, the question on how to perform the key managementand its standardization was asked.The meeting was successful in order to continue standardization efforts under ITU in theSG 17 addressing security issues, especially Questions 5 and 11. This activity is part of

the external liaison with EU project FLAMINGO as described in detail in Section 4.2.2.3.3.3.3 Contribution to ITU Workshop on "Future Trust and Knowledge

Infrastructure"

UZH held a presentation on "Tussles for Edge Network caching" at the ITU Workshop on"Future Trust and Knowledge Infrastructure", which took place on April 24, 2015 inGeneva, Switzerland. The workshops goal was to stimulate discussion on futureconverged ICT services and information infrastructure.

In this talk the Tussle Analysis was applied to a major SmartenIT scenario, to analyze andpredict socio-economic consequences, when content from social networks is cached innano Data Centers. Since there were several security and trust experts in the audience,valuable feedback on the proposed solution and evaluation was received. Therefore,UZHs presentation not only ensured SmartenITs visibility in a world-wide established andinfluential standardization organization, it also provided the basis for the establishment of avaluable feedback for the project to further improve the developed uNaDa cachingstrategies. Most importantly, the talk brought attention to the newly standardized TussleAnalysis, which supports its deployment by ITU member in the future development of ITUrecommendations.

3.3.3.4 Contributions on authentication for IoT at IETF ACE

UZH is also active in IETF in the WG ACE looking on authentication for constraint

environments. The current active Internet draft, entitled Two-way Authentication for IoT,see [5], was updated with new sections and feedback from the community for upcomingIETF meetings. Furthermore, WP2 assumes to integrate the proposed authenticationmechanisms, as a use-case scenario in the future of SmartenIT as the proposed solutionis a potential use-case in the Inter-cloud scenario in WP. In parallel UZH investigated howthe IETF work can be transferred to the ITU activity in the area of IoT.Based on the positive feedback in the years before, UZH continued the work on the two-way authentication in year 3 of SmartenIT. This includes an update of the draft entitledTwo-way Authentication for IoT. The first update published in December 2014 includedan update of the assumed architecture and use-cases description in general [16]. In June2015 UZH updated the draft again including now handshake description and hardware

requirements for more constraint device class1 devices [15].Due to the publications of IETF drafts and the participation in IETF meetings UZH wasinvited to present the security solution in the industry (e.g., Siemens Technology, Surfsara)as well as in the ITU-T in Study Group 17.

Beyond development of security solution as published within IETF ACE UZH was invited topresent its efficient data format TinyIPFIX at the NMRG workshop in conjunction with IETF93 in July 2015. This is an application that uses a template-based format for messagecontent based on the IPFIX standard for monitoring in IP networks. Together with thedevelopment of a new header format UZH was able to overcome the additional 20 Byteheader for IPFIX to make the format available for constraint devices and save message.


27/105



All mentioned activities are part of the external liaison with EU project FLAMINGO asdescribed in D5.4. Due to the positive feedback UZH will continue the security activity inIETF beyond the project end of SmartenIT.

3.3.3.5 Contributions on cross-layer cooperation at IETF ALTO WG

ALTO protocol extensions within the WG charter: The base ALTO protocol is now RFC7285 and the ALTO WG has been re-chartered in August 2014. The new charter ispublished on http://tools.ietf.org/wg/alto/charters. The ALTO Cost Calendar concept isintegrated in its extension item 3 that in particular plans Protocol extensions to convey aricher set of attributes to allow applications to determine not only "where" to connect butalso "when" to connect.. ALTO WG contributors are requested to provide, besides WGitems textual contributions, robust and running code on protocol functions. ALBLF puts thefocus on an elaborated ALTO Client that interoperates with ALTO Servers from differentcompanies and institutions written in different software environments. The ALBLFachievements are the following:

Implementation of an RFC 7285 compliant interoperable ALTO Client: this includesimplementation updates to support changes in transaction formats and protocol rules.

Protocol extension Multi-Cost ALTO used in the MUCAPS design: the related drafthas been adopted as an ALTO WG document at the IETF92 in Dallas and its iterationsare listed below.

o draft-randriamasy-alto-multi-cost-10 by S. Randriamasy and W. Roome (ALU)and N. Schwan (Thales) was presented at IETF92 Dallas in March 2015, wasadopted as a WG document and posted as draft-ietf-alto-multi-cost-00 in May 222015 and presented the updates at IETF93, see [25]

o draft-ieft-alto-multi-cost-00: Multi-Cost ALTO, (work in progress) S.Randriamasy and W. Roome (ALU) and N. Schwan (Thales), May 22nd 2015,http://tools.ietf.org/html/draft-randriamasy-alto-multi-cost-10.txt, see [27]

o draft-ieft-alto-multi-cost-01: Multi-Cost ALTO, (work in progress) S.Randriamasy and W. Roome (ALU) and N. Schwan (Thales), October 19th2015,presented at the ALTO WG virtual interim meeting related to IETF94 on October27th2015, https://tools.ietf.org/html/draft-ietf-alto-multi-cost-01, see [29]

ALTO Cost Calendar - suitable to the MUCAPS evolution and supporting Cloud-ISPinterfaces in the best effort traffic case. This protocol extension is part of the currentALTO WG charter. The related drafts and their presentation are listed below:

o ALTO Cost Calendar, S. Randriamasy (ALU), R. Yang (Yale), Q. Wu (Huawei),L. Deng (China Mobile), N. Schwan (Thales), IETF draft draft-randriamasy-alto-cost-calendar-03, March 9th 2015, Presented at the 92th IETF, Dallas USA,http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-03.txt, see [26]

o ALTO Cost Calendar, S. Randriamasy (ALU), R. Yang (Yale), Q. Wu (Huawei),L. Deng (China Mobile), N. Schwan (Thales), IETF draft draft-randriamasy-alto-cost-calendar-04, July 6th 2015, Presented at the 93th IETF, Prague CzechRep., http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-04.txt, see [28]

o ALTO Cost Calendar, S. Randriamasy (ALU), R. Yang (Yale), Q. Wu (Huawei),

L. Deng (China Mobile), N. Schwan (Thales), IETF draft draft-randriamasy-alto-cost-calendar-05, October 19th2015, presented at the ALTO WG virtual interim


28/105



meeting related to IETF94 on October 27th 2015, http://tools.ietf.org/id/draft-randriamasy-alto-cost-calendar-05.txt, see [30].

Proposal extending the ALTO charter: inter-ALTO

A presentation was done at IETF92 on: Inter-ALTO: A second attempt?.

A draft was written, see [24]. All use-cases were rewritten from scratch. The use-caseswere simplified and generalized.

The draft was presented at IETF93 in Prague, together with another draft: Pathextensions for the ALTO protocol: submitted as draft-wydrych-alto-paths-00.

The next steps depend on WGs interests.

Relation to SmartenIT: DTM might take inter-ALTO-gathered information whencalculating costs and setting up tunnels. It might replace remote traceroute in RB-

HORSTs topology proximity monitor

3.3.4 SmartenIT standardization bodies and meeting attendance

The SmartenIT T5.2 contributors attended standardization body meetings and monitoredactivity in the following groups, as detailed in this section:

ITU-T: by UZH,

IETF ACE WG: by UZH

IETF ALTO WG: by ALBLF and AGH

IRTF ICNRG by ICOM

3.3.4.1 ITU Telecommunication Standardization Sector

MAR: ITU-T Tutorial SG 17, April 2015

Based on Corinna Schmitt`s visit at ITU in November 2014 she was invited by the SG 17chair Martin Euchner to present a tutorial on security research under the umbrella of theexternal liaison between SmartenIT and FLAMINGO.

The tutorial entitled Two-way Authentication for Tiny Devices was held on April 15, 2015in front of SG 17 members (around 15 participants). The tutorial covers a brief overviewabout the research, the application area, developed solutions TinyDTLS and TinyTO, and

lessons learned. The audience acknowledged these standard-based solutions, which allowfor the support of a two-way authentication on constraint devices, like sensor nodes (e.g.,TelosB or OPAL). The audience was pleased to learn that not only theoretical ideas werepresented, but existing solutions and successfully running code. The following discussionsraised the question of what can be a common definition for constraint devices. This seemsto be a dedicated need for the ITU, since no formal definition is in place. Furthermore, thequestion on how to perform the key management and its standardization was asked. .

For the UZH participation the meeting can be considered as a successful disseminationactivity from SmartenIT and FLAMINGO, since this work originating from these projects inmain parts paved the path to continue standardization efforts within the ITU SG 17,

especially questions 5 and 11, addressing relevant security aspects of constraineddevices.


29/105



3.3.4.2 Internet Engineering Task Force (IETF) ACE WG

UZH participated in the IETF 93 held in Prague end of July. Corinna Schmit gave apresentation on TinyIPFIX in the NMRG Workshop and took part in the WG ACE meeting.This participation was done outside the scope of SmartenIT.

3.3.4.3 Internet Engineering Task Force (IETF) ALTO WG

MAR-ALBLF-2015-ALTO-IETF92

Sabine Randriamasy, the leader of task T5.2 Standardization in SmartenIT has attendedthe ALTO WG session at the 92thIETF that took place on March 26th2015 in Dallas, as acontributor the ALTO WG and its re-chartering inputs.

The ALTO WG has now a new chair: Jan Seedorf from NEC who replaces Enrico Maroccofrom Telecom Italia. For this meeting, the agenda preference has been given to agendawork-items and work items generating list discussion.

ALBLF contributes since 2010 with protocol extension proposals under which 2 werepresented and discussed at most of the ALTO WG meetings:

Multi-Cost ALTOoptimizes the ALTO transactions by conveying jointly multiple costsand supporting constraints combining AND and OR operators and besides proposesnew ALTO costs abstracting QoE impacting metrics.

The ALTO Cost Calendar provides time-based cost values helping to decide bothwhere and when to connect. ALBLF also co-authors an extension proposing ALTOcosts based on TE metrics collected via routing protocols. These three extensionproposals relate to and motivated the ALTO re-charter item number (iii).

2 decisions were taken during this meeting:

Moving the IETF draft ALTO deployment considerations to the Working Group LastCall step,

Adopting Multi-Cost ALTO as a working group document.

During this meeting, Piotr Wydrych from AGH presented t