Two stupid ip questions;

[Bohn Christopher A Capt AFRL/IFSD]

Good day,

> Any ideas why people decided on a decimal IP address notation 

The IP address we're used to seeing is 256-radix, which probably was
originally represented as hex.  e.g., 00.00.00.00 .. FF.FF.FF.FF -- which,
of course, is representable in exactly 32 bits (hence, 32-bit IP)

So, our 216.33.20.4 maps to D8.21.14.04

Take care,
cb
*-*-*-*-*                                                     *-*-*-*-*
Christopher A. Bohn, Capt, USAF     || christopher.bohn@sn.wpafb.af.mil
Digital Simulation Systems Engineer || cbohn@computer.org
Collaborative Simulation Technology ||
          and Applications Branch   || v (937)255-4429x3576  (DSN785)
Information Directorate             || f (937)255-4511       (DSN785)
Wright Research Site                ||
Air Force Research Laboratory       || http://members.aol.com/EngrBohn/
         http://www.if.afrl.af.mil/div/IFS/IFSD/IFSD_home.html
*-*-*-*-*                                                     *-*-*-*-*


> -----Original Message-----
> From: Eugene Leitl [mailto:eugene.leitl@lrz.uni-muenchen.de]
> Sent: Tuesday, June 01, 1999 1:42 PM
> To: Rob Nelson
> Cc: mdavis@kieser.net; Simon Hogg; beowulf@beowulf.gsfc.nasa.gov
> Subject: Re: Two stupid ip questions;
> 
> 
> Rob Nelson writes:
>  > >> 2)  what's with these ip addresses with no dots?  Is 
> this in an rfc or
>  > >> something? (or is it straight decimal to hex conversion?)  e.g.
>  > >> http://3626046468/ maps to www.angelfire.com (216.33.20.4)
> 
> Any ideas why people decided on a decimal IP address notation 
> http://3626046468/
> http://d8211404/
> instead of a much more natural hexadecimal one?
> 
> And won't it be just horrible typing monstrosities like
> http://1.2.4.8.16.32.64.128.1.2.4.8.16.32.64.128/
> in IPv6? Hexadecimal notation would seem definitely more 
> compact here...
> http://d8211404d8211404d8211404d8211404/
> 
> Still, quite difficult to memorize, unless you're an idiot savant,
> that is.
> 
> -- Eugene 
>