This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
AS690 advisory update
- Previous message (by thread): AS690 advisory update
- Next message (by thread): AS690 advisory update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Steve Heimlich
heimlich at ans.net
Tue Nov 14 20:39:38 CET 1995
Elliot, Ignore the advisory. If AS2 is the origin, we will route traffic for that particular prefix/masklen using the most common policy already in place for routes in AS2. If the common policy is for us to send traffic destined for AS2 via our peer AS1, we will continue to do so for the new prefix/masklen. Steve > > > 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 ANS in the origin field > to AS#1 so ANS knows where to look for for the routes? > > - elliot alby/sprintlink implementation >
- Previous message (by thread): AS690 advisory update
- Next message (by thread): AS690 advisory update
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]