Re: ASN draft

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

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22548; 7 Feb 95 2:03 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa22544; 7 Feb 95 2:03 EST
Received: from interlock.ans.net by CNRI.Reston.VA.US id aa24000; 7 Feb 95 2:03 EST
Received: by interlock.ans.net id AA27261 (InterLock SMTP Gateway 1.1 for iwg-out@ans.net); Tue, 7 Feb 1995 01:53:10 -0500
Received: by interlock.ans.net (Internal Mail Agent-2); Tue, 7 Feb 1995 01:53:10 -0500
Received: by interlock.ans.net (Internal Mail Agent-1); Tue, 7 Feb 1995 01:53:10 -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.225301pst.6232@cesium.clock.org>
Date: Mon, 6 Feb 1995 22:52:59 -0800

| Why should a prefix be tied to an AS?  That's just the way Merrit organized
| things,  but I think that was one honking mistake, looking back on it now.

Tsk, tsk, using "should" instead of "must" gets you picked
on. :)

Why should a prefix be tied to an AS?  Well, because not
doing so causes aggregation to blow chunks, causes certain 
software to go into nightmare mode, and gives me headaches.

(Especially when I look at certain ugly as-path filter lists,
or start thinking about multihomed internets).

However, historically, prefixes have floated between or among
more than one AS; it happens, and it may get worse as time
marches on. (People still run EGP, gr, and soon the PRDB
barrier will drop and routes from DREN et al. will start
spilling into the world.  We (this includes DREN, whose
people understand the future in this respect) are in search
of solutions...)   So given this, and the fact that we
have existence proof that doing it can work, there is no
reason why a prefix must be tied to an AS.

Moreover, as I said somewhere else, aggregation and other
things can break the ties between prefix and AS.

However, imho, originating a prefix from more than one AS
is a bad idea.  (Yes, even though this generally means BGP
or manual route-tagging for all multihomed internets...).

	Sean.