Re: autosys to a PS

Mike Nittmann <nittmann@wis.com> Fri, 10 March 1995 20:09 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11542; 10 Mar 95 15:09 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa11538; 10 Mar 95 15:09 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa13195; 10 Mar 95 15:09 EST
Received: by interlock.ans.net id AA44919 (InterLock SMTP Gateway 3.0 for iwg-out@ans.net); Fri, 10 Mar 1995 14:44:13 -0500
Message-Id: <199503101944.AA44919@interlock.ans.net>
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-2); Fri, 10 Mar 1995 14:44:13 -0500
Received: by interlock.ans.net (Protected-side Proxy Mail Agent-1); Fri, 10 Mar 1995 14:44:13 -0500
Date: Fri, 10 Mar 1995 14:03:47 -0600 (CST)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mike Nittmann <nittmann@wis.com>
To: yakov@watson.ibm.com
Cc: bgp@ans.net, roll@stupi.se
Subject: Re: autosys to a PS
In-Reply-To: <199503101826.AA03401@interlock.ans.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 10 Mar 1995 yakov@watson.ibm.com wrote:

> Folks,
> If anyone else on this list, besides Peter Lothberg, has
> a serious objections to moving the document to a PS, please
> speak up NOW !!!
> 
> Yakov.
> 


well, looking at the semantics of AS numbers: an AS number makes only 
sense when there is at least one domain that names a communicating entity.
I did not find a communicating entity with only an AS number and not at 
least one domain attached to it. (well, who has such an aimal, please 
come forward).

AS numbers are just numbers. The space is much bigger than the IP address 
space (no class structure here that augments the distribution 
granularity).

How about a total different scheme: 
automatically issue an AS number when issuing a domain. This way the 
entity that requests a domain name gets automatically at least one AS 
number.

This fits the bill for small entities that require only one domain and 
will eventually build their own AS. 
Those that have more than one domain will automatically have more AS 
numbers, which they need not use. 

Entities that would need more AS numbers than domains will still go 
through an AS number request process.

What this does overall: AS registration will hav etwo paths: one 
automatic path connected to the domain registration: makes two 
registrations with one transaction. The othe rpath is requesting of 
additional AS numbers wi1~hich should then be treated restrictively as 
described in the paper.

The overall work load should go down, and I would say that's the point of 
it all. And only As requests that go out of the normal will require 
action.

How about that?

Mike


---------------------------------------------------------------------------------
Michael F. Nittmann                                              nittmann@wis.com
Network Architect
B3 Corporation                                             (715) 387 1700 xt. 158
---------------------------------------------------------------------------------