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]/

Limitation in the RPSL DB

Previous message (by thread): Limitation in the RPSL DB
Next message (by thread): Limitation in the RPSL DB

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Joao Luis Silva Damas joao at ripe.net
Tue Aug 7 12:00:48 CEST 2001

At 10:56 +0100 7/8/01, Stephen Burley wrote:
>Hi
>     We have hit a small problem with the RPSL DB structure. As the 
>RPSL DB is supposed to reflect the real routing world we need some 
>functionality adding to the DB. It is possable for PA that is part 
>of a multihomed customer to have a differant origin to that of the 
>main block of ip space. Can we get this refelected the in RPSL DB 
>structure? Would you like me to explain further?
>

Hi Stephen,

yes please explain further. From what I read in your mail, you solve 
this by registering "route" objects for each block and their 
corresponding "origin" attributes, so I guess you mean something 
different.

Joao

>Regards
>Stephen Burley
>UUNET EMEA Hostmaster

--

Previous message (by thread): Limitation in the RPSL DB
Next message (by thread): Limitation in the RPSL DB

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]