 So GDPR, the General Data Protection Regulation, was passed by the EU in 2016, in May of 2016. It is, as Ronald was saying, it's four basic things. The right to privacy, the right to be forgotten, privacy built into systems by default, and the right to data transfer. It takes effect next year. It is already in effect. GDPR took effect in May of 2016. The enforcement penalties take place on the 25th of May, 2018. Now here's where there's two things on the penalty side that are important for everyone to know. Number one, GDPR is extra-territorial, which means that an EU citizen anywhere on the planet has GDPR goes with them. So say you're a pizza shop in Nebraska, and an EU citizen walks in, orders a pizza, gives them the credit card, stuff like that. If you, for some reason, store that data, GDPR now applies to you, Mr. Pizza Shop, whether or not you do business in the EU because an EU citizen's data is with you. Number two, the penalties are much stiffer than they ever have been. In the old days, companies could simply write off penalties as saying that's cost of doing business. With GDPR, the penalties are up to 4% of your annual revenue, or 20 million euros, whichever is greater. And there may be criminal sanctions against the charges against key company executives. So there's a lot of questions about how this is going to be implemented. But one of the first impacts you'll see from a marketing perspective is all the advertising we do, targeting people by their age, by their personal identifiable information, by their demographics. Between now and May 25, 2018, a good chunk of that may have to go away because we may not, there's no way for you to say, well, this person's an EU citizen, this person's not. People give false information all the time online. So how do you differentiate every company, regardless of whether they're in the EU or not, we'll have to adapt to it or deal with the penalties? Think about the principles that GDPR gives you. Look at that, I think. Some of these are just good data management practices and principles. It happens to be around personal data for GDPR right now, but those principles are just valid for probably any kind of data. So if you're on a digital transformation journey with all the change and with all the opportunity that brings, actually these practices and principles from GDPR, they should be helping drive things like your digital transformation. And for a lot of our customers, change is the only constant they've got. So actually managing all this whilst everything is changing around you, it's tough for a lot of them. How are people thinking about the data layer, where it lives, on-prem, in the cloud, think about GDPR compliance, all that sort of good stuff. How are you and Red Hat, how are you asking people to think about that? So data management is a big question. We build storage tooling. We understand how to put the bytes on disk and persist and maintain the storage. It's a different question, what are the data services and what is the data governance or policy around placement. And I think it's a really interesting part of the ecosystem today. We've been working with some research partners in the Massachusetts Open Cloud and Boston University on a project called Cloud Dataverse, and it has a whole policy question around data. Because there, scientists want to share data sets. You have to control and understand who you're sharing your data sets with. So it's definitely a space that we are interested in, understand that there's a lot of work to be done there. And GDPR just kind of shines a light right on it. It says policy and governance around where data is placed is actually fundamental and important. And I think it's an important part because you've seen some of the data issues recently in the news. And we've got to get a handle on where data goes. And ultimately, I'd love to see a place where I'm in control of how my data is shared with the rest of the world. GDPR provides for two types of things that a business must do. It must provide insight into the data that it's created, that it's captured about a business or an individual legal entity. And it must also then provide the processes for mediating or taking action against that data according to whatever the customers want. Tell us a little bit about that. So these are two important features because of GDPR. First thing, GDPR has 99 articles and 173 articles and 99 term technological ways. There are other ways, legal ways to do it, but technologically what they want. Like if Peter decides that I need to know from this bank or this social media company how much information you have about me and what are you doing with it. They have to provide that information in 30 days. That is called right to access. And the second thing is you can come and say, well, I'm not using these five things which you sold me earlier. I don't want you to use that information or even have information on that for me or my son or my kid. So you can tell them, delete that information or mask that. And that's all the right to? Right to erasure, right to remove the data. And these two things are very important. This gives customer, they make customer the king. They make the individual the king. He can say, tell me what you have on me and delete what you have on me. Now the laws have been in the books, at least in the EU for GDPR for a while. But the fines start getting leveled in May. Now we've heard that there... GDPR is a big thing for us and our customers and prospects as well. So we are actively working on getting GDPR compliant. Today our platform is FIPS compliant. So that's already a big stepping stone to getting there. So we look at GDPR in one of... in two ways again, right? One is the solution that we provide to our customers. The data platform and the data protect, as we call it, being GDPR compliant. Meaning the data that lands on that system, the ability to delete the data, the ability to say who has access to the data, role-based access, things like that. The second aspect is our support and the fact that, you know, we have access to a lot of customer information ourselves, right? The fact that, you know, we can, you know, look at their systems and make sure that everything that we do internally is also GDPR compliant so that the customers and our support systems and our Salesforce database is all GDPR as well. So both those elements come into play and we are actively working on all of them.