Domain & VLXAN...•Resume normal operation till conflict resolution Conflict Figure 11. Conflict...

Domain & VLXAN

Server-1 Server-2

Server-3Server-4

VTEP-1 VTEP-2

VTEP-3VTEP-4

• Server-1, Port 1/1• Server 2: VXLAN, VTEP-2• Server 3: VXLAN, VTEP-3• Server 4: VXLAN, VTEP-4

• Server 1: VXLAN, VTEP-1• Server-2, Port 1/2• Server 3: VXLAN, VTEP-3• Server 4: VXLAN, VTEP-4

• Server 1: VXLAN, VTEP-1• Server 2: VXLAN, VTEP-2• Server 3: VXLAN, VTEP-3• Server-4, Port 1/4

• Server 1: VXLAN, VTEP-1• Server 2: VXLAN, VTEP-2• Server-3, Port 1/3• Server 4: VXLAN, VTEP-4

Figure 1.

Internet & OCT Blockchain

Server-1 Server-2

Server-3Server-4

VTEP-1 VTEP-2

VTEP-3VTEP-4

• Server-1, Port 1/1 • Server-2, Port 1/2

• Server-4, Port 1/4 • Server-3, Port 1/3

Figure 2.

Internet & OCT Blockchain

Server-1 Server-2

Server-3Server-4

VTEP-1 VTEP-2

VTEP-3VTEP-4

• Server-1, Port 1/1• Server 2: BC, VTEP-2• Server 3: BC, VTEP-3• Server 4: BC, VTEP-4

• Server 1: BC, VTEP-1• Server-2, Port 1/2• Server 3: BC, VTEP-3• Server 4: BC, VTEP-4

• Server 1: BC, VTEP-1• Server 2: BC, VTEP-2• Server 3: BC, VTEP-3• Server-4, Port 1/4

• Server 1: BC, VTEP-1• Server 2: BC, VTEP-2• Server-3, Port 1/3• Server 4: BC, VTEP-4

Figure 3.

MPLS

Data Center

Corporate Office

Data Center

Branch Office

Branch Office

Branch Office

Branch Office

Branch Office

Branch Office

Public Internet

Metro E

Wireless

Dedicated Circuits

Figure 4. WAN

Data Center

Corporate Office

Data Center

Branch Office

Branch Office

Branch Office

Branch Office

Branch Office

Branch Office

MPLS

Public Internet

Metro E

Wireless

Dedicated Circuits

Dialup

Figure 5. SD-WAN

Colo 1 Colo 2 Colo 3

BD-WAN Controller Cluster

BD-WAN BD-WAN BD-WAN

CPE

CPE CPE CPE

CPE CPE CPE

LogicalPhysical Figure 6. BD-WAN

LBG LBG

Public Cloud

Services

BD-WAN Secure Cloud

Global Blockchain

Content Providers

BD-WAN Controller BD-WAN

• Instructions (Vector, Policy, QoS Marking…)• Resources (Local, Transocean, Cloud, Content)• Estimated Cost / Resource Unit

• Proposal Acceptance• Instructions Download For Execution• Minimum Threshold Cost Paid In Tokens

• Counters Set• Start of Operation

• Transaction Verified over Blockchain• Counters Set• Start of Operation

Initial State

Figure 7. Initial State


• Asynchronous Notifications for Payment (intokens) needed from the Unit for smoothoperation

• Payment Notification Acknowledgement• Extra amount paid in tokens

• Counters Set• Resume Normal Operation

• Transaction Verified over Blockchain• Counters Set• Resume Normal Operation

Steady StateCounters about to expire on controller

Figure 8. Steady State


• Transaction Verified over Blockchain• Counters Reset

• Counters about to expire on Unit• Extra amount paid in tokens

• Counters Reset• Resume Normal Operation

• Resume Normal Operation

Steady StateCounters about to expire on controller

Figure 9. Steady State


• Controller interrupts the Unit with some newinstruction sets

• Controller refunds the Unit with the remainingToken balance (if any) • Unit acknowledges the new instruction sets

• Unit verifies the refund over the blockchain• Unit paid to the Controller at least the minimum

threshold amount required for normal operation

• Counters Set• Start of Operation

• Controller verifies the new transaction over theblockchain

• Counters set• Start of Operation

Interrupt

Figure 10. Interrupt


• Asynchronous Notification for Payment neededfrom the Unit for smooth operation

