Five Policy Proposals to Improve RIPE Documents
Dear colleagues, Later today, we will publish five policy proposals on the Address Policy Working Group Mailing List. We wanted to let you know in advance what these are about. In the Address Policy WG sessions at RIPE 67 and RIPE 68, it was discussed that the language in several RIPE Documents should be improved by changing instances of “should” to “must” where this was creating unwanted ambiguity. You can find more information here: https://ripe68.ripe.net/presentations/288-APWG-co-presentation-should.pdf After receiving guidance from the RIPE community, RIPE NCC has decided to start the process to clarify the language in these RIPE Documents by submitting these proposals into the PDP. For clarity, and as instructed by the community, there will be one proposal per RIPE Document. If you wish to provide your feedback to a specific proposed change, please make sure that you reply to the appropriate announcement and thread. Kind regards Marco Schmidt Policy Development Officer RIPE NCC
On 23/10/2014 12:12, Marco Schmidt wrote:
Later today, we will publish five policy proposals on the Address Policy Working Group Mailing List. We wanted to let you know in advance what these are about.
2014-07: support. 2014-08: support. 2014-09: don't support. 2014-10: support. 2014-11: support. Nick
On Thu, Oct 23, 2014 at 08:15:27PM +0100, Nick Hilliard wrote:
On 23/10/2014 12:12, Marco Schmidt wrote:
Later today, we will publish five policy proposals on the Address Policy Working Group Mailing List. We wanted to let you know in advance what these are about.
2014-09: don't support.
Why? Kind regards, Job
participants (3)
-
Job Snijders
-
Marco Schmidt
-
Nick Hilliard