[ARIN-consult] Community Consultation on IRR Route Validation. attorney client communication.

Andrew Dul andrew.dul at quark.net
Wed Apr 1 11:02:37 EDT 2015

On 4/1/2015 7:47 AM, John Curran wrote:
> On Apr 1, 2015, at 10:43 AM, Andrew Dul <andrew.dul at quark.net> wrote:
>> On 3/31/2015 2:09 PM, John Curran wrote:
>>> On Mar 31, 2015, at 4:52 PM, Gert Doering <gert at space.net> wrote:
>>>> ...
>>>> Now, I understand that you can buy a maintainer object, and thus protect
>>>> your own address space - but as a user of the RADB, how can I see which
>>>> objects are legitimate, and which (paid-for!) maintainers just put in
>>>> stuff that does not belong to them?
>>> On a (slightly) related question...  Are there organizations, e.g. security
>>> or management service providers, that put entries in routing registries and 
>>> update them on behalf of their customers?   I've heard folks mention this now
>>> and then, but have no direct experience (and it could easily be relevant to 
>>> understanding goals and requirements for any changes)
>> I have created IRR records on behalf of customers in the past.  This is
>> most often done for stub networks who are either singly homed to your
>> network or multihomed with another network.  The customer often doesn't
>> have the experience and/or currently doesn't or doesn't want to maintain
>> the technical expertise to manage these types of routing records.
> How often does that pose a problem when the customers move on
> to another provider?  Is that a minor issue or do we end up with
> outdated cruft in the IRR as a result?
I haven't seen it cause a problem, but I guess it could in some cases. 
Usually it just creates cruft.  Although for some customers who have
their own AS the old crufty record still has their origin AS and thus
ends up working fine once, especially if the new provider adds that AS
to their AS-SET.


More information about the ARIN-consult mailing list