…nes an extension to the multicast portion of the IPv6 addressing architecture [ RFC4291 ]. The current architecture does not contain any built-in support for dynamic address allocation. The extension allows for use of IIDs to allocate multicast addresses. When a link-local unicas…

…d interface identifier as specified in "IP Version 6 Addressing Architecture" [ RFC4291 ]. The modified EUI-64 interface identifier is used in stateless address autoconfiguration. As in other links that support IPv6, EUI-64-based interface identifiers are not mandatory and other …

…reservation of a /20 IPv6 address prefix from the Global Unicast Address pool [ RFC4291 ] for documentation purposes allows such conflicts to be avoided. ¶ The key words " MUST ", " MUST NOT ", " REQUIRED ", " SHALL ", " SHALL NOT ", " SHOULD ", " SHOULD NOT ", " RECOMMENDED ", "…

…It is binary encoded. Note: A sender MUST NOT use an IPv4-mapped IPv6 address [ RFC4291 ], but should instead use an IPv4 Address parameter for an IPv4 address. Combined with the Source Port Number in the SCTP common header, the value passed in an IPv4 or IPv6 Address parameter i…

…nes an extension to the multicast portion of the IPv6 addressing architecture [ RFC4291 ]. The current architecture does not contain any built-in support for dynamic address allocation. The extension allows for use of IIDs to allocate multicast addresses. When a link-local unicas…

…nes an extension to the multicast portion of the IPv6 addressing architecture [ RFC4291 ]. The current architecture does not contain any built-in support for dynamic address allocation. The extension allows for use of IIDs to allocate multicast addresses. When a link-local unicas…

…4 prefixes MUST NOT appear as IPv4-mapped IPv6 addresses ( Section 2.5.5.2 of [ RFC4291 ). There MUST be only one instance of ROAIPAddressFamily per unique AFI in the ROA. Thus, the ROAIPAddressFamily structure MUST NOT appear more than twice. The addresses field contains IP pref…

… ]. If an IPv6 address is used, a valid textual representation as described in [RFC4291], Section 2.2 , MUST be used. Syslog applications SHOULD consistently use the same value in the HOSTNAME field for as long as possible. The NILVALUE SHOULD only be used when the syslog applica…

…reservation of a /20 IPv6 address prefix from the Global Unicast Address pool [ RFC4291 ] for documentation purposes allows such conflicts to be avoided. ¶

…. Similarly, endpoints could regard a change in address to a link-local address RFC4291 or an address in a private-use range RFC1918 from a global, unique-local RFC4193 , or non-private address as a potential attempt at request forgery. Endpoints could refuse to use these address…

…d by two colons ("::"). Notes: "semicolon" should be "colon" Added reference to RFC4291. Verifier: Forward reference to RFC4291 is inappropriate. RFC 3781 , "Next Generation Structure of Management Information (SMIng) Mappings to the Simple Network Management Protocol (SNMP)", Ma…

…d by two colons ("::"). Notes: "semicolon" should be "colon" Added reference to RFC4291. Verifier: Forward reference to RFC4291 is inappropriate. RFC 3781 , "Next Generation Structure of Management Information (SMIng) Mappings to the Simple Network Management Protocol (SNMP)", Ma…