Getting your routers future-proof?
Stucchi, Massimiliano
This talk is about the Home Networking Control Protocol (RFC7788) and how these specifications can be used to create a future-proof, IPv6 compliant SOHO router. Almost two years ago, RFC7788 introduced the Home Networking Control Protocol - also called homenet - which "enables discovery of network borders, automated configuration of addresses, name resolution, service discovery, and the use of any routing protocol that supports routing based on both the source and destination address." Many routers in SOHO environments nowadays run different forms of BSDs, prominently being OpenBSD and FreeBSD under the hood of a PFSense install. Homenet's focus is specifically on IPv6-enabled networks, although support for IPv4 is also included. Homenet introduces many new functionalities in a home network, and makes it easy for devices to interconnect, making it a better platform to support the IoT now and in the future. In this talk, I will discuss all the services and protocols involved in the homenet specifications and documents, and will outline how these can be integrated into the BSDs by showing configurations for OpenBSD and FreeBSD.
 Hello, everyone. And I'm Max. Well, my name is actually Longer, but you prefer, you want to prefer Max. We recently had a new colleague at the Reipens CC from China. He said, well, he sent an email. Hi, I'm Max. I'm his name. I don't remember. You can call me Max and I reply, no. That's me. Who am I? I work at the Reipens CC. We are the registry for. You spent your time at Reipens CC. I spent my time at the Reipens CC. OK. Handing is correcting me. Yeah. So no, no, no, no, no. And I like to say the goal of my job is to not have a job anymore because I am the IPv6 program manager. I do training, so I train people. I also have a voice award in what the Reipens CC does about IPv6. So what is this about? Making your routers future proof. Why? Because things are changing. Recently, we came across an important date. Six years ago, there was World IPv6 launch day, which means that actually Wednesday, last Wednesday, was six years after the 6th of June, 2012. What does this mean? This means that something has happened. And when I say my goal is to not have a job anymore, it means that I want to see this going better and better. We have. We are in a moment where, well, I've been saying this for years, and people start, well, people tend to not believe me anymore. But IPv6 is happening. 50% in India and Belgium, but they have different markets. You know what's the difference between the two? Why they do more than 50%? There's a big, huge difference between the two countries. What's the cellular geo? Yeah, reliance, GAO. GAO. In India, India is mobile, while Belgium is fixed. The difference in Belgium, Belgium is divided into two parts, and the two, yes. It's more complicated than that. But let's keep it simple. It's not being informed from the framework, but it's more complicated than that. You know what I mean. Those are more complicated. Don't. Let's keep it simple. So let's say there was a sort of an internal competition between ISPs to say who would do it first. And that led to India and Belgium being more than 50%. Then we. I just thought the one side wanted to make sure they cannot communicate with the other side. Could also have been. One is before, one is for six. Yeah? Only. Yes. Could be. I think that's right. Could also be that, yes. Making sure, oh, let's use this new protocol so the others don't know it. But then also the US, around 40%. And you might think, well, I'm from the US. I live there, but I don't see much happening on my landline. And that's also because mobile. Yes, mobile phones in the US are leading a lot. Many other countries are around 30%, because maybe one of the big ISPs there moved over. The others are still waiting. But what I like to say is that things are happening. But we also have a changing world. We have more than half of the population on the internet. And if I look at you, you have more than one device that connects to the internet, which means that we need so many IP addresses that we can't live with IPv4 for much longer. We tried to stretch the lifetime of IPv4 so much, blah, blah, blah. And then there's this buzzword that I generally don't like to use, but it's true that the internet of things is also going to change how we do things on the internet. There are cases where also where I come from, I come from Milan, from Italy, and I was so happy to see that they're doing something smart, like putting sensors on the trash bins to see where, to have an idea of how full the trash bin is, and then give a different route to the trucks, so the trucks would spend 50% less fuel on overage. So this means that the internet will be different in five or 10 years. And if you think about how it was five or 10 years ago, it was also way, way, way different, which might lead to something similar to what we have. I told you I do training. We have an exercise in our basic IPv6 training course that's called Future Casa, the house of the future, where you have smart things inside your house. And again, I don't really like the idea of having smart things in the house that much, but people seem to. And this is one of the situations you might end up into. Imagine you have an ISP, you have your V6 internet, you're connected to an ISP, whatever, you get a big chunk of IP addresses, and then inside your house, all the functionalities are split in between different networks. So everything is layer three. So this is what we want to go towards. Does anyone agree? Agree? No. No. Sorry? This is what we want, or this is what's going to happen? OK, why would you not want something like that? Of course V6 is shit. OK, let's not get into that. I know you, and I know you like to sit here in the front. But yes? I think for the first time, it's much bigger than the internet world. It's one perfect for the entire thread network. The routing has done differently. It's been about a few minutes. But I don't know, I don't think it's a point that you want to split the network and get to the last support. OK, why? One thing is, I don't know, I think mobility, if you move from one to the other. OK, yeah, but these are not things that are going to move between houses unless you sell them. No, not these things. But there may be other moving devices who want to be part of the network, and may run 15.4. OK. But imagine you have different devices in your house, and you want to separate them. So that you could. I have a point there. There's a time which is right now catering to the devices. It's not led into different stuff. It's a flash, flash, etc. OK. So I don't know what we gain by doing this. Well, one of the reasons for doing this can be security, because you can isolate every single device into its own network, and then make sure that security is tied for every one of those. That can be one. I think just having those things go up actually becomes a potential security problem. Yes, I said initially that I don't like the idea that much, but this is what we're going to get. Because we already have smart thermostats. And if you check those, you have cases where the thermostats lost connectivity to the internet, and the houses went up to 45 degrees, because they were still thinking, oh, I have to heat up the house. This is not what you're going to get. They will not be on separate networks. It'll be all the same. Yeah, well, that's what I'm going to show in a moment. So ISPs should assign you between a slash 56 and a slash 48. So enough networks to separate, to then branch your network into something more. And you need to have a slash 64 for each subnet. It's not mandatory, not really a hard line. Many people don't agree on this, and there are long discussions, especially at the ITF, about how right it is to have something like this. For the moment, that's what we have. And if you want to allow Slack to work, stateless auto configuration, that's what you want to have. Consider that in this case, you have a slash 64. It's big enough that you don't have to worry about the hosts in there. But then comes HomeNet. So one day, 2014, earlier than that, 2013, they chartered a working group at the ITF. And the idea was to define some rules for how Home networks should be and what services you should have in those Home networks. So they came up with a series of protocols and functions to be used for Home networks to fully enable IPv6 and maybe provide IPv4. I've added that maybe. That's because IPv4, in this case, becomes a second class citizen. So everything is focused on IPv6, and then IPv4 comes second. So how is this? What do we get with HomeNet? Zero configuration networks. And we'll see that in a moment. You're supposed to have multiple subnets. In that case, you have, let's say, how many of you know what unique local IPv6 addresses are. So very few people. Basically, it's the corresponding. I haven't said this, but it's the same as private addresses in IPv4, although they have a totally different use case. Those are supposed to be used for internal communication in networks that are not supposed to be connected to the internet. So you're not going to route unique local addresses. They are fc-sev. fc-00-sev. You want to have one of those also in your network, that network as a back end. In case you lose connectivity, you can still address hosts using private addressing. In that case, you can have multiple routers and multiple connectivity to different ISPs. Multiple upstreams with multiple prefixes coming into your network. And together with that, you get name resolution inside your small network, because it's important to be able to name routers when you connect them. Now, what does this translate into? Bubble, internal routing protocol, very simple, very chatty protocol, was the one that was decided to be the reference implementation for HomeNet. Then you get the HCPv6 client, server, prefix delegation client, and prefix delegation server. So that means that you act as a client, but inside your network, you're going to run prefix delegation as well. You're going to run a DHCPv6 server as well. You run DHCPv4, and then this is the heart of it, the distributed node consensus protocol, which is also called then HNCP, because HomeNetworkingControlProtocol is a profile of the NCP. Basically, what it does is manage who is responsible for services. If you have multiple routers all doing HomeNet, you have to elect the one that will do the DHCPv6 server. You have to elect the one that will do the name resolution. You have to elect the one that will do all the routing at one time. So this protocol is what you need to define who is going to do what. And then you have DNS. You need a multicast DNS proxy. You need a resolver, because you need to provide it. And then you have an authoritative server, because you have to provide your internal naming services. And then, important still, you have to provide Slack, stateless sort of configuration. Now, what are the biggest selling points then of HomeNet? Biggest selling point is that you don't have to configure anything. Imagine you have a device with 10 ethernet ports, and you have your ethernet port coming from your cable modem. You can connect it anywhere you want. You don't have to define a one interface, because discovery is done with basically DHCP sensing. If I can obtain something with DHCP, then good. That's my external interface. The others will be internal. I have internal naming for my devices. Everything is dual stack with NAT to DP4. Thanks to Babbel, I have loop avoidance. I can basically connect my routers even in a loop. I can daisy chain them. I can add multiple routers as I want, like range extenders. Think about that. And I can also connect them via Wi-Fi, for example. So I can have a router delegate a network to another via Wi-Fi, and that still would work. So this, yes? I have a situation where my edge router could be changing from time to time. Because I basically live in moving houses. And so I have my DHCP server on an internal machine for my internal network. So is my router now going to say, oh, there's my external network because it's serving DHCP? No. No, there's a specific case. If I connect the router internally, what I use is they use a keyword in the DHCP request that says home net. And if I'm a router that's internal to my network, and I see a request coming with the home net keyword in there, I just discard it. So I won't be seen in there. Yeah, there is a mechanism for avoiding that. Yeah. And that works for both v4 and v6 in prefix delegation. But thanks for the question. Now, I have different interface categories. And this is important because I can define them manually, or I can let them auto-discovery. I have the internal interfaces, which are the ones that interchange the NCP information. I have the external ones that are the ones where I can get DHCP v6 prefix delegation. I have the leaf interface just for clients. And then I have the guest for untrusted clients. With basically what I haven't discussed yet is also the fact that in home net, you have predefined security sets, security policies. So whenever you define interfaces as internal, external, leaf, or a guest, then they get different profiles for security also. Now, what does this translate into? I used to, at the training courses, I do it manually on a flip chart. But here, I decided to spend some time and show you how this could work. And this is a setup that I had at home at a certain point when we were testing some of the functionalities. So I have my main router. Imagine I have a house and I have my router. I connect to an ISP. And I get a slash 48, because I'm lucky. But you can also do it with a hurricane electric if you want to try this. Now, this is my main router. My main router will have a certain number of ethernet interfaces. Voila. Each and every one of those will get a different slash 64, because that's the way it works. And that's the reason why I get so many networks. Then I can connect another router. And then there is a mechanism in HomeNet which defines the delegation that should happen here. Delegation should be, at least, well, when I try it first time, I walk eight bits. I walk two nibble boundaries to get to a slash 56 from a slash 48. And then my local router there will also have different interfaces with different slash 64s, because it has enough networks to do that. Now I can connect a third router. I can use another slash 64. And my router here will get a slash 60, because I try to walk eight bits from slash 56. But I end up with the only ability to hand out one slash 64, which wouldn't be enough for this router to work, because I need also this router needs to have one slash 64 per interface. But I walk four bits back and I get a slash 60. And then I can also have another router connected to the main one, gets another slash 56. And then I can also create a loop using wireless if I want. So this is one of the cases where in my house I could create redundancy. And this is all managed by my bubble profile inside my network. So it avoids the loops. It makes sure that routing happens using the best path, in this case. Anything to add, Henning? You're falling asleep, so it looks horrible going. So a router has. The IPv6 prefix or prefixes, because going back one step. Oh, now I ended up in here. Sorry. I could actually connect a second router to the internet using a different ISP. And then the same scheme of propagation would happen in there. And I would have my hosts, but also my various routers, with multiple subnets. And I know this can sound confusing. But if I have my host, my laptop, with multiple IPv6 subnets, then I can change. I can have one of the ISPs just go away. My main router will die. One of the two routers will die. Two external routers will die. And I will just stop receiving router advertisements for that network. Or I will get a router advertisement with a lifetime of zero telling me to delete all those addresses from my host. And I will just move gracefully to the second connectivity. There's also a specific draft. Well, it's becoming an RFC that explains how that works. It will be an RFC pretty soon. So I have auto-signed unique local IPv6. And I have an IPv4 network out of 10 slash 8, and that is applied at the border. So every router in my architecture will decide to get 1 slash 24 out of 10 slash 8. And it will be a random one. It will auto-assign an address in there. And in the OpenWRT implementation, I can decide it to be any address in the slash 24 or just be the first one. Yes? Do you mind the ULA prefix to be the same for the ULA network? Just one big prefix. I have one prefix for the entire network. But then all my local routers will get 1 slash 24 out of 10 slash 8 in IPv4. For ULA, I have one unique prefix. I don't have different separates. No, that wouldn't make sense. Yes. So what do we have in terms of implementation? The only full implementation on OpenWRT. Not in base, but you have to install a separate package. There's no other known full implementation and not even in commercial CPEs right now. Not that we have found. And there is Spark software. So there is someone who brought the proof of concept when developing the home net draft. And then it just lies abandoned. Or there is a very small subset of home net working somewhere, but with no real implementation. The only one fully working, OpenWRT. And that's the one I, for example, use at home. That's the one that's the reference implementation at the moment. So yes? How much of the interminational dependence on the ISP to Blue-Wade UI devices? You can run home net also only on IPv4, but that means that you would have unique local everywhere for IPv6. And that would sometimes, some operating systems might be slowed down by the fact that you have unique local. So because they will attempt to use that to talk to the. Does it provide the native storage in a store? Does that provide, sorry? Does it also provide DNF6 for native storage in a gateway? No, it's not meant to be there. No, it's not in the specifics. You can add it. You can add NAT64 or 464XLAT if you want. Actually, I ran with that for about a month at home, because when there was an issue with managing IPv4 in the translation, and I couldn't use it. So yeah. I ran with home net and NAT64 on the edge. Yes. So I was looking at this, and in December, when I became the IPv6 program manager, I decided to, OK, let's look at this and see if there's anything that could be done. So I was thinking, OK, PSD routers are widespread, especially in SOHO environments. And why can't we leverage this? But I underestimated the effort, and I didn't consider the fact that there were many other projects that I would have gotten involved with. So I ended up looking at getting a plan, which I didn't end up having fully implemented by now. So what do you have? You have freeBSD and openBSD. And I didn't include, well, PFSense here, because then it comes after you've finished with freeBSD there. So you have bubble. BubbleD is in ports. Fine. You have wide DHCP for DHCP v6, and that's in ports for both of them. That's good. You have a Slack daemon. That's included in base. Simple. But we're missing something, and that's basically HNCP. HNCP exists in different implementations. There's SHNCP. That's a very simple one. There's one in Python. There's also, but those are very, very limited. And then there's one. That's the reference implementation, the one for OpenWRT, which has some issues. And I'll tell them in the next slide. But, well, DNS servers and proxy, you can get everything. So you have the different pieces, and then you have to find a way to tie them together. You're missing the one that decides who's going to do what. And then based on this, everything else should be kind of orchestrated. Because the way it works is that it runs as an orchestrator, which tells you should do this, you should do that, based on the priority, based on your capacity. You should do use server, manage DNS. You do DHCP v6, and so on. So we're missing the glue. But I've started looking at it, and it's full of Linuxisms. So you have to basically deeply look at that and reverse engineer half of it, because it's very, very OpenWRT oriented. And it contains a lot of stuff that's done especially for it. So you have to actually modify big parts, big chance of that. So here, my idea is to tell you, there is this. This is a great opportunity to bring IPv6 to the masses, to a lot of people, because it will enable all the IoT, all the new functionalities that we're going to have. And basically, this is it. And I'm open for questions. You've already asked them during the, yeah. Why didn't you call? Sorry? Why didn't you call? Call. If you wanted home.net to be upset, why didn't you call? Pick up the phone or the email and say, hey. Because I started working on it, and I ended up not having enough time to finish that. But yeah, we can talk. I'm saying we're interested. Yeah, OK, good. I certainly know what this is. Sorry? I certainly know what home.net is. OK. Yeah. Please. So I mentioned about the mobility. But you can't say it's not the mobility. It's one of the outdoor dials. And then it's the, you know, it's half to the next to a different router. Yeah. It's not responding anymore. Changing the perfects. Yeah. You're not changing it. If you want a different router, then you keep your previous prefects. No, you don't keep your previous prefix. But if you have two board of routers, they will both announce the router advertisements in the network, so you end up with two different prefixes coming from two different sources. And you install both of them. So you have both of them on your network card at the same time, and then you choose which one to use, too. So if you go to your previous slide, where we are just having slash extroperfections to the leaf roots, you mean this one? You really want me to go through all the? So here we are actually manufacturing slash 64 here. Oh, not manufacturing. Well, you branched them out of what you're. Yeah? So it's from the top program you have to see. You had a band connected to be on the lower left row also. And if you were to move down there, the prefix will remain the same? You mean if you move a host from one part to the other? No, you would have to change it. But as soon, well, if the host does a handover from, say, this to this one, then when it moves, it will send a router solicitation, and it will get a new router advertisement with the new prefix, and will just install the new one. And forget about the old one. Another question was, a lot of home-rock solutions are building up high-eulivity based on layer 2, in which case it's almost like a big, sublime concept. So do we really have to worry about, where do you see the component going forward? Could the high-eulivity coming from these extenders, which are doing it to layer 2 and giving you one domain to work with? What's it doing? I think it will. That's a nice question. Because having layer 2 helps in simplicity in the end. Because you have one prefix for the whole house, and that's it. And you? I think the euro is also working towards that. Yes, yes. But euro has different applicabilities, as far as I remember. And in this case, you want to be segmented, because you have to locally control everything and make sure it gets routed the way you want, the way the local router wants. Any other question? Yeah? Yeah. Today. Mm-hmm. How about I get you benefit out of it? Immediately? You know, house mixed with VST, macro-ass, micro-ass. Yeah. What would be my immediate benefit? Well, the immediate would be, you don't have to configure much. You don't have to do much. Imagine the case where you have a grandmother with a router, and then you can tell her to plug the cable wherever she wants, and that would make it easy. Imagine a house where you have a border router, and then you can connect any kind of other routers wherever you want, and they will just work. Well, most of the time. Yes. But then you win with that. Rather than then having range extenders, like we were discussing, where if you just have to browse the internet, control a few things, having this helps in simplicity and making your house easier to manage in the end, the local network easier to manage. Sorry, could you get benefit out of it today? Yes. But also imagine, oh, sorry, the range extenders, you could do that. If there's a part you want to reach of your house with another router, you can actually multi-home a router with two other routers using Wi-Fi, and it would just work. So the advantages are quite a few. Yes. I know this was a short one, but there's not much else to say about it. Yeah? Would home that have any understanding of a network virtual full internet links? Yes. Yeah, yeah. You can just multi-home, and it's very simple. You don't do BGP, you don't do anything else you just have. You just will see the different prefixes installed on your different addresses from different prefixes installed on your cards. And then it's up to the host to decide which one to use. But there's also other work being done on multi-homing without BGP using router advertisements, and that's a different story. Yeah, Jim? The reality here is that most home networks are wireless. Maybe not for this audience. But most people don't have a lot of wire on the walls, and they take their smarts from a set home and just get it plugged into the HVMC, and it runs until 11 to two. So whatever. They just presumably come out. So there you have one, the Liar 2 domain. Yeah. How is this? Well, in this case, you would have like for, what is the question? Because you have one layer to domain, but you don't need much else. Right, but you don't segmentation at that point. No, you don't need it. You have one port. Yeah. What you do, plus port. Well, the thing is if you have like a 2.4G network and a 5G network, then they would be separated, basically. That would be the way home networks would do it, in that case. But other than that. You don't get segmentation, which is a big part of the security. Yeah, that's true. It's not as simple as your TV is. Yeah, that's true. That's true. But that's something probably that was a bit overlooked than defining home networks. Well, there's space for a new document. Here. There's a way to do it. You can actually segmentate. Sure, you can still do that, yeah? That's why I say there's space for a nice new document. Yeah? Yes? What exactly is the advantage of giving a lamp 18 quintillion IP addresses if you don't have the map? You don't have to map. Well, that's one of the advantages. But couldn't that be done with, say, only one quintillion? Yeah? Yes, you could. But the answer, the simple answer is if you don't give a lamp of slash 64, the lamp will not be able to get an address out of that. So unfortunately, there's a bunch of, yes, we can discuss in this. But the way things are is that if you don't give a slash 64 to a network where you want devices to connect automatically, then you will be breaking more than 30 RFCs. And, huh? So? Yeah. Burn here. Breaking RFCs is something you could only do if you know exactly what you're doing. Exactly. I don't need to leave the rules. You can run IPv6 networks with different sources. So now can we find out whether IPv6 is a good idea? We can. Well, with handing, there's no reason. But yes, sorry. Handing? Give me a second. But to, sorry, to extend one, you would say those of us who live in North America and our ISP will be able to give us a slash 64 to give us a six. There's no way to do state and solid configuration using young extenders. Yeah. So the way they do that is that they basically think the same way they think in IPv4. And they force you to do not six six in that case. What's the smallest allocation I can give the customer? Well, you can give them a slash 64. But the recommendation from communities a slash 56. I'm saying that from mentality. What's the smallest allocation I can give the person in the evening? Slash 56. That's the suggestion. That's the smallest suggestion you can get. If I have to work with, it doesn't really depend on the global products or anything. Sorry? For this, connect to work. We don't really depend on the global perfect delegation to the end devices. The phone itself can be IPv6 only based on the ULA. Yes. And it can have the band connectivity from the translation. Yeah. In fact, that's the point. When you lose connectivity, you will have ULA still working in there. And that's. So how do you know you're part of that network? You also have an IPv6 ULA perfect. And you can talk to these devices. Yeah. Yes, exactly. What I see though is most of the phone devices, other than probably the lock on the door, they have a fixed power source. And they can afford to have a Wi-Fi interface on it. Where it just becomes a normal user-end device connected to a Wi-Fi network with the extenders and things. You are fine. The only place where I see a sensor is the lock on the door where you cannot run wires and get them fired. And then to depend on a low power network. And that's where your band and other things come again. Yeah. It's like, I just see it in the plugs. I mean, there's different stats also coming out. What the end story would be. Yeah. Yes. Well, but we're talking about different things. I mean, if you talk about, I wouldn't put my door lock on low pan, because that means that my lock has a reachability of a few kilometers. And I. Yes. I mean, you are understanding if you would probably be very interested in something else. There have to be some other mechanism. Yeah. Yeah. So it's, yes. But that's what Jim was saying, that we should think about how to segment also the wireless part in this case. Because in the specifics, it only mentions the physical interfaces. And then you should be actually doing separation also on the wireless part. Because most of the things that we see now, most of the new sensors or the new devices that we see have an ESP, whatever that connects to the local wireless network. And then you have everything on one big segment, instead of having all separated. So yeah, we should also think about that. Do you agree, Jim? Yeah. I think there are largely ways to do it as well. Sorry? There are actually techniques to do it as well. Yeah. Yes. To go back to the slash 56, putting your right IPv6 at the C. Yes, OK. Although I'm not here officially for the right and C. When you talk to ISPs and they try and justify handing out 64s, what do you and your, I live in North America, so I feel the same problem. What do you all say? We have that in our region as well. Don't worry. But when you have these conversations with the ISP, what do you hear back from them? What is their rationale? Why are they doing this? Well, the reason mostly is that they, no. The reason is mostly thinking about a, and I can be form mindset. And thinking, oh, what's the smallest thing I can give them? Exactly. But then the counter argument is, look at how many you have. Like this small, if I remember correctly in the matter, the smallest allocation is a 36. And if you have a slash 36, we're talking about 2 million slash 56s. So no. It's a half a million, two to the 20, one million. One million. One million slash 56s. I mean, with the smallest allocation you can get, you can serve one million households. Where's the problem? I mean, if you have more than a million customers, or you plan on having more than a million customers, you can get worried. But we have a better argument in our region, because we hand out, the smallest one we hand out is a slash 32. So you have 16 million. And then without questions, you can get up to slash 29, which means 128 million. Why would you have to care about the single network you hand out to one of your customers when you can serve 128 millions? And we have entire countries with, say, 2 million people. And you're one of the ISPs there. And even if there are only two, then the two of you have a potential to serve 256 million households. Why would you have to be careful about what you use? What they're thinking is, yeah, nobody will need more than 640k. Nobody ever needs more than that. Yeah. Yeah. It's the same. You run with the same exact mentality. Isn't it? 24. 18 million addresses. Yeah? I don't know. May. That's exactly the same. Engineer. This is the truth, though, that when you allocate a slash, that's a 29, that you actually have another, that we can actually aggregate. You don't actually give spaces between. Yeah, that's what I. So in reality, then, that's not really fixed. And we do it out of, it's not written in stone. But whenever we, for example, you have a slash 29. And if you didn't get that way in the past, like more than 10 years ago, what we do nowadays, what we've been doing for almost 10 years, is sparse allocation. So basically, he got a slash 29, but we reserved three more bits. So if they ever come back and want to get more address space, we don't hand out a new subnet, but we just enlarge the one they have. So you left some continuous growth room. Yeah? Yeah. Yes. So but the same does adding, as far as I remember. I'm not 100% sure, but it's possible. Never estimate North America. No, no, no. Well, not saying anything. You're crazy. Not saying anything bad. Just saying we have different policies. I'll criticize North America. You don't have to. These room taxes, if you don't want to. Oh, OK, OK. It's a whole other country. It's a whole other country. We demand our slice of the IPv6 range as well. Yeah, no, that in theory you could. Actually, it's the last 29 we've covered. Yeah? OK, well, thank you very much. Thank you. Thank you.
 Hello, everyone.  And I'm Max.  Well, my name is actually Longer, but you prefer, you want to prefer Max.  We recently had a new colleague at the Reipens CC from China.  He said, well, he sent an email.  Hi, I'm Max.  I'm his name.  I don't remember.  You can call me Max and I reply, no.  That's me.  Who am I?  I work at the Reipens CC.  We are the registry for.  You spent your time at Reipens CC.  I spent my time at the Reipens CC.  OK.  Handing is correcting me.  Yeah.  So no, no, no, no, no.  And I like to say the goal of my job is to not have a job  anymore because I am the IPv6 program manager.  I do training, so I train people.  I also have a voice award in what the Reipens CC  does about IPv6.  So what is this about?  Making your routers future proof.  Why?  Because things are changing.  Recently, we came across an important date.  Six years ago, there was World IPv6 launch day, which  means that actually Wednesday, last Wednesday, was six  years after the 6th of June, 2012.  What does this mean?  This means that something has happened.  And when I say my goal is to not have a job anymore, it  means that I want to see this going better and better.  We have.  We are in a moment where, well, I've been saying this for  years, and people start, well, people tend to not believe  me anymore.  But IPv6 is happening.  50% in India and Belgium, but they have different markets.  You know what's the difference between the two?  Why they do more than 50%?  There's a big, huge difference between the two countries.  What's the cellular geo?  Yeah, reliance, GAO.  GAO.  In India, India is mobile, while Belgium is fixed.  The difference in Belgium, Belgium is divided into two  parts, and the two, yes.  It's more complicated than that.  But let's keep it simple.  It's not being informed from the framework, but it's more  complicated than that.  You know what I mean.  Those are more complicated.  Don't.  Let's keep it simple.  So let's say there was a sort of an internal competition  between ISPs to say who would do it first.  And that led to India and Belgium being more than 50%.  Then we.  I just thought the one side wanted to make sure they  cannot communicate with the other side.  Could also have been.  One is before, one is for six.  Yeah?  Only.  Yes.  Could be.  I think that's right.  Could also be that, yes.  Making sure, oh, let's use this new protocol so the others  don't know it.  But then also the US, around 40%.  And you might think, well, I'm from the US.  I live there, but I don't see much happening on my landline.  And that's also because mobile.  Yes, mobile phones in the US are leading a lot.  Many other countries are around 30%, because maybe one of  the big ISPs there moved over.  The others are still waiting.  But what I like to say is that things are happening.  But we also have a changing world.  We have more than half of the population on the internet.  And if I look at you, you have more than one device that  connects to the internet, which means that we need so many  IP addresses that we can't live with IPv4 for much longer.  We tried to stretch the lifetime of IPv4 so much, blah,  blah, blah.  And then there's this buzzword that I generally don't like  to use, but it's true that the internet of things is also  going to change how we do things on the internet.  There are cases where also where I come from, I come from  Milan, from Italy, and I was so happy to see that they're  doing something smart, like putting sensors on the  trash bins to see where, to have an idea of how full the  trash bin is, and then give a different route to the  trucks, so the trucks would spend 50% less fuel on  overage.  So this means that the internet will be different in five  or 10 years.  And if you think about how it was five or 10 years ago, it  was also way, way, way different, which might lead to  something similar to what we have.  I told you I do training.  We have an exercise in our basic IPv6 training course  that's called Future Casa, the house of the future, where  you have smart things inside your house.  And again, I don't really like the idea of having smart  things in the house that much, but people seem to.  And this is one of the situations you might end up  into.  Imagine you have an ISP, you have your V6 internet, you're  connected to an ISP, whatever, you get a big chunk of IP  addresses, and then inside your house, all the  functionalities are split in between different networks.  So everything is layer three.  So this is what we want to go towards.  Does anyone agree?  Agree?  No.  No.  Sorry?  This is what we want, or this is what's going to happen?  OK, why would you not want something like that?  Of course V6 is shit.  OK, let's not get into that.  I know you, and I know you like to sit here in the front.  But yes?  I think for the first time, it's much bigger than the  internet world.  It's one perfect for the entire thread network.  The routing has done differently.  It's been about a few minutes.  But I don't know, I don't think it's a point that you want  to split the network and get to the last support.  OK, why?  One thing is, I don't know, I think mobility, if you move  from one to the other.  OK, yeah, but these are not things that are going to move  between houses unless you sell them.  No, not these things.  But there may be other moving devices who want to be part  of the network, and may run 15.4.  OK.  But imagine you have different devices in your house, and  you want to separate them.  So that you could.  I have a point there.  There's a time which is right now catering to the devices.  It's not led into different stuff.  It's a flash, flash, etc.  OK.  So I don't know what we gain by doing this.  Well, one of the reasons for doing this can be security,  because you can isolate every single device into its own  network, and then make sure that security is tied for  every one of those.  That can be one.  I think just having those things go up actually becomes a  potential security problem.  Yes, I said initially that I don't like the idea that much,  but this is what we're going to get.  Because we already have smart thermostats.  And if you check those, you have cases where the  thermostats lost connectivity to the internet, and the  houses went up to 45 degrees, because they were still  thinking, oh, I have to heat up the house.  This is not what you're going to get.  They will not be on separate networks.  It'll be all the same.  Yeah, well, that's what I'm going to show in a moment.  So ISPs should assign you between a slash 56 and a  slash 48.  So enough networks to separate, to then branch your  network into something more.  And you need to have a slash 64 for each subnet.  It's not mandatory, not really a hard line.  Many people don't agree on this, and there are long  discussions, especially at the ITF, about how right it is to  have something like this.  For the moment, that's what we have.  And if you want to allow Slack to work, stateless auto  configuration, that's what you want to have.  Consider that in this case, you have a slash 64.  It's big enough that you don't have to worry about the  hosts in there.  But then comes HomeNet.  So one day, 2014, earlier than that, 2013, they  chartered a working group at the ITF.  And the idea was to define some rules for how Home  networks should be and what services you should have in  those Home networks.  So they came up with a series of protocols and functions to  be used for Home networks to fully enable IPv6 and maybe  provide IPv4.  I've added that maybe.  That's because IPv4, in this case, becomes a second class  citizen.  So everything is focused on IPv6, and then IPv4 comes  second.  So how is this?  What do we get with HomeNet?  Zero configuration networks.  And we'll see that in a moment.  You're supposed to have multiple subnets.  In that case, you have, let's say, how many of you know  what unique local IPv6 addresses are.  So very few people.  Basically, it's the corresponding.  I haven't said this, but it's the same as private addresses  in IPv4, although they have a totally different use case.  Those are supposed to be used for internal communication in  networks that are not supposed to be connected to the  internet.  So you're not going to route unique local addresses.  They are fc-sev.  fc-00-sev.  You want to have one of those also in your network, that  network as a back end.  In case you lose connectivity, you can still address hosts  using private addressing.  In that case, you can have multiple routers and multiple  connectivity to different ISPs.  Multiple upstreams with multiple prefixes coming into  your network.  And together with that, you get name resolution inside  your small network, because it's important to be able to  name routers when you connect them.  Now, what does this translate into?  Bubble, internal routing protocol, very simple, very  chatty protocol, was the one that was decided to be the  reference implementation for HomeNet.  Then you get the HCPv6 client, server, prefix  delegation client, and prefix delegation server.  So that means that you act as a client, but inside your  network, you're going to run prefix delegation as well.  You're going to run a DHCPv6 server as well.  You run DHCPv4, and then this is the heart of it, the  distributed node consensus protocol, which is also called  then HNCP, because HomeNetworkingControlProtocol is  a profile of the NCP.  Basically, what it does is manage who is responsible for  services.  If you have multiple routers all doing HomeNet, you have to  elect the one that will do the DHCPv6 server.  You have to elect the one that will do the name resolution.  You have to elect the one that will do all the routing at  one time.  So this protocol is what you need to define who is going  to do what.  And then you have DNS.  You need a multicast DNS proxy.  You need a resolver, because you need to provide it.  And then you have an authoritative server, because  you have to provide your internal naming services.  And then, important still, you have to provide Slack,  stateless sort of configuration.  Now, what are the biggest selling points then of  HomeNet?  Biggest selling point is that you don't have to  configure anything.  Imagine you have a device with 10 ethernet ports, and you  have your ethernet port coming from your cable modem.  You can connect it anywhere you want.  You don't have to define a one interface, because  discovery is done with basically DHCP sensing.  If I can obtain something with DHCP, then good.  That's my external interface.  The others will be internal.  I have internal naming for my devices.  Everything is dual stack with NAT to DP4.  Thanks to Babbel, I have loop avoidance.  I can basically connect my routers even in a loop.  I can daisy chain them.  I can add multiple routers as I want, like range extenders.  Think about that.  And I can also connect them via Wi-Fi, for example.  So I can have a router delegate a network to another via Wi-Fi,  and that still would work.  So this, yes?  I have a situation where my edge router could be changing  from time to time.  Because I basically live in moving houses.  And so I have my DHCP server on an internal machine  for my internal network.  So is my router now going to say, oh,  there's my external network because it's serving DHCP?  No.  No, there's a specific case.  If I connect the router internally, what I use is  they use a keyword in the DHCP request that says home net.  And if I'm a router that's internal to my network,  and I see a request coming with the home net keyword in there,  I just discard it.  So I won't be seen in there.  Yeah, there is a mechanism for avoiding that.  Yeah.  And that works for both v4 and v6 in prefix delegation.  But thanks for the question.  Now, I have different interface categories.  And this is important because I can define them manually,  or I can let them auto-discovery.  I have the internal interfaces, which  are the ones that interchange the NCP information.  I have the external ones that are the ones  where I can get DHCP v6 prefix delegation.  I have the leaf interface just for clients.  And then I have the guest for untrusted clients.  With basically what I haven't discussed yet  is also the fact that in home net,  you have predefined security sets, security policies.  So whenever you define interfaces  as internal, external, leaf, or a guest,  then they get different profiles for security also.  Now, what does this translate into?  I used to, at the training courses,  I do it manually on a flip chart.  But here, I decided to spend some time  and show you how this could work.  And this is a setup that I had at home at a certain point  when we were testing some of the functionalities.  So I have my main router.  Imagine I have a house and I have my router.  I connect to an ISP.  And I get a slash 48, because I'm lucky.  But you can also do it with a hurricane electric  if you want to try this.  Now, this is my main router.  My main router will have a certain number  of ethernet interfaces.  Voila.  Each and every one of those will get a different slash 64,  because that's the way it works.  And that's the reason why I get so many networks.  Then I can connect another router.  And then there is a mechanism in HomeNet  which defines the delegation that should happen here.  Delegation should be, at least, well, when I try it first time,  I walk eight bits.  I walk two nibble boundaries to get to a slash 56 from a slash 48.  And then my local router there will also have different interfaces  with different slash 64s, because it has enough networks  to do that.  Now I can connect a third router.  I can use another slash 64.  And my router here will get a slash 60,  because I try to walk eight bits from slash 56.  But I end up with the only ability  to hand out one slash 64, which wouldn't be enough for this  router to work, because I need also this router needs  to have one slash 64 per interface.  But I walk four bits back and I get a slash 60.  And then I can also have another router connected  to the main one, gets another slash 56.  And then I can also create a loop using wireless if I want.  So this is one of the cases where in my house  I could create redundancy.  And this is all managed by my bubble profile inside my network.  So it avoids the loops.  It makes sure that routing happens using the best path,  in this case.  Anything to add, Henning?  You're falling asleep, so it looks horrible going.  So a router has.  The IPv6 prefix or prefixes, because going back one step.  Oh, now I ended up in here.  Sorry.  I could actually connect a second router to the internet  using a different ISP.  And then the same scheme of propagation  would happen in there.  And I would have my hosts, but also my various routers,  with multiple subnets.  And I know this can sound confusing.  But if I have my host, my laptop, with multiple IPv6 subnets,  then I can change.  I can have one of the ISPs just go away.  My main router will die.  One of the two routers will die.  Two external routers will die.  And I will just stop receiving router advertisements  for that network.  Or I will get a router advertisement  with a lifetime of zero telling me  to delete all those addresses from my host.  And I will just move gracefully to the second connectivity.  There's also a specific draft.  Well, it's becoming an RFC that explains how that works.  It will be an RFC pretty soon.  So I have auto-signed unique local IPv6.  And I have an IPv4 network out of 10 slash 8,  and that is applied at the border.  So every router in my architecture  will decide to get 1 slash 24 out of 10 slash 8.  And it will be a random one.  It will auto-assign an address in there.  And in the OpenWRT implementation,  I can decide it to be any address in the slash 24  or just be the first one.  Yes?  Do you mind the ULA prefix to be the same for the ULA network?  Just one big prefix.  I have one prefix for the entire network.  But then all my local routers will get 1 slash 24 out of 10  slash 8 in IPv4.  For ULA, I have one unique prefix.  I don't have different separates.  No, that wouldn't make sense.  Yes.  So what do we have in terms of implementation?  The only full implementation on OpenWRT.  Not in base, but you have to install a separate package.  There's no other known full implementation  and not even in commercial CPEs right now.  Not that we have found.  And there is Spark software.  So there is someone who brought the proof of concept  when developing the home net draft.  And then it just lies abandoned.  Or there is a very small subset of home  net working somewhere, but with no real implementation.  The only one fully working, OpenWRT.  And that's the one I, for example, use at home.  That's the one that's the reference implementation  at the moment.  So yes?  How much of the interminational dependence  on the ISP to Blue-Wade UI devices?  You can run home net also only on IPv4,  but that means that you would have unique local everywhere  for IPv6.  And that would sometimes, some operating systems  might be slowed down by the fact that you have unique local.  So because they will attempt to use that to talk to the.  Does it provide the native storage in a store?  Does that provide, sorry?  Does it also provide DNF6 for native storage  in a gateway?  No, it's not meant to be there.  No, it's not in the specifics.  You can add it.  You can add NAT64 or 464XLAT if you want.  Actually, I ran with that for about a month at home,  because when there was an issue with managing IPv4  in the translation, and I couldn't use it.  So yeah.  I ran with home net and NAT64 on the edge.  Yes.  So I was looking at this, and in December,  when I became the IPv6 program manager,  I decided to, OK, let's look at this  and see if there's anything that could be done.  So I was thinking, OK, PSD routers are widespread,  especially in SOHO environments.  And why can't we leverage this?  But I underestimated the effort, and I  didn't consider the fact that there were many other projects  that I would have gotten involved with.  So I ended up looking at getting a plan, which I didn't end up  having fully implemented by now.  So what do you have?  You have freeBSD and openBSD.  And I didn't include, well, PFSense here,  because then it comes after you've finished with freeBSD  there.  So you have bubble.  BubbleD is in ports.  Fine.  You have wide DHCP for DHCP v6, and that's in ports for both  of them.  That's good.  You have a Slack daemon.  That's included in base.  Simple.  But we're missing something, and that's basically HNCP.  HNCP exists in different implementations.  There's SHNCP.  That's a very simple one.  There's one in Python.  There's also, but those are very, very limited.  And then there's one.  That's the reference implementation, the one for  OpenWRT, which has some issues.  And I'll tell them in the next slide.  But, well, DNS servers and proxy, you can get everything.  So you have the different pieces, and then you have to find  a way to tie them together.  You're missing the one that decides who's going to do what.  And then based on this, everything else should be  kind of orchestrated.  Because the way it works is that it runs as an  orchestrator, which tells you should do this, you should do  that, based on the priority, based on your capacity.  You should do use server, manage DNS.  You do DHCP v6, and so on.  So we're missing the glue.  But I've started looking at it, and it's full of Linuxisms.  So you have to basically deeply look at that and reverse  engineer half of it, because it's very, very  OpenWRT oriented.  And it contains a lot of stuff that's done especially for it.  So you have to actually modify big parts, big  chance of that.  So here, my idea is to tell you, there is this.  This is a great opportunity to bring IPv6 to the masses, to  a lot of people, because it will enable all the IoT, all the  new functionalities that we're going to have.  And basically, this is it.  And I'm open for questions.  You've already asked them during the, yeah.  Why didn't you call?  Sorry?  Why didn't you call?  Call.  If you wanted home.net to be upset, why didn't you call?  Pick up the phone or the email and say, hey.  Because I started working on it, and I ended up not having  enough time to finish that.  But yeah, we can talk.  I'm saying we're interested.  Yeah, OK, good.  I certainly know what this is.  Sorry?  I certainly know what home.net is.  OK.  Yeah.  Please.  So I mentioned about the mobility.  But you can't say it's not the mobility.  It's one of the outdoor dials.  And then it's the, you know, it's half to the next to a  different router.  Yeah.  It's not responding anymore.  Changing the perfects.  Yeah.  You're not changing it.  If you want a different router, then you keep your  previous prefects.  No, you don't keep your previous prefix.  But if you have two board of routers, they will both  announce the router advertisements in the  network, so you end up with two different prefixes coming  from two different sources.  And you install both of them.  So you have both of them on your network card at the same  time, and then you choose which one to use, too.  So if you go to your previous slide, where we are just  having slash extroperfections to the leaf roots, you mean  this one?  You really want me to go through all the?  So here we are actually manufacturing slash 64 here.  Oh, not manufacturing.  Well, you branched them out of what you're.  Yeah?  So it's from the top program you have to see.  You had a band connected to be on the lower left  row also.  And if you were to move down there, the prefix will remain  the same?  You mean if you move a host from one part to the other?  No, you would have to change it.  But as soon, well, if the host does a handover from, say,  this to this one, then when it moves, it will send a router  solicitation, and it will get a new router advertisement with  the new prefix, and will just install the new one.  And forget about the old one.  Another question was, a lot of home-rock solutions are  building up high-eulivity based on layer 2, in which case  it's almost like a big, sublime concept.  So do we really have to worry about, where do you see  the component going forward?  Could the high-eulivity coming from these extenders, which  are doing it to layer 2 and giving you one domain to work  with?  What's it doing?  I think it will.  That's a nice question.  Because having layer 2 helps in simplicity in the end.  Because you have one prefix for the whole house, and that's  it.  And you?  I think the euro is also working towards that.  Yes, yes.  But euro has different applicabilities, as far as I  remember.  And in this case, you want to be segmented, because you have  to locally control everything and make sure it gets routed  the way you want, the way the local router wants.  Any other question?  Yeah?  Yeah.  Today.  Mm-hmm.  How about I get you benefit out of it?  Immediately?  You know, house mixed with VST, macro-ass, micro-ass.  Yeah.  What would be my immediate benefit?  Well, the immediate would be, you don't have to configure  much.  You don't have to do much.  Imagine the case where you have a grandmother with a router,  and then you can tell her to plug the cable  wherever she wants, and that would make it easy.  Imagine a house where you have a border router, and then you  can connect any kind of other routers wherever you want, and  they will just work.  Well, most of the time.  Yes.  But then you win with that.  Rather than then having range extenders, like we  were discussing, where if you just have to browse the  internet, control a few things, having this helps in  simplicity and making your house easier to manage in the  end, the local network easier to manage.  Sorry, could you get benefit out of it today?  Yes.  But also imagine, oh, sorry, the range extenders, you could  do that.  If there's a part you want to reach of your house with  another router, you can actually multi-home a router  with two other routers using Wi-Fi, and it would just  work.  So the advantages are quite a few.  Yes.  I know this was a short one, but there's not much else to  say about it.  Yeah?  Would home that have any understanding of a network  virtual full internet links?  Yes.  Yeah, yeah.  You can just multi-home, and it's very simple.  You don't do BGP, you don't do anything else you just have.  You just will see the different prefixes installed on  your different addresses from different prefixes  installed on your cards.  And then it's up to the host to decide which one to use.  But there's also other work being done on multi-homing  without BGP using router advertisements, and that's a  different story.  Yeah, Jim?  The reality here is that most home networks are wireless.  Maybe not for this audience.  But most people don't have a lot of wire on the walls, and  they take their smarts from a set home and just get it  plugged into the HVMC, and it runs until 11 to two.  So whatever.  They just presumably come out.  So there you have one, the Liar 2 domain.  Yeah.  How is this?  Well, in this case, you would have like for, what is the  question?  Because you have one layer to domain, but you don't need  much else.  Right, but you don't segmentation at that point.  No, you don't need it.  You have one port.  Yeah.  What you do, plus port.  Well, the thing is if you have like a 2.4G network and a  5G network, then they would be separated, basically.  That would be the way home networks would do it, in that  case.  But other than that.  You don't get segmentation, which is a big part of the  security.  Yeah, that's true.  It's not as simple as your TV is.  Yeah, that's true.  That's true.  But that's something probably that was a bit overlooked  than defining home networks.  Well, there's space for a new document.  Here.  There's a way to do it.  You can actually segmentate.  Sure, you can still do that, yeah?  That's why I say there's space for a nice new document.  Yeah?  Yes?  What exactly is the advantage of giving a lamp 18  quintillion IP addresses if you don't have the map?  You don't have to map.  Well, that's one of the advantages.  But couldn't that be done with, say, only one quintillion?  Yeah?  Yes, you could.  But the answer, the simple answer is if you don't give a  lamp of slash 64, the lamp will not be able to get an  address out of that.  So unfortunately, there's a bunch of, yes, we can discuss  in this.  But the way things are is that if you don't give a slash 64  to a network where you want devices to connect automatically,  then you will be breaking more than 30 RFCs.  And, huh?  So?  Yeah.  Burn here.  Breaking RFCs is something you could only do if you know  exactly what you're doing.  Exactly.  I don't need to leave the rules.  You can run IPv6 networks with different sources.  So now can we find out whether IPv6 is a good idea?  We can.  Well, with handing, there's no reason.  But yes, sorry.  Handing?  Give me a second.  But to, sorry, to extend one, you would say those of us who  live in North America and our ISP will be able to give us  a slash 64 to give us a six.  There's no way to do state and solid configuration using  young extenders.  Yeah.  So the way they do that is that they basically think the  same way they think in IPv4.  And they force you to do not six six in that case.  What's the smallest allocation I can give the customer?  Well, you can give them a slash 64.  But the recommendation from communities a slash 56.  I'm saying that from mentality.  What's the smallest allocation I can give the person in  the evening?  Slash 56.  That's the suggestion.  That's the smallest suggestion you can get.  If I have to work with, it doesn't really depend on the  global products or anything.  Sorry?  For this, connect to work.  We don't really depend on the global perfect delegation to  the end devices.  The phone itself can be IPv6 only based on the ULA.  Yes.  And it can have the band connectivity from the  translation.  Yeah.  In fact, that's the point.  When you lose connectivity, you will have ULA still  working in there.  And that's.  So how do you know you're part of that network?  You also have an IPv6 ULA perfect.  And you can talk to these devices.  Yeah.  Yes, exactly.  What I see though is most of the phone devices, other than  probably the lock on the door, they have a fixed power  source.  And they can afford to have a Wi-Fi interface on it.  Where it just becomes a normal user-end device connected to  a Wi-Fi network with the extenders and things.  You are fine.  The only place where I see a sensor is the lock on the door  where you cannot run wires and get them fired.  And then to depend on a low power network.  And that's where your band and other things come again.  Yeah.  It's like, I just see it in the plugs.  I mean, there's different stats also coming out.  What the end story would be.  Yeah.  Yes.  Well, but we're talking about different things.  I mean, if you talk about, I wouldn't put my door lock on  low pan, because that means that my lock has a reachability  of a few kilometers.  And I.  Yes.  I mean, you are understanding if you would probably be  very interested in something else.  There have to be some other mechanism.  Yeah.  Yeah.  So it's, yes.  But that's what Jim was saying, that we should think about  how to segment also the wireless part in this case.  Because in the specifics, it only mentions the physical  interfaces.  And then you should be actually doing separation also on the  wireless part.  Because most of the things that we see now, most of the new  sensors or the new devices that we see have an ESP, whatever  that connects to the local wireless network.  And then you have everything on one big segment, instead of  having all separated.  So yeah, we should also think about that.  Do you agree, Jim?  Yeah.  I think there are largely ways to do it as well.  Sorry?  There are actually techniques to do it as well.  Yeah.  Yes.  To go back to the slash 56, putting your right IPv6  at the C.  Yes, OK.  Although I'm not here officially for the right  and C.  When you talk to ISPs and they try and justify  handing out 64s, what do you and your, I live in North  America, so I feel the same problem.  What do you all say?  We have that in our region as well.  Don't worry.  But when you have these conversations with the ISP,  what do you hear back from them?  What is their rationale?  Why are they doing this?  Well, the reason mostly is that they, no.  The reason is mostly thinking about a, and I can  be form mindset.  And thinking, oh, what's the smallest thing I can give them?  Exactly.  But then the counter argument is, look at how many you have.  Like this small, if I remember correctly in the  matter, the smallest allocation is a 36.  And if you have a slash 36, we're talking about 2 million  slash 56s.  So no.  It's a half a million, two to the 20, one million.  One million.  One million slash 56s.  I mean, with the smallest allocation you can get, you  can serve one million households.  Where's the problem?  I mean, if you have more than a million customers, or you  plan on having more than a million customers, you can  get worried.  But we have a better argument in our region, because we  hand out, the smallest one we hand out is a slash 32.  So you have 16 million.  And then without questions, you can get up to slash 29,  which means 128 million.  Why would you have to care about the single network you  hand out to one of your customers when you can serve  128 millions?  And we have entire countries with, say, 2 million people.  And you're one of the ISPs there.  And even if there are only two, then the two of you have a  potential to serve 256 million households.  Why would you have to be careful about what you use?  What they're thinking is, yeah, nobody will  need more than 640k.  Nobody ever needs more than that.  Yeah.  Yeah.  It's the same.  You run with the same exact mentality.  Isn't it?  24.  18 million addresses.  Yeah?  I don't know.  May.  That's exactly the same.  Engineer.  This is the truth, though, that when you allocate a slash,  that's a 29, that you actually have another, that we can  actually aggregate.  You don't actually give spaces between.  Yeah, that's what I.  So in reality, then, that's not really fixed.  And we do it out of, it's not written in stone.  But whenever we, for example, you have a slash 29.  And if you didn't get that way in the past, like more than  10 years ago, what we do nowadays, what we've been  doing for almost 10 years, is sparse allocation.  So basically, he got a slash 29, but we  reserved three more bits.  So if they ever come back and want to get more address space,  we don't hand out a new subnet, but we just enlarge the one  they have.  So you left some continuous growth room.  Yeah?  Yeah.  Yes.  So but the same does adding, as far as I remember.  I'm not 100% sure, but it's possible.  Never estimate North America.  No, no, no.  Well, not saying anything.  You're crazy.  Not saying anything bad.  Just saying we have different policies.  I'll criticize North America.  You don't have to.  These room taxes, if you don't want to.  Oh, OK, OK.  It's a whole other country.  It's a whole other country.  We demand our slice of the IPv6 range as well.  Yeah, no, that in theory you could.  Actually, it's the last 29 we've covered.  Yeah?  OK, well, thank you very much.  Thank you.  Thank you.
Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_0_107.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_108_251.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_252_2243.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_2244_2543.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_2544_3035.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_3036_6215.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_6216_8567.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_8568_13259.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_13260_14411.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_14412_15767.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_15768_17867.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_17868_20375.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_20376_23819.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_23820_25187.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_25188_26591.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_26592_27167.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_27168_27359.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_27360_28199.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_28200_29111.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_29112_29267.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_29268_29423.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_29424_29579.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_29580_29663.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_29664_30287.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_30288_31055.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_31056_32483.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_32484_34307.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_34308_34571.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_34572_35555.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_35556_35963.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_35964_36047.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_36048_36311.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_36312_36551.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_36552_36659.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_36660_36707.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_36708_36899.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_36900_36971.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_36972_37019.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_37020_37151.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_37152_37247.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_37248_37355.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_37356_37979.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_37980_38843.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_38844_40163.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_40164_42263.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_42264_42311.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_42312_42371.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_42372_42431.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_42432_42623.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_42624_42971.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_42972_47447.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_47448_59579.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_59580_59627.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_59628_60047.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_60048_60479.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_60480_64919.png Massimiliano_Stucchi__Preparing_your_home_routers_for_the_future_64920_64925.png
Hello, everyone. And I'm Max. Well, my name is actually Longer, but you prefer, you want to prefer Max. We recently had a new colleague at the Reipens CC from China. He said, well, he sent an email. Hi, I'm Max. I'm his name. I don't remember. You can call me Max and I reply, no. That's me. Who am I? I work at the Reipens CC. We are the registry for. You spent your time at Reipens CC. I spent my time at the Reipens CC. OK. Handing is correcting me. Yeah. So no, no, no, no, no. And I like to say the goal of my job is to not have a job anymore because I am the IPv6 program manager. I do training, so I train people. I also have a voice award in what the Reipens CC does about IPv6. So what is this about? Making your routers future proof. Why? Because things are changing. Recently, we came across an important date. Six years ago, there was World IPv6 launch day, which means that actually Wednesday, last Wednesday, was six years after the 6th of June, 2012. What does this mean? This means that something has happened. And when I say my goal is to not have a job anymore, it means that I want to see this going better and better. We have. We are in a moment where, well, I've been saying this for years, and people start, well, people tend to not believe me anymore. But IPv6 is happening. 50% in India and Belgium, but they have different markets. You know what's the difference between the two? Why they do more than 50%? There's a big, huge difference between the two countries. What's the cellular geo? Yeah, reliance, GAO. GAO. In India, India is mobile, while Belgium is fixed. The difference in Belgium, Belgium is divided into two parts, and the two, yes. It's more complicated than that. But let's keep it simple. It's not being informed from the framework, but it's more complicated than that. You know what I mean. Those are more complicated. Don't. Let's keep it simple. So let's say there was a sort of an internal competition between ISPs to say who would do it first. And that led to India and Belgium being more than 50%. Then we. I just thought the one side wanted to make sure they cannot communicate with the other side. Could also have been. One is before, one is for six. Yeah? Only. Yes. Could be. I think that's right. Could also be that, yes. Making sure, oh, let's use this new protocol so the others don't know it. But then also the US, around 40%. And you might think, well, I'm from the US. I live there, but I don't see much happening on my landline. And that's also because mobile. Yes, mobile phones in the US are leading a lot. Many other countries are around 30%, because maybe one of the big ISPs there moved over. The others are still waiting. But what I like to say is that things are happening. But we also have a changing world. We have more than half of the population on the internet. And if I look at you, you have more than one device that connects to the internet, which means that we need so many IP addresses that we can't live with IPv4 for much longer. We tried to stretch the lifetime of IPv4 so much, blah, blah, blah. And then there's this buzzword that I generally don't like to use, but it's true that the internet of things is also going to change how we do things on the internet. There are cases where also where I come from, I come from Milan, from Italy, and I was so happy to see that they're doing something smart, like putting sensors on the trash bins to see where, to have an idea of how full the trash bin is, and then give a different route to the trucks, so the trucks would spend 50% less fuel on overage. So this means that the internet will be different in five or 10 years. And if you think about how it was five or 10 years ago, it was also way, way, way different, which might lead to something similar to what we have. I told you I do training. We have an exercise in our basic IPv6 training course that's called Future Casa, the house of the future, where you have smart things inside your house. And again, I don't really like the idea of having smart things in the house that much, but people seem to. And this is one of the situations you might end up into. Imagine you have an ISP, you have your V6 internet, you're connected to an ISP, whatever, you get a big chunk of IP addresses, and then inside your house, all the functionalities are split in between different networks. So everything is layer three. So this is what we want to go towards. Does anyone agree? Agree? No. No. Sorry? This is what we want, or this is what's going to happen? OK, why would you not want something like that? Of course V6 is shit. OK, let's not get into that. I know you, and I know you like to sit here in the front. But yes? I think for the first time, it's much bigger than the internet world. It's one perfect for the entire thread network. The routing has done differently. It's been about a few minutes. But I don't know, I don't think it's a point that you want to split the network and get to the last support. OK, why? One thing is, I don't know, I think mobility, if you move from one to the other. OK, yeah, but these are not things that are going to move between houses unless you sell them. No, not these things. But there may be other moving devices who want to be part of the network, and may run 15.4. OK. But imagine you have different devices in your house, and you want to separate them. So that you could. I have a point there. There's a time which is right now catering to the devices. It's not led into different stuff. It's a flash, flash, etc. OK. So I don't know what we gain by doing this. Well, one of the reasons for doing this can be security, because you can isolate every single device into its own network, and then make sure that security is tied for every one of those. That can be one. I think just having those things go up actually becomes a potential security problem. Yes, I said initially that I don't like the idea that much, but this is what we're going to get. Because we already have smart thermostats. And if you check those, you have cases where the thermostats lost connectivity to the internet, and the houses went up to 45 degrees, because they were still thinking, oh, I have to heat up the house. This is not what you're going to get. They will not be on separate networks. It'll be all the same. Yeah, well, that's what I'm going to show in a moment. So ISPs should assign you between a slash 56 and a slash 48. So enough networks to separate, to then branch your network into something more. And you need to have a slash 64 for each subnet. It's not mandatory, not really a hard line. Many people don't agree on this, and there are long discussions, especially at the ITF, about how right it is to have something like this. For the moment, that's what we have. And if you want to allow Slack to work, stateless auto configuration, that's what you want to have. Consider that in this case, you have a slash 64. It's big enough that you don't have to worry about the hosts in there. But then comes HomeNet. So one day, 2014, earlier than that, 2013, they chartered a working group at the ITF. And the idea was to define some rules for how Home networks should be and what services you should have in those Home networks. So they came up with a series of protocols and functions to be used for Home networks to fully enable IPv6 and maybe provide IPv4. I've added that maybe. That's because IPv4, in this case, becomes a second class citizen. So everything is focused on IPv6, and then IPv4 comes second. So how is this? What do we get with HomeNet? Zero configuration networks. And we'll see that in a moment. You're supposed to have multiple subnets. In that case, you have, let's say, how many of you know what unique local IPv6 addresses are. So very few people. Basically, it's the corresponding. I haven't said this, but it's the same as private addresses in IPv4, although they have a totally different use case. Those are supposed to be used for internal communication in networks that are not supposed to be connected to the internet. So you're not going to route unique local addresses. They are fc-sev. fc-00-sev. You want to have one of those also in your network, that network as a back end. In case you lose connectivity, you can still address hosts using private addressing. In that case, you can have multiple routers and multiple connectivity to different ISPs. Multiple upstreams with multiple prefixes coming into your network. And together with that, you get name resolution inside your small network, because it's important to be able to name routers when you connect them. Now, what does this translate into? Bubble, internal routing protocol, very simple, very chatty protocol, was the one that was decided to be the reference implementation for HomeNet. Then you get the HCPv6 client, server, prefix delegation client, and prefix delegation server. So that means that you act as a client, but inside your network, you're going to run prefix delegation as well. You're going to run a DHCPv6 server as well. You run DHCPv4, and then this is the heart of it, the distributed node consensus protocol, which is also called then HNCP, because HomeNetworkingControlProtocol is a profile of the NCP. Basically, what it does is manage who is responsible for services. If you have multiple routers all doing HomeNet, you have to elect the one that will do the DHCPv6 server. You have to elect the one that will do the name resolution. You have to elect the one that will do all the routing at one time. So this protocol is what you need to define who is going to do what. And then you have DNS. You need a multicast DNS proxy. You need a resolver, because you need to provide it. And then you have an authoritative server, because you have to provide your internal naming services. And then, important still, you have to provide Slack, stateless sort of configuration. Now, what are the biggest selling points then of HomeNet? Biggest selling point is that you don't have to configure anything. Imagine you have a device with 10 ethernet ports, and you have your ethernet port coming from your cable modem. You can connect it anywhere you want. You don't have to define a one interface, because discovery is done with basically DHCP sensing. If I can obtain something with DHCP, then good. That's my external interface. The others will be internal. I have internal naming for my devices. Everything is dual stack with NAT to DP4. Thanks to Babbel, I have loop avoidance. I can basically connect my routers even in a loop. I can daisy chain them. I can add multiple routers as I want, like range extenders. Think about that. And I can also connect them via Wi-Fi, for example. So I can have a router delegate a network to another via Wi-Fi, and that still would work. So this, yes? I have a situation where my edge router could be changing from time to time. Because I basically live in moving houses. And so I have my DHCP server on an internal machine for my internal network. So is my router now going to say, oh, there's my external network because it's serving DHCP? No. No, there's a specific case. If I connect the router internally, what I use is they use a keyword in the DHCP request that says home net. And if I'm a router that's internal to my network, and I see a request coming with the home net keyword in there, I just discard it. So I won't be seen in there. Yeah, there is a mechanism for avoiding that. Yeah. And that works for both v4 and v6 in prefix delegation. But thanks for the question. Now, I have different interface categories. And this is important because I can define them manually, or I can let them auto-discovery. I have the internal interfaces, which are the ones that interchange the NCP information. I have the external ones that are the ones where I can get DHCP v6 prefix delegation. I have the leaf interface just for clients. And then I have the guest for untrusted clients. With basically what I haven't discussed yet is also the fact that in home net, you have predefined security sets, security policies. So whenever you define interfaces as internal, external, leaf, or a guest, then they get different profiles for security also. Now, what does this translate into? I used to, at the training courses, I do it manually on a flip chart. But here, I decided to spend some time and show you how this could work. And this is a setup that I had at home at a certain point when we were testing some of the functionalities. So I have my main router. Imagine I have a house and I have my router. I connect to an ISP. And I get a slash 48, because I'm lucky. But you can also do it with a hurricane electric if you want to try this. Now, this is my main router. My main router will have a certain number of ethernet interfaces. Voila. Each and every one of those will get a different slash 64, because that's the way it works. And that's the reason why I get so many networks. Then I can connect another router. And then there is a mechanism in HomeNet which defines the delegation that should happen here. Delegation should be, at least, well, when I try it first time, I walk eight bits. I walk two nibble boundaries to get to a slash 56 from a slash 48. And then my local router there will also have different interfaces with different slash 64s, because it has enough networks to do that. Now I can connect a third router. I can use another slash 64. And my router here will get a slash 60, because I try to walk eight bits from slash 56. But I end up with the only ability to hand out one slash 64, which wouldn't be enough for this router to work, because I need also this router needs to have one slash 64 per interface. But I walk four bits back and I get a slash 60. And then I can also have another router connected to the main one, gets another slash 56. And then I can also create a loop using wireless if I want. So this is one of the cases where in my house I could create redundancy. And this is all managed by my bubble profile inside my network. So it avoids the loops. It makes sure that routing happens using the best path, in this case. Anything to add, Henning? You're falling asleep, so it looks horrible going. So a router has. The IPv6 prefix or prefixes, because going back one step. Oh, now I ended up in here. Sorry. I could actually connect a second router to the internet using a different ISP. And then the same scheme of propagation would happen in there. And I would have my hosts, but also my various routers, with multiple subnets. And I know this can sound confusing. But if I have my host, my laptop, with multiple IPv6 subnets, then I can change. I can have one of the ISPs just go away. My main router will die. One of the two routers will die. Two external routers will die. And I will just stop receiving router advertisements for that network. Or I will get a router advertisement with a lifetime of zero telling me to delete all those addresses from my host. And I will just move gracefully to the second connectivity. There's also a specific draft. Well, it's becoming an RFC that explains how that works. It will be an RFC pretty soon. So I have auto-signed unique local IPv6. And I have an IPv4 network out of 10 slash 8, and that is applied at the border. So every router in my architecture will decide to get 1 slash 24 out of 10 slash 8. And it will be a random one. It will auto-assign an address in there. And in the OpenWRT implementation, I can decide it to be any address in the slash 24 or just be the first one. Yes? Do you mind the ULA prefix to be the same for the ULA network? Just one big prefix. I have one prefix for the entire network. But then all my local routers will get 1 slash 24 out of 10 slash 8 in IPv4. For ULA, I have one unique prefix. I don't have different separates. No, that wouldn't make sense. Yes. So what do we have in terms of implementation? The only full implementation on OpenWRT. Not in base, but you have to install a separate package. There's no other known full implementation and not even in commercial CPEs right now. Not that we have found. And there is Spark software. So there is someone who brought the proof of concept when developing the home net draft. And then it just lies abandoned. Or there is a very small subset of home net working somewhere, but with no real implementation. The only one fully working, OpenWRT. And that's the one I, for example, use at home. That's the one that's the reference implementation at the moment. So yes? How much of the interminational dependence on the ISP to Blue-Wade UI devices? You can run home net also only on IPv4, but that means that you would have unique local everywhere for IPv6. And that would sometimes, some operating systems might be slowed down by the fact that you have unique local. So because they will attempt to use that to talk to the. Does it provide the native storage in a store? Does that provide, sorry? Does it also provide DNF6 for native storage in a gateway? No, it's not meant to be there. No, it's not in the specifics. You can add it. You can add NAT64 or 464XLAT if you want. Actually, I ran with that for about a month at home, because when there was an issue with managing IPv4 in the translation, and I couldn't use it. So yeah. I ran with home net and NAT64 on the edge. Yes. So I was looking at this, and in December, when I became the IPv6 program manager, I decided to, OK, let's look at this and see if there's anything that could be done. So I was thinking, OK, PSD routers are widespread, especially in SOHO environments. And why can't we leverage this? But I underestimated the effort, and I didn't consider the fact that there were many other projects that I would have gotten involved with. So I ended up looking at getting a plan, which I didn't end up having fully implemented by now. So what do you have? You have freeBSD and openBSD. And I didn't include, well, PFSense here, because then it comes after you've finished with freeBSD there. So you have bubble. BubbleD is in ports. Fine. You have wide DHCP for DHCP v6, and that's in ports for both of them. That's good. You have a Slack daemon. That's included in base. Simple. But we're missing something, and that's basically HNCP. HNCP exists in different implementations. There's SHNCP. That's a very simple one. There's one in Python. There's also, but those are very, very limited. And then there's one. That's the reference implementation, the one for OpenWRT, which has some issues. And I'll tell them in the next slide. But, well, DNS servers and proxy, you can get everything. So you have the different pieces, and then you have to find a way to tie them together. You're missing the one that decides who's going to do what. And then based on this, everything else should be kind of orchestrated. Because the way it works is that it runs as an orchestrator, which tells you should do this, you should do that, based on the priority, based on your capacity. You should do use server, manage DNS. You do DHCP v6, and so on. So we're missing the glue. But I've started looking at it, and it's full of Linuxisms. So you have to basically deeply look at that and reverse engineer half of it, because it's very, very OpenWRT oriented. And it contains a lot of stuff that's done especially for it. So you have to actually modify big parts, big chance of that. So here, my idea is to tell you, there is this. This is a great opportunity to bring IPv6 to the masses, to a lot of people, because it will enable all the IoT, all the new functionalities that we're going to have. And basically, this is it. And I'm open for questions. You've already asked them during the, yeah. Why didn't you call? Sorry? Why didn't you call? Call. If you wanted home.net to be upset, why didn't you call? Pick up the phone or the email and say, hey. Because I started working on it, and I ended up not having enough time to finish that. But yeah, we can talk. I'm saying we're interested. Yeah, OK, good. I certainly know what this is. Sorry? I certainly know what home.net is. OK. Yeah. Please. So I mentioned about the mobility. But you can't say it's not the mobility. It's one of the outdoor dials. And then it's the, you know, it's half to the next to a different router. Yeah. It's not responding anymore. Changing the perfects. Yeah. You're not changing it. If you want a different router, then you keep your previous prefects. No, you don't keep your previous prefix. But if you have two board of routers, they will both announce the router advertisements in the network, so you end up with two different prefixes coming from two different sources. And you install both of them. So you have both of them on your network card at the same time, and then you choose which one to use, too. So if you go to your previous slide, where we are just having slash extroperfections to the leaf roots, you mean this one? You really want me to go through all the? So here we are actually manufacturing slash 64 here. Oh, not manufacturing. Well, you branched them out of what you're. Yeah? So it's from the top program you have to see. You had a band connected to be on the lower left row also. And if you were to move down there, the prefix will remain the same? You mean if you move a host from one part to the other? No, you would have to change it. But as soon, well, if the host does a handover from, say, this to this one, then when it moves, it will send a router solicitation, and it will get a new router advertisement with the new prefix, and will just install the new one. And forget about the old one. Another question was, a lot of home-rock solutions are building up high-eulivity based on layer 2, in which case it's almost like a big, sublime concept. So do we really have to worry about, where do you see the component going forward? Could the high-eulivity coming from these extenders, which are doing it to layer 2 and giving you one domain to work with? What's it doing? I think it will. That's a nice question. Because having layer 2 helps in simplicity in the end. Because you have one prefix for the whole house, and that's it. And you? I think the euro is also working towards that. Yes, yes. But euro has different applicabilities, as far as I remember. And in this case, you want to be segmented, because you have to locally control everything and make sure it gets routed the way you want, the way the local router wants. Any other question? Yeah? Yeah. Today. Mm-hmm. How about I get you benefit out of it? Immediately? You know, house mixed with VST, macro-ass, micro-ass. Yeah. What would be my immediate benefit? Well, the immediate would be, you don't have to configure much. You don't have to do much. Imagine the case where you have a grandmother with a router, and then you can tell her to plug the cable wherever she wants, and that would make it easy. Imagine a house where you have a border router, and then you can connect any kind of other routers wherever you want, and they will just work. Well, most of the time. Yes. But then you win with that. Rather than then having range extenders, like we were discussing, where if you just have to browse the internet, control a few things, having this helps in simplicity and making your house easier to manage in the end, the local network easier to manage. Sorry, could you get benefit out of it today? Yes. But also imagine, oh, sorry, the range extenders, you could do that. If there's a part you want to reach of your house with another router, you can actually multi-home a router with two other routers using Wi-Fi, and it would just work. So the advantages are quite a few. Yes. I know this was a short one, but there's not much else to say about it. Yeah? Would home that have any understanding of a network virtual full internet links? Yes. Yeah, yeah. You can just multi-home, and it's very simple. You don't do BGP, you don't do anything else you just have. You just will see the different prefixes installed on your different addresses from different prefixes installed on your cards. And then it's up to the host to decide which one to use. But there's also other work being done on multi-homing without BGP using router advertisements, and that's a different story. Yeah, Jim? The reality here is that most home networks are wireless. Maybe not for this audience. But most people don't have a lot of wire on the walls, and they take their smarts from a set home and just get it plugged into the HVMC, and it runs until 11 to two. So whatever. They just presumably come out. So there you have one, the Liar 2 domain. Yeah. How is this? Well, in this case, you would have like for, what is the question? Because you have one layer to domain, but you don't need much else. Right, but you don't segmentation at that point. No, you don't need it. You have one port. Yeah. What you do, plus port. Well, the thing is if you have like a 2.4G network and a 5G network, then they would be separated, basically. That would be the way home networks would do it, in that case. But other than that. You don't get segmentation, which is a big part of the security. Yeah, that's true. It's not as simple as your TV is. Yeah, that's true. That's true. But that's something probably that was a bit overlooked than defining home networks. Well, there's space for a new document. Here. There's a way to do it. You can actually segmentate. Sure, you can still do that, yeah? That's why I say there's space for a nice new document. Yeah? Yes? What exactly is the advantage of giving a lamp 18 quintillion IP addresses if you don't have the map? You don't have to map. Well, that's one of the advantages. But couldn't that be done with, say, only one quintillion? Yeah? Yes, you could. But the answer, the simple answer is if you don't give a lamp of slash 64, the lamp will not be able to get an address out of that. So unfortunately, there's a bunch of, yes, we can discuss in this. But the way things are is that if you don't give a slash 64 to a network where you want devices to connect automatically, then you will be breaking more than 30 RFCs. And, huh? So? Yeah. Burn here. Breaking RFCs is something you could only do if you know exactly what you're doing. Exactly. I don't need to leave the rules. You can run IPv6 networks with different sources. So now can we find out whether IPv6 is a good idea? We can. Well, with handing, there's no reason. But yes, sorry. Handing? Give me a second. But to, sorry, to extend one, you would say those of us who live in North America and our ISP will be able to give us a slash 64 to give us a six. There's no way to do state and solid configuration using young extenders. Yeah. So the way they do that is that they basically think the same way they think in IPv4. And they force you to do not six six in that case. What's the smallest allocation I can give the customer? Well, you can give them a slash 64. But the recommendation from communities a slash 56. I'm saying that from mentality. What's the smallest allocation I can give the person in the evening? Slash 56. That's the suggestion. That's the smallest suggestion you can get. If I have to work with, it doesn't really depend on the global products or anything. Sorry? For this, connect to work. We don't really depend on the global perfect delegation to the end devices. The phone itself can be IPv6 only based on the ULA. Yes. And it can have the band connectivity from the translation. Yeah. In fact, that's the point. When you lose connectivity, you will have ULA still working in there. And that's. So how do you know you're part of that network? You also have an IPv6 ULA perfect. And you can talk to these devices. Yeah. Yes, exactly. What I see though is most of the phone devices, other than probably the lock on the door, they have a fixed power source. And they can afford to have a Wi-Fi interface on it. Where it just becomes a normal user-end device connected to a Wi-Fi network with the extenders and things. You are fine. The only place where I see a sensor is the lock on the door where you cannot run wires and get them fired. And then to depend on a low power network. And that's where your band and other things come again. Yeah. It's like, I just see it in the plugs. I mean, there's different stats also coming out. What the end story would be. Yeah. Yes. Well, but we're talking about different things. I mean, if you talk about, I wouldn't put my door lock on low pan, because that means that my lock has a reachability of a few kilometers. And I. Yes. I mean, you are understanding if you would probably be very interested in something else. There have to be some other mechanism. Yeah. Yeah. So it's, yes. But that's what Jim was saying, that we should think about how to segment also the wireless part in this case. Because in the specifics, it only mentions the physical interfaces. And then you should be actually doing separation also on the wireless part. Because most of the things that we see now, most of the new sensors or the new devices that we see have an ESP, whatever that connects to the local wireless network. And then you have everything on one big segment, instead of having all separated. So yeah, we should also think about that. Do you agree, Jim? Yeah. I think there are largely ways to do it as well. Sorry? There are actually techniques to do it as well. Yeah. Yes. To go back to the slash 56, putting your right IPv6 at the C. Yes, OK. Although I'm not here officially for the right and C. When you talk to ISPs and they try and justify handing out 64s, what do you and your, I live in North America, so I feel the same problem. What do you all say? We have that in our region as well. Don't worry. But when you have these conversations with the ISP, what do you hear back from them? What is their rationale? Why are they doing this? Well, the reason mostly is that they, no. The reason is mostly thinking about a, and I can be form mindset. And thinking, oh, what's the smallest thing I can give them? Exactly. But then the counter argument is, look at how many you have. Like this small, if I remember correctly in the matter, the smallest allocation is a 36. And if you have a slash 36, we're talking about 2 million slash 56s. So no. It's a half a million, two to the 20, one million. One million. One million slash 56s. I mean, with the smallest allocation you can get, you can serve one million households. Where's the problem? I mean, if you have more than a million customers, or you plan on having more than a million customers, you can get worried. But we have a better argument in our region, because we hand out, the smallest one we hand out is a slash 32. So you have 16 million. And then without questions, you can get up to slash 29, which means 128 million. Why would you have to care about the single network you hand out to one of your customers when you can serve 128 millions? And we have entire countries with, say, 2 million people. And you're one of the ISPs there. And even if there are only two, then the two of you have a potential to serve 256 million households. Why would you have to be careful about what you use? What they're thinking is, yeah, nobody will need more than 640k. Nobody ever needs more than that. Yeah. Yeah. It's the same. You run with the same exact mentality. Isn't it? 24. 18 million addresses. Yeah? I don't know. May. That's exactly the same. Engineer. This is the truth, though, that when you allocate a slash, that's a 29, that you actually have another, that we can actually aggregate. You don't actually give spaces between. Yeah, that's what I. So in reality, then, that's not really fixed. And we do it out of, it's not written in stone. But whenever we, for example, you have a slash 29. And if you didn't get that way in the past, like more than 10 years ago, what we do nowadays, what we've been doing for almost 10 years, is sparse allocation. So basically, he got a slash 29, but we reserved three more bits. So if they ever come back and want to get more address space, we don't hand out a new subnet, but we just enlarge the one they have. So you left some continuous growth room. Yeah? Yeah. Yes. So but the same does adding, as far as I remember. I'm not 100% sure, but it's possible. Never estimate North America. No, no, no. Well, not saying anything. You're crazy. Not saying anything bad. Just saying we have different policies. I'll criticize North America. You don't have to. These room taxes, if you don't want to. Oh, OK, OK. It's a whole other country. It's a whole other country. We demand our slice of the IPv6 range as well. Yeah, no, that in theory you could. Actually, it's the last 29 we've covered. Yeah? OK, well, thank you very much. Thank you. Thank you.
about? Making your routers future proof. Why? two parts, and the two, yes. It's more configuration, that's what you want to have. networks should be and what services you should a series of protocols and functions to be used for Home networks to fully enable IPv6 and maybe addresses in IPv4, although they have a totally resolution inside your small network, because into? Bubble, internal routing protocol, very node consensus protocol, which is also called router internally, what I use is they use a I can also create a loop using wireless if I for that network. Or I will get a router an address in there. And in the OpenWRT You can run home net also only on IPv4, but that especially in SOHO environments. And why can't we implemented by now. So what do you have? You have should do that, based on the priority, based on because it will enable all the IoT, all the new different sources. And you install both of them. any understanding of a network virtual full talk to these devices. Yeah. Yes, exactly. What I at how many you have. Like this small, if I have a better argument in our region, because we more than 10 years ago, what we do nowadays, what