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] 2016-04 To Last Call (IPv6 Sub-assignment Clarification)
- Previous message (by thread): [address-policy-wg] 2016-04 To Last Call (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 To Last Call (IPv6 Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JORDI PALET MARTINEZ
jordi.palet at consulintel.es
Mon Jan 15 14:31:39 CET 2018
The point is not only the PDP, as I believe we are still on time to correct the policy proposal, which I think is broken and contradicting itself. See my last email on the details, and a proposed text to resolve it, which according to the PDP, we can still apply I think, without the need to wait for the concluding phase and then the appeal. Regards, Jordi -----Mensaje original----- De: address-policy-wg <address-policy-wg-bounces at ripe.net> en nombre de Jim Reid <jim at rfc1035.com> Fecha: lunes, 15 de enero de 2018, 14:24 Para: JORDI PALET MARTINEZ <jordi.palet at consulintel.es> CC: <address-policy-wg at ripe.net> Asunto: Re: [address-policy-wg] 2016-04 To Last Call (IPv6 Sub-assignment Clarification) > On 15 Jan 2018, at 12:49, JORDI PALET MARTINEZ via address-policy-wg <address-policy-wg at ripe.net> wrote: > > I think the PDP has not been followed correctly. In that case Jordi, you can use the PDP to raise those concerns. Though I think you're actually complaining about Gerd's consensus declaration on 2016-04 rather than whether the PDP has been followed or not. I quote from Section 3.2 of the PDP: Anyone who believes that the proposal has not been handled correctly or that the WG chair has made an incorrect determination of consensus should first raise the matter with the WG chair. If the dispute cannot be resolved with the WG chair, the Appeals Procedure can be invoked. And from Section 4: 4. Appeals Procedure If a grievance cannot be resolved with the chair of the WG the matter can be brought to the attention of the Working Group Chairs Collective (WGCC). Anyone may submit an appeal. This must be submitted to the relevant WG mailing list(s) and to the Policy Announce Mailing List (policy-announce at ripe.net). The appeal will also be published by the RIPE NCC at appropriate locations on the RIPE web site. Any appeal should include a detailed and specific description of the issues and clearly explain why the appeal was submitted. An appeal must be submitted no later than four weeks after the appealable action has occurred. AFAICT it's you who isn't following the PDP. :-) You don't seem to have discussed your objections to the consensus determination with the WG co-chairs or indicated that those discussions failed to resolve your complaint. No matter. If we've passed that point, you can still appeal to the WGCC. But that requires a detailed and specific description of the issues and an explanation of why the appeal was necessary. That hasn't happened. At least not yet. ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
- Previous message (by thread): [address-policy-wg] 2016-04 To Last Call (IPv6 Sub-assignment Clarification)
- Next message (by thread): [address-policy-wg] 2016-04 To Last Call (IPv6 Sub-assignment Clarification)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]