[anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Richard Clayton
richard at highwayman.com
Thu Mar 21 02:02:01 CET 2019
In message <842FCFC4-B8E0-49CA-829A-4A5CDF44C7BD at consulintel.es>, JORDI PALET MARTINEZ via anti-abuse-wg <anti-abuse-wg at ripe.net> writes > This has been seen many times, even chain situations like > > <upstreams and peers> - AS X > \ > AS 3 - AS 2 - AS 1 > / > <upstreams and peers> - AS Y by the way, when I see AS 2 or 3 at the end of path I immediately assume that someone has been confused by the syntax of their router and meant to generate 64496 64496 64496 but instead generated 64496 3 the opposite error tends to create very long (but non-hijacking) AS paths which occasionally cause operational problems. -- richard Richard Clayton Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 185 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/anti-abuse-wg/attachments/20190321/d1cb918d/attachment.sig>
- Previous message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
- Next message (by thread): [anti-abuse-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]