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]/
[ipv6-wg] Y.IPv6RefModel is out of scope for the ITU
- Previous message (by thread): [ipv6-wg] comments on Y.Pv6RefModel
- Next message (by thread): [ipv6-wg] Y.IPv6RefModel is out of scope for the ITU
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at foobar.org
Sat May 26 13:51:26 CEST 2018
JORDI PALET MARTINEZ via ipv6-wg wrote on 26/05/2018 12:16: > I already said this before, but "... in running such networks vis > [via] the RIR policy making fora." is wrong. Stepping back a bit, what we're discussing here is not whether address assignment / allocation models should be dealt with by the RIRs or the IETF, but whether they are in scope for the ITU. The answer to this is that all aspects of IP number resource management are resoundingly out of scope for the ITU. This includes all IP number resource assignment and allocation issues, all addressing models, and by direct implication, the SG20 work on the Y.IPv6RefModel work item. There needs to be a crystal clear statement from the RIR community that this entire exercise is wildly out of scope for the ITU, that SG20 needs to cease and desist from reaching into areas outside their competence, and that the Y.IPv6RefModel work item needs to end, immediately and permanently. Nick
- Previous message (by thread): [ipv6-wg] comments on Y.Pv6RefModel
- Next message (by thread): [ipv6-wg] Y.IPv6RefModel is out of scope for the ITU
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]