I was surprised for you today. I'm I'm spoiling you. It's all about you I have a lot of things that I have planned for you today I'm gonna show you guys what I have set up so far. All right, baby.   Okay? She said that today was gonna be the day that she made up for that because yesterday she pranked me But I've been sitting in a room for Lily an hour. I don't know what you've been doing for an hour There is something but okay, just today. I'm spoiling you. It's all about you I have a lot of things that I have planned for you today. Wait, you promise me. There's not a prank I promise you kiss it. I promise. I promise. This is all about you I want to tell you guys I'm feeling better. I'm not as sick, but I'm still sick so I might sound congested So I'm still gonna be staying a little bit away from Mariah, but not too far. Yes I can't be too far away from her but you guys before we get on to this video before I show Bill his you know Epic surprise that you know, we have been waiting for for the longest time It's something that you've been wanting and you've been they like we need this we need this give me ideas Okay, well since he has no ideas give this video a big thumbs up if you guys haven't already go down He does subscribe button join our mobile family because you do not want to miss out on any single one of our videos So bill actually just saw the box out here. Is that the first surprise? The first remember come here. Come here. Nope. Don't play that game with me This video is all about me and multiple you said multiple surprises I can't like kiss you or touch you, but you said multiple surprises So more than one because you're making up for prank Okay, wait, so I can just suggest Okay, so you think about your lunch, okay, but before that I'm gonna show you your big surprise So guys dream tech came in clutch once again Are you not gonna get your surprise just shout out to dream tech for this epic as you guys can read right here What this is bill and I have been dying for one of these so we have the robot dream tech vacuum Which is a little robot thing, which is absolutely amazing. So all right, baby I'm gonna show you your epic surprises. What I've been setting up Because you already set the name open your eyes.  Don't touch me quick Come on. Why I'm gonna use a vacuum in me. I want to use the back the back Yes, I set up. I put it in the wall everything.  Can you give me some props of okay? I'm surprised.  No, you hold the camera. I want to use it. Are you kidding me? Oh, okay, I'll be careful. How does it seem to work? Try it out. There is this thing is actually that's so freaking cool They have different modes. Oh, whoa You can like change the setting. Oh eco-mode medium. What's turbo? All right, we're gonna end the video here.  No You have no idea what it's like getting a cordless vacuum compared to us having a normal guy's Having having to plug in a court because it's so amazing.  No, I took this out of your room actually what I got Okay, no right here. It looks like it's a little messy right here. Oh, yeah Oh It's a crack on the tile by the way Some of this is like look at that. It's back into dogs. So oh my god. How do you love it? Look at all this that was just from right now. That's all snaps for that's why I don't get a cat guys Or anything else get a cordless vacuum from dream tech also because look at this It's carbon fiber, and I love the color matches our color so well So shout out to dream tech for coming in clutch once again Again, I think the two main things that you need in a house guys is a robot vacuum that we got from them Yes, and a cordless vacuum because you need a regular vacuum when you have like normal mess ups And then the robot just comes in the clutch afterwards This is the dream tech t30 cordless stick vacuum I will put the purchase link down below with the code Mariah, which I'll put on the screen right here You will be getting 10% off on your purchase. Oh guys go get this now. This is absolutely insane I can't believe you guys see how much dirt they picked up Hey, all I can say is thank you dream tech for my first surprise of the day Yeah, I'm ready to see what else okay, but really what do you want for lunch? Oh Pick it's your day. Oh, it is my day Really think and figure it out and we'll be right back Okay guys so bill is outside as you guys saw the title in the thumbnail I have a huge surprise for him at the end of today's video. Um, so make sure you guys are watching all the way through I'm really excited to surprise him with this because in our apartment He always wanted us to do like a bubble bath and stuff like that so I'm going to give it for him I'm gonna surprise him with it So make sure you guys are watching all the way through bill actually did just pick out a restaurant So we're gonna show you guys once we get there. All right guys All right guys All right guys, we just made it to our destination. We're going to this burrito place It's calling an off-brand of Chipotle. I wanted something else, but Mariah didn't want it I just didn't quit cuz I have a I was surprised. I'm really anxious and I was really want to get But this is surprising me for the day Okay, but anyways, I actually really do like burritos and it's like a Chipotle But it's not it's better than Chipotle. Honestly in my opinion.  You want to go to Target? Yeah, I'm gonna go to Target. I have to get a few things. I also get makeup. Yeah What is it? It doesn't matter, we'll see. Okay, can you just give me something so That's it. All right guys, we'll talk to you later. Wait, no So guys it is pouring rain. So we had a hurry up and hurry back. It started raining and we were in Target Like holy crap. We saw the lighting out the window and we did we were like we gotta go So I have a surprise for Bill. I don't know if you can tell what it is, but it'll be arriving at 245 I'm gonna whisper it to you guys really quick. I'm gonna whisper it to you guys We just ate. Is it dessert? He really wanted one so I got him some. All I know is I hope it's dessert because It's going to be here in 25 minutes. So we just had burrito.  I bought after safe just hold tight. I know Did you guys?   Yeah, so we're just decided just to come right home and Surprises early, but I'm getting ready because she says the main surprise is here So I don't know what she's doing, but apparently the main surprise is in the house and Wait, so can you do that after the one comes in that you ordered yes But I'm gonna need you to get I'll give you a little hint. I need you to get into your swim trunks Nice, I'm gonna swim in in the rain I feel like that'd be kind of fun We're doing something and it's been very special and romantic. Okay. All right. Well, I guess I'm gonna go get in my swimsuit And we'll see you guys a little bit. I can't wait. All right, let's go. All right, baby Guess that the front door. Oh dear here. What is it?  I'm coming over. I'm gonna set up the camera Hold on. I'm saying the camera. There's stuff in here that's surprising you with all right. I want my surprise.  Well, it's your decision to film this video I know what it is open it open your eyes. Okay, it's because you got that over Coconut milk, this is not a sweet cream cold. I don't think that we're supposed to add it.  It literally tastes like straight milk. Mmm. Not gonna lie. This is still fire though I'm fine with it. Okay. What is this? I was actually gonna say I didn't want any like food or anything, but this is a perfect little this is like dessert I know yeah, I was gonna get you this sweet cream cold foam, but I know you don't care for that It's actually really good. It's just if you get paintings guys. This is not what a painting looks like it looks more pink But this is more white Yeah, let's go we're gonna eat this right now I am just gonna rush over to the surprise because I want to see it and Mariah said it's a huge and it's gonna be hot So we'll see I don't know what that means, but we'll see like it. I got my strong chung-chung guys But sorry you the hot thing because you're looking hot right now Snooom a status them it has never been average in the Senate You can't even see ready my dance for you. Okay. This is the show No, it's not because I'm in my so much right. This is the surprise. Yeah, I told I have to make a fake Guys, please come down below ten out of ten for Mariah, I want to see those comments down below right now Oh The hell is that? No, we know What's up some ballerina Why are you actually a ballerina?  Yeah There we go. All right. There we go. There's not a surprise. You got me like two of jobs for what? Actually This video is for me not for Mariah, so if anything you should be giving me money You praise me yesterday.  I don't know why just sitting in the water like freaks me out I seriously don't know why but I don't like them But I know Bill always wanted to do like a bath And so I thought it'd be like a romantic thing to kind of have a bath You know since he's not feeling good. I think it's cute. So I did get in this bath bomb I know it's growing but obviously Ariel But the blue or the green and the white looked so dope and never actually tried a bath bomb before something Kind of cute and then I got some both with a bubble bath So it's like bubbly and then of course I had it to get some wine Cupcake wine sparkly rosé and I got our little glasses So it's kind of gonna be a little like romantic type of feel I'm really excited to get his reaction. I'm gonna call him in here and Tell him what we have in mind. Are you ready? Yes, I am done done I showed them all the squad the floor and got what are you? Why are you hot? I have to show you how good the camera looks. You were getting so close to our face No, wait, what's that? What's that? Tick-tock? Hold on before you even show. Look at how good the lighting looks All right, baby. Come on In the bath, yeah, I know you've been asking to take a bubble bath with me for the longest time So I thought it's a pie.  Never she hates baths. So oh, I hate them I don't know why it just I don't know why it freaks me out But I feel like there's gonna be like bugs in the tub I know the greatest even though you're feeling a lot you're feeling really good today I thought I'd give us a little bubble bath. So I got you never tried before but I got you got you a bath So I got two different types of bubble like for fizzers. So I want to see which one Yeah, I think this was this is like this is called champagne. So it matches our champagne. That'll be dope Cool, let's get where's the water? I gotta fill it up first So I have to wait for you to fill it up This don't look like much about bath. Oh my god. Okay. Is there any bugs make sure no spider Make sure don't spider around here guys. I'm like freaking out. I don't know why bounce freak me out So we got the whole bath tub filled up and let me just tell you it literally took like 20 full minutes I don't know why it took so long But hey, we're here the bathroom's filled up and we're gonna throw in this bath Me neither. I don't know what it even does. I know you put them in there and they dissolve But I really I've seen them, but I forget what they do. I know they dissolve. All right, ready Oh Volcano no, I Know I think some of them maybe like the the lighter ones This one's like big so it was all you can see it way better than the camera Yeah Is it floating?  Yeah? It's just a ring. Hold on Will you marry me?   That was inside the bath bomb guys. That's actually funny. All right. Now. We got some bubble. It's actually really hot I'm not naked guys I don't know how hot it was babe I told you thought I was Tripping he literally thinks everything is hotter than it actually is It's better when you get in there. No, it's nice. It's nice now. Look at all these bubbles. I don't need more What does this do foaming bath? Oh, we have to try this now. Wait. So is this the main surprise? Is this the main surprise? What? Oh, it's actually really relaxing. I know right? I wish our bathtub was bigger Well, whenever we get a new bathtub, we'll definitely have to get a uh Bigger one. Oh, there's gonna be 10 different smells in here Uh-oh, do you even know how to do it? Do you want me to do it? My hands are gonna be slippery. I've never done this in a bath. I've only done this once. What was the colorado? Um, that was for when we uh hit a million. We hit a million on youtube.  This would be so much easier if I had uh You know non soapy hands, but don't try this at home guys. We are professionals. How's this gonna work? Point it that way. Why? Don't point up at the ceiling. You're pointing it towards me. Babe stop What you're literally pointing is where it's me. I'm gonna point it this way.  Are you ready? No, no, no. Okay, wait stop for something. We have to toast or something. What are we toasting to? I don't know. Hit a 12 million on tiktok. Oh, we just hit 12 million on tiktok We also are at 1.4 million on youtube. Aim at toast. Thank you guys so much for everything We're toasting to our mobile squad today and for this surprise because this surprise is awesome ready? Huh, what did it hit? I have no idea. Oh, this is not how you pour champagne by the way. Oh, that was intense Right, can we cheers? Yeah to the best surprise and for eternity for eternity Descent right We need more bubbles in here.   Wait, what do you mean? It doesn't matter. It doesn't matter. We gotta shut off the cameras, you know Oh, so that's that's the surprise part. Give me in the back. Okay. Give me in the back. Give me some champagne And that's one of the fun release Guys I okay knock on the library. Thank you so much for making up for pranking me the other day Doesn't make me feel any better because I'm still gonna prank her as for everyone that's going on my instagram And giving me prank ideas. I have been looking and I have been responding to some of you guys So make sure to go follow me on instagram DM me some prank ideas because I might look at yours. There's a lot to look through so if I get to yours I will respond. I might do one of your pranks. Oh my god.  I'm just getting over being sick But I do feel a lot better and for all of you that were hitting the like button or recent video You guys literally I've done yourself. Thank you so much for everyone that liked the video Make sure to like this video as well And make sure you guys stay tuned for our marble vlogs now. We're gonna be filming a little q and a on that channel right now Yes before or no after before after the fun part. Yeah, which one?  I guess we'll have to find out. Make sure to subscribe to our second youtube channel Marble Vlogs and we will see you guys in the next video. But until then


