<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thank you, both!</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
...that kinda sucks, though.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I don't see any rationale in RFC 5308 for why the HELLO packet may only contain the LLA - does anyone know/remember why? (I'm hoping that understanding the rationale will make this an easier pill to swallow.) Obviously this behaviour/requirement is net-new
to the IPv6 TLVs, as there's no LLA-cognate in IPv4 (APIPA doesn't count). There is in OSI, I think, but I'm still too sane to read those docs.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
It makes sense that you would not want LLAs in LSPs, only GUAs, but does that imply that you
<b>must</b> use either ULAs or GUAs in order to establish IPv6 routes in IS-IS, in an IPv6 environment? That makes about as much sense to me as forcing LLAs for next-hops.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
-Adam</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<div>
<p class="MsoNormal" style="margin-top: 0px; margin-bottom: 0px;"><b><span style="font-size:10.0pt; color:#44546A">Adam Thompson</span></b><span style="font-size:9.0pt; color:#44546A"><br>
Consultant, Infrastructure Services<br>
<img class="EmojiInsert" alt="1593169877849" style="" data-outlook-trace="F:1|T:1" src="cid:08137327-c747-4c98-8b91-e05a17c86091"><br>
100 - 135 Innovation Drive<br>
Winnipeg, MB, R3T 6A8<br>
(204) 977-6824 or 1-800-430-6404 (MB only)<br>
<a href="mailto:athompson@merlin.mb.ca"><span style="color:#44546A">athompson@merlin.mb.ca</span></a><br>
<a href="http://www.merlin.mb.ca/"><span style="color:#44546A">www.merlin.mb.ca</span></a></span></p>
</div>
<br>
</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> NANOG <nanog-bounces+athompson=merlin.mb.ca@nanog.org> on behalf of Saku Ytti <saku@ytti.fi><br>
<b>Sent:</b> May 4, 2021 01:44<br>
<b>To:</b> Mark Tinka <mark@tinka.africa><br>
<b>Cc:</b> nanog list <nanog@nanog.org><br>
<b>Subject:</b> Re: IS-IS and IPv6 LLA next-hop - just Arista, or everyone?</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Tue, 4 May 2021 at 07:24, Mark Tinka <mark@tinka.africa> wrote:<br>
<br>
> Junos:<br>
>> 2c0f:feb0::1/128 *[IS-IS/18] 02:43:49, metric 5870<br>
> to fe80::1205:caff:fe86:4ac3 via et-4/0/2.0<br>
> to fe80::5287:89ff:fef3:25c3 via et-4/0/2.0<br>
> to fe80::1205:caff:fe86:4b10 via et-5/0/2.0<br>
> > to fe80::5287:89ff:fef3:2610 via et-5/0/2.0<br>
><br>
> IOS XE:<br>
> I2 2C0F:FEB0::1/128 [115/6410]<br>
> via FE80::1205:CAFF:FE86:4AC3, TenGigabitEthernet1/0/0<br>
> via FE80::1205:CAFF:FE86:4B10, TenGigabitEthernet0/0/0<br>
> via FE80::5287:89FF:FEF3:25C3, TenGigabitEthernet1/0/0<br>
> via FE80::5287:89FF:FEF3:2610, TenGigabitEthernet0/0/0<br>
><br>
> IOS XR:<br>
> i L2 2c0f:feb0::1/128<br>
> [115/5870] via fe80::1205:caff:fe86:4b10, 02:45:22, HundredGigE0/3/0/0 (!)<br>
> [115/5810] via fe80::f60f:1bff:feb0:75c4, 02:45:22, HundredGigE0/2/0/1<br>
><br>
<br>
SROS:<br>
2001:218:0:1000::1/128 Remote ISIS 48d22h13m 18<br>
fe80::42de:adff:fe98:87e4-"lag1" 25301<br>
<br>
----<br>
<a href="https://tools.ietf.org/html/rfc5308">https://tools.ietf.org/html/rfc5308</a><br>
<br>
For Hello PDUs, the "Interface Address" TLV MUST<br>
contain only the link-local IPv6 addresses assigned to the interface<br>
that is sending the Hello. For LSPs, the "Interface Address" TLVs<br>
MUST contain only the non-link-local IPv6 addresses assigned to the<br>
IS.<br>
----<br>
<br>
These are hello derived:<br>
A:ytti@a04.chcgil09.us.bb# show router isis adjacency<br>
r22.chcgil09.us.bb-re0 detail |match Neigh<br>
IPv6 Neighbor : fe80::42de:adff:fe98:87e4<br>
IPv4 Neighbor : 129.250.3.205<br>
<br>
Vendors do not have the option to use GUA while being RFC5308 compliant.<br>
<br>
<br>
-- <br>
++ytti<br>
</div>
</span></font></div>
</body>
</html>