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] Y.IPv6RefModel is out of scope for the ITU
- Next message (by thread): [ipv6-wg] Y.IPv6RefModel is out of scope for the ITU
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Sun May 27 14:01:23 CEST 2018
On 26 May 2018, at 12:51, Nick Hilliard <nick at foobar.org> wrote: > > 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. ABSOLUTELY! Well said Nick. IMO this point is far more important than commenting on the contents of Y.IPv6RefModel. I hope the WG realises that. At this point however, that crystal clear statement should come from the WG because they’re the ones that SG20 has asked to comment on the document. If the RIR community wants to say something similar, they would probably use a different path: presumably a Liaison Statement from the NRO to ITU-T. As would ISOC, IETF/IAB, etc if they decided to comment on ITU mission creep into matters that are out of scope.
- Previous message (by thread): [ipv6-wg] Y.IPv6RefModel is out of scope for the ITU
- 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 ]