<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Helvetica, Arial, sans-serif">We run a couple hundred
routers in our network, all dual-stacked.<br>
<br>
Primarily, we use IS-IS as our IGP, supporting both IPv4 and IPv6
address families.<br>
<br>
However, due to poor IS-IS support in Quagga, we run OSPFv2 and
OSPFv3 between servers that offer Anycast-based services (DNS,
NTP, TACACS+, e.t.c.) and our service routers that route for them.
We then redistribute (restrictively) from OSPFv2 and OSPFv3 into
IS-IS to get those routes into the backbone.<br>
<br>
Quagga had a few issues back in March with an update that broke
OSPFv3. There was an interim hack in March, and a full fix in
April for that issue. So one wants to be on quagga-0.99.24.1_1 or
later.<br>
<br>
All works well.<br>
<br>
IPv4 traffic is MPLS-switched, while IPv6 traffic is carried
natively in the core. We've started deploying router code that
supports LDPv6, but that's another story.<br>
<br>
Mark.<br>
</font><br>
<div class="moz-cite-prefix">On 4/Jun/15 17:02, Philip Matthews
wrote:<br>
</div>
<blockquote cite="mid:CFF78ECA-724B-47E8-9CBD-A46CF8C1BE6E@magma.ca"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Folks:
<div>
<div><br>
</div>
<div><span class="Apple-style-span" style="font-family: Calibri;
font-size: 15px; ">We are the co-authors of an
Internet-Draft of some design choices people need to make
when designing IPv6 and dual-stack networks (<a
moz-do-not-send="true"
href="https://tools.ietf.org/html/draft-ietf-v6ops-design-choices"><a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-v6ops-design-choices">https://tools.ietf.org/html/draft-ietf-v6ops-design-choices</a></a>). </span></div>
<div><span class="Apple-style-span" style="font-family: Calibri;
font-size: 15px; "><br>
</span></div>
<div><span class="Apple-style-span" style="font-family: Calibri;
font-size: 15px; ">We are looking for information on the IGP
combinations people are running in their dual-stack
networks. We are gathering this information so we can
document in our draft which IGP choices are known to work
well (i.e., people actually run this combination in
production networks without issues). The draft will not name
names, but just discuss things in aggregate: for example,
"there are 3 large and 2 small production networks that run
OSPF for IPv4 and IS-IS for IPv6, thus that combination is
judged to work well".</span><span class="Apple-style-span"
style="border-collapse: separate; font-family: Helvetica;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-align: -webkit-auto; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;
-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto; -webkit-text-stroke-width:
0px; font-size: medium; ">
<div><font size="2" face="Calibri"><span style="font-size:
11pt; ">
<div> </div>
<div>If you have a production dual-stack network, then
we would like to know which IGP you use to route
IPv4 and which you use to route IPv6. We would also
like to know roughly how many routers are running
this combination. Feel free to share any successes
or concerns with the combination as well. </div>
<div> </div>
<div>We are looking particularly at combinations of
the following IGPs: IS-IS, OSPFv2, OSPFv3, EIGRP.</div>
<div>If you run something else (RIP?) then we would
also like to hear about this, though we will likely
document these differently. [We suspect you run
RIP/RIPng only at the edge for special situations,
but feel free to correct us].</div>
<div><br>
</div>
<div>And if you have one of those modern networks that
carries dual-stack customer traffic in a L3VPN or
similar and thus don’t need a dual-stacked core,
then please email us and brag ...</div>
<div><br>
</div>
<div>Philip Matthews</div>
<div>Victor Kuarsingh</div>
<div><br>
</div>
</span></font></div>
</span></div>
</div>
</blockquote>
<br>
</body>
</html>