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/db-wg@ripe.net/
Description of Inter-AS Networks in the RIPE Routing Registry
- Previous message (by thread): Description of Inter-AS Networks in the RIPE Routing Registry
- Next message (by thread): Description of Inter-AS Networks in the RIPE Routing Registry
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Curtis Villamizar
curtis at ans.net
Fri May 7 20:46:45 CEST 1993
> > Does this mean that if ANS or Merit announces the FixW FDDI, Barrnet > > and NASA can't add a pair of routers only peering with each other on > > the ring? > > No! > Any peering across the inter-AS network ispossible. > It means that the ripe-81 model can only describe one AS announcng > the inter-AS network *itself* to twhe world. ripe-81 allows only > one originating AS (in bgp terms) per net. Daniel, I knew that the peering relationship was possible, but Barrnet and NASA then have to ask ANS to change the database entry (to insure that ptraceroute will still work) even if the two routers did not peer with and ANS router. I was suggesting that we might want to have each AS announce it's own routers or have a way for them to explicitly delagate that authority to someone else. Otherwise you could get caught up in squabbles between competing network providers over "proper" ownership of this authority. Curtis
- Previous message (by thread): Description of Inter-AS Networks in the RIPE Routing Registry
- Next message (by thread): Description of Inter-AS Networks in the RIPE Routing Registry
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]