[routing-wg] route objects changes (AS migration)
- Previous message (by thread): [routing-wg] route objects changes (AS migration)
- Next message (by thread): [routing-wg] Clear ip bgp * timing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ruediger Volk, Deutsche Telekom T-Com - TE141-P1
rv at NIC.DTAG.DE
Fri Mar 11 20:48:13 CET 2011
Hello Sergey, > Hello, > > we are under migration from one AS12772 to new one AS56341. > Currently, in RIPE DB networks have route-objects with old AS12772. > > Could you tell me when I need make changes (modify or remove/add) in RIPE > DB: > 1) add new route objects before migration and remove old after migration; this is the right way to do it; this is called "make before break"; RPSL and the RIPE database support this by allowing route objects with different "origin:" for the identical prefix at the same time. > 2) modify route objects after migration; that's "wrong" because this means that you create a time window during which your actual announcement is NOT documented/authorized by a matching route object. (Also keep in mind: route[6] objects use prefix AND origin AS as combined primary key. So two route objects with different origin: attribute should be considered fundamentally different. It may be correct to say "replace the route object".) > 3) remove old route objects after migration and then create new objects. you would make the time window mentioned for 2 even longer Best regards, Ruediger Ruediger Volk Deutsche Telekom AG -- Internet Backbone Engineering E-Mail: rv at NIC.DTAG.DE
- Previous message (by thread): [routing-wg] route objects changes (AS migration)
- Next message (by thread): [routing-wg] Clear ip bgp * timing
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]