…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…
…pported 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 …
… 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…
…: Optional. The true IP address of the client machine, in dotted quad format or rfc3513 defined hexed IPv6 address. Notes: In general this parameter is not necessary as the address of the client can be determined from the IP address from which the HTTP request came. The parameter…
…: Optional. The true IP address of the client machine, in dotted quad format or rfc3513 defined hexed IPv6 address. Notes: In general this parameter is not necessary as the address of the client can be determined from the IP address from which the HTTP request came. The parameter…
…: Mark Doll Date Reported: 2005-08-29 Section 2 says: F800::/6 Reserved by IETF RFC3513 FA00::/7 Reserved by IETF RFC3513 FC00::/7 Reserved by IETF RFC3513 It should say: F800::/6 Reserved by IETF RFC3513 FC00::/7 Reserved by IETF RFC3513 Notes: Section 2 states "There are no ove…
…: Mark Doll Date Reported: 2005-08-29 Section 2 says: F800::/6 Reserved by IETF RFC3513 FA00::/7 Reserved by IETF RFC3513 FC00::/7 Reserved by IETF RFC3513 It should say: F800::/6 Reserved by IETF RFC3513 FC00::/7 Reserved by IETF RFC3513 Notes: Section 2 states "There are no ove…
← Previous
Page 2