Re: Domain names for ISP infrastructure links
At 17:25 1/7/97, John W. Stewart III wrote:
conventions are fine
and it's helpful to users and operators alike for names to contain a fair amount of information
but "standardizing" with fixed-width fields, pop codes, next-hop router, etc. doesn't seem that productive when providers are gonna do what they want anyway.
No... we're going to mandate OID-style router names for the world's Internet providers: <isoc-tree>.<internet-infrastructure branch>. <iso country code>.<city ordinal>.<provider #>. <facility #>.<rack #>.<shelf #>.<router ordinal> Great fun to watch (it could be happening this way in the alternate universe next door.) ;-) /John
John Curran supposedly said:
At 17:25 1/7/97, John W. Stewart III wrote:
conventions are fine
and it's helpful to users and operators alike for names to contain a fair amount of information
but "standardizing" with fixed-width fields, pop codes, next-hop router, etc. doesn't seem that productive when providers are gonna do what they want anyway.
No... we're going to mandate OID-style router names for the world's Internet providers:
<isoc-tree>.<internet-infrastructure branch>. <iso country code>.<city ordinal>.<provider #>. <facility #>.<rack #>.<shelf #>.<router ordinal>
Great fun to watch (it could be happening this way in the alternate universe next door.)
;-) /John
Which is exactly why I asked the question if people are serious about this. I have great fun specifying things (hey thats why I like the IETF :-) and would happily spend a few hours coming up with all sorts of great specifications but I want to know if they have any chance of being adopted. ---> Phil
On Tue, 7 Jan 1997, John Curran wrote:
At 17:25 1/7/97, John W. Stewart III wrote: No... we're going to mandate OID-style router names for the world's Internet providers:
<isoc-tree>.<internet-infrastructure branch>. <iso country code>.<city ordinal>.<provider #>. <facility #>.<rack #>.<shelf #>.<router ordinal>
Great fun to watch (it could be happening this way in the alternate universe next door.)
Maybe it time to troll to see if anyone wants GOSIP NSAP address to use for their in-addrs?? ;) -dorian
<isoc-tree>.<internet-infrastructure branch>. <iso country code>.<city ordinal>.<provider #>. <facility #>.<rack #>.<shelf #>.<router ordinal>
Great fun to watch (it could be happening this way in the alternate universe next door.)
Ow, can't we get the ZIP code and the longditude and lattitude in there as well? :-> Alex Bligh Xara Networks
From: "Alex.Bligh" <amb@xara.net>
<isoc-tree>.<internet-infrastructure branch>. <iso country code>.<city ordinal>.<provider #>. <facility #>.<rack #>.<shelf #>.<router ordinal>
Great fun to watch (it could be happening this way in the alternate universe next door.)
Ow, can't we get the ZIP code and the longditude and lattitude in there as well? :-> Not to forget (for US folks) the CLLI code for the serving CO for the emergency dialup on the aux port. For instance MAE-East is served by the Lewinsville CO in McLean, VA -> MCLNVALV. ---Rob
On Wed, 8 Jan 1997, Alex.Bligh wrote:
<isoc-tree>.<internet-infrastructure branch>. <iso country code>.<city ordinal>.<provider #>. <facility #>.<rack #>.<shelf #>.<router ordinal>
Great fun to watch (it could be happening this way in the alternate universe next door.)
Ow, can't we get the ZIP code and the longditude and lattitude in there as well? :->
Nah, that's what geographic IP addresses are for. (Ok, look up the other addresses for those interfaces... I want to know _where_ my packets are going) ;-) -- Billy Biggs ae687@freenet.carleton.ca
participants (6)
-
Alex.Bligh -
Billy Biggs -
Dorian R. Kim -
John Curran -
Philip J. Nesser II -
Robert E. Seastrom