Decentralization - Revision history

KI5QKX: mw push

2026-03-01T01:14:38Z

mw push

← Older revision		Revision as of 01:14, 1 March 2026
Line 63:		Line 63:
	* [[IPIP Mesh]]		* [[IPIP Mesh]]
	* [[BGP]]		* [[BGP]]
	* [[~~Ways to Connect~~]]		* [[Provisioning Methods]]

KI5QKX: mw push

2026-02-28T23:20:33Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 5:		Line 5:
	Instead, ARDC stewards the address space while independent operators bring portions of 44Net online using different technical approaches. These approaches coexist within the same address space, but they are not automatically integrated with one another.		Instead, ARDC stewards the address space while independent operators bring portions of 44Net online using different technical approaches. These approaches coexist within the same address space, but they are not automatically integrated with one another.

	== One ~~Address Space~~, ~~Many Networks~~ ==		== One address space, many networks ==

	Because 44Net is decentralized, participation happens through multiple independent systems rather than a single unified service. Think of 44Net as shared addressing used by many independently operated networks, rather than one global network run from a single place.		Because 44Net is decentralized, participation happens through multiple independent systems rather than a single unified service. Think of 44Net as shared addressing used by many independently operated networks, rather than one global network run from a single place.

	== Three ~~Ways~~ to ~~Put~~ 44Net on ~~Your Network~~ ==		== Three ways to put 44Net on your network ==

	There are several common ways to make 44Net addresses reachable from participating systems:		There are several common ways to make 44Net addresses reachable from participating systems:
Line 25:		Line 25:
	* Often used for regional or collaborative networks		* Often used for regional or collaborative networks

	=== [[BGP\|BGP ~~Announcements~~]] ===		=== [[BGP\|BGP announcements]] ===
	* Independently operated networks announce their own 44Net prefixes		* Independently operated networks announce their own 44Net prefixes
	* Requires upstream connectivity and an {{Term\|ASN}}		* Requires upstream connectivity and an {{Term\|ASN}}
Line 33:		Line 33:
	Sometimes these seem like stages or upgrade levels, but they are really just different methods of participation. Many networks use a combination of these approaches based on the nature of each project.		Sometimes these seem like stages or upgrade levels, but they are really just different methods of participation. Many networks use a combination of these approaches based on the nature of each project.

	== Why ~~These Systems Are Independent~~ ==		== Why these systems are independent ==

	The separation between Connect, Mesh, and BGP is a natural consequence of 44Net’s decentralized nature.		The separation between Connect, Mesh, and BGP is a natural consequence of 44Net’s decentralized nature.
Line 52:		Line 52:
	Connectivity in 44Net emerges from cooperation between participants rather than centralized control.		Connectivity in 44Net emerges from cooperation between participants rather than centralized control.

	== Can I ~~Move~~ or ~~“Port” My Subnet Between Systems~~? ==		== Can I move or “port” my subnet between systems? ==

	No. A subnet allocation is effectively tied to its origin. There is no migration path because the systems are independent by design.		No. A subnet allocation is effectively tied to its origin. There is no migration path because the systems are independent by design.
Line 58:		Line 58:
	You can, however, operate subnets in multiple systems simultaneously. You can even have multiple subnets accessible through a single router you operate, as long as you manage the routing appropriately. But there is no way to “port” a subnet from one system to another.		You can, however, operate subnets in multiple systems simultaneously. You can even have multiple subnets accessible through a single router you operate, as long as you manage the routing appropriately. But there is no way to “port” a subnet from one system to another.

	== See ~~Also~~ ==		== See also ==

	* [[44Net Connect]]		* [[44Net Connect]]

KI5QKX: mw push

2026-02-27T22:06:31Z

mw push

← Older revision		Revision as of 22:06, 27 February 2026
Line 25:		Line 25:
	* Often used for regional or collaborative networks		* Often used for regional or collaborative networks

	=== [[BGP Announcements]] ===		=== [[BGP\|BGP Announcements]] ===
	* Independently operated networks announce their own 44Net prefixes		* Independently operated networks announce their own 44Net prefixes
	* Requires upstream connectivity and an {{Term\|ASN}}		* Requires upstream connectivity and an {{Term\|ASN}}

KI5QKX: mw push

2026-02-27T21:54:08Z

mw push

