Decentralized Internet address - Historie editací

Chronos v 16. 9. 2016, 05:41

2016-09-16T05:41:11Z

← Starší verze		Verze z 16. 9. 2016, 07:41
Řádek 88:		Řádek 88:
	To be able to connect to virtual network there will be some routers with known physical address location where clients can connect. Such nodes can allow to connect only to single virtual router or to multiple virtual routers and networks.		To be able to connect to virtual network there will be some routers with known physical address location where clients can connect. Such nodes can allow to connect only to single virtual router or to multiple virtual routers and networks.

			<pre>
	Client Server		Client Server
	Virtual IP: 3.34.60.6.2 => 6.22.673.3.11		Virtual IP: 3.34.60.6.2 => 6.22.673.3.11
	Physical IPv4: 1.2.3.4 => 5.6.7.8		Physical IPv4: 1.2.3.4 => 5.6.7.8
			</pre>

	====Takedown resistance====		====Takedown resistance====

Chronos v 16. 9. 2016, 05:40

2016-09-16T05:40:30Z

@@ Řádek 66: / Řádek 66: @@
 IPv6 address space can be mapped under particular network '''3.6.''' like '''3.6.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x''' or
 '''3.6.$0123.$4567.$89ab.$cdef.$0123.$4567.$89ab.$cdef''' or simply as '''3.6.$0123456789abcdef0123456789abcdef'''
 ==Potential problems==

Chronos v 8. 10. 2015, 17:18

2015-10-08T17:18:24Z

← Starší verze		Verze z 8. 10. 2015, 19:18
Řádek 40:		Řádek 40:
	This allows also to use MAC address as unique host address. For example: '''5.3.$fe45026371ec'''		This allows also to use MAC address as unique host address. For example: '''5.3.$fe45026371ec'''

	=====Address assignment====		====Address assignment====

	Authority could simply assign network addresses to entities. As length and address segment size are basically unlimited then there is no need to assign ''address range'' but rather just single address. For example authority could assign simply top level addresses like '''2''', '''34''', '''312312'''. Smaller number takes less memory as source or destination address. If entity receive for example assignment '''28''' then it can assign further lower level addresses like '''28.5''', '''28.6''' and so on. Network operator can assign address to their clients like '''28.6.17.22''' and then client can further connect its multiple local networks as '''28.6.17.22.3''', '''28.6.17.22.5'''. AS you can see variable long address can give much of freedom in address assignment. It is just matter of how long base address is assigned. Most problem with prefix based subnetting is avoided here and address can be just few bytes long.		Authority could simply assign network addresses to entities. As length and address segment size are basically unlimited then there is no need to assign ''address range'' but rather just single address. For example authority could assign simply top level addresses like '''2''', '''34''', '''312312'''. Smaller number takes less memory as source or destination address. If entity receive for example assignment '''28''' then it can assign further lower level addresses like '''28.5''', '''28.6''' and so on. Network operator can assign address to their clients like '''28.6.17.22''' and then client can further connect its multiple local networks as '''28.6.17.22.3''', '''28.6.17.22.5'''. AS you can see variable long address can give much of freedom in address assignment. It is just matter of how long base address is assigned. Most problem with prefix based subnetting is avoided here and address can be just few bytes long.

			===Packet header===

			All fields are encoded as VARBLOCK type.

			{\| class="wikitable"
			\| Version \|\| Source \|\| Destination \|\| Hop limit
			\|}

			* '''Version''' - Number of protocol version. 1 - means DIA1
			* '''Source''' - source address from where packet is originating
			* '''Destination''' - destination address where packet is heading
			* '''Hop limit''' - maximum number of routers through which packet can travel before it is dropped
			* '''Next header''' - type of next header data block

	===Mapping IPv4 and IPv6===		===Mapping IPv4 and IPv6===
Řádek 62:		Řádek 76:

	If particular source or destination address is not supported by router then router should inform source node about the problem. So maximum supported address could be detected on single path.		If particular source or destination address is not supported by router then router should inform source node about the problem. So maximum supported address could be detected on single path.

			===Needed processing power===

			As address consists of dynamic numbers encoded as variable length numbers then cost of processing packets is higher in comparison to static address.

Chronos v 8. 10. 2015, 16:44

2015-10-08T16:44:41Z

← Starší verze		Verze z 8. 10. 2015, 18:44
Řádek 9:		Řádek 9:
	===Dynamic address size===		===Dynamic address size===
	* Allow variable length address.		* Allow variable length address.
			* Avoid future limitation and need to introduce new address format and protocol
	* Allow short address for embedded and IoT devices.		* Allow short address for embedded and IoT devices which have low available memory.

	===Dynamic address segment===		===Dynamic address segment===
Řádek 39:		Řádek 40:
	This allows also to use MAC address as unique host address. For example: '''5.3.$fe45026371ec'''		This allows also to use MAC address as unique host address. For example: '''5.3.$fe45026371ec'''

			=====Address assignment====

			Authority could simply assign network addresses to entities. As length and address segment size are basically unlimited then there is no need to assign ''address range'' but rather just single address. For example authority could assign simply top level addresses like '''2''', '''34''', '''312312'''. Smaller number takes less memory as source or destination address. If entity receive for example assignment '''28''' then it can assign further lower level addresses like '''28.5''', '''28.6''' and so on. Network operator can assign address to their clients like '''28.6.17.22''' and then client can further connect its multiple local networks as '''28.6.17.22.3''', '''28.6.17.22.5'''. AS you can see variable long address can give much of freedom in address assignment. It is just matter of how long base address is assigned. Most problem with prefix based subnetting is avoided here and address can be just few bytes long.

	===Mapping IPv4 and IPv6===		===Mapping IPv4 and IPv6===

