DS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
<div align="justify" style="background-color: black; position: relative; left: 30px; width: 90%;"> | <div align="justify" style="background-color: black; position: relative; left: 30px; width: 90%;"> | ||
<blockquote>In core Domain Space, service paths are routed from the wild with an ICANN suffix and guidance for normal (end) users across the DS boundary.<br>Paid service is explictly or implicitly limited to such paths by the particular service. | <blockquote>In core Domain Space, service paths are routed from the wild with an ICANN suffix and guidance for normal (end) users across the DS boundary.<br>Paid service is explictly or implicitly limited to such paths by the particular service. | ||
<blockquote> Once the DS boundary is crossed, an attempt is to made differentiate paid support paths from developing production .</blockquote> | <blockquote> Once the DS boundary is crossed, an attempt is to made differentiate paid support paths from developing production by requiring .dom routing for the latter.</blockquote> | ||
DevOps users can just add my nameservers to thier resolution in lieu of the guidance above. The below is <i><span style="font-family: 'Beth Ellen', cursive, sans-serif;">DevOps</span></i> oriented but is relevant to all classes including ip-anonymous. | DevOps users can just add my nameservers to thier resolution in lieu of the guidance above. The below is <i><span style="font-family: 'Beth Ellen', cursive, sans-serif;">DevOps</span></i> oriented but is relevant to all classes including ip-anonymous. | ||
</blockquote> | </blockquote> | ||
