<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body style="background-color: rgb(255, 255, 255); color: rgb(0, 0,
0); font-family: Tahoma; font-size: 16px;" bgcolor="#FFFFFF"
text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 12/Aug/16 12:32, Andrew Alston
wrote:<br>
<br>
</div>
<blockquote style="border-left: 2px solid #009900 !important;
border-right: 2px solid #009900 !important; padding: 0px 15px 0px
15px; margin: 8px 2px; background-color: white !important; color:
null !important;"
cite="mid:AMSPR03MB5347C063A77313094CA548FEE1F0@AMSPR03MB534.eurprd03.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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"><span style="color:#1F497D"><o:p></o:p></span>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Firstly, we by
default allocate a /48 per customer. We do this because I
strongly subscribe to the belief that if there is a
possibility that someone may want to subnet, they should get
at minimum a /56, and if they are an enterprise, a /48 is
kinda bare minimum. It was therefore simply easier to stick
to a single prefix length size and go /48 all the way.</span></p>
</div>
</blockquote>
<br>
That's reasonable.<br>
<br>
We still do the /56 or /48 thing based on customer type, but
everyone has their style, provided the customer is able to create
multiple subnets within their networking environment, i.e., don't
assign /64's or /128's to customers, in the name of all that is
sweet and holy.<br>
<br>
<br>
<blockquote style="border-left: 2px solid #009900 !important;
border-right: 2px solid #009900 !important; padding: 0px 15px 0px
15px; margin: 8px 2px; background-color: white !important; color:
null !important;"
cite="mid:AMSPR03MB5347C063A77313094CA548FEE1F0@AMSPR03MB534.eurprd03.prod.outlook.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The next issue
was, enabling the SLAAC to the customer (since that only
works on /64s), and to do this, we’re pushing config to the
CPE’s that takes a /64 out of the /48 that’s routed and
automagically puts it on the LAN interface with SLAAC
enabled. This works perfectly with the CPE’s we are using,
and we’re testing it with other CPE’s to have more variety
of choice of CPE as well.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Sadly, the
CPE’s we’ve seen did NOT do this straight out of the box so
we have to push a config on installation when a new customer
connects.</span></p>
</div>
</blockquote>
<br>
The CPE's are not DHCP-PD friendy?<br>
<br>
<br>
<blockquote style="border-left: 2px solid #009900 !important;
border-right: 2px solid #009900 !important; padding: 0px 15px 0px
15px; margin: 8px 2px; background-color: white !important; color:
null !important;"
cite="mid:AMSPR03MB5347C063A77313094CA548FEE1F0@AMSPR03MB534.eurprd03.prod.outlook.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">The next
biggest issue was customers who for some bizarre reason
wanted to run CPE’s behind the CPE’s supplied (effectively
doing dual-NAT on the v4), and if those don’t support v6 or
aren’t configured for it, there isn’t a huge amount we can
do.</span></p>
</div>
</blockquote>
<br>
Yes. You do get some customers who have had their CPE for a long
time, and run the ISP-supplied CPE in Bridge mode. You're right, if
the customer's own CPE does not support IPv6, or is not fully
compliant with your BNG and back-end systems, you can't do much
about that.<br>
<br>
The point is you have provided the support, and if they upgrade
their CPE software, change their CPE or dump it and use the CPE you
have supplied, they will be golden. No one can ask more of you than
that :-).<br>
<br>
For the BNG-to-CPE point-to-point connection, did you go for
DHCPv6-IA_NA or ND/RA?<br>
<br>
<br>
<blockquote style="border-left: 2px solid #009900 !important;
border-right: 2px solid #009900 !important; padding: 0px 15px 0px
15px; margin: 8px 2px; background-color: white !important; color:
null !important;"
cite="mid:AMSPR03MB5347C063A77313094CA548FEE1F0@AMSPR03MB534.eurprd03.prod.outlook.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">With regards to
actual machines picking up the v6 where the above scenario
isn’t happening, zero problems, and we’re actively seeing a
large number of V6 DNS requests to our DNS servers coming
from the customers and we’ve seen a massive increase in our
V6 traffic levels since enabling this – so we know for a
fact customers are actually using the v6 in fairly large
volumes. In particular I see a LOT of v6 to Google,
Facebook, Amazon AWS, and various other sites.</span></p>
</div>
</blockquote>
<br>
This is great.<br>
<br>
Of course, things will always be better if customers are running as
current an OS release as possible, as Happy Eyeballs and IPv6 will
generally be better-supported out of the box in that code.<br>
<br>
<br>
<blockquote style="border-left: 2px solid #009900 !important;
border-right: 2px solid #009900 !important; padding: 0px 15px 0px
15px; margin: 8px 2px; background-color: white !important; color:
null !important;"
cite="mid:AMSPR03MB5347C063A77313094CA548FEE1F0@AMSPR03MB534.eurprd03.prod.outlook.com"
type="cite">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">So far so good
though, but we’re constantly monitoring and hopefully in the
next few weeks once we have collected a lot more statistics
I’ll be able to share those as well.</span></p>
</div>
</blockquote>
<br>
Well done.<br>
<br>
Beer is in order for more war stories in the coming months :-).<br>
<br>
Mark.<br>
</body>
</html>