IANA registration

Pete Forman <pete.forman@westerngeco.com> writes:

PostgreSQL typically uses port 5432 for client-server communications.
It would be a good idea to register this with IANA. This will help to
avoid a clash with other services that might try to use the port.
Might someone with a reasonable grasp of the low level messages in
PostgreSQL care to submit a registration?

http://www.iana.org/
http://www.iana.org/cgi-bin/usr-port-number.pl
http://www.isi.edu/in-notes/iana/assignments/port-numbers

This seems like a good idea. They seem to want a particular person's
name as contact, so I suppose one of the core group should do it.
Has anyone already initiated the process; if not, shall I?

regards, tom lane

Pete Forman <pete.forman@westerngeco.com> writes:

PostgreSQL typically uses port 5432 for client-server communications.
It would be a good idea to register this with IANA. This will help to
avoid a clash with other services that might try to use the port.
Might someone with a reasonable grasp of the low level messages in
PostgreSQL care to submit a registration?

http://www.iana.org/
http://www.iana.org/cgi-bin/usr-port-number.pl
http://www.isi.edu/in-notes/iana/assignments/port-numbers

This seems like a good idea. They seem to want a particular person's
name as contact, so I suppose one of the core group should do it.
Has anyone already initiated the process; if not, shall I?

This seemed like a Marc job to me. Marc?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

PostgreSQL typically uses port 5432 for client-server communications.
It would be a good idea to register this with IANA. This will help to
avoid a clash with other services that might try to use the port.
Might someone with a reasonable grasp of the low level messages in
PostgreSQL care to submit a registration?

http://www.iana.org/
http://www.iana.org/cgi-bin/usr-port-number.pl
http://www.isi.edu/in-notes/iana/assignments/port-numbers

This seems like a good idea. They seem to want a particular person's
name as contact, so I suppose one of the core group should do it.
Has anyone already initiated the process; if not, shall I?

This seemed like a Marc job to me. Marc?

They ask for some (high level) details on the protocol features/packet
format. If Tom (or someone; could be me but I've been swamped) could
help out with a few sentences, we'll get this done a bit faster ;)

Presumably for port 5432 it is just the connection handshake stuff...

- Thomas

On Tue, 27 Mar 2001, Bruce Momjian wrote:

Pete Forman <pete.forman@westerngeco.com> writes:

PostgreSQL typically uses port 5432 for client-server communications.
It would be a good idea to register this with IANA. This will help to
avoid a clash with other services that might try to use the port.
Might someone with a reasonable grasp of the low level messages in
PostgreSQL care to submit a registration?

http://www.iana.org/
http://www.iana.org/cgi-bin/usr-port-number.pl
http://www.isi.edu/in-notes/iana/assignments/port-numbers

This seems like a good idea. They seem to want a particular person's
name as contact, so I suppose one of the core group should do it.
Has anyone already initiated the process; if not, shall I?

This seemed like a Marc job to me. Marc?

Will do ... *nod*

The Hermit Hacker <scrappy@hub.org> writes:

This seemed like a Marc job to me. Marc?

Will do ... *nod*

Ok, fine here. BTW, I was thinking that rather than filling in their
webform in any detail, it'd make the most sense to just supply a link
to our protocol documentation, presently

http://www.postgresql.org/users-lounge/docs/7.0/postgres/protocol.htm
or
http://www.postgresql.org/devel-corner/docs/postgres/protocol.html

Even though the latter is nominally unstable docs, the URL doesn't
have built-in obsolescence in it ;-)

Maybe we should arrange for a more stable path to the "current release"
docs, ie a symlink without a version number?

regards, tom lane

On Tue, 27 Mar 2001, Tom Lane wrote:

Ok, fine here. BTW, I was thinking that rather than filling in their
webform in any detail, it'd make the most sense to just supply a link
to our protocol documentation, presently

http://www.postgresql.org/users-lounge/docs/7.0/postgres/protocol.htm
or
http://www.postgresql.org/devel-corner/docs/postgres/protocol.html

Even though the latter is nominally unstable docs, the URL doesn't
have built-in obsolescence in it ;-)

If it's in the devel-corner it does!

Maybe we should arrange for a more stable path to the "current release"
docs, ie a symlink without a version number?

But there is...

http://www.postgresql.org/docs/special/protocol.html

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================

Vince Vielhaber <vev@michvhf.com> writes:

Maybe we should arrange for a more stable path to the "current release"
docs, ie a symlink without a version number?

But there is...

http://www.postgresql.org/docs/special/protocol.html

No, that's just the first page of that chapter. If the 'next' link
worked ...

regards, tom lane

On Tue, 27 Mar 2001, Tom Lane wrote:

Vince Vielhaber <vev@michvhf.com> writes:

Maybe we should arrange for a more stable path to the "current release"
docs, ie a symlink without a version number?

But there is...

http://www.postgresql.org/docs/special/protocol.html

No, that's just the first page of that chapter. If the 'next' link
worked ...

It's what you provided:

http://www.postgresql.org/users-lounge/docs/7.0/postgres/protocol.htm

But it's been changed.

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================

Did we get anywhere with this?

PostgreSQL typically uses port 5432 for client-server communications.
It would be a good idea to register this with IANA. This will help to
avoid a clash with other services that might try to use the port.
DB2, Interbase, MS SQL, MySQL, Oracle, Sybase, etc. are already
registered.

Might someone with a reasonable grasp of the low level messages in
PostgreSQL care to submit a registration?

http://www.iana.org/
http://www.iana.org/cgi-bin/usr-port-number.pl
http://www.isi.edu/in-notes/iana/assignments/port-numbers

--
Pete Forman -./\.- Disclaimer: This post is originated
WesternGeco -./\.- by myself and does not represent
pete.forman@westerngeco.com -./\.- opinion of Schlumberger, Baker
http://www.crosswinds.net/~petef -./\.- Hughes or their divisions.

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Bruce Momjian writes:

Did we get anywhere with this?

Marc said on 2001-03-27 that he was going to make the submission.

The port assignments listing published by IANA was last updated on
2001-05-03 and does not yet have an entry for 5432.
--
Pete Forman -./\.- Disclaimer: This post is originated
WesternGeco -./\.- by myself and does not represent
pete.forman@westerngeco.com -./\.- opinion of Schlumberger, Baker
http://www.crosswinds.net/~petef -./\.- Hughes or their divisions.