Hello, good morning. I'm Irene Diaz, a software engineer at Red Hat. And this is my colleague, Sarita. Hello, everyone. Good morning. And thank you for getting up early in the morning to come for our presentation. And today, we are going to talk about two onboarding options, that one with ignition and other being FDO, and other being ignition for IoT devices. So this is today's agenda. We are going to discuss what is onboarding in broad terms. Then we are going to present to you what are the options that Fedora IoT has for onboarding, as well as future steps on what is coming up for Fedora. So what is device onboarding? What do we care and so on? So device onboarding happens after we make an image, provision it, and then we have to give the devices all the configurations and secrets that they need in order to perform its final need. During this onboarding process, we also hope to get a connection from the device to the final IoT platform. The platform is what the device needs in order to get updates and some other software and so on. This whole process, of course, needs to be secure in its steps. And there shouldn't be a need for human intervention, so the whole process would be hands off. So if you can imagine, if we are trying to onboard a thousand devices in the middle of a mountain, an engineer cannot be bothered to go to the onboarding side. We simply need someone to ship the devices over there, power them on and everything else would be automatic, secure, and no need for human intervention. Fedora has two different options in order to do this, so Salida is going to give an overview about them. Yes, so let's get a brief introduction to these two options. What is FDO? It's basically FIDO device onboarding protocol. It's an open industry standard protocol developed by FIDO Alliance. FIDO Alliance is basically formed by a couple of tech-leading companies, such as Intel, Google, and many to name. A little bit of history to FDO. FDO was initially known as SDO, which is the secure device onboarding developed by Intel. Later, it was contributed to FIDO Alliance to become FDO with the announcements. Whereas Ignition, it's a part of Koro's ecosystem, which is internally developed by In-House and Red High, and maintained by a group called Koro's working group. The basic difference between the two options, I think it's in their infrastructure because of the distributed nature of FDO, it requires a proper complex infrastructure, maybe a server-side and the client-side implementations, which we will see in details later. Comparatively, I would say Ignition has a simpler infrastructure, which basically revolves around one configuration file. Although this configuration file, it can be linked to other configuration files, which will be merged at the runtime. That's the basic difference, but we'll see the more details as we go ahead. So how do FDO and Ignition fit with Fedora IoT? So in order to make a Fedora IoT image, you would be using Image Builder. There have been previous talks in this conference about what is Osbley Composer, Image Builder, and so on, so if you haven't seen them, I would recommend you to check those other talks. So you would use a blueprint in order to make a Fedora IoT simplified installer or a raw image, then use Image Builder to produce that image. And then, once the image has been provisioned, you would use either FDO or Ignition, probably both at the same time, and at first boot, the devices would be onboarded. And Serita is going to explain a little bit more about Ignition, about FDO. So let's see some of the key features of FDO. The whole idea of FDO, it works around providing maximum security during the end-to-end onboarding process. So of course, the first thing comes is no manual intervention, there comes a zero touch, where are the maximum possibilities that security threats can be there. FDO works by the principle of establishing a chain of trust. To explain this a little bit more, I would like to go to the next slide, where we have the whole, this is the FDO protocol, which is going to tell us about in a bit, about the flow and how it works. But a few of the concepts to explain the chain of trust. So FDO can be seen or divided into two phases. One happens at the device manufacturing site, and the other, it happens at the onboarding site. So at these two phases, they can be in different timelines. So there has to be security in terms of its ownership, which is provided at each step. The ownership of the device, it can change during the whole time, a number of times. So apart from this, one of the features that's most spoken about FDO is lead binding, which solves a lot of problems related to onboarding in the industry. So what is lead binding is, so when the device is manufactured, device does not know that which platform it is going to get onboarded, or the configuration that it is going to onboard it with. This can be decided at later stages when the device actually goes to the onsite and that's when this feature allows flexibility in terms of device management, which is very useful. And yeah, that's the feature. And apart from this, FDO has other features such as reliability in terms of, if there are a number of devices, every time FDO works, it works the same way for all the devices. And even though the protocol is pretty complex for the end user, it's very simple to use. Even a simple worker can power on the device at the onboarding site and doesn't need to know what happens inside. It is platform independent and cost saving, I would say. I mean, the infrastructure does take, is expensive since it's complex and it has hardware software requirements, but it's a one-time job and it saves a lot of manual processes and even simplifies the errors that could possibly happen when a traditional manual onboarding is there. So yeah. So now FDO, in a little more detail, Sarita said there are two places where the hold onboarding process happens. On the left side of this slide, you see the device initialization part which happens at the manufacturing site and then we have the on-site onboarding part. So during device initialization, there are two entities that are important. First of all, the device and then the manufacturing server. The device would contact the manufacturing server in order to get a good ID and two different, I guess, documents would be generated. One are the device credentials will be hosted in the device and those device credentials tell the device where it would find the rendezvous server later on in the process, which is on the onboarding site. The manufacturing server would get an ownership voucher. This ownership voucher is a cryptographic document and using that document, which is a 509X certificate, the FDO protocol allows you to verify that you are the owner of the device at the current point in time. So in this point in time, the owner of the device is the manufacturing server. The onboarding is still going on, so the device would be moved to the onboarding site and meanwhile, the manufacturing server would transfer this ownership voucher to the owner onboarding server. So that right now, at this point in time, the owner of the device would be the owner onboarding server. As you can see in these lights, the communication starts, I mean, the device contacts the manufacturing server. That is what the arrow means, but the connections are uncertain and so on. So the device reaches the final point and then the owner onboarding server would transfer this ownership voucher to the Rendezvous server and in the Rendezvous server, we would have a mapping from a device UID to an IP and that IP is what the device will let it on use to contact the owner. So the device finally reaches its final step and it would use the device credentials in order to find where its Rendezvous server is. So it would contact the Rendezvous server, the Rendezvous server would check if that guy UID makes sense to him and if so, it would tell the device where its owner is. Then the device will contact the owner, they would establish a chain of trust based on the keys that the device has in its device credentials and the keys that the owner has in the ownership voucher. The owner would transfer some keys to the service info API server and the device would then contact the service info API server in order to do these final onboarding steps which is where the device would get all the configurations and keys that it needs in order to work.  So as we said before, in order to build the Federal IoT image you would need a blueprint. In order to use FDO, you need a simplified installer blueprint and the only thing that you need to add to this configuration apart from any other configuration that you might need is customization.fdo, I guess, part where you would place what is the URL to your manufacturing servers because as we said before, the only thing that the device needs is just an IP to get to the manufacturing server and everything else would be automatic from that point on. So we would use Image Builder. If you're using the command line you would run Composer CLI, Compose Start Over Tree and then the name of your blueprint which is a Tommel file. Then you would select the type of image that you need, any other further parameters. Since Fedora IoT is an OSC based operating system which means that it has a immutable file system, you would need a commit in order to fetch the file system and so on, so you would use that and then the Image Builder would speed Federal IoT Simplified Installer Image, which is an ISO. You would provision the device, it would boot and the whole process that we saw in the previous slide would happen and the device would know what to do and so on. So, but I mean, we are onboarding the device. How do I get the configuration and so on? The FDO standard has a normative part which are the service info modules. Its service info module is a configuration, I guess, module where you can put some atomic instructions and it works with a key value protocol. So in this slide, you can see that we have a couple of configuration things. This is a YAML file. So we can, for instance, establish an initial user. As you see there, I'm creating a user and giving it a password and some SSH keys. We can also move, I mean, copy files from the service info API server to the final device. We can run some commands. We can establish this encryption in a given this level and we can also specify if we want that the device wants to be rebooted after the onboarding process has happened or not. You have an URL over there where you can see which are the F-SIMs that the FDO Alliance is working on. Red Hat has a couple which haven't been published there but we are working towards making them part of the standard. And if you are interested, you can go to Federal IoT, FIDO, then by support RS because our implementation is in Rust in order to contribute or find any more information. And now with Ignition. So let's see some of the features that, what is Ignition, what it can do and how does it work. Ignition can be described as the first boot configuration tool, although it can be used for provisioning purposes. It basically runs in the NITRA-MFS at the first boot. The things that you can do with Ignition involves things such as configuring users, disk manipulations which you can create partitions and enabling the system deservices. All of these features, they are supported by CoreOS but Federal IoT only supports a part of Ignition. So not all the features that you can do with Federal IoT will see in details what Federal IoT can perform to. And Ignition's configuration file, basically it's JSON document which can be embedded inside the ISO or it can be kept at a remote location where it can be fetched during the onboarding process. Ignition follows a declarative pattern. That means Ignition knows what stage it is going to be rather than how to do those things. So for example, if it's going to get some disk manipulations done, it knows that it has to partition the disk or what to do, but the how to do part, it gets it done by the OS, underline OS tools and utilities. So Ignition doesn't have to worry about how to do part. The nature of Ignition, it promotes immutable infrastructure, meaning that the configurations once provisioned or after the first boot cannot be changed. If user needs to do some changes in the configuration, reprovisioning has to be done. This part is a bit expensive in terms of reprovisioning compared to FDO, if after updating configurations at runtime, new configurations can also be applied. There is no need of reprovisioning the device. Also the automatic configurations are deleted once successful provisioning is done from the VM data which is useful because the sensitive information is not accessible once the device is provisioned. It does support STTPS and config verification that's a useful tool too. So how would you configure Ignition in order for a device to be onboarded? As Alita said, you simply need a JSON configuration file. The current version is free for zero. And as we said before, in Fiber IoT, we don't support all the features that Ignition has. In our case, we enable file links and directories creation. We also can create system units, users and groups, as well as the other Ignition metadata configurations, such as retrieving a remote file and so on. As you see there is a JSON file and this might cause a problem because as you know, JSON files are not human friendly. So in order to avoid using JSON files, you have butane. So butane is a source to, is a transpiler which is a source to source compiler. Butane would take a butane configuration file written in YAML which is more human friendly and then you would use the butane transpiler in order to get the JSON configuration file. And why would we, I mean, why would we do that? Because while we are transpiling one configuration file to another, we would get any, I mean, we would get warnings if there are any errors. And we also check based on the variant that we are defining over there. I don't know if you can see it, but we are using the RedForge variant. If the options that we are given to the butane configuration file are supported by the variant that we want. And yeah, currently the RedForge variant is on version 110. And we are targeting Ignition 330. Yeah, so some examples. If everything goes well, you would run Ignition as shown in the first example. And butane would speed a JSON Ignition configuration file. In something goes wrong. For instance, in the second example, I forgot to establish an install section in the unit. So butane would tell me, hey, we've got an error there. And if I'm using something that is not supported altogether in the bottom sample, you would see that butane would simply give an error saying that, hey, the file system configurations are not enabled for this variant that you are using. So how would you use butane in order to onboard that device? You have two different options. As I said before, you can either copy the whole JSON file into a section in the image builder blueprint. But instead of using JSON, you would have to transform it to base 64. And then if you want to do that, you would only have the option to use, I mean, to produce a simplified installer. So you would simply call Composer CLI, choose the image type that you want. For instance, the IoT simplified installer in this case. And then you would get the image. The other options that you have is to specify, as I said before, a remote URL with the ignition configuration file with effects at first vote. So if you choose to do that, you can either produce a simplified installer, which is an ISO or a raw image, which is a, yeah, compressed raw image. In the case of the raw image, you would run the command that is there and then you would have the image. In both cases, you would have to provision the device and then at first vote, yeah, ignition would work and the device would get onboarded. So after seeing FDO and ignition, you must be wondering which one to go for, which is the option. But to be honest, it's not the one-to-one comparison. It's rather two options that you can choose based on the project requirements. What security features are to be used in the project and, of course, the infrastructure. We are based on the differences between the two options. So it's up to the requirements of the project. And yes, the combination of the both can also be used together. For example, some of the features or some of the things that you can do with FDO and ignition or you can create the user part or disk manipulation or others that can be kept for ignition and the rest of the protocol stays with FDO. So some of the future enhancements that are coming with FDO, one of them being the service info per device feature. So what's this? Irina earlier explained about the service info modules that we have for FDO. Currently, what happens is all the devices get onboarded with the same configuration file. That's, we call it the base of the default configuration. But with this feature, it will be possible for the user to onboard different devices with different settings if they want service-specific configuration. For example, for SSH key, we have started with that. And if the user doesn't want the device-specific one, it still has the option to get onboarded with the default ones. Another thing is that we are trying to move to database storage. Currently, what we have is all the files, configuration file, which is ownership vouchers and the other configuration files are being stored at the file system, which is really not feasible when considering a number of devices. So database will be a good option. We are working on that. One of the things that we are trying to do is moving from VARP to AXEM. VARP is a web framework that we use in FDO. But it does not comply to FIPS. FIPS is basically a cryptographic standard that we use. And VARP internally uses trust DLS, which uses string that ring rate does not comply with FIPS. So we are moving to AXEM. And we are missing a bit on the left side of the slides, but forget us. This is related to the future of Ignition. So Ignition is developed by the CoreOS team. As you saw, we don't support everything that Ignition does. So we are working towards enabling a file system customizations after, I mean, during the onboarding process, because right now you would do that in the image building process. And we have aesthetic partition tables, so you cannot change that unless you change the code in OSB Composer. So yeah, all that you have been seeing right now, it will be coming for Fedora 38 as soon as we get back from this conference. That is the soonest part. Yeah, but it would definitely be for Fedora 39. Yeah, that's all. And we'll have to take your questions now if you want. That's all. Thank you. Oh, yeah. So we've been asked, where can we get those documentation or information? So, where? So, but I think that he's asking, where would I configure this? Am I right? Okay, we do have our documentation in the link that I showed you in the next slide. There is a file which is called the how to. You have examples over there in order to know how to configure this. And if you are interested in how the protocol works for our specific FDO F-SIMS because some of them are not part of the standard. Under the same repo, there is a docs folder where you have docs F-SIMS and you have the specification over there. If you are looking for the F-SIMS that are going to be part of the standard, which are the ones about the file copying, the commands and some other one that I'm forgetting about, those things are in the FIDO Alliance F-SIM repo in GitHub. Does that dance? Yes, yes, each F-SIM has a set of configuration things that you need to configure. It's not the same to create an user to create a file. So, for users you have, can I set a password? Can I set a SSH key? Whereas with files you have the options to set permissions and yeah, that is the difference. Each F-SIM has its own configuration parameters and so on. Okay, another one. So, we've been asked whether we... For ignition. Yeah, so... Let me check if I understood. You are asking whether we have thought about signing the ignition configuration file so that we know that the device would get the configuration file that it needs. We haven't thought about it to the best of my knowledge. So, we'll take up that with the team and with the CoreOS... Yeah, and we'll tell you when we have the opportunity. Are we good? Thank you. Thank you.


