<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 11/28/21 16:20, Jean St-Laurent via
NANOG wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:000a01d7e463$1b6cf660$5246e320$@ddostest.me">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">I
like to put some servers behind that scheme.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">2601::443:xxxx
for https servers<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">2601::25:xxxx
for MTA servers.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">2601::993:xxxx
for IMAP<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">It
gives a quick note of what is that ip even though it’s ipv6
and usually non-human readable. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Not
sure what kind of scheme is use by medium/big ISP. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Do
you go by zip code of the area covered or some kind of
logical to help people know what is behind that ipv6
network?</span></p>
</div>
</blockquote>
<br>
We really aren't clever with IPv6 address design and assignment. The
most we do is assign:<br>
<br>
- 1x /48 to Loopbacks for all routers.<br>
- /48's per PoP for infrastructure links.<br>
- /48's per city for /56 assignments to customers.<br>
- /48's per city for assignments to customers. <br>
<br>
We don't try to co-ordinate them in a "meaningful" way that would
offer visual identification. We feel that is just too much work, and
that getting IPv4/IPv6 parity for day-to-day operations is a
challenge in and of itself, without trying to be fancy.<br>
<br>
Mark.<br>
</body>
</html>