← Older revision		Revision as of 21:54, 27 February 2026
Line 13:		Line 13:
	There are several common ways to make 44Net addresses reachable from participating systems:		There are several common ways to make 44Net addresses reachable from participating systems:

	=== 44Net Connect ===		=== [[44Net Connect]] ===
	* Provides a reachable 44Net address directly to a device or local network		* Provides a reachable 44Net address directly to a device or local network
	* Uses a managed WireGuard-based service		* Uses a managed WireGuard-based service
Line 19:		Line 19:
	* Suitable for experimentation, services, and individual participation		* Suitable for experimentation, services, and individual participation

	=== IPIP Mesh ===		=== [[IPIP Mesh]] ===
	* A cooperative overlay network operated by participating nodes		* A cooperative overlay network operated by participating nodes
	* Routers form tunnels with peers and exchange routes		* Routers form tunnels with peers and exchange routes
Line 25:		Line 25:
	* Often used for regional or collaborative networks		* Often used for regional or collaborative networks

	=== BGP Announcements ===		=== [[BGP Announcements]] ===
	* Independently operated networks announce their own 44Net prefixes		* Independently operated networks announce their own 44Net prefixes
	* Requires upstream connectivity and an {{Term\|ASN}}		* Requires upstream connectivity and an {{Term\|ASN}}

KI5QKX: mw push

2026-02-27T21:50:26Z

mw push

← Older revision		Revision as of 21:50, 27 February 2026
Line 27:		Line 27:
	=== BGP Announcements ===		=== BGP Announcements ===
	* Independently operated networks announce their own 44Net prefixes		* Independently operated networks announce their own 44Net prefixes
	* Requires upstream connectivity and an {{Term\|ASN}} ~~(or an upstream provider's ASN)~~		* Requires upstream connectivity and an {{Term\|ASN}}
	* Operators manage routing policy and infrastructure themselves		* Operators manage routing policy and infrastructure themselves
	* Used by organizations or established network operators		* Used by organizations or established network operators

KI5QKX: mw push

2026-02-27T21:47:49Z

mw push

New page

{{DISPLAYTITLE:How Connect, IPIP Mesh, and BGP Fit Together}}

44Net is a '''decentralized network space'''. There is no single backbone, central router, or network operations center coordinating connectivity for all participants.

Instead, ARDC stewards the address space while independent operators bring portions of 44Net online using different technical approaches. These approaches coexist within the same address space, but they are not automatically integrated with one another.

== One Address Space, Many Networks ==

Because 44Net is decentralized, participation happens through multiple independent systems rather than a single unified service. Think of 44Net as shared addressing used by many independently operated networks, rather than one global network run from a single place.

== Three Ways to Put 44Net on Your Network ==

There are several common ways to make 44Net addresses reachable from participating systems:

=== 44Net Connect ===
* Provides a reachable 44Net address directly to a device or local network
* Uses a managed WireGuard-based service
* Requires minimal routing knowledge
* Suitable for experimentation, services, and individual participation

=== IPIP Mesh ===
* A cooperative overlay network operated by participating nodes
* Routers form tunnels with peers and exchange routes
* Connectivity emerges from relationships between operators
* Often used for regional or collaborative networks

=== BGP Announcements ===
* Independently operated networks announce their own 44Net prefixes
* Requires upstream connectivity and an {{Term|ASN}} (or an upstream provider's ASN)
* Operators manage routing policy and infrastructure themselves
* Used by organizations or established network operators

Sometimes these seem like stages or upgrade levels, but they are really just different methods of participation. Many networks use a combination of these approaches based on the nature of each project.

== Why These Systems Are Independent ==

The separation between Connect, Mesh, and BGP is a natural consequence of 44Net’s decentralized nature.

Each method has its own:

* control plane
* operational responsibilities
* trust relationships
* routing mechanisms

ARDC assigns address space, but does not operate a unified routing system for all users. As a result, no automatic coordination exists between participation methods.

A subnet reachable via Connect is not automatically part of the Mesh.
A Mesh network does not automatically appear via BGP.
A BGP-announced network operates independently unless operators choose to interconnect.

Connectivity in 44Net emerges from cooperation between participants rather than centralized control.

== Can I Move or “Port” My Subnet Between Systems? ==

No. A subnet allocation is effectively tied to its origin. There is no migration path because the systems are independent by design.

You can, however, operate subnets in multiple systems simultaneously. You can even have multiple subnets accessible through a single router you operate, as long as you manage the routing appropriately. But there is no way to “port” a subnet from one system to another.

== See Also ==

* [[44Net Connect]]
* [[IPIP Mesh]]
* [[BGP]]
* [[Ways to Connect]]