Federated ONS Experimental Platform Demo

AFNIC R&D

Single-Root ONS Issues and Alternative Requirements

• Issues– ONS resolution at the root level is managed by a single

entity– Could use the authority to block certain

Organizations/Countries from using the ONS namespace– Could also use data from ONS resolution for economic

intelligence

• Requirements– No single entity is authoritative for the whole ONS

namespace– The sovereign ONS peer roots should be independent and

cooperate with each other

9

Federated ONS Architecture (F-ONS)

DNS Root

"ons-peer.com"  

ONS Peer Root

American

ONS

Local

ONS

"ons-peer.asia"  

ONS Peer Root

Japanese

ONS

Local

ONS

French

ONS

Maltese

ONS

"ons-peer.eu"  

ONS Peer Root

Local

ONS

Local

ONS

10

Federated ONS – How it works?

ONS Peer Root (Tree)

ONS Peer Root (Tree)

ONS Peer Root (Tree)

11

Tests : Phase 1

S.NO Scenario Originating Root

Test Results

1. Simple Case ons-peer.eu OK

2. Redirection ons-peer.eu OK

14

Tests : Phase 2

S.NO Scenario Originating Root

Test Results

1. Adding a new prefix (Malta) onseu.test OK

2. Querying Malta onsam.test NOK

3. Querying Malta(After updating the Mapping Table)

onsam.test OK

4. Moving Malta from «onseu.test» to «onsas.test»

onsam.test NOK

5. Querying Malta(After updating the Mapping Table)

onsam.test OK

15

CMT

European Root American Root Asian Root

Contributions/Future Work

• Contribution– F-ONS architecture– A Functionally tested F-ONS platform ready to export– Recommendation to the F-ONS requirements committee– Use the experience obtained for real business use-case

(Proxi-produit)

• Future Work– Quantitative tests– Benchmarking DNS based F-ONS to P2P based– Benchmarking DNS based F-ONS to DNS based single

root ONS

Questions ?