Re: ASN draft

Sean Doran <smd@cesium.clock.org> Tue, 07 February 1995 04:43 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18315; 6 Feb 95 23:43 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18311; 6 Feb 95 23:43 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa22059; 6 Feb 95 23:43 EST
Received: by interlock.ans.net id AA50719 (InterLock SMTP Gateway 1.1 for iwg-out@ans.net); Mon, 6 Feb 1995 23:12:35 -0500
Received: by interlock.ans.net (Internal Mail Agent-2); Mon, 6 Feb 1995 23:12:35 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Mon, 6 Feb 1995 23:12:35 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Sean Doran <smd@cesium.clock.org>
To: bmanning@isi.edu, pst@cisco.com
Subject: Re: ASN draft
Cc: bgp@ans.net, jhawk@panix.com, tony@mci.net
Message-Id: <95Feb6.201222pst.6230@cesium.clock.org>
Date: Mon, 6 Feb 1995 20:12:20 -0800

| The ASN is the number that defines administrative bounds.
| In a route registry it denotes span of control.  If an AS
| has the ASN redefined to only be a route tag, then what
| will replace it in the route registry to denote span of
| control?

Bill -

   Are you suggesting that the purpose of an ASN is to
provide something convenient to tag routes with at the
registry level, rather than something that is used to
uniquely identify an AS, where an AS is a clump of routers
with an identical and consistent routing policy?

   If so, you are out of your tree.

	Sean.   

P.S.:
| Of course they could still bite my butt with flaps, but that is a fact'o'life
| in the internet world.  

It's a fact of death, actually, with a sizeable handful of
routers maxing out their CPU dealing with those flaps.

This will be a big topic at NANOG.

P.P.S.: | If we could get a working IDRP base from any
        | commercial router vendor

Personally, I believe that Cisco has more important things
to be spending Paul and Ravi's time one than IDRP development.