IRR ibjects rather than manual ASN entries please?

[jzp-IAR]

Why manual ASN registration for the alert - any chance we could give you an IRR as-set to be able to watch for instance all infrastructure ASNs and customers as they modify without needing to log in and change your settings.

[karlinjf]

Because I don't want to send people unwanted mail, since some of the emails will in fact be false positives. Unless you feel that operators should have to deal with it regardless

[jzp-IAR]

Because I don't want to send people unwanted mail, since some of the emails will in fact be false positives. Unless you feel that operators should have to deal with it regardless

Erm, you misunderstood my poorly phrased, quick question while we were at the conference. Let me try again:
"Why should I, as a registered user, be manually entering one or more ASNs? Why can't I say 'send me all alerts for an IRR macro or as-set' and you all expand that on the backend?"

This would also address the static character length limit mpetach hit when entering the pile of y! ASNs. Static limits bad, layers of abstraction good.

[karlinjf]

True enough, it's a good suggestion. I'll add it to my todo list for the next round of work on the site.

Josh

[iand]

I'd like to echo jzp's request - just so you know it's not a singleton requirement.
Being able to register a short piece of valid rpsl would match my wishes exactly.
In my case, it'd be an as-set and a route-set.