About 44Net - Revision history

KI5QKX: mw push

2026-03-01T01:14:29Z

mw push

← Older revision		Revision as of 01:14, 1 March 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:About 44Net}}		{{DISPLAYTITLE:About 44Net}}

	This page provides historical background and context. For onboarding and provisioning paths, start with [[GetStarted\|Getting Started]], [[~~Ways to Connect~~\|~~Ways to Connect~~]], and the [[~~Main Page Draft\|~~Main Page]].		This page provides historical background and context. For onboarding and provisioning paths, start with [[GetStarted\|Getting Started]], [[Provisioning Methods\|Provisioning Methods]], and the [[Main Page]].

	== What 44Net is and is not ==		== What 44Net is and is not ==

KI5QKX: mw push

2026-02-28T18:34:57Z

mw push

← Older revision		Revision as of 18:34, 28 February 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:About 44Net}}		{{DISPLAYTITLE:About 44Net}}

	This page provides historical background and context. For onboarding and ~~connection~~ paths, start with [[GetStarted\|Getting Started]], [[Ways to Connect\|Ways to Connect]], and the [[Main Page Draft\|Main Page]].		This page provides historical background and context. For onboarding and provisioning paths, start with [[GetStarted\|Getting Started]], [[Ways to Connect\|Ways to Connect]], and the [[Main Page Draft\|Main Page]].

	== What 44Net is and is not ==		== What 44Net is and is not ==

KI5QKX: mw push

2026-02-27T21:47:17Z

mw push

← Older revision		Revision as of 21:47, 27 February 2026
Line 40:		Line 40:

	44Net does not operate as a centrally delivered service. The network is sustained by participants who treat it as something worth maintaining for those who come after them.		44Net does not operate as a centrally delivered service. The network is sustained by participants who treat it as something worth maintaining for those who come after them.
			For a deeper explanation of how independent participation methods coexist, see [[Decentralization]].

	Related pages:		Related pages:

KI5QKX: mw push

2026-02-25T23:50:15Z

mw push

← Older revision		Revision as of 23:50, 25 February 2026
Line 21:		Line 21:
	For more historical background as told by people who were there at the beginning, watch [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].		For more historical background as told by people who were there at the beginning, watch [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].

	== Why public ~~addressing is relevant~~ ==		== Why public addresses? ==

	Using publicly routable space changes what you can learn and build:		Using publicly routable space changes what you can learn and build:

KI5QKX: mw push

2026-02-25T23:48:13Z

mw push

KI5QKX: mw push

2026-02-25T23:30:48Z

mw push

← Older revision		Revision as of 23:30, 25 February 2026
Line 5:		Line 5:
	== What 44Net is and is not ==		== What 44Net is and is not ==

	44Net is shared technical infrastructure used and maintained by the people who participate in it. Participants operate systems on publicly routable IPv4 space, enabling projects that require ~~direct reachability,~~ stable addressing, and Internet-visible services.		44Net is shared technical infrastructure used and maintained by the people who participate in it. Participants operate systems on publicly routable IPv4 space, enabling projects that require stable addressing and Internet-visible services.

	44Net is not a consumer ISP product or a managed hosting platform. Participants run and maintain their own systems, coordinate with one another, and contribute to the long-term health of the network.		44Net is not a consumer ISP product or a managed hosting platform. Participants run and maintain their own systems, coordinate with one another, and contribute to the long-term health of the network.
