updated with IP addresses, which seems like another great
> > development.
> > >
> > > Maybe it’s worth sending them feedback that if they provide IP
> addresses
> > > for institutions who haven’t signed up, they need to make it clear to
> > > publishers that these a
rovide IP addresses
> > for institutions who haven’t signed up, they need to make it clear to
> > publishers that these are non-verified and publishers should always
> confirm
> > with the institution before making changes.
> >
> > Deborah
> >
> >
> >
t;
>
> From: Code for Libraries On Behalf Of Lolis,
> John
> Sent: Saturday, 5 December 2020 12:25 PM
> To: CODE4LIB@LISTS.CLIR.ORG
> Subject: Re: [CODE4LIB] The IP Registry
>
> It seems to me that they have a glaring omission in not notifying a
> registrant when someone submitted or
for Libraries On Behalf Of Lolis, John
Sent: Saturday, 5 December 2020 12:25 PM
To: CODE4LIB@LISTS.CLIR.ORG
Subject: Re: [CODE4LIB] The IP Registry
It seems to me that they have a glaring omission in not notifying a
registrant when someone submitted or modified an IP address range
It seems to me that they have a glaring omission in not notifying a
registrant when someone submitted or modified an IP address range for their
institution. Seems like a no-brainer to me.
As for *publishers* providing IP address ranges to update an institution's
IP range, *what are they
They portray themselves as offering accurate IP ranges, when what
they've got amounts to some guess-work. They don't really have any way
to catch errors like the Choopa.net example Tom Keays gave, or the
consortium sub-range in mine. Unless, of course, the way they catch
those is to rely on
A couple of years ago, when I was reviewing the IP set up for Scitation for
my institution, I noticed it included an unfamiliar IP range,
216.155.128.000 - 216.155.128.063. This was not the first time I had
encountered this range (although I don't have a record of what the previous
vendors were
Yikes, this does sound like we're being forced into a service whether we
want to use it or not. At our institution we're the default owner of a
range of IPs we manage on behalf of a public library consortium that we're
not actually a part of (so the consortium shouldn't be accessing our
I am concerned by the fact that the IP Registry appears to have gone
around figuring out the IP ranges for schools based on public records
from the IANA and a bunch of vendor records. I'm sure that was
difficult, and their site says it took four years. When it was done,
they announced that
The experience of having to change IPs with publishers and vendors is what
ultimately pushed me to sign up even though I was feeling kind of
skeptical. The proxy migration actually happened a couple years ago
before we signed up for the IP Registry, so the fun of trying to figure out
who I
It is one thing to sign up for a service and another to see how it performs
when you need it. Jeremiah: It sounds like you had a good experience about the
IP Registry when you really needed it—changing the IP address of a proxy
server. Can you (or anyone else) talk more about that experience?
I was skeptical at first, too, but took the leap anyway and signed us up
here at Eastern Oregon University. It went through our campus IT and legal
departments first and the were okay with it. As I was setting things up I
noticed if there’s any question as to whether or not your institution owns
All,
Anyone have experience with theipregistry.org?
I took a look at it today and I'm not sold. The concept is good. But I
am skeptical of people wanting to insert themselves into my
institution's workflow.
Will Martin
Head of Digital Initiatives, Systems and Services
Chester Fritz
13 matches
Mail list logo
