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]/
[address-policy-wg] 2018-02 New Policy Proposal (Assignment Clarification in IPv6 Policy)
- Previous message (by thread): [address-policy-wg] Proposal Implemented: 2016-04, "IPv6 Sub-assignment Clarification"
- Next message (by thread): [address-policy-wg] 2018-02 New Policy Proposal (Assignment Clarification in IPv6 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Schmidt
mschmidt at ripe.net
Tue Apr 17 15:55:11 CEST 2018
Dear colleagues, A new RIPE Policy proposal, 2018-02, "Assignment Clarification in IPv6 Policy" is now available for discussion. This proposal aims to clarify the definition of “Assign” in ripe-699 (section 2.6). The non-permanent provision of up to a /64 prefix to third parties shall not be considered a sub-assignment. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-02 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to <address-policy-wg at ripe.net> before 15 May 2018. Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [address-policy-wg] Proposal Implemented: 2016-04, "IPv6 Sub-assignment Clarification"
- Next message (by thread): [address-policy-wg] 2018-02 New Policy Proposal (Assignment Clarification in IPv6 Policy)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]