Line 11:		Line 11:
	== History and origins ==		== History and origins ==

	44Net traces back to 1981, when Hank Magnuski requested IP address space from Jon Postel for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.		44Net traces back to 1981, when [https://en.wikipedia.org/wiki/Hank_Magnuski Hank Magnuski] requested IP address space from [https://en.wikipedia.org/wiki/Jon_Postel Jon Postel] for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.

	Over time, those early packet-radio experiments expanded into a broader ~~ecosystem~~. As connectivity methods changed, the same address space supported routing experiments, infrastructure projects, and community-built services across many kinds of links.		Over time, those early packet-radio experiments expanded into a broader system. As connectivity methods changed, the same address space supported routing experiments, infrastructure projects, and community-built services across many kinds of links.

	In 2019, a portion of ~~legacy~~ AMPRNet address space was sold. The proceeds ~~enabled the creation and~~ long-term funding of [https://www.ardc.net ARDC], which supports ongoing 44Net operations as well as broader grants for open communications and digital infrastructure.		In 2019, a portion of AMPRNet address space was sold. The proceeds established long-term funding of [https://www.ardc.net ARDC], which supports ongoing 44Net operations as well as broader [https://www.ardc.net/grants grants] for open communications and digital infrastructure.

	The evolution has been additive rather than substitutive. New technologies have layered onto earlier practices, while the core idea — learning by operating real networks — has remained ~~consistent~~.		The evolution has been additive rather than substitutive. New technologies have layered onto earlier practices, while the core idea — learning by operating real networks — has remained steady.

	For ~~firsthand~~ historical background, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].		For more historical background as told by people who were there at the beginning, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].

	== Why public ~~address space changes what you can build~~ ==		== Why public addressing is relevant ==

	Using publicly routable space changes what you can learn and build:		Using publicly routable space changes what you can learn and build:
	* ~~services~~ can be directly reachable without depending only on NAT traversal		* Services can be directly reachable without depending only on NAT traversal.
	* ~~routing~~, naming, and security practices can be tested in realistic conditions		* Networks can operate independently of any single hosting provider or transit network.
	* ~~projects~~ can grow from ~~one~~ host to routed subnets and multi-site networks		* Routing, naming, and security practices can be tested in realistic conditions.
			* Projects can grow from a single host to routed subnets and multi-site networks.

	In short, 44Net makes it possible to conduct experiments under real operational conditions rather than only in isolated lab environments.		In short, 44Net makes it possible to conduct experiments under real operational conditions rather than only in isolated lab environments.
