This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
FYI: new 2.00 whois server runs now on port 4444
- Previous message (by thread): FYI: new 2.00 whois server runs now on port 4444
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David.Kessens at ripe.net
David.Kessens at ripe.net
Fri Jun 28 16:14:47 CEST 1996
Hi Bill, > Bill Manning writes : > > > > I thought we already have one: port 43 for whois services. > > > > We will put the production code on port 43 as soon as the code looks stable > > for a while. > > > > Please correct me if I missed your point. > > > > David K. > > > > I am sorry that I was not clear. I beleive that, even with a superset > of the whois protocol, this is no longer whois as defined and should > therefor apply for a new well-known port. > > Local conversations with several others here at IETF do not support > this view, so I expect that it (the view) will remain a minority > opinion. Its something I thought worth mentioning in passing... :) Thanks for your explanation. As Curtis points out: I don't see a need for a new port number as long as we stay backward compatible. However, one might want to put a special 'for computer usage' server behind another port, to make a clear separation of functionality possible. But it's still not really needed since Gerald Winters claims that the RAWhois server is fully backwards compatible with the old scheme. Kind regards, David K.
- Previous message (by thread): FYI: new 2.00 whois server runs now on port 4444
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]