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]/
[routing-wg]More specific prefix announce
- Previous message (by thread): [routing-wg]Re: More specific prefix announce
- Next message (by thread): [routing-wg]The Cidr Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Max Tulyev
president at ukraine.su
Fri Sep 2 08:26:49 CEST 2005
Hello! In practice, it works fine. You might like to set a hole: line in X.X.0.0/20 route object for X.X.6.0/23, and also create a separate route object for X.X.6.0/23. > Hello. > Unfortunately, I'm not so experienced in the question to anwer that. > Therefore I ask for help and will be thankful for any clarification. > > We have a /20 ASSIGNED PI address block and an AS. Is it allowed by RIPE > policy to intentionally announce more specific prefix than one we > have from our AS to upstream ASes? > For example, announce our X.X.0.0/20 to upstream A and announce both > X.X.0.0/20 and X.X.6.0/23 to B? -- WBR, Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
- Previous message (by thread): [routing-wg]Re: More specific prefix announce
- Next message (by thread): [routing-wg]The Cidr Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]