…encodings. A host identified by an Internet Protocol literal address, version 6 RFC3513 ] or later, is distinguished by enclosing the IP literal within square brackets ("[" and "]"). This is the only place where square bracket characters are allowed in the URI syntax. In anticipa…

…encodings. A host identified by an Internet Protocol literal address, version 6 RFC3513 ] or later, is distinguished by enclosing the IP literal within square brackets ("[" and "]"). This is the only place where square bracket characters are allowed in the URI syntax. In anticipa…

…ncodings. A host identified by an Internet Protocol literal address, version 6 [RFC3513] or later, is distinguished by enclosing the IP literal within square brackets ("[" and "]"). This is the only place where square bracket characters are allowed in the URI syntax. In anticipat…

…encodings. A host identified by an Internet Protocol literal address, version 6 RFC3513 ] or later, is distinguished by enclosing the IP literal within square brackets ("[" and "]"). This is the only place where square bracket characters are allowed in the URI syntax. In anticipa…

…OTOCOL" [RFC791], "Internet Protocol Version 6 (IPv6) Addressing Architecture" [RFC3513], "INTERNET REGISTRY IP ALLOCATION GUIDELINES" [RFC2050], and related regional Internet registry address management policy documents. Some relevant terms include: allocate - the transfer of cu…

…+----------------------------+ The special behavior of this prefix defined in [ RFC3513 ] must no longer be supported in new implementations (i.e., new implementations must treat this prefix as Global Unicast). Existing implementations and deployments may continue to use this pre…

…COL" [ RFC791 ], "Internet Protocol Version 6 (IPv6) Addressing Architecture" [ RFC3513 ], "INTERNET REGISTRY IP ALLOCATION GUIDELINES" [ RFC2050 ], and related regional Internet registry address management policy documents. Some relevant terms include: allocate - the transfer of…

…+----------------------------+ The special behavior of this prefix defined in [ RFC3513 ] must no longer be supported in new implementations (i.e., new implementations must treat this prefix as Global Unicast). Existing implementations and deployments may continue to use this pre…

…e has become problematic with the introduction of IP Version 6 (IPv6) addresses RFC3513 ]. This document defines multiple textual conventions (TCs) as a means to express generic Internet network layer addresses within MIB module specifications. The solution is compatible with SMI…

…-+----------------------------+ The special behavior of this prefix defined in [RFC3513] must no longer be supported in new implementations (i.e., new implementations must treat this prefix as Global Unicast). Existing implementations and deployments may continue to use this pref…

…+----------------------------+ The special behavior of this prefix defined in [ RFC3513 ] must no longer be supported in new implementations (i.e., new implementations must treat this prefix as Global Unicast). Existing implementations and deployments may continue to use this pre…

…A has marked the IPv6 address prefix 0000 001, reserved for NSAP Allocation in [RFC3513], simply as Reserved. IANA is holding the registry for "OSI NSAPA Internet Code Point" implied by Section 6 of [RFC1888] in abeyance until a replacement for that Section is approved for public…

… has marked the IPv6 address prefix 0000 001, reserved for NSAP Allocation in [ RFC3513 ], simply as Reserved. IANA is holding the registry for "OSI NSAPA Internet Code Point" implied by Section 6 of [RFC1888] in abeyance until a replacement for that Section is approved for publi…

… supported by the SSH implementation on loopback addresses only ([RFC3330] and [RFC3513]). o "127.0.0.1" and "::1" indicate listening on the loopback interfaces for IPv4 and IPv6, respectively. Note that the client can still filter connections based on information passed in the o…

…Dv2 Reports can be sent with the source address set to the unspecified address [RFC3513], if a valid link-local IPv6 source address has not been acquired yet for the sending interface. (See section 5.2.13. for details.) There are two MLD message types of concern to the MLDv2 prot…