Re: ASN draft

Bill Manning <bmanning@isi.edu> Tue, 07 February 1995 13:18 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01229; 7 Feb 95 8:18 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01225; 7 Feb 95 8:18 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa03967; 7 Feb 95 8:18 EST
Received: by interlock.ans.net id AA24907 (InterLock SMTP Gateway 1.1 for iwg-out@ans.net); Tue, 7 Feb 1995 08:05:01 -0500
Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 7 Feb 1995 08:05:01 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 7 Feb 1995 08:05:01 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Bill Manning <bmanning@isi.edu>
Message-Id: <199502071304.AA20097@zephyr.isi.edu>
Subject: Re: ASN draft
To: Sean Doran <smd@cesium.clock.org>
Date: Tue, 7 Feb 1995 05:04:52 -0800 (PST)
Cc: bmanning@isi.edu, bgp@ans.net, jhawk@panix.com, pst@cisco.com, tony@mci.net
In-Reply-To: <95Feb6.222004pst.6231@cesium.clock.org> from "Sean Doran" at Feb 6, 95 10:19:56 pm
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 772

> You will note that in my brief definition of an ASN as
> something that uniquely identifies an AS, I mentioned
> nothing about how the ASN should be used.
> 
> How ASNs tend to be used is in BGP (for tagging NLRI) and in
> policy-routing databases and configurations.   In both
> cases, the ASN describes an AS and nothing else.
> 
> People sometimes tend to think of ASes and ranges of address
> space as inseperable to the point where an ASN is simply a
> short-hand for a range of address space.
> 

The current draft defines/redefines the ASN strictly as a routing tag,
depreciating any other use.  As you indicate in the above paragraphs,
you believe that there are other valid uses of AS and ASN notation.

So, we agree here.  The draft should change.

-- 
--bill