Thread

Re: [HACKERS] cidr

Paul A Vixie <vixie@vix.com> — 1998-07-20T21:45:18Z

> > i didn't realize that anybody else was working on an IP address
> > data type or i'd've posted this six months ago when i first wrote
> > it.  it lacks only the stuff needed to make it usable as a UNIQUE
> > KEY.  it depends on BIND-8's libraries.
> 
> Interesting -- looks nice at first glance, and does some things that
> neither Aleksei nor I had thought of.  I guess a merge of the three
> variations is in order.  At least I'll be doing that locally, and will
> make the result available.

i would be happy if given a chance to consult with whomever wants to do
the work of merging the various ipaddr proposals, and would even do some
work if appropriate.  i would like an indexable "cidr" data type (you
ought not call it an ipaddr, it can be either a net or a host, and the
net is variable sized, so it really is a "cidr") to become part of the
standard postgres system.  but i mostly want to use it in apps, and i
mostly wanted to learn how to extend postgres -- i have no undying love
for the implementation i posted here, nor do i know the process for making
this a standard data type.  so, i will help if someone else is driving.

Re: [HACKERS] cidr

Bruce Momjian <maillist@candle.pha.pa.us> — 1998-07-20T23:36:15Z

> > > i didn't realize that anybody else was working on an IP address
> > > data type or i'd've posted this six months ago when i first wrote
> > > it.  it lacks only the stuff needed to make it usable as a UNIQUE
> > > KEY.  it depends on BIND-8's libraries.
> > 
> > Interesting -- looks nice at first glance, and does some things that
> > neither Aleksei nor I had thought of.  I guess a merge of the three
> > variations is in order.  At least I'll be doing that locally, and will
> > make the result available.
> 
> i would be happy if given a chance to consult with whomever wants to do
> the work of merging the various ipaddr proposals, and would even do some
> work if appropriate.  i would like an indexable "cidr" data type (you
> ought not call it an ipaddr, it can be either a net or a host, and the
> net is variable sized, so it really is a "cidr") to become part of the
> standard postgres system.  but i mostly want to use it in apps, and i
> mostly wanted to learn how to extend postgres -- i have no undying love
> for the implementation i posted here, nor do i know the process for making
> this a standard data type.  so, i will help if someone else is driving.

Sounds like a plan.  Paul is a DNS expert, and we have people involved
who know PostgreSQL well.

As far as the name, we just want a name that makes it clear to novices
what the module does.  ip_and_mac is pretty clear.  I have no idea what
a cidr is.  If you can think of a more descriptive name, let's go for
it.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

Re: [HACKERS] cidr

Matthew N. Dodd <winter@jurai.net> — 1998-07-21T03:58:32Z

On Mon, 20 Jul 1998, Bruce Momjian wrote:
> As far as the name, we just want a name that makes it clear to novices
> what the module does.  ip_and_mac is pretty clear.  I have no idea what
> a cidr is.  If you can think of a more descriptive name, let's go for
> it.

I think most people who would use the IP related types do know what a CIDR
is.

An IP address should be just that, a discrete IP, no netmask, nothing.

A CIDR is a type able to represent a range of IP addresses (what one of
the previous patches did by storing an address and a netmask.)

MAC addresses speak for themselves.

I'll let others describe all the nifty functions that the first two types
will/can have (IP - IP, IP - CIDR, CIDR - CIDR).

/* 
   Matthew N. Dodd		| A memory retaining a love you had for life	
   winter@jurai.net		| As cruel as it seems nothing ever seems to
   http://www.jurai.net/~winter | go right - FLA M 3.1:53	
*/