Talk:Parse an IP Address: Difference between revisions

Content added Content deleted
m (→‎other IP address formats: specified the formats and which RFC it is described in. -- ~~~~)
(→‎other IP address formats: clarified the ISATAP IP address format. -- ~~~~)
Line 50: Line 50:
I noticed that at least two (or more) other formats for IP address aren't represented in the examples (used for input):
I noticed that at least two (or more) other formats for IP address aren't represented in the examples (used for input):


* "slash" or CIDR or netmask format: <tt> 11.22.33.44/25 </tt>
* "slash" or CIDR or netmask format: <tt> w.x.y.z/25 </tt> for instance.
* IPv4-compatible address: <tt> 0:0:0:0:0:0:w.x.y.z </tt> or <tt> ::w.x.y.z </tt>
* IPv4-compatible address: <tt> 0:0:0:0:0:0:w.x.y.z </tt> or <tt> ::w.x.y.z </tt>
* IPv4-mapped address: <tt> 0:0:0:0:0:FFFF:w.x.t.z >/tt> or >tt> ::FFFF:w,x,y,z </tt>
* IPv4-mapped address: <tt> 0:0:0:0:0:FFFF:w.x.t.z </tt> or <tt> ::FFFF:w,x,y,z </tt>
* 6to4 address: combining the global prefix 2002::/16 with the 32 bits of a public IPv4 address of the node, described in RFC 3056.
* 6to4 address: <tt> 2002::/16 </tt> described in RFC 3056.
* ISATAP address (Intra-Site Automatic Tunnel Addressing Protocol): <tt> FR80::/64 </tt> described in RFC 4214.
* ISATAP address (Intra-Site Automatic Tunnel Addressing Protocol): <tt> :::5EFE:w.x.y.z </tt> and also <tt> FE80::/64 </tt> described in RFC 4214.
* Teredo address (formed by combining the 2001::/32 Teredo prefix with the public IPv4 address of a Teredo server and other elements. Teredo is an IPv6 transition technology described in RFC 4380.
* Teredo address: <tt> 2001::/32 </tt> described in RFC 4380.
-- [[User:Gerard Schildberger|Gerard Schildberger]] 14:06, 23 April 2012 (UTC)
[All of this is way over my comprehension level.] -- [[User:Gerard Schildberger|Gerard Schildberger]] 14:06, 23 April 2012 (UTC)
Retrieved from "https://rosettacode.org/wiki/Talk:Parse_an_IP_Address"