[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

IPv6 Loopback/Point-to-Point address allocation

Subject: IPv6 Loopback/Point-to-Point address allocation
From: shopik+lists at nvcube.net (Nikolay Shopik)
Date: Mon, 11 Sep 2017 10:35:15 +0300
In-reply-to: <CAAeewD81+ouLZYmNLc2pkFToJ_x1GT5NB94kFTyi4HQUz0J-EA@mail.gmail.com>
References: <[email protected]> <CAPkb-7Cc+VmfONHH8ZCMATOHsSzSmRv9_D+wOQ7-XbwOy45g7A@mail.gmail.com> <[email protected]> <CAAeewD81+ouLZYmNLc2pkFToJ_x1GT5NB94kFTyi4HQUz0J-EA@mail.gmail.com>

On 10/09/2017 14:25, Saku Ytti wrote:
> However I don't think market would generally appreciate the
> implications linklocal brings to traceroute, where least bad option
> would be just to originate hop-limit exceeded from loop0, with no
> visibility on actual interface.

rfc5837 would help but it seems market universally ignore it for some 
reason unknown to me (lack of interest and IPv6 adoption?)

We find LL is simpler, operation wise at some cases.

Follow-Ups:
- IPv6 Loopback/Point-to-Point address allocation
  - From: owen at delong.com (Owen DeLong)

References:
- IPv6 Loopback/Point-to-Point address allocation
  - From: kvicknair at reservetele.com (Kody Vicknair)
- IPv6 Loopback/Point-to-Point address allocation
  - From: baldur.norddahl at gmail.com (Baldur Norddahl)
- IPv6 Loopback/Point-to-Point address allocation
  - From: bellman at nsc.liu.se (Thomas Bellman)
- IPv6 Loopback/Point-to-Point address allocation
  - From: saku at ytti.fi (Saku Ytti)

Prev by Date: 2017 NANOG Elections General Information
Next by Date: 2017 NANOG Elections General Information
Previous by thread: IPv6 Loopback/Point-to-Point address allocation
Next by thread: IPv6 Loopback/Point-to-Point address allocation
Index(es):
- Date
- Thread