Ira Magaziner, thank you for joining us. Ira was from 1993 to 1998, a senior advisor for policy development for President Clinton. Vince Surf is always referred to as the father of the Internet. Someone once said, well, if Vince Surf is the father of the Internet, Ira Magaziner is the father of ICANN. Well, I suppose that's true in a way. It was an idea that I conceived of and then helped put into effect. How did it come about? You say that so simply, I conceived of it. Well, if I can provide some context. In 1995, President Clinton approached me and said, would you coordinate a team that could help set a plan for what I would do if I to be re-elected to help keep the good economy going that we've helped start? And I formed a high-level team at the White House and among certain cabinet agencies. And what I understood was that long-term growth really depended upon technology waves, in other words, major technology advances that then play out into economic progress. And we did an analysis that said, look, there are three major technological advances that have taken place, one being the Internet, the second being the sequencing of the human genome, and the third being renewable energy that could lead to long-term growth. And we decided the Internet was the ripest one to really accelerate economic growth, that the U.S. had been a leader in developing Internet-related technologies, and that what was lacking was a policy framework, a global policy framework that could be implemented, that could allow the Internet to take off. So we spent 1995, 1996 developing a paper on what would be required to make the Internet successful. And it included what we saw, I mean, it included efforts to deal with copyright issues, deal with digital signatures, deal with privacy issues, issues of censorship, issues of coordination, technical coordination, and so on. And what we found was that, in a way, there were a lot of people who wanted to invest in the Internet. There was a lot of potential in the technology, but it seemed very uncertain to them as to whether it was robust enough to handle all that investment that they wanted to put in. So for example, as you know, the Internet is coordinated by a series of servers. One of my first days in looking at this, I went to a couple of universities where the servers were in the basements, and I could walk in, I could just pull the plug, I mean, there was no security, there was nothing. I also found out, as I was trying to put together the policy paper of what needed to be done, that there were 53 lawsuits at that time challenging the validity of the Internet routing system in courts all around the world. And at that time, the IANA, the numbering system, was coordinated by John Postell at the University of Southern California out of an office that was treacherous to walk in. I mean, it was a small office you walk in and there were piles of paper everywhere and so on. And I gathered that at an early Internet society meeting when there were only a thousand people on the Internet, somebody said, hey, we need somebody to keep track of the addresses, and he raised his hand and there it was. And then on the other hand, you had Network Solutions, a company, and he did what he did under a DARPA contract, Defense Department contract, that worked solutions which coordinated the main name system of a company in Virginia under the U.S. Commerce Department contract. And the two of them didn't really get along very well. And there were all these lawsuits challenging his authority, University of Southern California was being sued, Commerce Department was being sued, and so on. So there was a very uncertain legal environment. I also was visited by people from the European Union and elsewhere who said we are concerned that this is really a U.S. government-controlled entity and we think your Defense Department and CIA and so on are controlling it and we're nervous about signing up to that. Members of Congress visiting saying this is ours, we invented it, we should keep it fueled by lobbyists who wanted to make sure that we kept it in a certain way. So there were a lot of these issues and then there was, I forget the exact name, the Moral League of something or other talking about all the Internet pornography and we had to censor the Internet. And then there were moves in Europe and in Canada and elsewhere to put a bit tax on every bit of transmission in the Internet. There was moves in the intellectual, among the international trade community to put up tariffs. There was debates going on about intellectual property protection and so on. So there were all these uncertainties that existed that were holding back what we thought could be a potentially huge economic vehicle for growth globally. So what we set about to do in an initial paper we wrote was to decide how to address each of these issues and we came up with policy prescriptions which then would require global negotiations to get signed up globally for this. And the ICANN piece was one piece of that. I had to handle the technical coordination and a lot of the lawsuits were about that. There were people with so-called alternate solutions and so on. And the U.S. Sea people wanted to get out from underneath the lawsuits they had and they wanted the government to protect them, the government didn't want to do it and so on. So basically what we did is we issued a paper in 1996 after Clinton got elected which talked about how to deal with each of these issues. And we went and negotiated a treaty at the international trade body to keep the Internet free of tariffs. We set up legislation to get the Internet of Tax Freedom Act, which would allow for no taxation on Internet sales. We got an international convention on digital signatures so that they would be recognized and negotiated that. We negotiated the copyright agreements, the global copyright agreements that could protect Internet investments and a variety of other measures that were all done in 1997 and 1998. With ICANN, that represented in some ways the thorniest problem because the Internet society felt that they should have control of that. There were other bodies, the International Telecommunications Union, who after 10 years of rejecting the Internet protocols all of a sudden decided they should take control of the Internet once it started to take off. And they had the weight of the U.N. behind them. And you had various other groups that all had conflicting ideas. And of course the people bringing the lawsuits. So what I thought about was that we need to do something new here that if the U.N. takes this over, it will take way too long. I mean the U.N. and also even the European Union wanted to have government set standards for the Internet. But yet the U.N. would seem like a natural place to go, right? And I respect the U.N. but it's way too slow moving for something like the Internet, way too bureaucratic. It takes 10 years to get something past the ITU. The Internet was very fast-moving technology. And what we had to do was, the very essence of the Internet was a decentralized medium where the creativity of everybody could create new standards, create new technologies, create new everything. And the last thing you wanted to do was make that all have to go through some bureaucracy to get approved, right? And that's the only way that the U.N. agencies can work. And they also have 100-some people at the table, right? So it would have been crippling for the Internet to have that happen. On the other hand, if you had the sort of anarchy that was going on where the Internet Society claimed this, USC had this, John Postel, this, that, and all these lawsuits, then that gave no protection. It was kind of like a wild west environment that people didn't want to invest into. And then you had various corporate interest groups who wanted to control things and so on. So it seemed to me that the best way to do this was that you needed something that could move faster than a U.N. bureaucracy. With all the different stakeholders in the Internet, you needed something that would be stakeholder base and more democratic in its approach so that people had the buy-in to it. You needed something that would be recognized by governments, and this was very important, because that would protect against the lawsuits. So you had to get the U.S., the EU, the Japanese, the Australians, others to recognize it. Yeah, you had to get a lot of buy-in. But you had to begin with that framework. And so we conceived of something that was the first of its kind. And when I first proposed it to people, they said, well, that's dangerous to do something that's never been done before because you don't have the precedence. But we felt it was the only way that we could really create something that could stand the test of time. So you were then thrust into a position of getting acceptance. Exactly. We basically went through a green paper and a white paper process, as you know. But in a way equally as important was, I set out around the world talking to different governments and different associations and stakeholders, corporate groups, trade associations that had an interest in internet commerce and so on. And basically tried to persuade them of this kind of structure, an organization that would be apolitical, made up of technical people. But stakeholder-based, everybody would have a say. Governments wouldn't run it, but they would have an advisory role and importantly they would recognize it. And that you could put that together in a way that could move faster than a global UN body, but still have structure to it and importantly enough resources. We had to make sure of getting money to it so it could defend lawsuits and so on. And of research and infrastructure to build the stake or the model, defend lawsuits and so on and be recognized by governments. So that was the task. Let me ask you this though. It's very unusual, the whole concept of ICANN, the bottom up philosophy of policy being formed from the bottom and working its way up to the board. Very unique. Yeah. How'd you come up with that? Why that system? Well, it seemed to fit the internet. It seemed to fit what the internet was. I mean, to some extent, I grew up in the United States in the late 60s, early 70s, when, in college in that period, when there was a lot of emphasis on student movements that were democratic and so on and I was involved in some of them. And it struck me that with something like the internet where you want to preserve the kind of creative chaos of the internet, that that kind of model could work. And in fact, it was the only thing that could probably work. And so even though when I first proposed it to people in the cabinet in the US and elsewhere, they thought it was crazy that you can never get somehow that to work. You need something that's more top-down, button-down, you know, organized, they would say. And I would say the last thing the internet needs is bureaucracy and it's gonna be much better if it's stakeholder-based and bottoms up rather than top-down. Even though there'll be lots of meetings and lots of debates and everything else, people will be bought into it and you'll actually wind up succeeding faster than if you try to do these big multi-government bureaucratic processes. And that, I think, turned out to be true. Was your model on Bill Clinton's mind or was he into other areas? No, he was into other areas.  And frankly, when he asked me to put together something to say, well, what can I work on in my second term? There was a list of things that the cabinet came up with, all of which we put aside, they were more conventional. And when I came back to the meeting and said, what I want to do is put a framework in place to let the internet take off. I think a lot of the cabinet people, who sometimes can be turf-oriented and we're looking at this guy sitting in the White House, what's he gonna do? When I said that, they said, I think, breathe this, I release the internet, okay, what the hell's that? I don't care. I'll let him go do that. And I think President Clinton saw the potential of it, but he wasn't really where he was focused. How about the Hill, Weimar? What was the reaction on the Hill, if any? So in the beginning, we weren't up on the Hill. Although we got delegations coming to us. Once we started to develop policy, we managed actually to develop bipartisan coalitions. For example, in the four major bills that we did on digital signatures, internet tax, freedom, copyright protection, and so on. I have Republican and Democratic sponsors in both. And in a period in 97, 98, when we were in the middle of the whole impeachment and Winsky thing, and very little was moving in the Congress, all of our bills passed with bipartisan majorities up around 70 votes. And I learned my lesson doing healthcare reform before, that you needed to build bipartisan coalitions early. And we did that, and so our bills passed. And I remember President Clinton asked me at one point, do you want me to put the stuff you're doing in the State of the Union speech? And I said, no, because if you put it in the State of the Union speech, the Republicans are gonna oppose it, right? They're gonna do it. I said, let's just care into the radar, do this quietly, and work on these coalitions. So you were more than content that it wasn't out there? Yeah, we didn't want it. And I mean, we weren't hiding anything, but we weren't looking for the public. You didn't want to draw fire. Yeah, exactly. So there were people, Republicans like Spencer Abraham who co-sponsored the digital signature on Hatch, who was involved with the copyright, Chris Cox on the tax piece, and so on. So we had bipartisan support, along with obviously the Democrats. So we managed to get those legislation through, and then also on the treaty negotiations. I mean, I spent a lot of time in Brussels and among the individual countries. And we were worried a bit about the Brussels bureaucracy linking up with the Geneva bureaucracy. And one of the things we did, you know, the president of the EU in any given year can overrule the bureaucracy on something. And the presidency was with Luxembourg, we were trying to get the key agreement with the EU. And so I went to Luxembourg, which people in the State Department said, what are you doing that for? And I said, well, look, they actually could overrule the bureaucracy. And so I spent a couple of days there. And for them, the internet was a great thing for their own economy. So they basically bought in and actually it turned out that when we had the final meeting on the negotiation, the president of Luxembourg, who was the president of the EU, overruled the bureaucracy and agreed to the treaty. So we had a lot of effort to kind of go out to countries. I went to France where they had the Minitel and there was a lot of resistance in France to the Minitel. And I purposely, the first day I was there, I did an interview with Le Monde at the airport. And before I went to see the French government, I said, look, you know, in five or 10 years, there's gonna be over a billion people on the internet. If 40 million Frenchmen are missing, nobody's gonna notice and you're gonna wind up behind. So that got quoted. And obviously they weren't very happy when they met with me, but it had its impact. And I think they realized that they couldn't go with their own if the internet was gonna take off globally. And so they basically eventually gave up the Minitel for the internet. Let me ask you this, Ira. Back then, back in 1998, was there any idea, did you conceive that the internet would end up being what it is today? It's interesting because we put out a paper called The Emerging Digital Economy. And it projected that what we call the internet economy could grow at 10 times the rate of the regular economy. And the day after we put it out as a publication of the US government, the internet bubble began. I mean, anybody who was under 30 that nobody used a computer could raise a million dollars to start a company. And the internet grew at 300 or 400% a year, then it collapsed. But if you look at the trend line over 20 years, it grew at about 10 times the rate of the regular economy, about 35% a year. So we did see that could happen. But I remember, I used to say, for example, that there could be a billion people on the internet in 10 years.  Actually, I was conservative. It was actually more than that by the time of time. And we used to talk about how much commerce there could be on the internet if we set it up right. And we underestimated, if anything. Even though people at the time thought we were being grandiose and we were overestimating. So yeah, I think we saw the potential. We saw the potential for, certainly economically, if we get electronic commerce moving. But also we saw the political and democratizing influence that the internet can have. And also that it could be a force for international cooperation. Did you get pushback in those early days over this idea of having a non-governmental entity take over the DNS or manage the DNS? Sure. I mean, there were people within the administration opposing it. The Japanese government initially didn't like it. The U didn't like it. And certainly members of Congress didn't like it. But what about within the administration itself? Yeah, there were people in the administration who thought that, I think some of you would say, this is a hippie-like thing you're trying to do here. And it's not proper governance and so on and so forth. And I just kept coming back at them and saying, look, you don't understand the internet. I mean, the internet by its nature is a rebellious entity, right? It finds its route around an attempt to control it. And its real power is that it mobilizes a vast number of people to do things which then can be adopted in a horizontal way. It's not something that has to get approvals all up the chain.  What you need is an orderly process. You need an orderly framework, a legal framework. But the worst thing you could do is take away its democratizing strength. So I prevailed in the arguments and I think, and there were others with me, it wasn't just me, but we prevailed in the administration and then eventually convinced other governments that this was the way to go. Let me follow up on that. So in 98, I believe it was 98, prior to ICANN, the meeting that you had in Reston where the white paper was under discussion. I've heard it characterized, Ira Magazine are basically, the white paper was there and he walked away basically saying, you guys work it out. Is that an oversimplification of what occurred in that meeting? A little bit. I went away but I kept a close watch and made sure that it would get worked out. And I think, again, if I had tried to impose from my office in the White House exactly what was gonna happen, that would have been antithetical to exactly what I was saying should happen, right? So I'm curious, did that ever happen? So after, ICANN's formed, right? So ICANN's there and functional. Did you ever have to hold back and say, was there ever an attempt by anybody, any of the executive cabinet departments or the Hill or anyone else to try and get involved? Yeah, but what I had done is we had two events at the White House where we announced the internet policy. And we had bipartisan representation there even during the impeachment. And enough stakeholders there so that they were part of it, including, I had the Secretary of the Treasury come, I had Secretary of Commerce come, I had the others come that were relevant. And so that everybody was brought into it. So the exclusivity was the buffer? Yeah, and the president was there and so on and so forth. And then we had the leaders in Congress who had participated on both sides of the aisle. So they were all there, kind of blessing the approach twice. And so the opposition didn't really have anywhere to go politically. So it sounds like you were pretty confident that people were gonna buy into the model. It doesn't sound like you had much to doubt that the model would take off. I wasn't sure in the beginning. I think by then I felt like we could sell it. But in the beginning, no, I wasn't confident. But I think I believed it was the right approach. And there were a lot of battles that took place in my office with different interest groups. I mean, there were hundreds and hundreds of interest groups, as you can imagine. And they all had their own thing and they all had some. Do you think history validated your faith? Well, you know, it's always hard to tell what the counterfactual is. I think so, and I'll tell you why. But if you look at all the growth of the internet that's taken place, not just the number of users, but the number of languages, Wi-Fi, mobile, everything.  And unlike the 53 lawsuits paralyzing things, right? You don't see that happening now. You don't see people holding back on their investments because they don't have faith in the security of the internet or the legal sound basis of the internet. So I think you've had something which has grown at amazing speed. Any democratic process in ICANN as one of them is messy. I mean, that's what they are, is messy. So ICANN has had its bumps along the way and it's had its frictions and it's had its fights and it's everything else. But that's democracy. But on balance, it's like the dog that didn't bark in the old Sherlock Holmes. I mean, the internet has worked. It's scaled up. It's done everything you would want it to do technically. It's not broken down in lawsuits or political disputes that have paralyzed it and it's handled tremendous technological innovation all along the way at a rapid speed. Now, would that have happened if we never did what we did? You never know. The important thing is it did happen, right? And so the internet is what it is today. So at the very least, we didn't screw it up, right? Let me ask you this. What do you think either during your time when you were involved with ICANN or after that period, what do you think was the greatest risk to ICANN? I think the greatest risk all along has probably been the risk that governments would come in and try to take control in a way that was beyond what was appropriate. And I think the other great risk is that, and I've said this to ICANN over the years, is that ICANN itself would become too much of a powerful bureaucracy itself. In other words, that it would accumulate too much money and too much power and so on so that it kind of, you know, meet the new boss same as the old boss, right? This is interesting. So expand on that a bit. So your concern was that it would become its own bureaucracy. Yeah, its own bureaucracy and its own power center. In other words, you know, it was set up to be democratic and to some extent a bit messy in its processes. And if somebody came in, especially as, you know, one of the benefits as you know is that the price of domain names came down significantly with competition which was part of what we wanted to achieve. But we financed ICANN independently because we didn't want it to depend on governments and so on by taking a little cut out of the domain names. As the internet exploded, ICANN got a lot of money as a result. And one of the things I've said to them over the years is you got to be careful here. You know, you don't want to start staying in, you know, first class hotels and flying your own planes around the world and do all this kind of stuff because people will start to resent it.  And as you become bigger, there'll be a risk of that. So I think that was a risk. And I think ICANN has sometimes gotten closer to that than I'd like, but it's usually pulled back mainly because the community has forced it to pull back. During this most recent debate around the decoupling from the US government, there were some serious tensions among different parts of the community and the ICANN board and so on and I tried to help out where I could. They asked me to help out. But with all that, and there have been governments who've tried to come in and including the US government and do more than they should, but with all that, it's basically worked, I think. I mean, it's, as I said, been messy, but it's worked. And the proof is in the result. I mean, the internet functions and it functions tremendously. Is it problematic for you that it seems like almost every year ICANN was called up to the Hill on either the House side or the Senate side to go to hearings? No, I think it's American democracy. I think it's appropriate for, you know, we have a congressional branch, it's appropriate for them to make inquiries and so on and I think ICANN should hold itself down. But does it make ICANN look subservient to the US government when viewed from the outside? It did before, but remember in the original white paper, we proposed that the US government give up the contract back in, I forget it was, 2000 or something. We proposed it within a couple of years and had the US election gone, I was gonna say a different way. Which election? 2000. I'm hesitating because it's still unclear how that election actually went. But any event, in 2000 when the administration shifted, if it had not shifted, if Al Gore had been elected president, I think what happened recently would have happened in 2000 and or thereabouts during those years and that's what we'd originally planned. So this is interesting.  What you seem to be saying is it was mature enough back then that could have occurred and the reason it didn't happen earlier was political. I think so. I think it could have been, I don't know what the right year is, but I think after three, four years, it probably could have matured enough. I think, but in any event, it's fine. I mean, it happened. And I think it's important that it happened. And that's why, when I left the White House, people reached out to me to say, well, would you get involved? And I can't. And I thought it was inappropriate actually because I had helped set up a lot of these things related to the internet. And I also had offers to get involved with internet companies and so on, because I knew the industry quite well, obviously. And even though I could have made a lot of money doing that, I thought it was inappropriate because when you've helped set something up and you've been in charge of helping regulate it and so on, while in Washington, I don't think you should profit on that by going into it after you leave. So I stayed away from ICANN, other than coming to an occasional celebration or if somebody wanted my advice. You know what you sound like?  Well, I thought it was appropriate to step back after the reasons I said. And I think when I was asked by the community or by the ICANN board to be of help on something, I did, but only if I was asked. Two and a half year period between when Strickling announced the desire to make the transition happen and when it actually happened. In that period, did you ever think it's not gonna fly? Oh, yes, I actually thought it might not fly. And I think the administration was serious about it and would make it happen on their side, but I thought there was a definite possibility that the Congress would stall it and as a result of interest group pressure and money. And in Washington, the best way to kill something is to delay it. You know what you say is not I'm against it, but you say I gotta study it more, I gotta do this, I gotta do that. And if it had been delayed too long into the election process or into now the new administration, I'm not sure that it would have happened. That's right, because the Trump campaign actually issued a press release saying they opposed the transition. That's right. And so when they asked me to get involved and I agreed to be on a technical advisory committee and help do some, I don't wanna call it negotiations, among different parts of the community and the board and so on, I was happy to do it. And in a way, I was sort of a non-threatening voice from the past, kind of neutral party who could come in and be there for a while to kind of help with discussions, but nobody saw me as any kind of threat of anything. And so hopefully I was helpful to them in doing it, but the main thing I kept emphasizing to them is you gotta get this done quickly.  You can't let the clock run out. And I think they came very close to losing it. What were your interactions like with Postel? Well, I can give you one story. I mean, initially he was very suspicious of me because I was the government. And I don't know if you knew John, but he was a guy with a big scruffy beard and sandals and the government came to town. But we got friendly and I invited him to the White House and because of the way he looked at me, about four hours to get him past security, but I took him to lunch in the senior White House lunch room and you had all these kind of very self-important cabinet offices, you know, secretaries and others having lunch. And I was sitting there with Postel and they were all kind of looking over at this guy with sandals and a robe. And I thought to myself, you know, 100 years from now, nobody's gonna remember any of these cabinet secretaries, but they are gonna remember John Postel as one of the founders of the internet. And- Did Postel himself think that? If he did, he never said it to me. I mean, I thought he was a very kind of humble guy. He was, and I was very honored when they invited me to come speak at his funeral and I got a proclamation from the president to give to his family. But, and I think I remember saying that, although it's tragic that he's passed, it's actually fitting that he's one of the first in the internet-founded generation to go to heaven, so now he can help keep the addresses for everybody when they come, you know. Let me ask you this, I heard one story and I want you to elaborate on it, tell me how much of it is fiction, how much of it is truth, that at one point John had reassigned one of the roots and that you had threatened to send marshals in to deal with this? Actually, you're conflating two different stories. Okay. And I'll tell you each one. I did get a call, I was actually in Davos, at one of those Davos conferences, and I got a call from, let's just say, national security, at the way of it, saying that they had observed that the internet was being rerouted and they were concerned about it and they weren't sure who was doing it or what. And I thought to myself, there's actually only one person who can probably do that successfully. So I made a call to John and then he was sort of evasive. It was about midnight in Switzerland, so it was early afternoon in California. But it became clear to me that he had actually done this on purpose because I think he was protesting some things that we might be thinking of doing. And so I called the president of USC and said, look, you know, we're gonna come down and you like a ton of breaks if you don't get this in order. He called John and so on and we got it sorted out. I had alerted the White House. The president was in a White House dinner or something and said, look, I don't think we're gonna have to do anything here, but just in case. So this went up to the level of the president? Yeah, well, the president's chief of staff, yeah. And, but then John said, okay, I'll put it back to normal. And he did. The other case that I thought you were getting at is that we did have an issue with network solutions at one point where they were walking at actually turning over some of the control that was needed to ICANN. And in that case, I did make a threat that we were gonna send federal marshals to seize the A-Root server. And that worked pretty well to get them to agree. It did the trick. It did the trick, yeah. So you raised an interesting thing when you were talking about Postel. Because of the timeframe that this occurred, there was a lot of distrust in government. Absolutely. I mean, we were talking the post-watergate. Especially in the internet community. It's a very kind of laissez-faire community, a very kind of. And that was at the root based on what you've previously told us. Those feelings sound like they were very much at the root, forgive the pun, or at the, in the foundation of ICANN. I think ICANN was one of the reasons why it was a model that could work is that a lot of the parts of the community at the internet society and elsewhere that were let's say more anarchistic in their tendencies saw this as preferable to having the government take over something. Although at one point, some people from ISOC had gone to the ITU to try to forge an alliance with them of some sort where ISOC, and that wasn't gonna go anywhere. It had to kind of beat that back. But yeah, I think ICANN did, it was a tent in which we could gather all the forces in the sense that a lot of the more anti-government people in the internet community could say, okay, well, there's not the government taking over. A lot of the governments could say, well, okay, we get this, but we'll have a seat at the table, we'll be there at the advisory board and we'll see what's going on. And if we don't like it, we can always do something different. And so it was a tent in which we could gather together what were a very disparate group of forces, because then you have the corporate communities and the corporate communities were very divided too. I mean, the internet gaming people were an entirely different affair than the high-tech community. It was developing technology at the time in the Netscapes and the Microsofts and so on. And they were very different than the big commercial enterprises that were concerned about trademark protection on the internet and so on. So you had, even within the business community, you had dozens of interest group factions that you had to kind of weave together. And there was a set of organizations in Washington, lobbying trade groups, dozens of them, that we had to kind of keep on board with everything we were doing. And remember, it wasn't just ICANN, we were doing the Tech Freedom Act, we were doing the digital things, we were doing the privacy, we were doing encryption, which was a whole separate thing because that brought in the whole NSA and the security community and had a handle encryption. And so we had to balance all these organizations' concerns on all these issues.  So it was a kind of exciting time. And after I had kind of dredged through failure in trying to put healthcare reform in place at the White House, it was kind of exhilarating to be able to take this and knowing that this was gonna be equally as important in many ways, equally as complex and global, but it worked. You know, when I asked Vince Cerf, I said, how would you characterize historically ICANN's relationship with the U.S. government? What he said to me was, I think it was difficult and problematic and not necessarily supportive. How would you react to that? I think if he's talking about the government writ large, I think that's correct. I think, I don't know if he was talking specifically about what we did, but Vince and I worked together pretty well, I think. And I was very supportive when he became head of ICANN. So elaborate, how was it problematic? How was the relationship between the USG and ICANN problematic? I'm sorry, are you talking about afterwards? Yeah. Oh, I'm sorry. I was thinking of the time I was there. No, after its formation. After 1998, ICANN is formed. His characterization was... Yes, I'm sorry. So afterwards formed, yeah. I was thinking of the period before we came into doing what we were doing. There were bills going through the Congress to censor the internet, to set standards for the internet, you know, it said, we beat all that back. But I see what you're saying. After ICANN was formed and I was out of it, I left the White House. And then you had the Bush White House. I think you had a number of people there that were more traditional in their view of government control of things. And so I think ICANN did have a lot of difficulty trying to keep itself alive and existing during that period when there was that more controlling and security-oriented group of people in the White House. Now, Vint would be more able to tell you about that because I was gone and that wasn't involved then, but I know that was true. Let me ask you this, Ira. You had mentioned your concerns about the affluence, if you will, of ICANN as its revenues increase and the potential dangers there. In the early stages, the White Paper didn't lay out a funding model. It left that to the community. Well, actually, we had in mind putting a small surcharge. Was that in the White Paper? Can't recall it was in the White Paper, but I know it was what we had planned. I mean, I have it in our planning documents. But was it for the community itself to figure out how that would work or? Well, the details of it, yes. But what we said is, look, you need your own revenue source. If you're dependent upon governments for revenue, you're not gonna get anywhere. And you can't be out with a tin cup collecting in Times Square. So you need a sustainable source of revenue. If, and I remember the memo I wrote saying, if the internet takes off the way we all think it can, and if, I think, I can't remember it was like $50 or $75 just to register the main name then. I said, if you bring that cost down, price down, which we expect you will. And then you take 50 cents off the top of each one and say, that could give you a sustainable revenue model. Another alternative is you could do something with commerce. There's a very, very small, almost minuscule charge. But I think we always envisioned that the domain names would be the best way to do it. And we discussed it at that time. We didn't impose it. It wasn't up to us to impose it. It was up to ICANN to develop it. But that was in the planning documents. Ira, in closing, is there anything that the US government, the executive branch, should have done differently in either the formation or nurturing of ICANN? Well, look, I think in the formation, I mean, obviously, I was involved. I think we did the best we could. Could we have done things better, maybe? But it worked. When you look at the four separate bills through Congress, three separate treaties, the formation of ICANN, all done in two years, that's pretty good by government speed. So I think, and the framework that we put in place in all those areas has stood the test of time. So I think I feel pretty good about what we were able to accomplish. I think Scott Cook once said, in a speech he made, I made the world safe for the internet, essentially. But I think, so I feel pretty good about that. I also think that the Obama administration, Larry Strickland, and so on, did an excellent job in bringing in the final step here of internationalizing ICANN. I think he had just the right touch of putting it out there, getting support within the administration for it, relating to the community, letting them develop it, and working with them, but sort of nudging a little bit here and there. I think he was masterful in doing it, and I credit him, as I do Steve Crocker and others that were involved with having it happen. Let me ask you a question that I posed to Steve Crocker. Was the stewardship transition a result of a bunch of things coming together at the right time? You had Strickland, head of NTIA, Fadi Shahadi, ICANN's CEO, and them interacting against the backdrop of the Snowden revelations. How important was this nexus of those three things, or was it not? You know, I can't say, I wasn't close enough to it. I think, certainly I think Fadi and Strickland and Steve and the others did a very good job with this, and I think there are a lot of, you know, the committees that I interacted with, the people that worked on those committees, I think did a very good job, and so I think there was a confluence of events. I think having the Obama administration there with a sophisticated understanding of the internet and of the need for it to be global in order for it to flourish, I think was very important. So I credit the White House for what it did in supporting Strickland and the Commerce Secretary and so on.  So, and I'm glad it happened. I think the internet is poised now to continue to transform the world in very positive ways, and I'm happy that I had some small role to play in it back in the late 90s. With that, I'll say thank you very much, Ira Magazine, I appreciate you talking to us. My pleasure.