Hi there,
> Thanks for creating my account.
You are most welcome.
> I had one question about the customer alarms. The tutorial
> says the Customer Alarms are to check:
> "Are my single-homed customers routes being announced with
> myself as the expected transit provider?"
> Does the system also check for more-specific announcements
> from the customer prefix blocks that might show up with a
> different source ASN?
We do monitor more specifics. However, this particular alarm type focuses on matching the upstream of the origin, i.e. YYYY in AS
sequence {XXXX, YYYY, ZZZZ}. This means that the highjacked more specific route would only be detected if announced over someone
else than YYYY. The type of alarm you are implying will become available in the version of myASn that integrates into the RIPE NCC
LIR Portal, for it'll allow the user to monitor IP space originating from any ASN. One of the remaining issues is how to facilitate
users, whom are non-LIRs, with access to the system. We are currently looking into several feasible workarounds. Our aim is to
provide this service to the entire community. Both related and non-related ideas are always welcome ;)
LIR Portal: https://lirportal.ripe.net/lirportal/index.html
I hope above answers your question. There should be a beta of the next version ready for demonstration by the next RIPE meeting in
January. Watch this space for more information.
Best regards,
Matthew Williams
Ps. I have cc'd Maximo Alves, the developer working on myASn, in case he has something to add.
> -----Original Message-----
> From: metzger(a)ripe.net [mailto:metzger@ripe.net] On Behalf Of
> Joe Metzger
> Sent: 28 October 2003 18:25
> To: matthew(a)ripe.net
> Subject: Re: myASn Super User Account Created
>
>
> Matthew,
> Thanks for creating my account.
>
> This looks like a very interesting project! I was looking at
> putting together something similar to help monitor and track
> problems with Spammers hijacking address space for short
> intervals and using them to inject spam.
>
>
> I had one question about the customer alarms. The tutorial
> says the Customer Alarms are to check:
> "Are my single-homed customers routes being announced with
> myself as the expected transit provider?"
>
> Does the system also check for more-specific announcements
> from the customer prefix blocks that might show up with a
> different source ASN?
>
>
> Is the myastesting(a)ripe.net mailing list the appropriate
> place to ask this kind of question?
>
>
> --Thanks!
> Joe Metzger
>
> Matthew Williams wrote:
> >
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Dear myASn Test User,
> >
> > We have created a super user account for you with the requested
> > password. You have also been added to our mailing list
> > "myasntesting(a)ripe.net". Please help us to improve the
> current alpha
> > version by sending your comments to
> mailto:myasntesting@ripe.net. The
> > latest "bug" and
> "requested features" lists are accessible from the
> > help page after login.
> >
> > Some useful links:
> > - - - -------------------
> > * myASn Login: http://www.ris.ripe.net/cgi-bin/myas/index.cgi
> >
> > * myASn Help: http://www.ripe.net/ris/myasnhelp.html
> >
> > * myASn FAQ: http://www.ripe.net/ris/myasnfaq.html
> >
> > * myASn Glossary: http://www.ripe.net/ris/myasngls.html
> >
> > * myASn Tutorial:
> > http://www.ripe.net/ris/Talks/myAS_TUTORIAL_MEGABIT.pdf
> >
> > Thank you for signing up as a myASn test user!
> >
> > Kind regards,
> > The RIS Team
> >
> > Ps. We are in the process of changing the project name from
> "myAS" to
> > "myASn".
> >
> > ---
> > > Matthew Williams (MW243-RIPE)
> > > Customer Liaison Engineer
> > > RIPE NCC - http://www.ripe.net/np/
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: PGP 7.0.4
> >
> > iQA/AwUBP56aIcHkFbJe+GdoEQJ5MQCg0R+egHb4GgAmJsp5xBzZYtMq4fkAoNmh
> > GhPIefYXOy+oQ/8OosNrBzrM
> > =7WnO
> > -----END PGP SIGNATURE-----
>
> --
> Joe Metzger
> metzger(a)es.net
> Network Engineering, ESnet
> Lawrence Berkeley National Laboratory
>