Line 33:		Line 34:

	44Net is sustained by a shared model:		44Net is sustained by a shared model:
	* [https://www.ardc.net ARDC] ~~provides~~ legal ~~stewardship~~, fiduciary ~~continuity~~, and organizational ~~support~~		* [https://www.ardc.net ARDC] bears legal, fiduciary, and organizational responsibilities of maintaining the address space.
	* ~~participants~~ operate systems, run services, maintain links, and collaborate on ~~best practices~~		* Participants operate systems, run services, maintain links, and collaborate on project development.

	This balance ~~keeps~~ the network stable enough to build on ~~over time~~, while remaining open to experimentation and change.		This balance helps keep the network stable enough to build on for the long term, while remaining open to experimentation and change in the short term.

	44Net does not operate as a centrally delivered service~~. It more closely resembles shared infrastructure that participants help maintain and build upon. Address space and core infrastructure persist over time, while individual projects come and go~~. The network ~~continues because~~ participants treat it as something worth maintaining for those who come after them.		44Net does not operate as a centrally delivered service. The network is sustained by participants who treat it as something worth maintaining for those who come after them.

	Related pages:		Related pages:
Line 47:		Line 48:
	== Participation norms ==		== Participation norms ==

	Over ~~time~~, several practices have become common across the 44Net community:		Over the years, several practices have become common across the 44Net community:
	* ~~experimentation~~ and learning are encouraged		* Experimentation and learning are encouraged.
	* ~~non~~-commercial use and community benefit are expected		* Sharing knowledge and working in the open are valued.
	* ~~operators~~ are expected to run their systems responsibly		* Non-commercial use and community benefit are expected.
	* ~~unused~~ resources are returned so others can build		* Operators are expected to run their systems responsibly.
			* Unused resources are returned so others can build.

	== Ways people encounter 44Net ==		== Ways people encounter 44Net ==

	People often arrive at 44Net through ~~a specific~~ project~~, community,~~ or technical path~~. Those first impressions are real, but they represent only one part of a larger~~ ecosystem.		People often arrive at 44Net through one project or technical path before discovering the broader ecosystem.

	Some encounter ~~44Net~~ through regional RF networks ~~such as HamWAN~~ or ~~other microwave and mesh efforts~~. Others ~~first see~~ it through services ~~like~~ IRLP, ~~experimentation platforms~~, ~~research collaborations~~, or ~~connection methods such as~~ 44Net Connect. ~~Each reflects a~~ different ~~facet of~~ the ~~same shared~~ network.		Some encounter it through regional RF networks or IPIP Mesh links. Others encounter it through services such as IRLP, AREDN, HamNET, or 44Net Connect. Because participation is decentralized, 44Net looks different from place to place, and no single project or approach defines the network.

	~~Because participation is decentralized~~, ~~44Net does not look the same everywhere. For some operators it centers on RF networking. For others it involves~~ routing, ~~infrastructure experimentation, public services~~, ~~or learning how real networks operate. No single project or approach defines~~ the ~~whole~~ network.		The underlying infrastructure exists so many kinds of efforts can coexist. Address space, routing, and coordination provide continuity, while participants shape what the network becomes through the systems they choose to build and maintain.

	~~The underlying infrastructure exists so many kinds of efforts can coexist~~. ~~Address space~~, ~~routing~~, ~~and coordination provide continuity~~, ~~while~~ participants ~~shape what~~ the ~~network~~ becomes ~~through the systems they choose to~~ build ~~and maintain~~.		This mirrors amateur radio itself. Many operators first encounter ham radio through a single activity — voice repeaters, HF contesting, digital modes, emergency communications, or building hardware — yet amateur radio as a whole is defined by the diversity of what participants choose to explore. In the same way, 44Net becomes what its participants build with it over time.

	Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.		Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.

	== ~~Terminology and quick facts~~ ==		== What’s in a name? ==

			People use several names when talking about the network, often reflecting how they first encountered it or which aspect they are thinking about at the moment. In practice, these terms overlap more than they differ.

			Many participants use '''44Net''' when describing the present-day community and the evolving ecosystem of projects built on the address space. The name tends to emphasize participation and ongoing experimentation.

			'''AMPRNet''' is still widely heard, especially when discussing the origins of amateur packet radio networking or the early history of the network. For some operators the term carries historical continuity, while others use it interchangeably with 44Net.

			Operators also refer to '''network 44''' when speaking specifically about the IP address block itself — a habit that dates back to the original Class A allocation. In conversation, the phrase often serves as a neutral shorthand that avoids implying any particular project or technology.

	* '''44Net''' and '''AMPRNet''' are often used interchangeably.		Rather than strict definitions, these names reflect different perspectives on the same long‑running system. What matters in practice is the shared infrastructure and the community of people who continue to build on it.
	* 44Net has no single topology; it is ~~a federation of independently operated systems connected through~~ shared ~~addressing~~ and community ~~coordination.~~
	* Participation spans a wide technical range, from a single reachable node to ~~independently operated routed infrastructure.~~
	* Both RF-linked and Internet-transported approaches are used across the ecosystem.

KI5QKX: mw push

2026-02-25T22:50:42Z

mw push

← Older revision		Revision as of 22:50, 25 February 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:About 44Net}}		{{DISPLAYTITLE:About 44Net}}

	~~44Net is the long-running amateur radio network built around the 44~~.~~0.0.0/8 address space~~, ~~used~~ and ~~maintained by licensed amateurs and supported through shared stewardship~~.		This page provides historical background and context. For onboarding and connection paths, start with [[GetStarted\|Getting Started]], [[Ways to Connect\|Ways to Connect]], and the [[Main Page Draft\|Main Page]].

	This page provides deeper background and context. For onboarding and connection paths, start with [[GetStarted\|Getting Started]], [[Ways to Connect\|Ways to Connect]], and the [[Main Page Draft\|Main Page]].		== What 44Net is and is not ==

	= What 44Net ~~Is (~~and ~~Is Not)~~ =

	44Net is shared technical infrastructure used and maintained by the people who participate in it. Participants operate systems on publicly routable IPv4 space, enabling projects that require direct reachability, stable addressing, and Internet-visible services.		44Net is shared technical infrastructure used and maintained by the people who participate in it. Participants operate systems on publicly routable IPv4 space, enabling projects that require direct reachability, stable addressing, and Internet-visible services.
