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] Policy building - call for volunteers
- Previous message (by thread): [address-policy-wg] Policy building - call for volunteers
- Next message (by thread): [address-policy-wg] Policy building - call for volunteers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Martin Stanislav
ms at uakom.sk
Tue Mar 29 11:50:50 CEST 2022
Hi James, On Tue, Mar 29, 2022 at 08:59:44AM +0200, James Kennedy wrote: > > 2.1. The task force recommends that as resource holders have full > responsibility over the registration of their IPv4 PA assignment(s), > they are free to make assignments or not. If the community accepts > this recommendation, the relevant RIPE Policies should be updated > accordingly, and documenting IPv4 PA assignment(s) will stop being a > policy requirement. Is this line of thought that a responsibility over the registration of an aggregate IP resource implies optional documenting of a resouce subset explained somewhere? Was utilization of an aggregate resource the only reason to document details? Thank you for comments or pointers. Martin
- Previous message (by thread): [address-policy-wg] Policy building - call for volunteers
- Next message (by thread): [address-policy-wg] Policy building - call for volunteers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]