[routing-wg] FW: discussion about rogue database objects

Hi,

On Wed, Nov 12, 2014 at 11:18:25AM +0400, poty at iiat.ru wrote:
> I'm not sure the problem is imminent first hand.

The problem is real, and needs to be fixed.

> I'm sure that the routing is not RIPE NCC's business.

As long as nobody else is providing a high-quality and well-authenticated
IRR DB for RIPE region objects, it *very much* is the RIPE NCC's business.

> I believe that the routing object should be created at the place where
> it can be checked properly.

Please provide suggestions how that will help RIPE region LIRs properly
document their routing policy if out-of-region networks are involved.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 811 bytes
Desc: not available
URL: </ripe/mail/archives/routing-wg/attachments/20141112/586108d8/attachment.sig>