Line 11:		Line 9:
	44Net is not a consumer ISP product or a managed hosting platform. Participants run and maintain their own systems, coordinate with one another, and contribute to the long-term health of the network.		44Net is not a consumer ISP product or a managed hosting platform. Participants run and maintain their own systems, coordinate with one another, and contribute to the long-term health of the network.

	= History and ~~Origins~~ =		== History and origins ==

	44Net traces back to 1981, when Hank Magnuski requested IP address space from Jon Postel for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.		44Net traces back to 1981, when Hank Magnuski requested IP address space from Jon Postel for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.
Line 23:		Line 21:
	For firsthand historical background, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].		For firsthand historical background, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].

	= Why ~~Public Address Space Changes What You Can Build~~ =		== Why public address space changes what you can build ==

	Using publicly routable space changes what you can learn and build:		Using publicly routable space changes what you can learn and build:
Line 32:		Line 30:
	In short, 44Net makes it possible to conduct experiments under real operational conditions rather than only in isolated lab environments.		In short, 44Net makes it possible to conduct experiments under real operational conditions rather than only in isolated lab environments.

	= Stewardship ~~Model~~ =		== Stewardship model ==

	44Net is sustained by a shared model:		44Net is sustained by a shared model:
Line 47:		Line 45:
	* [[Contributing]]		* [[Contributing]]

	= Participation ~~Norms~~ =		== Participation norms ==

	Over time, several practices have become common across the 44Net community:		Over time, several practices have become common across the 44Net community:
Line 55:		Line 53:
	* unused resources are returned so others can build		* unused resources are returned so others can build

	= Ways ~~People Encounter~~ 44Net =		== Ways people encounter 44Net ==

	People often arrive at 44Net through a specific project, community, or technical path. Those first impressions are real, but they represent only one part of a larger ecosystem.		People often arrive at 44Net through a specific project, community, or technical path. Those first impressions are real, but they represent only one part of a larger ecosystem.
Line 67:		Line 65:
	Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.		Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.

	= Terminology and ~~Quick Facts~~ =		== Terminology and quick facts ==

	* '''44Net''' and '''AMPRNet''' are often used interchangeably.		* '''44Net''' and '''AMPRNet''' are often used interchangeably.

KI5QKX: mw push

2026-02-25T22:42:19Z

mw push

← Older revision		Revision as of 22:42, 25 February 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:About 44Net}}		{{DISPLAYTITLE:About 44Net}}

	~~{{Lead\|~~44Net is the long-running amateur radio network built around the 44.0.0.0/8 address space, used and maintained by licensed amateurs and supported through shared stewardship.}}		44Net is the long-running amateur radio network built around the 44.0.0.0/8 address space, used and maintained by licensed amateurs and supported through shared stewardship.

	This page provides deeper background and context. For onboarding and connection paths, start with [[GetStarted\|Getting Started]], [[Ways to Connect\|Ways to Connect]], and the [[Main Page Draft\|Main Page]].		This page provides deeper background and context. For onboarding and connection paths, start with [[GetStarted\|Getting Started]], [[Ways to Connect\|Ways to Connect]], and the [[Main Page Draft\|Main Page]].

KI5QKX: mw push

2026-02-25T22:41:51Z

mw push

← Older revision		Revision as of 22:41, 25 February 2026
Line 23:		Line 23:
	For firsthand historical background, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].		For firsthand historical background, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].

	= Why Public Address Space ~~Matters~~ =		= Why Public Address Space Changes What You Can Build =

	Using publicly routable space changes what you can learn and build:		Using publicly routable space changes what you can learn and build:
