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:12:23 CEST 2018
On 26 May 2018, at 12:51, Nick Hilliard <nick at foobar.org> wrote: > > 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. Jordi, it’s not wrong. But no matter. We can agree to disagree about that. Your comment here is unhelpful. Please focus on the actual document rather than rat-holing and shed painting about what others have said about it. Says he hypocritically for commenting on your comments about my comments. :-) > 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.
- 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 ]