DS: Difference between revisions

Line 3:

<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> ~~Off these paths most stuff will route with~~ the ~~.dom suffix in core~~ DS, ~~whatever one it uses in the wild~~.</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.

<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>

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>

Navigation menu

Page actions

Page actions

Personal tools

About

Search

forewords

novel

Tools

@@ Line 3: / Line 3: @@
 <table style="background-color: black;"><tr><td width=80% valign=top>
 <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> Off these paths most stuff will route with the .dom suffix in core DS, whatever one it uses in the wild.</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.
+<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>
+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>
 <div style="position: relative;top: 2px;">