Limitation in the RPSL DB

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.
---