Chronos v 8. 10. 2015, 16:27

2015-10-08T16:27:31Z

← Starší verze		Verze z 8. 10. 2015, 18:27
Řádek 47:		Řádek 47:

	IPv6 address space can be mapped under particular network '''3.6.''' like '''3.6.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x''' or		IPv6 address space can be mapped under particular network '''3.6.''' like '''3.6.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x''' or
	'''3.6.$0123.$4567.$89ab.$cdef.$0123.$4567.$89ab.$cdef''' or simply as '''3.6.$0123456789abcdef0123456789abcdef'''		'''3.6.$0123.$4567.$89ab.$cdef.$0123.$4567.$89ab.$cdef''' or simply as '''3.6.$0123456789abcdef0123456789abcdef'''

	==Potential problems==		==Potential problems==

Chronos v 8. 10. 2015, 16:27

2015-10-08T16:27:16Z

← Starší verze		Verze z 8. 10. 2015, 18:27
Řádek 46:		Řádek 46:
	For example you can address entire IPv4 address space under '''3.5''' network using address like '''3.5.x.x.x.x'''		For example you can address entire IPv4 address space under '''3.5''' network using address like '''3.5.x.x.x.x'''

	~~You~~ ~~can~~ ~~also~~ ~~map~~ ~~IPv4~~ ~~address space~~ under particular network '''3.6.''' like '''3.6.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x'''.		IPv6 address space can be mapped under particular network '''3.6.''' like '''3.6.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x''' or
		⚫	'''3.6.$0123.$4567.$89ab.$cdef.$0123.$4567.$89ab.$cdef''' or simply as '''3.6.$0123456789abcdef0123456789abcdef'''

⚫	~~Or IPv6 could be also mapped in various ways like~~ '''3.6.$0123.$4567.$89ab.$cdef.$0123.$4567.$89ab.$cdef''' or simply as '''3.6.$0123456789abcdef0123456789abcdef'''

	==Potential problems==		==Potential problems==

Chronos v 8. 10. 2015, 16:26

2015-10-08T16:26:04Z

@@ Řádek 20: / Řádek 20: @@
 ===Address notation===
-Address can be simply written as numbers separated by dots like: '''1.22.36.4222.5.56'''
+Address can be simply written as numbers separated by dots like: '''1.22.36.4222.5.58'''
 Here first number is top most address segment and further numbers are define lower levels of address. Address space can be imagined as tree where branches can grow as necessary.
@@ Řádek 32: / Řádek 32: @@
 Then for example host with address '''4.55.3''' can simply address host with address '''4.55.2.7.73.5'''
 ==Potential problems==

Chronos v 8. 10. 2015, 15:38

2015-10-08T15:38:29Z

@@ Řádek 20: / Řádek 20: @@
 ===Address notation===
-Address can be simply written as numbers separated by dots like "1.22.36.4222.5.56". Here first number is top most address segment and further numbers are define lower levels of address. Address space can be imagined as tree where branches can grow as necessary.
+Address can be simply written as numbers separated by dots like: '''1.22.36.4222.5.56'''
 This allows mapping of one address space to another.
-Network in address space 2: 7.2.73
+Network in address space 1: '''4.55.2'''
 [[Kategorie:Síť]]

Chronos v 8. 10. 2015, 15:22

2015-10-08T15:22:10Z

← Starší verze		Verze z 8. 10. 2015, 17:22
Řádek 4:		Řádek 4:
	* Allow multiple address domains and inter-addressing. This should enable anyone to design own address registration authority. To communicate with other domains there is necessary to establish inter-domain addressing rules. Because length of address should be variable then anyone could map fully own top level address domain to other address domain.		* Allow multiple address domains and inter-addressing. This should enable anyone to design own address registration authority. To communicate with other domains there is necessary to establish inter-domain addressing rules. Because length of address should be variable then anyone could map fully own top level address domain to other address domain.
	* Mapping entire address space into node in other address space.		* Mapping entire address space into node in other address space.
			* Avoid single entity like IANA to rule entire global address space and charge for assigned address ranges.
			* Support inter-planetary addressing independent to single entity located on single planet

	===Dynamic address size===		===Dynamic address size===

Chronos: Založena nová stránka: ==Motivation== ===Decentralization=== * Allow multiple address domains and inter-addressing. This should enable anyone to design own address registration authority. To…

2015-10-08T15:17:57Z

Založena nová stránka: ==Motivation== ===Decentralization=== * Allow multiple address domains and inter-addressing. This should enable anyone to design own address registration authority. To…

Nová stránka

==Motivation==

===Decentralization===
* Allow multiple address domains and inter-addressing. This should enable anyone to design own address registration authority. To communicate with other domains there is necessary to establish inter-domain addressing rules. Because length of address should be variable then anyone could map fully own top level address domain to other address domain.
* Mapping entire address space into node in other address space.

===Dynamic address size===
* Allow variable length address.
* Allow short address for embedded and IoT devices.

===Dynamic address segment===
* Allow one address segment to be more then 256

==Description==

===Usage of variable length numbers===

===Address notation===

Address can be simply written as numbers separated by dots like "1.22.36.4222.5.56". Here first number is top most address segment and further numbers are define lower levels of address. Address space can be imagined as tree where branches can grow as necessary.
This allows mapping of one address space to another.
Network in address space 1: 4.55.2
Network in address space 2: 7.2.73
Mapped space 2 under network space 1: 4.55.2.7.2.73

[[Kategorie:Síť]]