Limitation in the RPSL DB

On Tue, 7 Aug 2001, Stephen Burley wrote:

>    Date: Tue, 7 Aug 2001 10:56:12 +0100
>    From: Stephen Burley <stephenb at uk.uu.net>
>    To: db-wg at ripe.net
>    Subject: Limitation in the RPSL DB
>    
>    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?

e.g.

195.219.118 is an ASSIGNED PA that is part of the ALLOCATED PA
195.219.96.0 - 195.219.127.255 and there are two distinct route
route objects, with distinct "origin:".

   route:        195.219.0.0/19
   descr:        Teleglobe UK NET
   origin:       AS8297
   mnt-by:       AS8297-MNT
   changed:      ip-addr at teleglobe.com 20010806
   source:       RIPE

   route:         195.219.118.0/24
   descr:         Ogic Network
   origin:        AS15699
   mnt-by:        OGIC-MNT
   changed:       jmejias at adam.es 20001003
   source:        RIPE

Maybe that's what you are loking for.

Regards.
__

Pierre Thibaudeau                     |   e-mail: <prt at teleglobe.net>
TELEGLOBE CANADA                      |   e-page: <prt-p at teleglobe.net>
1000, rue de La Gauchetiere ouest     |
Montreal, QC   H3B 4X5                |      Tel: +1-514-868-7257
Canada                                |      fax: +1-514-868-8446

>    Would you like me to explain further?
>    
>    Regards
>    Stephen Burley
>    UUNET EMEA Hostmaster
>