Re: inet increment w/ int8

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Douglas McNaught <doug(at)mcnaught(dot)org>, Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: inet increment w/ int8
Date: 2005-05-23 16:08:21
Message-ID: 20050523160820.GD30011@ns.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Bruce Momjian (pgman(at)candle(dot)pha(dot)pa(dot)us) wrote:
> Douglas McNaught wrote:
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >
> > > I modified the TODO. I think we only need an INT4. I realize INT8
> > > would be for IPV6 but I can't imagine a network that has more than INT4
> > > hosts (not part of the network address).
> >
> > Actually "increment the host address" isn't a well-defined concept for
> > IPV6. The "host" part of the address (if you're on an Ethernet) is
> > generally the 64 bit MAC address.
>
> So if the network card dies the machine has a new IPv6 address and you
> just update your DNS? Do you update your routing tables?

Generally routing isn't done to the last 48 bits (dunno where 64 bit
came from, but MAC's are 48 last I checked :).

DNS to that level would need to be changed though, yes.. :/

(I'm not exactly a big fan of this development, in fact, I think it's a
bunch of poo, but then, I don't write the standards).

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stef 2005-05-23 16:16:03 Obtaining Firing Statement clause in (pl/perlu) Trigger Function
Previous Message Bruce Momjian 2005-05-23 15:55:01 Re: inet increment w/ int8