 Good morning. We'll get started in a few more minutes here. Hello. Hello. Thank you. Yeah. Hey, Tom. Got a couple of minutes here. Yeah, sure. All right, Tom, you ready? Yep. Sorry, let's make a stop. I'm going to share a screen. You can see. The meeting notes. Looks good. Okay. Announcements to start with that. So. There's a few people on the call. So hopefully the message was received by most. They're not saying time started yesterday in North America. And we'll be in two weeks in most of Europe. So for the, this meeting and next week's meeting will be. At this time, wherever you are, and then in Europe, it will be an hour later again. Which I think then means it's an hour later in the US. But to be honest, I get confused when I start thinking about it too. So anyway, so thank you to. I think the senior who's updated all the meeting invites. So moving on to upcoming events. We had a good chat through these last week, if I remember rightly. Has anyone planning on attending. Connected America, which is in. Two and a bit weeks. And we've got private 5G and the edge. Isn't that telecom TV as well? Yes, it is. So that's probably how they usually have virtuals on that. Yes, that's true. Good point. Then we've got in a month. Five weeks or so. Keep calling up some with. Planet to talk today, which is in person only. And they sold out. All of the co-located events are sold out. I believe the schedule for the talk today is now done. So I'm going to see that you were part of the. Putting together of that schedule. So thanks for doing that. And then. Yeah, maybe something to discuss in a minute is this. There's a further session in a bit more detail. Taylor's put together a bunch of good. Starting info for what we could do in that. So rather than it really each of these individually, I think most of these we went through last week. I guess, are there any changes to people's views, opinions, participation, et cetera? I want to go back real fast to the informal event. At the coupon. I'd like to encourage people that are. On the waiting list for cloud night of talk today. To come to the afternoon. And be able to be ready for birds of a feather. Possibly a shorter versions instead of a. You know, like a full presentation. They're not going to have. A big screen and, and my depth or anything. So it's going to be more informal. But if we can set it up. Where it's more like a real birds of a feather, if they want to, or at least a discussion about the topic. So some way to tie that in and get. Get the people that would have been there anyways to. Join us. I think that'll be good. Okay. Do you think we can use the. Collocated events team to. Maybe contact the people on the wait list and. Make them aware of this. There's a further session. And kind of share. I think we, we can at least ask them. So if we can take a little bit of time and. Figure out the. You know, how we want to, what we want to say and, and where to send them and everything. Maybe even. We could make like a Google form or something. And say, hey, if, if you're interested in joining us. We can. We can send over. To Google form or something and say, Hey, if you're interested in joining us for this informal thing and you had a. Topic to discuss, but something like that so that. We can send over. Here's what we'd like to do. For this informal thing. And, and then the team. If they're okay with it, they can contact them. For us. Yeah. Yeah, I just thought a couple of sentences here. So this Nikolai. Yeah. Haven't been joining for a while. So I'm, I'm one of those people on the waiting list. The problem is that the waiting list is for the whole. Collocated events. So you don't really. I mean, there's no distinguishments. Okay. I'm on the waiting list for telco day. That's, that's the way that I see it. I mean, I registered myself on Friday and. I don't get a chance to choose on which collocated event. I want to join. Anyway, that's one thing. I think is. If you. Control over schedule and you cannot. As an item. On the back of the schedule, like, okay. This, this, this, and then at 2pm, birds of a feather. Open discussion, whatever you want to call it. Short description. People might be interested. But I'm not going to, I'm not going to, I'm not going to talk about the official schedule. I'm not going to talk about the official schedule. I'm not going to talk about the official schedule. As far as the schedule, what do you, where do you mean? Are you talking about the official schedule? Yes. Yes. I don't think we're going to make it under the official schedule. So we're going to have to do. There's going to be some marketing that'll be needed. To let people know. Now. During cloud of telco day, we can communicate it. It's going to be an informal meeting. But I doubt we'll be on the official. Cube con schedule. I can try to ask, but I don't want to depend on that. Yeah, I mean, if you're booking the room in any case, right? I mean. Because you need the room, you cannot just do it in the hallway. I guess. Yeah, we may end up in the, you know, open meeting areas and stuff. Yeah. We're going to try to get a room. But there's lots of things going on. So if other than the, if you're not part of the official sessions, then it's more difficult to get a room. So this may be like an open area where we take up. But tables that are nearby each other. So I think we're going to try to get a room. And more of an open discussion. What was your. Topic. That's on the waiting list. Oh, you mean the waiting list for the telco day. Topics. I mean, like talks. Oh, okay. Okay. I was like on the waiting list for the attendee. Yeah. I also submitted something as a cost speaker with, with a colleague on the waiting list. Yeah. I don't remember exactly. I can check. All right. Anyway, that's, that's not, yeah, that's not done. Okay. Yeah. I think that the wait list. Taylor's talking about is. So for example, I presented, I submitted a. Yeah. Of course. They're on the wait list for. Yeah. Do you know if, if it will be an accessible area because, you know, there might be, you know, passes only. You know. So if you're not. All out there. If you have a coupon pass, then I, I think it's going to be possible to get where, wherever we'd be for then formal. If you're don't have a coupon pass, then. Yeah, of course. Yeah. You need to do the coupon. Yes. Right. So we would. And I, I think. Yeah. I think that Lucina had some ideas of, of a few areas that may work at the, at the place for like an open area. And we'll look at more into that. And then. If we don't have a set location, we're going to try to go to one of those. And we would be communicating that. And the, I think the. We're going to be, we're going to be talking about. We're going to be talking about the location of the location. On a workday. And then if we can. Decide on it. A few days ahead. Then we say that. And then just say, here's where we're going to be. But probably. One of the main things would be to decide. We're going to announce our location. On somewhere like. Posting to. Whatever that could be Twitter. It could be to the mailing list. If you're not on that. I'd get on the. Working group. And then we would just say, please meet here. And. And then, of course, during cloud night of telco day for any folks there we can. Attending we can message. But if you're on the waiting list for the co-located event. Attending. Not presenting, but attending. But you do have a all acts. You have a coupon pass. You have a coupon pass. You have a coupon pass. And then as long as you can see those messages, then you can meet up there. We'll do our best to try to get people. Available. And then. I think a Google doc for some type of. Topic ideas and. Potential. I mean, I guess it's a potential attendance sort of thing. So we can get a head count and stuff. But I think we need to run this like more like a. And then the. A real birds of a feather where the. Present. I don't even want to call them presentations. They're just someone's. Basically like you'd have a whiteboard and someone writes, here's a topic I want to talk about. And they get five minutes or 10 minutes or something. And then there's. Discussions about things. Besides our plan. If you didn't hear it weeks ago, we were saying. We may want to use part of this time as a working session to do. To dig into some topics like maybe we want to. Work on the C and CF glossary and adding more terms that are. Important for the telecom networking, pod native telecom networking. Or working through best practices that we pick or something like that. So it probably be split between an open discussions and, and some working session time. Okay. I have a related question for this meeting is. I mean, shall I wait for the end of the call and ask them or. Um, you can, is it, you said related as. Yeah, it's agenda item for discussion or just go ahead. I don't. Yeah, my question is more or less, do you have any rough statistics of. Like from the previous telco days is the how to say that the, the interest of like, you know, is it a rising, I guess it is, you just don't have visibility. I mean, I'm a reviewer on the networking track for the main cube, I have visibility there. But I mean, it would be interesting. At least my, my, my impression is that from the main networking. Track, like the telcos seem to be a little bit moving away. So they may be moved to this. Pre event like all located event. I don't know. It's just like, is there a big interest or this, I mean, is it rising? That's, that's done, you know, for, for people to present on telco days. I'm not sure I fully understand, but in terms of, so, so we, there were quite a lot of CFPs received for the telco day. Yeah. I mean, is, is the number of CFPs like, you know, significantly moving up, you know, compared to, for example, for the previous for the Detroit, for example. Yeah, good question. There's something we can ask. I can't remember what the number of CFPs was at the last two. No need for exact numbers. It's just like a trend. I mean, is it like going up or kind of sitting on the same? I don't know. It's just like a generic. Yeah. To be honest, I haven't really looked and thought about it. It seems to me to be either going up or staying the same. Okay. You know, I wouldn't want to put my name against that statement. But I think, I think that's a good question. And success factor. The, I know that the last one and also this one to an extent, there's a desire to have. A virtual aspect. The very first one we had both. I think that was helpful. The last one, there was a lot of requests in North America. I think the attendance would improve. There's still, there's a lot of travel restrictions right now. And there were, there were some. For the North America as well, but I think it's a, for a lot of people, it's even more restrictions this year. And there's people that want to be a part of it. But they're asking for. A remote. And I think we have a pretty good split between. North America. And EU. For. Telcom companies that are interested. So ideally for the. Cloud native telco day. EU. I'm sorry, for North America, we can get some sponsors and interests and they'll, we'll be able to offer the, the virtual event. And I think that'll, if we're doing, if, if we can get that and get some more sponsors and stuff, then it should improve like going forward as well. So if we have a better attendance, even if part of it's virtual, then I think the interest of that and then the value that people see will cause it to have more the next year. Did you find something Tom, as far as the. So, so there was some post event data that was shared after each. About number of registered attendees and stuff like that, but. Nothing I can see at the moment, which explained the number of CFPs. Okay, so for last year's Europe event. We received 43 CFPs. Wow. For this year's event. We received. 39. So the European one this year was 39. Okay. The US event in the autumn last year was 28. So 43 then 28 and 39. Okay. So Europe seems to be more proactive. Yeah. Yeah, that's interesting. So in terms of the informal session. Whatever, whatever you want to call it. So the, as well as the discussion we just had about people on the presenting waitlist essentially coming in. You know, starting a conversation about the topic they were due to present. There were these other. These other ideas that we discussed. I think last week. I wonder if anyone's got anything else to add to those things or any thoughts. We've mentioned about where it's going to be. That's to be confirmed. So just some, some, sorry, it took me a while to read. Yeah. So at least what, what I'm saying, I mean, I'm, I'm just going to share a thought. I don't know how to, how to exactly form or a farm. Formulate it to the exact topic, but it's like. I'm seeing at least from where I am. I'm seeing this, this trend where, you know, like we get questions. I was certified with this or with that. And I mean, to me, it sounds like the interest is forming its own. How to say it's certification in between the different vendors, like the major players are, you know, sitting together and saying, okay, I work with you. You work with me. I certify you. Certify me done. I don't care about CNCF or guiding principles or this or that. I mean, do we need to somehow at least talk about this or see what's, what's out there and try to enumerate what we know. Or I don't know you. It's like, you know, talking about competition, if you will. Right. Some of the, some of the. Submissions. And I'm not sure what the cloud native taco day agenda is. I need to read through. And I'm not a co-chair or a committee member on that. But I know that some of the submissions that people were talking about were related to things like Silva. The etiquette. Project from elephant and. And other things out there. So it's. That's happening there. And we're definitely looking at things and encouraging people to join in. And talk about them. So. If do you know of others like nephew? Silva. Elephant etiquette. Those would be. Other. Groups that are working on similar things. Do you know of other ones or is there anything in particular. That you're thinking about. Yeah, I would point out open shift, just like, not, not, not as a finger point, but like there's something that sticks out at least. I mean, like when I've been interacting with. Different customers and vendors and so on. It's always like, Oh, by the way, do you work with open shipping? It's like seems to be the baseline for a lot of. People out there. Right. So I don't know if this is exactly a. Like, I mean, if you can compare it to nephew, for example, right, but, but. It's. Yeah, I think it's a great question. I think it's a great topic to discuss it. The kind of informal day, but also. There is a. Yeah. There is a panel session. Which is about project silver. So it may be focused on. Kind of environmental things. Yeah. However, one of. One of the things that some of the participants in silver are quite keen on is having a better process for. Or a better approach to. That interoperability certification. And I've no doubt that operators will have. Opinions they may or may not be willing to share. As well. On, you know, on the applicability or usefulness of. The various approaches that have been taken over the years. And yeah, I think it's a great discussion because it's. It comes up every couple of years, you know. Elephant tried to do it with. Was it called. P was it or something. Then I could try to help with law, you know, with that. And now silver. I think it's the same, same problems being. Tackled from different angles. Maybe it's something. That kind of. Kind of falls into one or both of these points here. You know, almost like. The CNC, CF certification topic. Kind of wider question about. Certification in general. What we can tell. Red hat seems to have a. Certification. Well, it's called CNS certification. So they have the platform. Testing where you can run. Open shift on your own, or you can run their cloud based stuff. So that you have. More of if you're running the platform side as well. And then they have a. The batching as well as a set of tests. In it. They have. A large portion of it. I think it's probably the majority, but I'd have to look through the whole set of tests. I posted a link to the GitHub and zoom chat. But the. A large portion. Was. They were in the CNS certification test. Were used. They were, it's re-implemented. It's a different language, but. Coverage for the same set of tests. And. Most of them, I would say are generic. With maybe little bits that. Are. Potentially some of those tests are a little bit different. But I think it's a little bit different. To be open shift specific. And then the other set of tests are not that are not. Essentially. Copies or. Reimplementations of the. CNCS. Versions are. Open shift. Best practices. So if you're doing this on an open shift platform, here's the things that you should. Do. Do good things. I would say that that's a positive. That if we're leading. Here's best practices and here's tests that we're doing. If others are picking those up and trying to utilize them. It can be. You know, red hat is going to make sure anything works. Really, really well with open shift. Project. Silva under the. Linux foundation Europe. You know, there's. There's something there that. There. I would say. They liked what was happening. Potentially. This is my view from the outside. They like what was happening in the different areas like. And the. CNS certification and the best practice that we're doing. And they wanted something else. I think Tom, you might have some. Potentially some input on, on that, but there's something that was missing. Or they wanted to add something or. When, when there's a four or. A new product that comes out when there's an existing one that's similar. But not, it's not an exact copy. Then there was something missing usually. Of course, there are just straight up copies of. You know, even physical hardware. Or someone. Reverse engineers, everything. And just tries to put out a competing product with no differentiation. I think for. Anarchy. Silva. The open shift stuff. There's. There's at least for part of it. There's things that are. Missing or they, they want it to go differently. So. That's why you have. Others. But maybe. There's probably a lot of room for discussion around. What was missing and what do you lack over here? I know the nefias. Thing was be. Who's focused on helping with best practices for onboarding. Deployment and all of that sort of thing. And. I was hearing that for the CNF working group, the test suite, the test bed, all of the stuff that we've been doing for years. Like where are the best practices that are going to help with onboarding? And. I think that's why we're seeing projects like nefio that are going to help us get ops and what we've worked on. Other people are doing as well. Okay. Maybe it's worth. Move this down. There's a. Central but other. You know, start making a list of other topics that might be of interest to the community like this. Okay. Anything else on. On this informal. Stay. Okay. So. Let's have a look at the issues and the PRs. So open PRs. And. Is a PR open. Do not run contains with a privileged flag. Okay. There's got loads of approvals. I think we can. Merge that any objections to me. Merging this before approvals. Okay. So. Rather go through these one by one. Is there any update on any of the issues in terms of people. Newly assigning themselves to something or working on something. Well, in my case, I started reviewing the. Lightness. I think it's a lot of. Proof. 251. Issue. Yeah, I think it's. There's a lot of. Things to maybe discuss there. So I go to take a look and to the Google docs. There's a link on the bottom. And do we have any full requests that we can close out before we dig into the open ones? Oh, well, yeah. He just show the other one. Oh, sorry. Yeah, no, there's the only the one open. Oh, great. I didn't see the. The other one got closed out. So we, I don't think that we. One thing to remember that I, I didn't do. I don't know what to do and hopefully we'll do on the next one. Victor, whoever. Update the. Best practices for dev. Document to. Add a best new best practice into the document. So if we've, we've just accepted the. Privilege flag best practice. But it's not in the. List of. List of practices. We just have the document in the docs directory. So ideally going forward. And maybe we need like to update instructions. If you're going to do a pull request for a new best practice also added into the. The dev document. Does what I'm saying make sense. Yeah. In that way we can have references. Yeah, I'd like to be able to. Point people. Hey, there's new best practices that were just published and they're in the, in this one document. So we just keep pointing them to the. One main document and they're saying more and more best practices there. Yep. Yeah, that's true. All right, cool. Let's jump back in that liveness, I guess. So, so regarding the lightness. Yeah, thanks. Thanks Taylor for, for starting the discussion there. Yeah, it is, it is great. Like, I mean, the only thing that I was thinking about that particular best practices. How can we, what could be exactly that the best practice besides defining aligning sprouts in the. The definition. I mean, I was just thinking loudly, like a maybe. Some proportion of some numbers or how to calculate. The different parameters or things like that. So. Yeah, that's, that's why I would like to. To open the discussion there, like if someone has. Some ideas. To encourage people to use that particular feature most mostly. How to use it in the best way, like a. Specific numbers or certain. Proportions. I think that that could be a good. Good idea. Like. I don't know if that makes sense when I say. It's my point. I think you were. Had some reference links to some stuff. Can you bring up the, the liveness probe. 251. Tom. Sorry. No worries. And then scroll down. So this one's pretty minimal. There's some references here. And maybe click on the doc that. In the comment down below. There's a comment. Yeah. I think this one might have more. The interaction. Yeah, there we go. Okay. Yeah, they, well. The red is, I think, copied from somewhere else. So all of that needs to be filled. So you have there on the side, Victor, let's see. This is motivation. Yeah. I think it's a fast fell pattern. Yeah, exactly. It's like, I was just thinking a lot. Maybe what could be the benefits to use these. The only one came to my mind was a bit fast. Your body's behaving bad. So just. Terminated and a new one. I guess that's a main important to have a light, like this probe there. You know, I think there's a lot of ways to define it. Like. The first one is like the type of a lightness probe. Which could be. Or different types. Like common by STP and TCP requests. Or just your CP. And. And also. There are. Once that you choose. The type of a lightness proof. So you have the type of a lightness probe. So you have to define certain parameters. So. The thing is like, I mean. You can choose whatever adjust to your needs. But I don't know if like that could be like. A good practice to. Have some. Like. Like different portion, like the pain of the number, for example, I'd say that. The best. I don't know. The initial delay in seconds. Parameter. Has some kind of relation with the. And sequence. Or things like that. So. I think. If someone has. Playing around with those numbers and can give us some. Like roles of time or something like that. Where we can use as a, as a best practice. That could be also. Great. Like having some, some, some numbers or some, some things. That can people use them. In that real world. So do you think. And of course, I'm just talking discussion here. Are you thinking that those would be part of the main best practice? Or would we put those down in the. Like the notes section. And can you scroll down to the notes section? So this is notes, caveats. And constraints. It doesn't have to be negatives. Or alternatives. We can have it for additional information that we're not. Saying you must do these things. So these could be. Maybe less strong recommendations. But here's some things to look for. So what, what are you thinking that would it be something more of here's something that you should look at and consider, or do you think it should be part of the best main best practice? What are you thinking, Victor? Well, first of all. The first, the first step is having that information. I think if we have that information. Yeah. Probably the best place to put that information. Could be in that section notes. It's a note. But yeah, I couldn't find like a. A quick search. Those, those kind of information. But if we have it, definitely maybe that's the best place to put that information. Yeah. The only thing that I will avoid to have it is. Very. Yeah. Yeah. The only thing that I will avoid to have it is very. A standard like a. I mean. Yeah. It's for sure like life and it's proofs are a great thing to, to monitor the, the healthy of the. The CNF. Or any. Application in general. But, but yeah, I would like to see something more. Like a. And if we have that information, probably, yeah, that's the best place maybe to put in. In this section. As a. So the initial note. Yeah, I don't know. For example, like, if, if you choose like a. Very. Small time frame, maybe you can have an impact on your CPU probably. I'm not saying I don't know. Like, let's say that you choose like a one millisecond or something like that. So every one millisecond is. Calling your command that you have defined in the, like mis-proof. So which. Probably can be translated as. Like. Over using the CPU to just to. Monitor the app itself. So I think I didn't have, it has to be a balance between. The amount of resources that you are using in the app versus. The amount of resources that you're using to monitor the. The healthiness of the app. But yeah, probably I need to dig more in this idea because. That's the only thing that I came to my mind. I just wanted to bring. That topic in this. This, this meeting. Yeah, I guess it depends a little bit on the type of the function that you think if it's something that's on the critical path. You would most likely want to know immediately. It's tight. I mean, when it fails and helps responding. If it's something like, I don't know. User. Management something. Yeah. I mean, you don't need to ping it too often. Probably if it's still there. Exactly. Yeah, that's a good point. So for me, that seems like. That's a good point. That's the content that will be going to this. What we're calling notes section. Maybe this could have a better. Title there. But if you're implementing this best practice, then here's some things you should look into. And here's some things you should. Be aware of. So you don't have problems. As well as. You know, we may say, don't set it to liveness where it checks every 20 minutes. If you can even do that. I don't know if, if they. Kubernetes constraints it, but I think there's a. Something that would be too high. And then something too. Too often. But it seems like something that we could put into this area. And then. It would be encouraging people to think about those things. Yeah, I agree. But I guess in general, like. Let's let's try to get some feedback about these best practice. I guess. Again, Taylor, thanks for. Putting all these. Together. And it started the conversation. But yeah, definitely we need. Exercise on the. Here on this document. How's, how's that? Just as a start, I can delete the red since we actually have some content and then. Rewarded that portion a little bit and then we can. Add more content on that section. I think that we, we are missing the, the Nikolay comment. About the. All depends on the. The type of the workload. So probably. I don't know if you want to. Absolutely. Putting this as kind of a start. TBD we need to add more. Okay. TBD add information about the type of workload. And the. And say that again. I don't know if that is a word. How critical is it like. Each of these. These are. These are just. For us to talk about. And anyone can come and do suggest edits on these. If you want to. Directly work with us. On these. And you feel like this is a topic. Then let me know we can. Even give direct edit access right now. It's anyone. If you want to. And let me know we can even give direct edit access right now. It's anyone with link can add comments. And suggest edits. So you can, of course, add comments like Victor's done. But you can also. Just do a suggest edit. So it can look like this. So this is. What is this? It's a live-ness. All. Pod types should have. Live-ness. Checks. And then that's going to be there as a suggest. I'm going to remove this. When we just have that. So now. That's there. So this is for those who haven't done this. Anyone that doesn't have edit access. You just start typing or deleting or changing. It'll come up like this. And then we can simply. Check it and add that in. So definitely encourage folks to add anything here. And I do want to point out that we have. Oh, you may not see where I did that. Sorry. I forgot. Yeah. I'm going to share my screen. Tom, can you go up to workload context so that. My words don't sound. Yeah. Yeah. See that. So that one's. And now I can, that one's a suggest edit. And then I can, um, any of us that have added access can just accept that as a change. So. Um, I feel free to just add stuff into any of these. Um, before we run out of time, I do want to point out that all of the get have issues that are best practice proposals. I believe all of them. Um, if there's any missing, let us know. I think all of them have links to draft Google docs for each of the best practice. I think that's a good idea. I think that's a good idea. I think that's a good idea. I think people just add directly to those. And work with us. Of course, people can add comments to the get up issues. But if they want to directly add comment or comments to it, the draft documents, definitely appreciate that. What else do we have on the agenda to close it out, Tom? I think that's it for today's agenda. Thank you, Tom. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. I just noticed that in the open source summit in North America, there will be a. A cold. The event. The LFN networking. The one summit. So. I just put it there. Nice. The one. It disappeared. The list of events. That'll be why. So that's the lesson. That's in Vancouver as well. Okay. That's in May. All right. And that's nearly backed back to the big 5G event. Hoping to see some of y'all there. There's a lot of parties. A lot of different, sorry. Telecom orgs, not parties. I was saying parties for orgs. There probably will be parties, but hoping to see. I don't know. I don't know. I don't know. I'm. I'm. Trying to. Have a CNCF print presence at big five. I, for those that don't know, I'm actually local to Austin. I'm planning on going. Whatever the case and try to promote cloud native and made up. There's. A pretty large. Group of people. It seems to be. More open to. I think that's the. There's another event, which I'm not seeing on the. In this list. Oh, maybe connected America, I think it's more. Specific to. Telecom for. North America. And I think this big 5G would just be open. So Tom. I like Vodafone. I take a, I would at least take a look and then. Make sure that folks know, but I think. It would probably be a good event for anyone, even if you're not a North American telecom. Yeah. I'll share the details. I. Let's just. We'll struggle. Just given the. Location. That seems to be the case with travel right now. Unfortunately. I thought we were getting done with that post as well. I know we're not totally done with COVID, but getting a little better on travel, but. Yeah. Yeah. And the one summit. Event. I don't. We should look into that for. Our own collaboration. Group and what we're trying to do. Thanks for noting that. Thank you. Okay. Let's let's close the call. Thanks. Thank you. Okay. Let's let's close the call. Thanks. Catch you next week. Yes. Thanks. Bye. Thank you. Bye.