CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Deliverable D2.2 - Core Transport System, with both Low-level and High-level Components
University of Oslo, Norway.
Dell EMC.
Karlstad University, Faculty of Health, Science and Technology (starting 2013), Department of Mathematics and Computer Science (from 2013). (DISCO)ORCID iD: 0000-0001-7311-9334
University of Oslo, Norway.
Show others and affiliations
2017 (English)Report (Refereed)
Abstract [en]

This document presents the core transport system in NEAT, as used for development of the

reference implementation of the NEAT System. The document describes the components

necessary to realise the basic Transport Services provided by the NEAT User API, with the

description of a set of NEAT building blocks and their related design choices. The design

of this core transport system takes into consideration the Transport Services and the API

(defined in Task 1.3) and in close coordination with the overall architecture (Task 1.2).

To realise the Transport Services provided by the API, a set of transport functionalities

has to be provided by the NEAT Core Transport System. These functionalities take the form

of several building blocks, or NEAT Components, each representing an associated implementation

activity. Some of the components are needed to ensure the basic operation of

the NEAT System—e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, the

NEAT Logic and the functionality to Connect to a name. Additional components are needed

for: (a) ensuring connectivity, by means of mechanisms for discovery of path support for

different protocols; (b) supporting end-to-end security; (c) the ability to apply different

policies to influence the decision-making process of the transport system; (d) providing

other important functionalities (e.g., a user-space SCTP stack, or gathering statistics for

users or system administrators).

This document updates Deliverable D2.1; in particular, the descriptions of NEAT components

presented here correspond to the implementation status at the time of writing,

and as such they replace those in D2.1.

Place, publisher, year, edition, pages
2017. , p. 115
National Category
Telecommunications
Research subject
Computer Science
Identifiers
URN: urn:nbn:se:kau:diva-70622OAI: oai:DiVA.org:kau-70622DiVA, id: diva2:1273846
Projects
A New, Evolutive API and Transport-Layer Architecture for the Internet (NEAT)
Funder
EU, Horizon 2020, 644334Available from: 2018-12-22 Created: 2018-12-22 Last updated: 2018-12-28Bibliographically approved

Open Access in DiVA

fulltext(1633 kB)22 downloads
File information
File name FULLTEXT01.pdfFile size 1633 kBChecksum SHA-512
517ae3cbd68ffe6413b27b40f899b77a1381067b88f0ef3ff5ae430443e8b9584446f6131183a3741ccccfa2587677ca0504a281bd14d88f5a7098dea6353be0
Type fulltextMimetype application/pdf

Authority records BETA

Brunström, AnnaGrinnemo, Karl-Johan

Search in DiVA

By author/editor
Brunström, AnnaGrinnemo, Karl-Johan
By organisation
Department of Mathematics and Computer Science (from 2013)
Telecommunications

Search outside of DiVA

GoogleGoogle Scholar
Total: 22 downloads
The number of downloads is the sum of all downloads of full texts. It may include eg previous versions that are now no longer available

urn-nbn

Altmetric score

urn-nbn
Total: 18 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf