Two stupid ip questions;

[jferg]

This is a multi-part message in MIME format.
--------------05EA8422E05458D3E3479836
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bohn Christopher A Capt AFRL/IFSD wrote:

> 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
> >

The library routines derived from the BSD work will normally accept
IP addresses in any of the long integer string specifications acceptable to
C compilers, e.g., leading "0" for octal, leading "0x" for Hexadecimal, a
straight decimal number, and the "dotted decimal" notation which is most
familiar.  In setting net masks, I frequently use hexadecimal.  While
"0xFFFFFF00" has little to offer over "255.255.255.0", when I want, say, a
10-bit host field, I prefer "0xFFFFFC00" to "255.255.252.0"; it just seems a
bit more intuitive to me.  I make no assertion that this works for
independently derived libraries.

--
Joe Ferguson, ApeX Systems Integration Corp.
Voice:  919.468.8150
FAX:    919.468.5288
email:  jferg@2boot.com



--------------05EA8422E05458D3E3479836
Content-Type: text/x-vcard; charset=us-ascii;
 name="jferg.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for jferg
Content-Disposition: attachment;
 filename="jferg.vcf"

begin:vcard 
n:Ferguson;Joe
x-mozilla-html:FALSE
org:ApeX Systems Integration Corp.
adr:;;;;;;
version:2.1
email;internet:jferg@2boot.com
title:Tech Director
x-mozilla-cpt:;0
fn:Joe Ferguson
end:vcard

--------------05EA8422E05458D3E3479836--