Aux root: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
← Older edit
No edit summary
No edit summary
 
(396 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__NOTOC__
<html><script language="javascript" type="text/javascript">
<html><script language="javascript" type="text/javascript">
<!--
<!--
Line 7: Line 8:
}
}
</script></html>
</script></html>
<div style="background-color: grey; color: white;">
 
<div style="position: relative;left: 40px;text-align: left;width: 500px;">
<div style="background-color: grey; color: white;"><div style="position: relative;top:10px;left:700px;width:800px;>
<span style="position: relative;left: 5px;> [[File:KASTALIEN.svg|left|thumb|125px|[http://sameboat.dom Go There]]]</span>
<blockquote><center>[[DNS|<h1 style="color:lime;">What is DNS?</h1>]]<h5>above is important</h5></center></blockquote>
Domain space (DS) is just the regular public internet with an added top level domain <b>.dom</b> 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.<br><br>
User name services are provided thru the <span class=plainlinks>[https://eg.meansofproduction.biz/eg/index.php/C-Liu <span style="color: pink;">.dom content mgt system</span>] (DCMS).<br>
KASTALIEN is the marque for a single authentication realm (SAR) in core domain space.
</span>.
</div>
<div style="position: relative;top: -180px;left: 40px;text-align: left;width: 650px;"><html><img width=175 src=https://meansofproduction.biz/images/yggdrisl.jpg><br><span style="position: relative;left: 5px;"><a style="color: white;" onclick="return checkRouting();" href=http://sameboat.dom>Go There</a></span></html>
<div style="position:relative;top:-200px;left:200px;width:400px;">
<h1 style="text-align: center;font-weight: 900;">.dom</h1>
<h1 style="text-align: center;font-weight: 900;">.dom</h1>
<h5 style="text-align: center;">Domain Engineering TLD</h5>
<h5 style="text-align: center;">Domain Engineering TLD</h5>
<h3 style="text-align: center;position: relative;top: 5px;left: 10px;">[[:de:Kastalien|<span  
<h3 style="text-align: center;position: relative;top: 5px;left: 10px;">[[:de:Das_Glasperlenspiel#Das_eigentliche_„Glasperlenspiel“_und_seine_Welt|<span  
     style="background-color: navy; color: silver;"> &nbsp; KASTALIEN &nbsp; </span>]] &nbsp;  
     style="background-color: navy; color: silver;"> &nbsp; KASTALIEN &nbsp; </span>]] &nbsp;  
     <span style="font-size: 12px;background-color: gainsboro; "> [[:en:Rectification of names| &nbsp;peer-peer name system ]]</span>&sup1;</h3><br><center><span style="background-color: darkslategray;color: white;">Alt-rooted: a name system distinct from just the priced IANA system alone is in use.<ref> see [[:en:Alt root|<span style="color: pink;">Alt root</span>]]</ref></span></center>
     <span class=plainlinks style="font-size: 12px;background-color: gainsboro; "> [https://fred.ai-integration.biz &nbsp;peer-peer name system ]</span>&sup1;</h3><br><center><span style="background-color: darkslategray;color: white;"> &nbsp; Aux-rooted: private name spaces supplement the public one. <ref> see [[:en:Alt root|<span style="color: pink;">:en:Alt root</span>]]</ref></span></center>
</div>
<html><div style="position:relative;left:-40px;top:20px;float:right;" >
<audio style="height:14px;" title=" Compared to What? Les McCann and Eddie Harris 1969. " controls source src="https://meansofproduction.biz/pub/ComparedToWhat.mp3" type="audio/mpeg"> This page has an audio but your browser does not support the audio element.</audio>
<div style="font-size:8px;color:cyan;"><center>This page has a music track, mouseover for title.</center></div></div></html><br><br>
</div></div>
 
<blockquote>
<blockquote>
<html>
<blockquote style="position:relative;left:675px;top:-280px;">
<img style="position: relative; top: 115px;right: 95px;" align=right width=160 src=https://meansofproduction.biz/images/DNSnBINDimV6.png><br>
These have been private or unused since their public epoch.
<a title="Pending general treatment of distributed ledger" href=https://namecoin.org><img style="position: relative; top: 245px; left: 55px;" align=right width=50px align=right src=https://meansofproduction.biz/images/namecoin.png></a><a title="Actually using regular DNSSEC" href=https://dnscrypt.info><img style="position: relative; top: 165px; left: 15px;" align=right width=50px align=right src=https://meansofproduction.biz/images/dnscrypt.cd47d19.png></a>
<table style="position:relative:top:-30px;background-color: navy; color: antiquwhite;" width=700>
</html>
<tr><th colspan=2><span style="position: relative;left: 30px;></span></th><th width=200>Epoch</th><th width=100>Vendor</th></tr>
Beginning in 2019, a migration of content from random distribution over my longstanding 3 ICANN domains*, is in progress, with the goal of almost all content being alt-routed, either same named, ICANN suffix to .dom, or the ICANN/IANA TLD just dropped. As used here. '''alt root''' refers to an autonomous peerage that routes TLDs upon discretion of the operators. A reasonable effort for a free service level is committed that just works by:
<tr><th>&lt;NAME&gt;</th><th>&lt;ZONE&gt;</th><th colspan=2></th></tr>
<blockquote>
<tr><td colspan=4><hr></td></tr>
adding the following name servers, which are non-recursive, in desired order to your active resolver(s):
<tr><td align=center>'kybernet'</td><td  align=center>'com'</td><td  align=center>before 2000</td><td  align=center>Verisign</td></tr>
 
<tr><td align=center>'commoditysoftware'</td><td  align=center>'org'</td><td  align=center>before 2014</td><td  align=center>Verisign</td></tr>
*ns.&lt;IANA_ZONE&gt;
<tr><td align=center>'thoughtcrime'</td><td  align=center>'biz'</td><td  align=center>before 2023</td><td  align=center>Neustar</td></tr>
<tr><td align=center>'greentravel'</td><td  align=center>'app'</td><td  align=center>before 4/2025</td><td  align=center>Dont Care</td></tr>
</table>
<hr width=700>
</blockquote>
<blockquote style="position:relative;top:-460px;font-size:16px;">
<b>tl;dr &mdash; Add an ns&lt;{&empty;,2,...}&gt;.meansofproduction.biz to ur name resolution.</b>
</blockquote>
<blockquote style="position:relative;left:20px;top:-435px;font-size:10px;">
Add 1 or more of these name servers ( or their addresses ) to use our aux root:
*ns.&lt;LINKING_ZONE&gt;
* . . .
* . . .
*ns&lt;n&gt;.&lt;IANA_ZONE&gt;
*ns&lt;n-1&gt;.&lt;LINKING_ZONE&gt;
 
where <p>&lt;LINKING_ZONE&gt; ::= &lt;DS_ZONE&gt;.&lt;IANA_ZONE&gt;<br> &nbsp; A '''linking zone''' is a bridge from the public name system, '''n''' in &lt;n-1&gt; is currently 2  and </p>
where &laquo;IANA_ZONE&raquo;, the '''linking zone''' in the priced name system and, &lt;n&gt; is currently 1, or their ip addresses if your resolver requires it and  
</blockquote><blockquote style="color: yellow;font-weight: 600;">where the linking zone uses the designated
&lt;IANA_ZONE&gt;
<ol><li>Donuts <b>sameboat.live</b> thru 2021-10;</li>
    <li>Neustar <b>ai-integration.biz</b> thru 2025-02 .</li>
    <li>TBA after 4723</li>
</ol>
</blockquote>
</blockquote>
The changing linking zone is key to my version of the alt root concept. Stability is supplied by continued support of the name while
it appears in the list above and ofc the underlying content.<br> Names within the alt system not subject to this change, only the alt-public/wild boundary is affected.


A simple map from the state approved name systems such as IANA into this alt-root is to simply drop the suffix or replace it with one(s) the name owner uses here.
<table style="position:relative;top:-430px;" width=100%><tr><td>
<blockquote style="color: yellow;font-weight: 60;">the zone rotations are
<table style="background-color: black; color: white;" width=700>
<tr><th colspan=2><span style="position: relative;left: 30px;> &lt;LINKING_ZONE&gt;</span></th><th width=200>Epoch</th><th width=100>Vendor</th></tr>
<tr><th>&lt;DS_ZONE&gt;</th><th>&lt;IANA_ZONE&gt;</th><th colspan=2></th></tr>
<tr><td colspan=4><hr></td></tr>
<tr><td align=center>'sameboat'</td><td  align=center>'network'</td><td  align=center>2022-05 &mdash; 2027 </td><td  align=center>Donuts</td></tr>
<tr><td align=center>'ai-integration'</td><td  align=center>'biz'</td><td  align=center>2005-03 &mdash; 2025-02</td><td  align=center>Neustar</td></tr>
<tr><td colspan=4><hr></td></tr>
<tr><td colspan=4 align=center>As of 25 Jan 2025 all IANA names via Square Space<br>Unclear/uninterested about their registry status, upstream authority if any.</td></tr>
<tr><td colspan=4><hr></td></tr>
<tr><td align=center>'meansofproduction'</td><td  align=center>'biz'</td><td  align=center>2006-11 &mdash; 2024-10</td><td  align=center>Neustar</td></tr>
<tr><td align=center>'meansofproduction'</td><td  align=center>nil (root)</td><td  align=center>2025-01-25</td><td  align=center>core DS</td></tr>
<tr><td align=center>aii.biz goes mostly private</td><td  align=center>N/A</td><td  align=center>2025-01-01</td><td  align=center>DS</td></tr>
<tr><td align=center>'sameboat'</td><td  align=center>'live'</td><td  align=center>2017-11 &mdash; 2022-11</td><td  align=center>Donuts</td></tr>
<tr><td align=center>&lt;apex&gt;<sup>*</sup></td><td  align=center>'live'</td><td  align=center>2022-08 &mdash;</td><td  align=center>DS</td></tr>
<tr><td align=center>renjuan</td><td  align=center>'org'</td><td  align=center>2025-05 &mdash;</td><td  align=center>Dont Care</td></tr>
</table>
<ul><li><sup>*</sup>Suffixes dropped in the wild are generally still routed in domain space.</li></ul>
&#42; <span style="font-size: 10px;color: lime;font-weight: 900;background-color: darkslategray; ">An example is thoughtcrime.biz, tcb.biz will route publicly thru March 2023 and then only via DS.</span>
</blockquote>
</blockquote>
<blockquote><hr></blockquote>
</td><td width=50% align=left>
<blockquote style="position:relative;top:-20px;left:-30px;">
The rotating linking zone  prevents any lock-in in the interface to the priced name system.
<blockquote>
<blockquote>
&#42; <span style="font-size: 10px;color: lime;font-weight: 900;background-color: darkslategray; ">An example is thoughtcrime.biz, thoughtcrime.dom is already the reference domain but tcb.biz will route publicly for a while and then only via my root for the .biz suffix.</span> ** <span style="font-size: 10px;color: lime;font-weight: 900;background-color: darkslategray; ">will be routed publicly via Neustar for a while after but not as linking zone.</span>
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 for core DS or other Operators designated suffix (which can be nil to replace a whole TLD).
Paid<span style="color: gold;">&sup2;</span><ref>Price for the full SaaS without any physical resources other than control and delivery bandwidth kept under  <html><a style="color: pink" title="Current fx" href=https://meansofproduction.biz/imu.php onclick="return popitup('https://meansofproduction.biz/imuq.php?qg=10')">10 &#24037;</a></html> per TLD quarter assuming only stability of fiat basket basis of the &#24037;.</ref>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.
</blockquote>
Names only routed in a domain space lack an IANA suffix (or equvalently use .dom) and are not affected by linking zone rotation.
<br><br>
Operators manage impact if any in their domain spaces across linking zone rotations, including determining their own epoch duration policies, those listed here are for core domain space.
</blockquote>
</td></tr></table>
<blockquote style="position:relative;top:-400px;">
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:
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:<br><br>
<ul>
<ul>
<li>Individual operators of the system determine which TLDs they recognize. The system administered here only allocates the TLDs FCFS to operators, it doesn't have the intent of acting  as a sole authoritative source even for the .dom name, which operators may override to establish cooperating alt roots. The TLD operators in essence agree to a common real TLD space which they may present internally differently, but which starts with the common public systems plus a single reserved name: ".dom" for their private/peer namespace.</li>
<li>IPV6 and TLS are defaults, 4 and plain text special cases.</li><br>
<li>IPV6 and TLS are defaults, 4 and plain text special cases.</li>
<li>Operators of domain spaces determine which TLDs they recognize. Core domain space allocates its TLDs FCFS to AKPERSONs, other operators may have different policies.  
<li>Simple name seeking registrars are prohibited. Registrars must offer the name service free bundled with value added services.</li>
For simple interop Operators use a single reserved name: ".dom" for their private/peer namespace.</li><br>
<li>A rich default common systems application environment which operators may optionally use is provided in which all users are identified and at least in principle, traceable.</li>
<li>Simple name rent seeking registrars are obviated in core DS as DCP there runs a unified registry/registrar but downstream Operators may instantiate multiple registrars, a single registrar isnt a system limitation but we dont support the billing components of FRED only the multiple registrars.</li>
</ul>
</ul><br>
An equivalent function is assumed for peer operators, as provided by my <span class=plainlinks>[https://dnseppus.meansofproduction.biz/doc/about <span style="color: cyan;"> DNS/EPP tooling</span>]</span> merged with the <span class=plainlinks>[https://fred.ai-integration.biz <span style="color: cyan;">FRED</span>]</span> Czech NIC software as maintained by me for my Ubuntu LTS targets. End users of the "sameboat/C-六" core PHP-Python CMS have significant consumer level DNS functionality upon sufficient entitlement.
Each domain space is served by an instance of the <span class=plainlinks>[https://fred.ai-integration.biz <span style="color: cyan;">FRED</span>]</span> NIC software adapted
for control by <span class=plainlinks>[https://devops1.sameboat.network/About%20DCP <span style="color: cyan;">DCP</span>]</span>.
</blockquote>
</blockquote>
<div style="position:relative;top:-300px;width: 85%;"><span  style="font-size: 10px; font-weight: 600;">"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." </span><div align=right><html><a style="color: lime;" href=https://ctext.org/analects/zi-lu#n1408>Analects, Book XIII, No. 3</a></html></div>
<html><img style="position:relative;left:235px;" width=150 align=right src=https://juan.ai-integration.biz/xasppage/xasppage.pl?XASPPAGE_STYLE=0&P=AUXROOT></html>
<hr>
<hr>
<references/>
<references/>
<blockquote>
<blockquote>
&sup3; <font size=1>"clean" means a newly formatted host OS instance; Our modifications of various elements such as letsencrypt included in the SaaS, woven through various process such as SSO, registration, etc.</font>
<html><a title="The Alt-Root I maintain (no warn DS link)" href=https://sameboat.dom><img align=right src=https://meansofproduction.biz/images/kastalien.png></a></html>
<html><a title="The Alt-Root I maintain" href=https://sameboat.live><img align=right src=https://meansofproduction.biz/images/kastalien.png></a></html>
</blockquote>
</blockquote>
<br>
</div>
</div>
<div style="width: 85%;><span  style="font-size: 10px; font-weight: 600;">"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." </span><div align=right><html><a style="color: lime;" href=https://ctext.org/analects/zi-lu#n1408>Analects, Book XIII, No. 3</a></html></div>
Retrieved from "https://eg.meansofproduction.biz/eg/index.php/Aux_root"