JACS Internet Addresses Rules

https://JACS.tech


https://medium.com/@jacstech/jacs-internet-addresses-rules-f51472ec834b


The blockchain is the core component of JACS that defines the rules governing the allocation of JACS addresses.
These rules are as follows:

Abundance
Unlike all other address allocation mechanisms, JACS cares less about the conservation of its NSAP addresses or its depletion over time.
There will be no refusal or justification needed by any requesting entity; there are enough addresses for every single grain of sand on earth and even beyond and for all future needs.
That said, there will be no precautions taken by JACS to prevent or limit stockpiling, that is the accumulation of resources beyond the actual legitimate need of a requesting entity.


Uniqueness
JACS guarantees that the allocated blocks are unique as the allocation is purely done over blockchain.
Every time a requesting entity requests an address block via a proper transaction, the allocated block is tied to that entity and is stored permanently over the blockchain, so that it can never be assigned to another requesting entity. Moreover, the AA field of the JACS address block will be derived from the blockchain public address of the requesting node (Ethereum blockchain at the start of the operation then JACS native blockchain)


Aggregation
One of the critical factors of all address allocation mechanisms, is the need to preserve the size of Internet global routing table.
Thus, addresses aggregation is crucial for the viability of the Internet routing system.
In the case of IPv4 or IPv6 addresses, the different RIRs ‘Regional Internet Registries’ allocation policies promote aggregation through the preferred use of PA ‘Provider Assigned’ addresses, but they still allow PI ‘Provider Independent’ allocations.
These PI allocations are the main reason behind the explosion of the size of the global routing table as these PI entries cannot be efficiently aggregated most of the time.
In JACS, there is no central authority providing the addresses, like: IANA, RIRs, LIRs, Service Providers, ANSI or any Government, it is the public blockchain that assigns address blocks for all requesting entities, so there is no concept of PA or PI addresses as there is no ‘Provider’ in reality.
When a requesting entity requests a new block over blockchain (maybe for any operation expansion or future use); JACS will recognize the entity and can then grant the entity further blocks that are contiguous with its original holdings, thus allowing the efficient aggregation to happen on the Internet core routers.
It’s worth mentioning that part of the future development of JACS will explore how to leverage JACS native public blockchain to, possibly, replace the existing routing protocols that run over the Internet routers.


Anonymity
In JACS, blockchain identities are anonymous. Moreover, payments are done using JACS tokens.
This implies that JACS has no knowledge (hence no control) about the entity that receives the allocation. Requesting entities can still — voluntarily — attach their contact information or policies for each allocation as part of the metadata, however it’s not mandatory.


Fairness
Fairness in the context that the policies should be equally applied to all entities irrespectively of their location, nationality, size, or any other factor.
JACS naturally and inherently achieves this goal.
The role of the judge is taken by the blockchain consensus. The participating nodes verify the transactions and ensure that everything happens the way it should be.