This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Mysteries of the Internet: AS65000
- Previous message (by thread): [anti-abuse-wg] Mysteries of the Internet: AS65000
- Next message (by thread): [anti-abuse-wg] Mysteries of the Internet: AS65000
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Mon Apr 15 03:49:03 CEST 2019
In message <rr9JsgDrv9scFAsh at highwayman.com>, Richard Clayton <richard at highwayman.com> wrote: >Hurricane Electric is seeing announcements from other ASs some of which >have AS65000 declared to be origin of the prefix I understand. The announcements are, in effect, mislabled. >Best practice is to remove internal use AS's from announcements -- not >much bad happens if you don't (well, you might not get as much >reachability if other folk are also using that reserved AS within their >networks...) Is anybody anywhere filtering out this kind of malarkey? >>The only other thing I feel compelled to say, or ask right now, is just >>this: Who should I be notifying if there is an issue with this ASN? > >the NOC for the people making the incorrect announcement Yes. And can you tell me who that is please? I'm asking for a bit of help here, because I'm out of my depth. But judging from the short bio sketch of you that I just now read on your personal web page, this would seem to be right up your alley. Regards, rfg
- Previous message (by thread): [anti-abuse-wg] Mysteries of the Internet: AS65000
- Next message (by thread): [anti-abuse-wg] Mysteries of the Internet: AS65000
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]