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/ipv6-wg@ripe.net/
[ipv6-wg] comments on Y.Pv6RefModel
- Previous message (by thread): [ipv6-wg] itu document on ipv6 addressing for iot
- Next message (by thread): [ipv6-wg] comments on Y.Pv6RefModel
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Fri May 25 11:07:13 CEST 2018
I lurk on this list. However I have to say something about this document, mostly because of what’s happening at ITU SG20. It’s taken a lot of work by Marco and others to persuade SG20 to engage with RIPE. And it’s important that we respond clearly. I just have three things to say. 1) The document is very poor. [I’m being uncharacteristically diplomatic.] It contains lots of errors. The proposed addressing plans are just wrong. It would be a *huge* mistake for anyone to adopt these and much, much worse if SG20 recommends them for global adoption. SG20 should abandon this fundamentally flawed document. Work on it simply has to stop. 2) IP addressing plans for IoT devices can’t and shouldn’t be discussed in isolation. They have to be developed in the context/circumstances of the networks where these devices will be used: ie alongside everything else that’s using or will be using the Internet. If members of SG20 have ideas on IP addressing plans, they are more than welcome to come to the RIR fora where their suggestions can be discussed/analysed and possibly incorporated into RIR address policy. That work can’t and shouldn’t take place at SG20. Or elsewhere in the ITU. 3) It’s unacceptable for the ITU to even attempt to get involved in IP addressing. It’s out of scope. They should stick to co-ordination of E.164 numbers and X.25 addresses. IP addressing is primarily a matter for the RIRs. And other Internet-related fora like RIPE, NANOG, IETF, etc. There’s no role for the ITU in this at all.
- Previous message (by thread): [ipv6-wg] itu document on ipv6 addressing for iot
- Next message (by thread): [ipv6-wg] comments on Y.Pv6RefModel
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]