cfriacas at fccn
Feb 14, 2012, 7:11 AM
Post #4 of 5
RE: Requested RIPE database object changes
[In reply to]
Pim, due to recent RIPEdb changes, the object is not completely visible
anymore -- auth: lines, i.e. MD5/PGP went away.
Afaik, the last person who updated the object is already in touch with
RIPE/NCC about this, to see what needs to be done. But i'm afraid our old
model of adding people/origins to this object is in danger... :-)
On Tue, 14 Feb 2012, juan.cerezo [at] bt wrote:
> Hi, Pim.
> It was a mistake of our ops people trying to create a replica of the 2002::/16 with origin AS8903 to pass the filter of the ipv6 transit provider.
> My apologies...
>> -----Original Message-----
>> From: pim [at] hosted [mailto:pim [at] hosted] On Behalf Of Pim
>> van Pelt
>> Sent: Tuesday, February 14, 2012 11:59 AM
>> To: ipv6-ops [at] lists; Cerezo Martin,JP,Juan,DMK2 R
>> Subject: Re: Requested RIPE database object changes
>> On Tue, Feb 14, 2012 at 11:03 AM, RIPE Database Notifications
>> <unread [at] ripe> wrote:
>>> This is to notify you that some objects in which you are referenced
>>> as a maintainer were requested to be changed, but *failed* the
>>> proper authorisation for any of the referenced maintainers.
>> Hoi Juan!
>> The 2002::/16 object is currently maintained by the people in
>> TOSE1-RIPE. May I ask what were you trying to accomplish by re-owning
>> the object to BTTEL-MNT ?
>> Pim van Pelt <pim [at] ipng>
>> PBVP1-RIPE - http://www.ipng.nl/