[anti-abuse-wg] [routing-wg] 2019-03 New Policy Proposal (BGP Hijacking is a RIPE Policy Violation) to be discussed on Anti-Abuse Working Group Mailing List

Hello,
my comments:
- section 4.0: Assessers should be under direct community control
(voted/approved by community/members), not just defined by NCC.

- section 4.0 + 7.0 should define minimal number of assessers

- reported incidents (reported by web-form defined at 4.0) should be
public, at least some metadata (prefix, offending ASN) to avoid
duplicate reports - with indication of assessment stage on that list

- Daniel

On 3/19/19 1:42 PM, Marco Schmidt wrote:
> Dear colleagues,
> 
> A new RIPE Policy proposal, 2019-03, "BGP Hijacking is a RIPE Policy
> Violation", is now available for discussion.
> 
> This proposed policy is of interest to both the Anti-Abuse and Routing
> working groups. The chairs of both these working groups have agreed to
> keep the discussion on one single mailing list to avoid duplication, and
> for formal consideration of the proposal within the RIPE Policy
> Development Process.
> 
> You are therefore requested to share your feedback on this proposal with
> the Anti-Abuse mailing list.
> 
> The goal of this proposal is to define that BGP hijacking is not
> accepted as normal practice within the RIPE NCC service region.
> 
> You can find the full proposal at:
> https://www.ripe.net/participate/policies/proposals/2019-03
> 
> We encourage you to review this proposal and send your comments to
> <anti-abuse-wg at ripe.net> before 17 April 2019.
> 
> Kind regards,
> 
> Marco Schmidt
> Policy Officer
> RIPE NCC
> 
> 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: </ripe/mail/archives/anti-abuse-wg/attachments/20190319/0c1b688d/attachment.sig>