Reading 'RFC3513: Internet Protocol Version 6 (IPv6) Addressing Architecture' I see:
2.5.4 Global Unicast Addresses
All global unicast addresses other than those that start with binary 000 have a 64-bit interface ID field (i.e., n + m = 64), formatted as described in section 2.5.1. Global unicast addresses that start with binary 000 have no such constraint on the size or structure of the interface ID field.
Any mask > 64 bits would encroach into the "interface ID" field of the address. Does anyone know if this bit-boundary is significant? Will this bit-boundary be [is it now] 'enforced' somehow?
From the same RFC:
The space allocated for Global Unicast has a binary prefix of 001.
The RFC seems to imply that all IPv6 global unicast addresses have an interface ID field of 64 bits and therefore have a netmask of 64bits, or less, although this is not specifically stated.
For example, should a point-to-point link have a /64 instead of an IPv4-analogous /126?
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...