RE: [lir-wg] rfc-ignorant.org
What about RFC954 dating from 1985... <snip> WHO SHOULD BE IN THE DATABASE DCA requests that each individual with a directory on an ARPANET or MILNET host, who is capable of passing traffic across the DoD Internet, be registered in the NIC WHOIS Database. MILNET TAC users must be registered in the database. To register, send via electronic mail to REGISTRAR@SRI-NIC.ARPA your full name, middle initial, U.S. mailing address (including mail stop and full explanation of abbreviations and acronyms), ZIP code, telephone (including Autovon and FTS, if available), and one network mailbox. Contact the DDN Network Information Center, REGISTRAR@SRI-NIC.ARPA or (800) 235-3155, for assistance with registration. </snip> Shouldn't it be made obsolete ?
What about RFC954 dating from 1985...
<snip> WHO SHOULD BE IN THE DATABASE
DCA requests that each individual with a directory on an ARPANET or MILNET host, who is capable of passing traffic across the DoD Internet, be registered in the NIC WHOIS Database. MILNET TAC users must be registered in the database. To register, send via electronic mail to REGISTRAR@SRI-NIC.ARPA your full name, middle initial, U.S. mailing address (including mail stop and full explanation of abbreviations and acronyms), ZIP code, telephone (including Autovon and FTS, if available), and one network mailbox. Contact the DDN Network Information Center, REGISTRAR@SRI-NIC.ARPA or (800) 235-3155, for assistance with registration. </snip>
Shouldn't it be made obsolete?
Well, formally, the document's status is as follows: 0954 NICNAME/WHOIS. K. Harrenstien, M.K. Stahl, E.J. Feinler. Oct-01-1985. (Format: TXT=7397 bytes) (Obsoletes RFC0812) (Status: DRAFT STANDARD) In other words, it defines the simple WHOIS protocol. However, as is not uncommon for RFC documents produced in those days, the document mixes operational requirements and procedures with actual protocol specification, thus the above quoted paragraph. I'm however not aware of any attempt at re-specifying the WHOIS protocol itself, so that the above document can be moved to historic status; if you want to play along those lines, "feel free". However, I'm not sure a re-specification of the WHOIS protocol is going to quiet the rfc-ignorant.org folks' on this point. The question appears to be: "must there be registered at least one e-mail address per assigned address block", be that in either ARIN, RIPE or APNICs whois databases. Regards, - Håvard
On Thu, 18 Jul 2002, Havard Eidnes wrote in reply to Pieterjan d'Hertog:
What about RFC954 dating from 1985...
<snip> WHO SHOULD BE IN THE DATABASE
DCA requests that each individual with a directory on an ARPANET or MILNET host, who is capable of passing traffic across the DoD </snip>
Shouldn't it be made obsolete?
I'm however not aware of any attempt at re-specifying the WHOIS protocol itself, so that the above document can be moved to historic status; if you want to play along those lines, "feel free".
Actually, there is: ftp://ftp.isi.edu/in-notes/search.ietf.org/internet-drafts/draft-campbell-whois-00.txt I've attempted to define the WHOIS (actually 'nicname') protocol to be independent of any expectations of output formats or what is in the database, and keep it to a simple question/answer protocol with a few basic niceties (such as 'help'). Another draft was put forward on the ietf-whois list some time ago which explicitly shifted 954 to Historic, although I cannot find this as an internet draft at the present time.
However, I'm not sure a re-specification of the WHOIS protocol is going to quiet the rfc-ignorant.org folks' on this point.
On this matter, it will, however they will find other aspects to complain about.
The question appears to be: "must there be registered at least one e-mail address per assigned address block", be that in either ARIN, RIPE or APNICs whois databases.
In the original mail to lir-wg, the range in question meets this criteria (the tech-c has an email address, the adminc-c does not), hence rfci's listing is incorrect by their own cited policy ;) -- Bruce Campbell RIPE Systems/Network Engineer NCC www.ripe.net - PGP562C8B1B Operations/Security
On Thu, 18 Jul 2002, Havard Eidnes wrote:
What about RFC954 dating from 1985...
<snip> WHO SHOULD BE IN THE DATABASE
DCA requests that each individual with a directory on an ARPANET or MILNET host, who is capable of passing traffic across the DoD Internet, be registered in the NIC WHOIS Database. MILNET TAC users must be registered in the database. To register, send via electronic mail to REGISTRAR@SRI-NIC.ARPA your full name, middle initial, U.S. mailing address (including mail stop and full explanation of abbreviations and acronyms), ZIP code, telephone (including Autovon and FTS, if available), and one network mailbox. Contact the DDN Network Information Center, REGISTRAR@SRI-NIC.ARPA or (800) 235-3155, for assistance with registration. </snip>
Shouldn't it be made obsolete?
Well, formally, the document's status is as follows:
0954 NICNAME/WHOIS. K. Harrenstien, M.K. Stahl, E.J. Feinler. Oct-01-1985. (Format: TXT=7397 bytes) (Obsoletes RFC0812) (Status: DRAFT STANDARD)
In other words, it defines the simple WHOIS protocol. However, as is not uncommon for RFC documents produced in those days, the document mixes operational requirements and procedures with actual protocol specification, thus the above quoted paragraph.
I'm however not aware of any attempt at re-specifying the WHOIS protocol itself, so that the above document can be moved to historic status; if you want to play along those lines, "feel free".
However, I'm not sure a re-specification of the WHOIS protocol is going to quiet the rfc-ignorant.org folks' on this point.
The question appears to be: "must there be registered at least one e-mail address per assigned address block", be that in either ARIN, RIPE or APNICs whois databases.
FYI, For the person object in APNIC database. e-mail: [mandatory] [multiple] [look-up key] Even with making email mandatory we still having problem with email address being out of date due to people forget to update the database with changes. Son
Regards,
- Håvard * Mailing List: hostmaster-staff * * Handled by majordomo@staff.apnic.net *
FYI, For the person object in APNIC database.
e-mail: [mandatory] [multiple] [look-up key]
Even with making email mandatory we still having problem with email address being out of date due to people forget to update the database with changes.
Oh, yes, I have no illusions about whether this will actually be a universal solution to any problem other than as a means to get the rfc-ignorant.org folks off our collective backs. People unwilling to provide a usable e-mail address will just fill in a non-usable (/dev/null'ed?) e-mail address. Regards, - Håvard
participants (4)
-
Bruce Campbell -
Havard Eidnes -
John Tran -
Pieterjan d'Hertog