Line 65:		Line 65:
	The underlying infrastructure exists so many kinds of efforts can coexist. Address space, routing, and coordination provide continuity, while participants shape what the network becomes through the systems they choose to build and maintain.		The underlying infrastructure exists so many kinds of efforts can coexist. Address space, routing, and coordination provide continuity, while participants shape what the network becomes through the systems they choose to build and maintain.

	44Net ~~is best understood not~~ as ~~one~~ application or technology~~, but~~ as a long-running environment where independent projects contribute to a shared ~~and~~ evolving network.		Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.

	= Terminology and Quick Facts =		= Terminology and Quick Facts =

	* '''44Net''' and '''AMPRNet''' are often used interchangeably.		* '''44Net''' and '''AMPRNet''' are often used interchangeably.
	* 44Net ~~is not one~~ single topology; it is ~~many~~ independently operated systems connected through shared addressing and community coordination.		* 44Net has no single topology; it is a federation of independently operated systems connected through shared addressing and community coordination.
	* Participation spans a wide technical range, from a single reachable node to independently operated routed infrastructure.		* Participation spans a wide technical range, from a single reachable node to independently operated routed infrastructure.
	* Both RF-linked and Internet-transported approaches are used across the ecosystem.		* Both RF-linked and Internet-transported approaches are used across the ecosystem.

KI5QKX: mw push

2026-02-25T20:30:15Z

mw push

New page

{{DISPLAYTITLE:About 44Net}}

{{Lead|44Net is the long-running amateur radio network built around the 44.0.0.0/8 address space, used and maintained by licensed amateurs and supported through shared stewardship.}}

This page provides deeper background and context. For onboarding and connection paths, start with [[GetStarted|Getting Started]], [[Ways to Connect|Ways to Connect]], and the [[Main Page Draft|Main Page]].

= What 44Net Is (and Is Not) =

44Net is shared technical infrastructure used and maintained by the people who participate in it. Participants operate systems on publicly routable IPv4 space, enabling projects that require direct reachability, stable addressing, and Internet-visible services.

44Net is not a consumer ISP product or a managed hosting platform. Participants run and maintain their own systems, coordinate with one another, and contribute to the long-term health of the network.

= History and Origins =

44Net traces back to 1981, when Hank Magnuski requested IP address space from Jon Postel for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.

Over time, those early packet-radio experiments expanded into a broader ecosystem. As connectivity methods changed, the same address space supported routing experiments, infrastructure projects, and community-built services across many kinds of links.

In 2019, a portion of legacy AMPRNet address space was sold. The proceeds enabled the creation and long-term funding of [https://www.ardc.net ARDC], which supports ongoing 44Net operations as well as broader grants for open communications and digital infrastructure.

The evolution has been additive rather than substitutive. New technologies have layered onto earlier practices, while the core idea — learning by operating real networks — has remained consistent.

For firsthand historical background, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].

= Why Public Address Space Matters =

Using publicly routable space changes what you can learn and build:
* services can be directly reachable without depending only on NAT traversal
* routing, naming, and security practices can be tested in realistic conditions
* projects can grow from one host to routed subnets and multi-site networks

In short, 44Net makes it possible to conduct experiments under real operational conditions rather than only in isolated lab environments.

= Stewardship Model =

