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/[email protected]/
[address-policy-wg] WHOIS replacement, was RE: Registry - not a policy proposal
- Previous message (by thread): [address-policy-wg] WHOIS replacement, was RE: Registry - not a policy proposal
- Next message (by thread): [address-policy-wg] 2009-01 New Draft Document and Impact Analysis Published (Global Policy for the Allocation of IPv4 blocks to Regional Internet Registries)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Conrad
drc at virtualized.org
Thu Jun 3 19:35:50 CEST 2010
On Jun 2, 2010, at 11:19 PM, Shane Kerr wrote: > This protocol already exists. Actually, multiple whois replacement protocols exist and more are coming, albeit outside of the IETF context (e.g., multiple incompatible (as I understand it) RESTful Whois implementations). > The best place to look is probably the IETF CRISP working group RFCs: Or Whois++ (RFC 1835) or Rwhois (RFC 2167). And we shouldn't forget (like some people can't forget the taste of Tequila after overindulging) X.500 and LDAP. > The effort to implement IRIS was largely unsuccessful, "largely"? > but not because > of missing technology IMHO. It was largely because nobody cares. The > problems it solves are real, but they are not any organization's primary > concerns. Right. No one knows how to make money by standardizing on how to query and display registration data and the amount of money saved by a standardized system has (to date) been insufficient to drive enough interest to fix the myriad issues with the existing whois system. As a result, folks implement whatever they feel will solve their specific problem rather than looking to solve the more generic problem, with the end result being the need for clients to know who they are querying in order to send the appropriate query and parse the resulting output. Sub-optimal, but not surprising. Regards, -drc [Speaking personally and representing no one but myself. Really.]
- Previous message (by thread): [address-policy-wg] WHOIS replacement, was RE: Registry - not a policy proposal
- Next message (by thread): [address-policy-wg] 2009-01 New Draft Document and Impact Analysis Published (Global Policy for the Allocation of IPv4 blocks to Regional Internet Registries)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]