Uhhhh.... it's nice to be able to change routing information in a timely fashion without needing intensive therapy afterward. The idea isn't inherently bad, but I'd not want the current ARIN acting as a route registry.
How would you feel about ARIN being the root of a registry hierarchy that works similar to the DNS? In that case, ARIN would not necessarily hold the route information, they would just be at the top of the search hierarchy just like the root name servers are at the top of the DNS hierarchy. ARIN would authoritatively identify the leaseholder of an address block and give you a pointer to that leaseholder's LDAP server where you could query for whatever info they have available. This could include route registry info. --Michael Dillon
## On 2003-03-04 09:26 -0000 Michael.Dillon@radianz.com typed:
Uhhhh.... it's nice to be able to change routing information in a timely fashion without needing intensive therapy afterward. The idea isn't inherently bad, but I'd not want the current ARIN acting as a route registry.
How would you feel about ARIN being the root of a registry hierarchy that works similar to the DNS?
I hope you meant IANA as the root of the registry ? ARIN is (just ;-) a RIR just like RIPE or APNIC
In that case, ARIN would not necessarily hold the route information, they would just be at the top of the search hierarchy just like the root name servers are at the top of the DNS hierarchy. ARIN would authoritatively identify the leaseholder of an address block and give you a pointer to that leaseholder's LDAP server where you could query for whatever info they have available. This could include route registry info.
--Michael Dillon
-- Rafi
Uhhhh.... it's nice to be able to change routing information in a timely fashion without needing intensive therapy afterward. The idea isn't inherently bad, but I'd not want the current ARIN acting as a route registry.
How would you feel about ARIN being the root of a registry hierarchy that works similar to the DNS? In that case, ARIN would not necessarily hold the route information, they would just be at the top of the search hierarchy just like the root name servers are at the top of the DNS hierarchy. ARIN would authoritatively identify the leaseholder of an address block and give you a pointer to that leaseholder's LDAP server where you could query for whatever info they have available. This could include route registry info. --Michael Dillon
I don't know that the other RIRs would be willing to promote ARIN to the position once held by the IANA as the arbitor of all IP address space. That said, why replicate the DNS? --bill
On dinsdag, maa 4, 2003, at 10:26 Europe/Amsterdam, Michael.Dillon@radianz.com wrote:
How would you feel about ARIN being the root of a registry hierarchy that works similar to the DNS? In that case, ARIN would not necessarily hold the route information, they would just be at the top of the search hierarchy just like the root name servers are at the top of the DNS hierarchy. ARIN would authoritatively identify the leaseholder of an address block and give you a pointer to that leaseholder's LDAP server where you could query for whatever info they have available.
So how are you going to reach the leaseholder's LDAP server if you're in the middle of checking their prefix to see if it's worthy of being included in your routing table?
participants (4)
-
bmanning＠karoshi.com -
Iljitsch van Beijnum -
Michael.Dillon＠radianz.com -
Rafi Sadowsky