DB V3 feature request

Hiya Engin,

Surely this is just a wrapper on the email processing submission side.
Objects will always need to be stored ( and output) in a.b.c.d - w.x.y.z
format since this can cover multiple network ranges.

I would like to see input accepted in these three forms, like most of the IP
perl libraries:

a.b.c.d/xx
a.b.c.d 255.255.255.X
a.b.c.d - w.x.y.z

I do not care if the object created always contains:

a.b.c.d - w.x.y.z

Cheers
Dave
----
Delay in replying caused by 2 weeks holiday.
----

On Thu, 31 May 2001, Engin Gunduz wrote:

->
->Dear Dmitry,
->
->On Wed, 30 May 2001, Dmitry Morozovsky wrote:
->> On Wed, 30 May 2001, Engin Gunduz wrote:
->>
->> EG> As a followup: We have prepared a list of known bugs for v3 software,
->> EG> which is at:
->> EG>
->> EG> http://www.ripe.net/ripencc/pub-services/db/issues.html
->>
->> Great, thank you.
->>
->> Small question: is there a plan to implement support for a.b.c.d/len
->> inetnums? surely we can write small wrapper, but...
->
->This would require some biggish changes in the structure, so not
->possible to implement right away. However we'll put this in our
->wish list.
->
->Regards,
->
->Engin Gunduz
->RIPE NCC Database Group
->
->
->>
->> Sincerely,
->> D.Marck                                   [DM5020, DM268-RIPE, DM3-RIPN]
->> ------------------------------------------------------------------------
->> *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
->> ------------------------------------------------------------------------
->>
->
->
->