44Net is sustained by a shared model:
* [https://www.ardc.net ARDC] provides legal stewardship, fiduciary continuity, and organizational support
* participants operate systems, run services, maintain links, and collaborate on best practices

This balance keeps the network stable enough to build on over time, while remaining open to experimentation and change.

44Net does not operate as a centrally delivered service. It more closely resembles shared infrastructure that participants help maintain and build upon. Address space and core infrastructure persist over time, while individual projects come and go. The network continues because participants treat it as something worth maintaining for those who come after them.

Related pages:
* [[Governance]]
* [[Policies]]
* [[Contributing]]

= Participation Norms =

Over time, several practices have become common across the 44Net community:
* experimentation and learning are encouraged
* non-commercial use and community benefit are expected
* operators are expected to run their systems responsibly
* unused resources are returned so others can build

= Ways People Encounter 44Net =

People often arrive at 44Net through a specific project, community, or technical path. Those first impressions are real, but they represent only one part of a larger ecosystem.

Some encounter 44Net through regional RF networks such as HamWAN or other microwave and mesh efforts. Others first see it through services like IRLP, experimentation platforms, research collaborations, or connection methods such as 44Net Connect. Each reflects a different facet of the same shared network.

Because participation is decentralized, 44Net does not look the same everywhere. For some operators it centers on RF networking. For others it involves routing, infrastructure experimentation, public services, or learning how real networks operate. No single project or approach defines the whole network.

The underlying infrastructure exists so many kinds of efforts can coexist. Address space, routing, and coordination provide continuity, while participants shape what the network becomes through the systems they choose to build and maintain.

44Net is best understood not as one application or technology, but as a long-running environment where independent projects contribute to a shared and evolving network.

= Terminology and Quick Facts =

* '''44Net''' and '''AMPRNet''' are often used interchangeably.
* 44Net is not one single topology; it is many independently operated systems connected through shared addressing and community coordination.
* Participation spans a wide technical range, from a single reachable node to independently operated routed infrastructure.
* Both RF-linked and Internet-transported approaches are used across the ecosystem.

← Older revision		Revision as of 23:48, 25 February 2026
Line 13:		Line 13:
	44Net traces back to 1981, when [https://en.wikipedia.org/wiki/Hank_Magnuski Hank Magnuski] requested IP address space from [https://en.wikipedia.org/wiki/Jon_Postel Jon Postel] for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.		44Net traces back to 1981, when [https://en.wikipedia.org/wiki/Hank_Magnuski Hank Magnuski] requested IP address space from [https://en.wikipedia.org/wiki/Jon_Postel Jon Postel] for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.

	Over time, those early packet-radio experiments expanded into a broader system. ~~As connectivity methods changed~~, ~~the same address space supported routing experiments~~, ~~infrastructure projects~~, and ~~community-built services~~ across ~~many kinds of links~~.		Over time, those early packet-radio experiments expanded into a broader system. Yes, there are still a few 1200bps VHF links out there, but today, people use high-speed microwave, fiber, and satellite to connect systems across neighborhoods, regions, countries, and around the world.

	In 2019, a portion of AMPRNet address space was sold. The proceeds established long-term funding of [https://www.ardc.net ARDC], which supports ongoing 44Net operations as well as broader [https://www.ardc.net/grants grants] for open communications and digital infrastructure.		In 2019, a portion of AMPRNet address space was sold. The proceeds established long-term funding of [https://www.ardc.net ARDC], which supports ongoing 44Net operations as well as broader [https://www.ardc.net/grants grants] for open communications and digital infrastructure.

	The evolution has been ~~additive rather than substitutive~~. New technologies have layered onto earlier practices, while the core idea — learning by operating real networks — has ~~remained steady~~.		The evolution has been cumulative. New technologies have layered onto earlier practices, while the core idea — learning by operating real networks — has endured.

	For more historical background as told by people who were there at the beginning, ~~see~~ [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].		For more historical background as told by people who were there at the beginning, watch [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].

	== Why public addressing is relevant ==		== Why public addressing is relevant ==

	Using publicly routable space changes what you can learn and build:		Using publicly routable space changes what you can learn and build:
	* Services can be directly reachable without depending ~~only~~ on NAT traversal.		* Services can be directly reachable without depending on NAT traversal.
	* Networks can operate independently of any single hosting provider or transit network.		* Networks can operate independently of any single hosting provider or transit network.
	* Routing, naming, and security practices can be tested in realistic conditions.		* Routing, naming, and security practices can be tested in realistic conditions.
	* Projects can grow from a single host to routed subnets and multi-site networks.		* Projects can grow from a single host to routed subnets and multi-site networks.

	In short, 44Net makes it possible to ~~conduct experiments~~ under real operational conditions rather than only in isolated lab environments.		In short, 44Net makes it possible to work under real operational conditions rather than only in isolated lab environments. This is especially important for learning about how the Internet works, and for building projects that need to be visible and reachable by others.

	== Stewardship model ==		== Stewardship model ==

	44Net is sustained by a shared model:		44Net is sustained by a shared model:
	* [https://www.ardc.net ARDC] bears legal, fiduciary, and organizational responsibilities of maintaining the address space.		* [https://www.ardc.net ARDC] bears the legal, fiduciary, and organizational responsibilities of maintaining the address space.
	* Participants operate systems, run services, maintain links, and collaborate on project development.		* Participants operate systems, run services, maintain links, and collaborate on project development.

Line 52:		Line 52:
	* Sharing knowledge and working in the open are valued.		* Sharing knowledge and working in the open are valued.
	* Non-commercial use and community benefit are expected.		* Non-commercial use and community benefit are expected.
	* Operators ~~are expected to run~~ their systems responsibly.		* Operators take responsibility for running their systems responsibly.
	* Unused resources are returned so others can build.		* Unused resources are returned so others can build.

Line 63:		Line 63:
	The underlying infrastructure exists so many kinds of efforts can coexist. Address space, routing, and coordination provide continuity, while participants shape what the network becomes through the systems they choose to build and maintain.		The underlying infrastructure exists so many kinds of efforts can coexist. Address space, routing, and coordination provide continuity, while participants shape what the network becomes through the systems they choose to build and maintain.

	~~This mirrors~~ amateur radio ~~itself~~. Many operators first encounter ham radio through a single activity — voice repeaters, HF contesting, digital modes, emergency communications, or building hardware — yet amateur radio as a whole is defined by the diversity of what participants choose to explore. In the same way, 44Net becomes what its participants build with it over time.		The spirit of 44Net is the spirit of amateur radio. Many operators first encounter ham radio through a single activity — voice repeaters, HF contesting, digital modes, emergency communications, or building hardware — yet amateur radio as a whole is defined by the diversity of what participants choose to explore. In the same way, 44Net can be one thing or many things. It becomes what its participants build with it over time.

	Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.		Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.
Line 69:		Line 69:
	== What’s in a name? ==		== What’s in a name? ==

	People use several names when talking about ~~the network~~, often reflecting how they first encountered it or which aspect they are thinking about at the moment. In practice, these terms overlap more than they differ.		People use several names when talking about it, often reflecting how they first encountered it or which aspect they are thinking about at the moment. In practice, these terms overlap more than they differ.

	Many participants use '''44Net''' when describing the present-day community and the evolving ecosystem of projects built on the address space. The name tends to emphasize participation and ~~ongoing experimentation~~.		Many participants use '''44Net''' when describing the present-day community and the evolving ecosystem of projects built on the address space. The name tends to emphasize participation and collaboration.

	'''AMPRNet''' is still widely heard, especially when discussing the origins of amateur packet radio networking or the early history of the network. For some operators the term carries historical continuity, while others use it interchangeably with 44Net.		'''AMPRNet''' is still widely heard, especially when discussing the origins of amateur packet radio networking or the early history of the network. For some operators the term carries historical continuity, while others use it interchangeably with 44Net still today.

	Operators also refer to '''network 44''' when speaking specifically about the IP address block itself — a habit that dates back to the original Class A allocation. In conversation, the phrase often serves as a neutral shorthand that avoids implying any particular project or technology.		Operators also refer to '''network 44''' when speaking specifically about the IP address block itself — a habit that dates back to the original Class A allocation. In conversation, the phrase often serves as a neutral shorthand that avoids implying any particular project or technology.

	Rather than strict definitions, these names reflect different perspectives on the same long‑running system. What matters in practice is the shared infrastructure and the community of people who continue to build on it.		Rather than strict definitions, these names reflect different perspectives on the same long‑running system. What matters in practice is the shared infrastructure and the community of people who continue to build on it.