Jump to content

Talk:Parse an IP Address: Difference between revisions

added two sections. -- ~~~~
(→‎Port 0: Fair enough)
(added two sections. -- ~~~~)
Line 41:
:::: We are indeed talking about IP addresses, but the task also asks us to deal with ports, and IP does not have ports without something like TCP or UDP. --[[User:Rdm|Rdm]] 14:10, 29 September 2011 (UTC)
::::: Fair enough. (And I wouldn't want to remove the port-awareness requirement, because of its impact on parsing.) --[[User:Short Circuit|Michael Mol]] 14:12, 29 September 2011 (UTC)
 
==format description of IP addresses==
 
I think it would be a good idea to provide a link (or links) describing the various (legal) formats of an IP address. -- [[User:Gerard Schildberger|Gerard Schildberger]] 14:06, 23 April 2012 (UTC)
 
==other IP address formats==
 
I noticed that at least two (or three) 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>
* IPv4-compatible address, IPv4-mapped address, 6to4 address, ISATAP address which is/are a mixture of IPv4 and IPv6: <tt> 11:22:33:44:55.66.77.88 </tt>
* 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.
-- [[User:Gerard Schildberger|Gerard Schildberger]] 14:06, 23 April 2012 (UTC)
Cookies help us deliver our services. By using our services, you agree to our use of cookies.