13TH IEEE International Conference on Network Protocols (ICNP'05)
DOI: 10.1109/icnp.2005.44
|View full text |Cite
|
Sign up to set email alerts
|

Typed Abstraction of Complex Network Compositions

Abstract: The

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
5
0

Publication Types

Select...
2
1
1

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(6 citation statements)
references
References 5 publications
1
5
0
Order By: Relevance
“…The work in this paper extends and generalizes our earlier work in TRAFFIC (Typed Representation and Analysis of Flows For Interoperability Checks [4]), and complements our earlier work in CHAIN (Canonical Homomorphic Abstraction of Infinite Network protocol compositions [8]). …”
Section: Related Work and Conclusionsupporting
confidence: 54%
See 1 more Smart Citation
“…The work in this paper extends and generalizes our earlier work in TRAFFIC (Typed Representation and Analysis of Flows For Interoperability Checks [4]), and complements our earlier work in CHAIN (Canonical Homomorphic Abstraction of Infinite Network protocol compositions [8]). …”
Section: Related Work and Conclusionsupporting
confidence: 54%
“…If parameters are multi-sorted, then ϕ and ψ must respect sorts, i.e., if ϕ(x) = y then both x and y must be of the same sort, e.g., both velocity parameters, or both density parameters, etc., and similarly for ψ. 4 Pre-and Post-Conditions. A typing or a typed specification for an untyped CFN M is an expression of the form (M : C * ) or, if fully spelled out,…”
Section: Overview Of the Netsketch Formalismmentioning
confidence: 99%
“…Other example flow types are given through-out the paper, however an exhaustive account of the nature (and semantic) of these flow types is beyond the scope of this paper. We refer the reader to our work on using strong-typing for the compositional analysis of safety properties of networking applications [3] for some insight as to how flowtypes could be type checked for safety. SNAFU Compilation: SNAFU has been designed to ensure that the abstract syntax tree (AST) of a SNAFU program maps to a task dependency diagram in the form of a directed acyclic graph (DAG) with a single root.…”
Section: The Snafu Programming Languagementioning
confidence: 99%
“…SNAFU Compilation: SNAFU has been designed to ensure that the abstract syntax tree (AST) of a SNAFU program maps to a task dependency diagram in the form of a directed acyclic graph (DAG) with a single root. 3 Nodes in the DAG represent values, sensors or tasks while edges represent data communication/dependency between nodes. The graph is evaluated by lower nodes executing (using their children as input) and producing values to their parents such that values percolate up toward the root of the graph from the leaves.…”
Section: The Snafu Programming Languagementioning
confidence: 99%
“…Interaction complexity has produced service incompatibilities that point out a fundamental weakness in our current layered-design methodology [7,8]. Increased choice has led to a proposal for end-to-end cross-layer negotiation [23].…”
Section: Related Workmentioning
confidence: 99%