Time to bring back "Connected Status"
In the beginning was the ARPANET, When SRI and BBN handled the NIC and NOC for the Internet, there was a field in the WHOIS database called "Connected Status." People could request IP networks (Class A/B/C) from SRI, but BBN would only route networks with the Connected Status on the ARPANET. You could do Whois queries to check the status of any network address. Companies could request IP addresses for internal use, without connected status. Around the time the NSFNET took over, the database sources started diverging. Connected Status was deleted from the WHOIS database. There was only one WHOIS database. NSFNET kept a seperate database of which networks were allowed to use the NSFNET. I know about all the routing specificiation language efforts, but is it possible to go back and do something simple? For networks which are announced on the Internet, add a Connected field to the regional address registries listing the AS Number(s) which could announce the network. Private, internal only networks would have an Unconnected status.
You know, that would be a great idea except for one thing. It's just too simple ;-) /Alex Kiwerski -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Sean Donelan Sent: Monday, April 28, 2003 4:01 PM To: nanog@merit.edu Subject: Time to bring back "Connected Status" In the beginning was the ARPANET, When SRI and BBN handled the NIC and NOC for the Internet, there was a field in the WHOIS database called "Connected Status." People could request IP networks (Class A/B/C) from SRI, but BBN would only route networks with the Connected Status on the ARPANET. You could do Whois queries to check the status of any network address. Companies could request IP addresses for internal use, without connected status. Around the time the NSFNET took over, the database sources started diverging. Connected Status was deleted from the WHOIS database. There was only one WHOIS database. NSFNET kept a seperate database of which networks were allowed to use the NSFNET. I know about all the routing specificiation language efforts, but is it possible to go back and do something simple? For networks which are announced on the Internet, add a Connected field to the regional address registries listing the AS Number(s) which could announce the network. Private, internal only networks would have an Unconnected status.
On Mon, Apr 28, 2003 at 07:00:50PM -0400, Sean Donelan wrote:
For networks which are announced on the Internet, add a Connected field to the regional address registries listing the AS Number(s) which could announce the network.
Well, this is exactly what route objects are for. Can't get too much simpler than that. The problem is that you have to protect the authoritative database(s) in order to avoid bogus origin declarations. RIPE does that quite nicely with their maintainer concept. A maintainer protecting and IP address range (inetnum) does also protect the creation of route objects for this IP range (but authority for routing information can be delegated to some other entity by using mnt-routes attribute). Without this kind of protection scheme[1], route origin documentation becomes worthless. See RADB with the hundreds and thousands of automatically generated "proxy route objects" which some people seem to believe being a great idea. Then again, I've pretty much given up hope that ISPs filter their customers properly. Filtering customers means losing money to the competition, sadly. Best regards, Daniel [1] http://www.ripe.net/ripencc/faq/database/route-creation-checks.html
For networks which are announced on the Internet, add a Connected field to the regional address registries listing the AS Number(s) which could announce the network. Private, internal only networks would have an Unconnected status.
you know, some nights are more resless than others and occasionally i have nightmares about the period in my life when I was informed that due to a clerical error, the 27 sites we had brought up over the previous 18 months had been assigned in the unconnected db and we had duplicate assignments that overlapped the connected db. the following six months were spent renumbering. :) murphy is a clerk. --bill
participants (4)
-
Alexander Kiwerski -
bmanning＠karoshi.com -
Daniel Roesen -
Sean Donelan