Transient Network Architecture http:hdl'handle'net2118tna

1
Transient Network Architecturehttp//hdl.handle.n
et/2118/tna

• Presented by Henry Jerez
• CNRI/UNM

2
What is TNA

• It is an architecture that postulates that
• All networks can be reduced to a particular case
  of persistently identified, transient, mobile,
  abstract entities that group into particular
  association
• It is an abstraction based persistent
  communication network for transient digital
  entities

3
TNA Principles

• Mobility and Ad Hoc characteristics as basic
  requirements
• Abstraction as the basis of internetworking and
  functionality
• Persistence

4
Mobility and Ad Hoc characteristics

• All components of the architecture are to be
  considered transient and mobile
• The components must operate in both
• Connected Full cohesive communication with the
  larger structure is assumed
• Disconnected limited or no connectivity with
  other groupings is possible
• While consolidation is possible all processes,
  services and mechanisms should assume a mobile
  deployment environment.
• Mobility is the ability of nodes to change
  association without breaking referential
  integrity.

5
Abstraction

• All entities that communicate in the system are
  abstracted as digital entities that encapsulate
  and express all system functionality inside of
  them
• All networks are logical abstractions of a group
  of digital entities organized with a common Goal
  ( more details about this on the next slide)

6
From circuit based to persistent end to end
7
Digital Entity Abstraction

• Digital entity abstraction requires the
  characterization of entities over a common
  neutral layer
• Part of the intrinsic behaviors of that layer
  include
• Self certification
• Data encapsulation
• A common set of rights expressiveness

8
Digital Entity Abstraction
9
Network abstraction

• We currently have identified two network
  abstractions
• Naming network abstraction characterized as a
  fully distributed system that performs delegation
  and resolution at three different levels
• Instance ( red )
• Local ( yellow )
• Global ( green )
• Routing network abstraction characterized as an
  interconnected mesh of digital entities or their
  aggregations with the following basic constructs
• Area of Influence ( basic grouping mechanism of
  nodes that share a common set of communication
  principles)
• Green Network ( Basic grouping of multiple AoIs)

10
Network Abstraction
11
Persistent Identification

• Persistently identify
• globally Digital entities
• Network components
• Communicating entities
• Services
• Processes
• Identification is based on a set of unique naming
  spaces with a distributed resolution and name
  assignment mechanism

12
Network Abstraction
13
Network Abstraction and Management

• We route packets over abstract networks to
  abstract locations at the top level
• We manage Abstract entities that are part of
  abstract networks
• We operate in the logical space and use tools to
  isolate the physical space
• We can fine tune our perception at any point

14
How do we use PIs

• We identify all Network entities with persistent
  identifiers
• We use these identifiers to route all traffic in
  the network
• We identify particular associations with
  persistent identifiers
• We provide secure distributed administration
• This enables seamless mobility

15
How do the pieces fit together
16
What can it do

• Network Protocol independent
• Enables new transmission paradigms
• It can move functionality at will

17
Current Research Tracks

• The MESH Network AoI Implementation
• Agent Coordination
• Basic DRM expressiveness

18
MESH platform
19
Agent Coordination
20
Security and DRM

• Ghost
• Shell
• Self signing
• Certification

21
Interoperability offers

• Networks control their AoI communication
  technology
• Networks choose their routing policies as long as
  they can understand the PIs
• Networks can perform translations aggregations
  and new implementations at will as long as they
  keep them local
• Networks can perform slow adoption

22
Interoperability Requirements

• Identifier persistence
• All traffic routed through persistent identifiers
• Respect Local implementation independence
• Keep the flow
• Respect the Ghost in the Shell approach