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
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Silvia Hagen
silvia.hagen at sunny.ch
Sun May 27 16:19:56 CEST 2018
Fully agree with Sander and others I was shocked when I saw this document.... Cheers Silvia -----Ursprüngliche Nachricht----- Von: ipv6-wg [mailto:ipv6-wg-bounces at ripe.net] Im Auftrag von Sander Steffann Gesendet: Sonntag, 27. Mai 2018 14:56 An: Jim Reid Cc: ipv6-wg at ripe.net; JORDI PALET MARTINEZ Betreff: Re: [ipv6-wg] Y.IPv6RefModel is out of scope for the ITU Hi, >> 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. > > Indeed. This is the biggest issue BY FAR with Y.IPv6RefModel. Or should be, > > It would be a serious problem if this key concern got overlooked by the WG in its efforts to point out the many errors and defects in that document. +1 We should help the ITU, where the help in this case comes down to: make them acknowledge that this work is already handled by existing organisations and groups, that the ITU does not have the experience and knowledge to improve on that, and that they should follow the lead of the established authorities in this area (= IP networking) instead of making things worse by inventing "standards" that have no relation to reality. Cheers, Sander
- Previous message (by thread): [ipv6-wg] Y.IPv6RefModel is out of scope for the ITU
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]