• Unit does NOT acknowledge the paymentnotification as it believes there is still someremaining balance (service not used, nosynchronization between Controller & Unit

• “Judge Needed” from the log over the blockchain

• Start new counters (clean counters)• Resume normal operation till conflict resolution

• Controller acknowledges the need for a judge• Start new counters (dean counters)• Resume normal operation till conflict resolution

Conflict

Figure 11. Conflict

Figure 12. Hexadecimal Conversion

Investors who wantto participate

OCTb OCTb

ERC-20 Tokens

OCTb Token HoldersOCTb OCTbOCTb

OpenCT Platform with OCT Tokens

OCTb Stake HolderOCTb OCTbOCTb

OCT Stake HolderOCT OCTOCT

OCT OCTOCT

OCT Stake Holder /Block Producer

OCT OCTOCT

Figure 13. OCT Reward System

OCT OCTOCT

OCT OCTOCT

EA

B

C

1

D

J

H

F

G

I

K

M

L

2

Figure 14. Blockchain Propagation

DestinationSource


LogicalPhysical

Figure 15 (a)

Figure 15 (b)

Figure 15 (c)

Figure 15 (d)

Figure 15 (e)

Figure 15 (f)

Figure 15 (g)

Figure 15 (h)

Figure 16 (a)

Figure 16 (b)

Figure 16 (c)

Figure 16 (d)

Figure 16 (e)

Figure 16 (f)

Figure 16 (g)cFigure 16 (h)

Figure 17. Hybrid Blockchain

Public Blockchain

Private BlockchainE

A

B

C

1

D

J

H

F

G

I

K

M

L

2

DestinationSource

Private / NetworkPublic / Assets

2

Destination

1

Source

[Figure 18] Blockchain Growth Management

BlockchainE

A

B

H

I

K

L

BArchiving

Compression

Removal

TCP/IP Verification

OpenCT BlockchainC

A

B

A

1

B

D

D

C

E

E

F

F

G

2

DestinationSource


Open CT BlockchainTCP/IP Verification [Figure 19] TCP/IP and OPEN CT Blockchain operating together

G

1

Source2

Destination

Figure 20. BaaT Protocol vs. data transport protocols

Feature UDP UDP-Lite TCP Multipath TCP SCTP DCCP RUDP[a]BaaT Encrypted BaaT Native

Packet header size 8 bytes 8 bytes 20–60 bytes 50–90 bytes 12 bytes[b] 12 or 16 bytes 14+ bytes74 bytes 50 bytes

Typical data-packet overhead 8 bytes 8 bytes 20 bytes ?? bytes 44–48+ bytes[c] 12 or 16 bytes 14 bytes74 bytes 50 bytes

Transport-layer packet entity Datagram Datagram Segment Segment Datagram Datagram DatagramSegment Segment

Connection-oriented No No Yes Yes Yes Yes Yes Yes Yes

Reliable transport No No Yes Yes Yes No Yes Yes Yes

Unreliable transport Yes Yes No No Yes Yes Yes No No

Preserve message boundary Yes Yes No No Yes Yes Yes No No

Delivery Unordered Unordered Ordered OrderedOrdered / Unordered Unordered Unordered Ordered Ordered

Datachecksum Optional Yes Yes Yes Yes Yes Optional Yes Yes

Checksum size 16 bits 16 bits 16 bits 16 bits 32 bits 16 bits 16 bits 32 bits 16 bits

Partialchecksum No Yes No No No Yes No No No

PathMTU No No Yes Yes Yes Yes ? Yes Yes

Flow control No No Yes Yes Yes No Yes Yes Yes

Congestion control No No Yes Yes Yes Yes ? Yes Yes

Explicit Congestion Notification No No Yes Yes Yes Yes ? Yes Yes

Multiplestreams No No No No Yes No No Yes Yes

Multi-homing No No No Yes Yes No No Yes Yes

Bundling /Nagle No No Yes Yes Yes No ? Yes Yes

[Figure 21] Governance

Pre-Token Crowdsale Token Crowdsale Reserve Miner Reward

% from the maximum supply of Tokens 10% 40% 35% 15%

Number of Tokens available

25,000,000 100,000,000 87,500,000 37,500,000

[Figure 22] Token Distribution

[Figure 23]

[Figure 24]

[Figure 25] The OCT rewarding system

[Figure 25] The OCT rewarding system

Investors who want to participate

ERC—20 tokens: OTCbc

c

OTCb Token Holders

OTCb Stake Holders

OTC Stake Holders

Open CT PlatformWith OCT Tokens

[Figure 26] The OSI Model

Layer 1: Physical

Layer 6: Presentation

Layer 7: Application

Layer 5: Session

Layer 4: Transport

Layer 3: Network

Layer 2: Data Link

Receive DataSend Data

Open CT Blockchain

BD WAN Controller

BD WAN Controller

Fig 27 - BD WAN Logical Diagram

BD WAN Unit

BD WAN Unit LBG Colo

Gateway

BD WAN Controller

Figure 28. OpenCT Marketplace - Bandwidth

Telco 1 Telco 2 Telco X

OpenCT Marketplace

Public Cloud / Public Internet Destination

Request

OpenCT Routing Decisions



Colo 1 Colo 2 Colo 3


BD-WAN BD-WAN BD-WAN

CPE

CPE CPE CPE

CPE CPE CPE

LogicalPhysical

LBG LBG

Public Cloud

Services

BD-WAN Secure Cloud

Global Blockchain

Content Providers

Figure 29. OpenCT Marketplace – Super, Mid, Mini

Global Marketplace

Intranet

Enterprise/ Carrier

Figure 29. OpenCT Marketplace – Super, Mid, Mini

Domain & VLXAN...•Resume normal operation till conflict resolution Conflict Figure 11. Conflict...

Documents

Transcript of Domain & VLXAN...•Resume normal operation till conflict resolution Conflict Figure 11. Conflict...