Hi Kai, > So, since anything _above_ /64 (e. g. /65 to /128) would be whitewashed by > the proposal, using a whole /48 PA or PI for /64s for WiFis would be ok, as > long as each WiFi user only gets less than a /64 »assigned«?
That's what the proposal currently says. > Proposal states: »Today, organisation networks usually include some kind of > guest networks, (public) WIFI hotspots in their offices, PTP-VPN links to > customers’ sites, or anything similar where devices of non-members of the > organisation would get assigned an IP out of the organisation’s prefix.« > > These days I configure P2P links as /64 (with ::1 and ::2 being the > endpoints), because ... people actually tried to hit me with cluebats when I > carried over IPv4-behaviour of /32 or /31 links into IPv6 (/127). Actually, using a /127 for point to point links is pretty common. There is even an RFC about it (https://tools.ietf.org/html/rfc6164). I use it a lot, also I the training courses I give. I reserve the whole /64 in the numbering plan just in case, but on the link I usually configure ::a/127 and ::b/127. > So, even after this proposal, I am not allowed to use my IPv6 PA or PI space > to build P2P-links outside my organisation, e. g. for peering, with a netmask > of /64? But at least anything above /64 (read: /127) in PI would be ok, which > currently isn't, neither for PA nor PI? Technically, yes. I still have to re-read the PA bit, because I'm not sure about that. I'll reply to that later. Cheers, Sander
