Aux root: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 93: Line 93:
</ul>
</ul>
Each domain space is controlled by an instance of the <span class=plainlinks>[https://fred.ai-integration.biz <span style="color: cyan;">FRED</span>]</span> NIC software adapted  
Each domain space is controlled by an instance of the <span class=plainlinks>[https://fred.ai-integration.biz <span style="color: cyan;">FRED</span>]</span> NIC software adapted  
for my Domain Control Program ([https://devops1.sameboat.network/About%20DCP DCP]).
for my Domain Control Program (<span class=plainlinks>[https://devops1.sameboat.network/About%20DCP <span style="color: cyan;">DCP</span>]</span>).
</blockquote>
</blockquote>
<hr>
<hr>

Revision as of 15:23, 6 January 2024

What is DNS?

above is important

Domain space (DS) is just the regular public internet with an added top level domain .dom and its support which operators use for greater control of their name spaces, as a peerage of autonomous operators routing names upon their discretion. The default in core domain space is all ICANN/IANA TLDs plus one but other operators may choose something else. Since the public roots are generally not affected, we use the term "Aux(lliary) root" instead of Alt-root.

User name services are provided thru the .dom content mgt system (DCMS).
KASTALIEN is also the marque for the single authentication realm (SAR).
.

.dom

Domain Engineering TLD

  KASTALIEN      peer-peer name system ¹


  Aux-rooted: private name spaces supplement the public one. [1]

This page has a music track, mouseover for title.


The following I formerly publicly routed but have been private or unused since their public epoch.

EpochVendor
<NAME><ZONE>

'kybernet''com'before 2000Verisign
'commoditysoftware''org'before 2014Verisign
'thoughtcrime''biz'before 2023Neustar

Add 1 or more of these name servers ( or their addresses ) to use our aux root:

  • ns.<LINKING_ZONE>
  • . . .
  • ns<n-1>.<LINKING_ZONE>


where

<LINKING_ZONE> ::= <DS_ZONE>.<IANA_ZONE>

  A linking zone is a bridge from the public name system, n in <n-1> is currently 2 and

the zone rotations are

<LINKING_ZONE>EpochVendor
<DS_ZONE><IANA_ZONE>

'ai-integration''biz'2005-03 — 2025-02Neustar

These may or may not have the name service.

'meansofproduction''biz'2006-11 — 2024-10Neustar
'meansofproduction'TBA2024-07-14TBA
'mecha.dom' split from aii.bizN/A2023-01-01DS
'sameboat''live'2017-11 — 2022-11Donuts
'sameboat''network'2022-05 — 2027 Donuts
'sameboat''live'2022-08 —DS
  • Suffixes dropped in the wild are generally still routed in domain space.*

* An example is thoughtcrime.biz, tcb.biz will route publicly thru March 2023 and then only via DS.

The rotating linking zone is a distinguishing feature of my alt root concept which otherwise is ordinary DNS/EPP. Although the facilities provided by overlaying services may obscure this fact it's essential to interoperability of private domain spaces with the public internet.

A compromise between stability and flexibility/independence from the priced system is struck by rotation of a IANA TLD and a period of dual routing of the old and new during the rotation. Canonical mappings from public (IANA) name space into a private domain space are to simply drop the IANA TLD, replace it by .dom or one designated for use in private spaces (which can be the same to replace the whole TLD).

Names only routed in a domain space lack an IANA suffix (or equvalently use .dom) and are not affected by linking zone rotation.

Operators manage impact if any in their domain spaces across linking zone rotations, including determining their own epoch duration policies, above are for core domain space.

Entitled users have access from recursion and additional basic name services for users below developer class up to continuous live maintenance by intelligent agency for operators.

As used here, the background operation of the public priced name systems are assumed as needed, excluded where desirable, e.g. for privacy or security. Our system is constructed using the standard unix networking software and forms a superspace of the public name system with these properties:

  • Operators of domain spaces determine which TLDs they recognize. Core space allocates its TLDs FCFS to AKPERSONs, other operators may override in their domain spaces. Operators use a single reserved name: ".dom" for their private/peer namespace.
  • IPV6 and TLS are defaults, 4 and plain text special cases.
  • Simple name seeking registrars are prohibited. Registrars must offer the name service free bundled with value added services.

Each domain space is controlled by an instance of the FRED NIC software adapted for my Domain Control Program (DCP).



"A superior man, in regard to what he does not know, shows a cautious reserve. If names be not correct, language is not in accordance with the truth of things. If language be not in accordance with the truth of things, affairs cannot be carried on to success. When affairs cannot be carried on to success, proprieties and music do not flourish. When proprieties and music do not flourish, punishments will not be properly awarded. When punishments are not properly awarded, the people do not know how to move hand or foot. Therefore a superior man considers it necessary that the names he uses may be spoken appropriately, and also that what he speaks may be carried out appropriately. What the superior man requires is just that in his words there may be nothing incorrect."