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? Regards Stephen Burley UUNET EMEA Hostmaster
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
--
On Tue, 7 Aug 2001, Stephen Burley wrote:
Date: Tue, 7 Aug 2001 10:56:12 +0100 From: Stephen Burley <stephenb@uk.uu.net> To: db-wg@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@teleglobe.com 20010806 source: RIPE route: 195.219.118.0/24 descr: Ogic Network origin: AS15699 mnt-by: OGIC-MNT changed: jmejias@adam.es 20001003 source: RIPE Maybe that's what you are loking for. Regards. __ Pierre Thibaudeau | e-mail: <prt@teleglobe.net> TELEGLOBE CANADA | e-page: <prt-p@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
Stephen, On Tue, Aug 07, 2001 at 10:56:12AM +0100, Stephen Burley wrote:
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?
Are you looking for this feature ?!?: mnt-routes The mnt-routes attribute may appear in an aut-num, inet- num, or route object. This attribute references a maintainer object which is used in determining authorization for the addition of route objects. After the reference to the maintainer, an optional list of prefix ranges (as defined in RPSL) inside of curly braces or the keyword "ANY" may follow. The default, when no additional set items are specified is "ANY" or all more specifics. The mnt-routes attribute is optional and multiple. See usage details in Section 9.1. [ rfc2725 ] David K. ---
participants (4)
-
David Kessens -
Joao Luis Silva Damas -
Pierre Thibaudeau -
Stephen Burley