Re: [v6ops] New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt - Privacy Properties

[Tim Chown <[e-mail]>]

> On 20 Jul 2017, at 18:25, Lorenzo Colitti <[e-mail]> wrote:
> 
> Tim, when you say /64 per office for your initial campus rollout, did you mean /64 per host?

No, this was back in around 2003/4-ish during a project called 6NET, when we had edge devices that would have been capable of being configured to route a /64 per office, and had good v6 support. There were various reasons discussed around isolation, accountability, etc.  Much of the same rationale of the prefix-per-host draft.  

And that was still early wireless days, and certainly pre-802.1x being anywhere near mainstream (we started work on eduroam a year or two before, but there were only very early open source supplicants and some not-cheap 3rd party ones.  So different now :).

Tim

> On Thu, Jul 20, 2017 at 7:21 PM, Tim Chown <[e-mail]> wrote:
> > On 20 Jul 2017, at 18:07, Lorenzo Colitti <[e-mail]> wrote:
> >
> > On Thu, Jul 20, 2017 at 6:52 PM, Tim Chown <[e-mail]> wrote:
> > > There are lots of different types of campus, and campus type networks.
> >
> > Well, the discussion was around best practice discussion, and in that light eduroam should be aspirational. It’s deployed in 70-80 countries, but the underlying 802.1x can be used in any campus, and on wired links as well.
> >
> > Which is, of course, technically a much better solution than relying on insecure DHCPv6.
> >
> > Additionally, there's the option of doing /64 per host (via RAs) in the enterprise. Same tracking and authorization properties, but no limitation on the number of addresses that can be used.
> 
> Yep, and I mention that when speaking to university admins, ad they like and understand the idea.  Though I have a feeling they may soon realise they’ll want more than a /48 to serve their campuses… and that’s an issue for campuses that want to follow 7934 and JJB’s draft.  We have three UK universities that have now gone for LIR status to obtain their own /32.
> 
> As an aside, we almost went with /64 per office in our initial campus rollout; the issue then was the extra cost of the routing image on $vendor’s hardware.
> 
> Tim
>