[1010] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: AS690 advisory update

daemon@ATHENA.MIT.EDU (Elliot Alby)
Tue Nov 14 14:45:22 1995

Date: Tue, 14 Nov 1995 14:38:19 -0500 (EST)
From: Elliot Alby <ealby@sprint.net>
To: Steve Heimlich <heimlich@ans.net>, nanog@merit.edu, ealby@sprint.net,
        kconners@sprint.net, insc@sprint.net, db-wg@ripe.net,
        engineer@sprint.net
In-Reply-To: <Pine.SV4.3.91.951114142826.4208K-100000@mercury.sprintlink.net>


> After this time, AS690 advisories will be ignored.  Policy toward
> routes registered in the IRR will be based solely on origin AS.
> The origin AS will be expanded to the set of route objects registered
> for that origin AS; the resulting list of prefixes will be used in
> generating router configurations, as today.

in the case of AS#1 routing AS#2, suppose AS#2 sent in the route object 
and list themselves as the origin, and put AS#1 in the advisory. in the 
new scenario, will ANS now only allow routes coming via the ASN in the 
ORIGIN field? i.e. will AS#2 have to change the ASN in the origin field 
to AS#1 so ANS knows where to look for for the routes? 
 
- elliot alby/sprintlink implementation
 

home help back first fref pref prev next nref lref last post