Another one feature request
Hello there colleagues, what about loosing requirements a little for inetnum ranges format? Specifically, do not require spaces around dash in the middle of two IPv4? I.e., 195.91.168.0-195.91.169.255 I suppose could be considered as valid range as 195.91.168.0 - 195.91.169.255 Thank you in advance :) Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Dear Dmitry, On Wed, 6 Jun 2001, Dmitry Morozovsky wrote:
Hello there colleagues,
what about loosing requirements a little for inetnum ranges format? Specifically, do not require spaces around dash in the middle of two IPv4? I.e.,
195.91.168.0-195.91.169.255
I suppose could be considered as valid range as
195.91.168.0 - 195.91.169.255
We will put this in our wish list too. Best regards, Engin Gunduz RIPE NCC Database Group
Thank you in advance :)
Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------
Engin, Engin Gunduz wrote:
On Wed, 6 Jun 2001, Dmitry Morozovsky wrote:
Hello there colleagues,
what about loosing requirements a little for inetnum ranges format? Specifically, do not require spaces around dash in the middle of two IPv4? I.e.,
195.91.168.0-195.91.169.255
I suppose could be considered as valid range as
195.91.168.0 - 195.91.169.255
We will put this in our wish list too.
having to confess that I didn't follow the reimp thread to the last detail - so this might have been an issue already in the past - I'd deeply like to see the possibility to send in again CIDR formed inetnum objects. Any chance? Cheers, Carsten Schiefner
Carsten Schiefner wrote:
Engin,
[...] having to confess that I didn't follow the reimp thread to the last detail - so this might have been an issue already in the past - I'd deeply like to see the possibility to send in again CIDR formed inetnum objects. Any chance?
Hello Engin, I just found this in one of my folders - so the issue has obviously and already been raised... Sorry for my 'me too', -C. --- begin forwarded message from Engin Gunduz --- Date: Thu, 31 May 2001 11:28:55 +0200 (CEST) From: Engin Gunduz <engin@ripe.net> To: Dmitry Morozovsky <marck@rinet.ru> cc: Hank Nussbacher <hank@att.net.il>, reimp-mig-tf@ripe.net, db-wg@ripe.net, lir-wg@ripe.net, ripe-dbm@ripe.net Subject: Re: DB V3 feature request Dear Dmitry, On Wed, 30 May 2001, Dmitry Morozovsky wrote:
On Wed, 30 May 2001, Engin Gunduz wrote: [...] 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 --- end forwarded message from Engin Gunduz ---
Hi Carsten, all, On Tue, 19 Jun 2001, Carsten Schiefner wrote:
Carsten Schiefner wrote:
Engin,
[...] having to confess that I didn't follow the reimp thread to the last detail - so this might have been an issue already in the past - I'd deeply like to see the possibility to send in again CIDR formed inetnum objects. Any chance?
Hello Engin,
I just found this in one of my folders - so the issue has obviously and already been raised...
Sorry for my 'me too',
No problem. Probably not everybody knows this: The archives of db-wg list (as well as the other wg lists) are available at: http://www.ripe.net/ripe/mail-archives/ A very handy reference ;) Best regards, Engin Gunduz RIPE NCC Database Group
-C.
--- begin forwarded message from Engin Gunduz --- Date: Thu, 31 May 2001 11:28:55 +0200 (CEST) From: Engin Gunduz <engin@ripe.net> To: Dmitry Morozovsky <marck@rinet.ru> cc: Hank Nussbacher <hank@att.net.il>, reimp-mig-tf@ripe.net, db-wg@ripe.net, lir-wg@ripe.net, ripe-dbm@ripe.net Subject: Re: DB V3 feature request
Dear Dmitry,
On Wed, 30 May 2001, Dmitry Morozovsky wrote:
On Wed, 30 May 2001, Engin Gunduz wrote: [...] 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 --- end forwarded message from Engin Gunduz ---
participants (3)
-
Carsten Schiefner -
Dmitry Morozovsky -
Engin Gunduz