Aux root: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| (41 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
<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:Kastalien|<span | ||
style="background-color: navy; color: silver;"> KASTALIEN </span>]] | style="background-color: navy; color: silver;"> KASTALIEN </span>]] | ||
<span style="font-size: 12px;background-color: gainsboro; "> [[:en:Rectification of names| peer-peer name system ]]</span>¹</h3><br><center><span style="background-color: darkslategray;color: white;">Alt-rooted | <span style="font-size: 12px;background-color: gainsboro; "> [[:en:Rectification of names| peer-peer name system ]]</span>¹</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> | ||
</div> | </div> | ||
<blockquote> | <blockquote> | ||
| Line 21: | Line 21: | ||
<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> | <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> | ||
</html> | </html> | ||
Beginning in 2019, a migration of | 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: | ||
<blockquote> | <blockquote> | ||
adding the following name servers, which are non-recursive, in desired order to your active resolver(s): | adding the following name servers, which are non-recursive, in desired order to your active resolver(s): | ||
* | *ns.<IANA_ZONE> | ||
* . . . | * . . . | ||
*ns<n>.< | *ns<n>.<IANA_ZONE> | ||
where « | where «IANA_ZONE», the '''linking zone''' in the priced name system and, <n> 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 | </blockquote><blockquote style="color: yellow;font-weight: 600;">where the linking zone uses the designated | ||
< | <IANA_ZONE> | ||
<ol><li | <ol><li>Neustar <b>meansofproduction.biz</b> thru 2020-10;**</li> | ||
<li>Donuts <b>sameboat.live</b> thru | <li>Donuts <b>sameboat.live</b> thru 2021-10;</li> | ||
<li> | <li>Neustar <b>ai-integration.biz</b> thru 2025-02 .</li> | ||
</ol>The | </ol> | ||
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. | |||
</blockquote> | </blockquote> | ||
<hr> | |||
* <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> | |||
Paid<span style="color: gold;">²</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 工</a></html> per TLD quarter assuming only stability of fiat basket basis of the 工.</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. | Paid<span style="color: gold;">²</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 工</a></html> per TLD quarter assuming only stability of fiat basket basis of the 工.</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. | ||
| Line 44: | Line 49: | ||
<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>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> | <li>IPV6 and TLS are defaults, 4 and plain text special cases.</li> | ||
<li>Simple name seeking registrars are prohibited. Registrars must offer the name service free bundled with value added services.</li> | |||
<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>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> | ||
</ul> | </ul> | ||
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. | 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. | ||
</blockquote> | </blockquote> | ||
<hr> | <hr> | ||
| Line 56: | Line 62: | ||
<br> | <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> | |||
Revision as of 23:53, 13 September 2020
.dom
Domain Engineering TLD
KASTALIEN peer-peer name system ¹
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:
adding the following name servers, which are non-recursive, in desired order to your active resolver(s):
- ns.<IANA_ZONE>
- . . .
- ns<n>.<IANA_ZONE>
where «IANA_ZONE», the linking zone in the priced name system and, <n> is currently 1, or their ip addresses if your resolver requires it and
where the linking zone uses the designated
<IANA_ZONE>
- Neustar meansofproduction.biz thru 2020-10;**
- Donuts sameboat.live thru 2021-10;
- Neustar ai-integration.biz thru 2025-02 .
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.
Names within the alt system not subject to this change, only the alt-public/wild boundary is affected.
* 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. ** will be routed publicly via Neustar for a while after but not as linking zone.
Paid²[2]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:
- 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.
- 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.
- 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.
An equivalent function is assumed for peer operators, as provided by my DNS/EPP tooling merged with the FRED 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.
³ "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.
"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."
