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/[email protected]/
[policy-announce] 2019-01 Proposal Accepted and Implemented (Clarification of Definition for "ASSIGNED PA")
- Previous message (by thread): [policy-announce] 2019-04 New Policy Proposal (Validation of "abuse-mailbox")
- Next message (by thread): [policy-announce] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Mon May 20 11:05:53 CEST 2019
Dear colleagues, Consensus has been reached on 2019-01, "Clarification of Definition for "ASSIGNED PA"". This proposal made it clear in the IPv4 Policy that the status "ASSIGNED PA" can also be used for assignments to an LIR's infrastructure. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-01 The new RIPE Document is called ripe-720 and is available at: https://www.ripe.net/publications/docs/ripe-720 This proposal is implemented with immediate effect. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Officer RIPE NCC
- Previous message (by thread): [policy-announce] 2019-04 New Policy Proposal (Validation of "abuse-mailbox")
- Next message (by thread): [policy-announce] 2018-06 Discussion Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]