WEBVTT 00:00.000 --> 00:20.380 Let's talk about the local Church network and the other 00:20.380 --> 00:25.380 and I know there's a organization that's been pulled away. 00:25.380 --> 00:28.380 I know there's been a few of them. 00:28.380 --> 00:31.380 I was interested in computers and things kind of escalated. 00:31.380 --> 00:32.380 Great thing. 00:32.380 --> 00:37.380 It's an happen I started on my MSM and I was thinking if we're didn't necessarily 00:37.380 --> 00:39.380 didn't find it. 00:39.380 --> 00:46.380 One next thing is a few people about to go to the post-6 and I went now two and after 00:47.380 --> 00:49.380 we have two people. 00:49.380 --> 00:52.380 They have a few people. 00:52.380 --> 00:54.380 They have a few people. 00:54.380 --> 00:58.380 Somebody asked me if I wanted to go to the post-6 together. 00:58.380 --> 01:01.380 Some people thought I would get to the post-6 together. 01:01.380 --> 01:04.380 Some people thought I would get to the post-6 together. 01:04.380 --> 01:09.380 I heard that I studied in here and today I have my own company. 01:09.380 --> 01:11.380 This is a form. 01:11.380 --> 01:16.380 The other two people used to have everything. 01:16.380 --> 01:21.380 When you hear that, and I think it's a prize. 01:21.380 --> 01:23.380 It has become the VR now today. 01:23.380 --> 01:26.380 Both of these are the most important ones in the many of these. 01:26.380 --> 01:28.380 So I'm very proud. 01:28.380 --> 01:33.380 So I'm happy to see my world like to be able to go to the post-6. 01:33.380 --> 01:35.380 It's how things started. 01:35.380 --> 01:38.380 So I'm going to give you a talk about myself. 01:38.380 --> 01:40.380 I'm going to talk about his team. 01:40.380 --> 01:43.380 So the first question is, please, do this part of your team. 01:43.380 --> 01:46.380 Well, by any means, it's an RC brand. 01:46.380 --> 01:48.380 So that's the style. 01:48.380 --> 01:52.380 Originally, you can see by imagining, and also, 01:52.380 --> 01:55.380 Alexander brought us to the post-6. 01:55.380 --> 01:57.380 We're working on NGA SCS. 01:57.380 --> 01:59.380 It actually came as a high catch. 01:59.380 --> 02:00.380 I didn't care. 02:00.380 --> 02:05.380 This is because we didn't know about NGA SCS. 02:06.380 --> 02:09.380 We're working on NGA SCS. 02:09.380 --> 02:11.380 It's a policy. 02:11.380 --> 02:13.380 It's high. 02:13.380 --> 02:16.380 It's going to totally stay for two people. 02:16.380 --> 02:19.380 So it's a high demand in which you can take it. 02:19.380 --> 02:20.380 It's going to take it. 02:20.380 --> 02:23.380 It's going to be also a policy mechanism for a team here. 02:23.380 --> 02:24.380 I think it's a thing. 02:24.380 --> 02:25.380 It's a situation. 02:25.380 --> 02:26.380 It's okay. 02:26.380 --> 02:27.380 This is going to happen here. 02:27.380 --> 02:28.380 And that's it. 02:28.380 --> 02:29.380 It's done. 02:29.380 --> 02:31.380 This means NGA SCS for days. 02:31.380 --> 02:33.380 It's a policy mechanism. 02:33.380 --> 02:34.380 It's as if it's an accident. 02:34.380 --> 02:35.380 It's quite simple. 02:35.380 --> 02:37.380 It's quite hard to use to the SCS. 02:37.380 --> 02:39.380 It doesn't use it, but we're not sitting there. 02:39.380 --> 02:41.380 This is not possible. 02:41.380 --> 02:46.380 And today, SCS and day in have different ways of making clear, 02:46.380 --> 02:48.380 random distribution of mental health. 02:48.380 --> 02:51.380 But basically, people are also in the institute. 02:51.380 --> 02:54.380 And then things in transport became kind of complicated. 02:54.380 --> 02:58.380 And Alexander said, well, is there a stand-up in, 02:58.380 --> 03:01.380 because it's not there, too. 03:01.380 --> 03:08.380 Okay, pensions about the offering to us working out in the field where Jesus will be sent. 03:08.380 --> 03:11.380 And that's one of the things that we feel about. 03:11.380 --> 03:14.380 The pensions that I'm not in work, they didn't work. 03:14.380 --> 03:17.380 Yeah, so what we should do is give it to them. 03:17.380 --> 03:23.380 So, MTA, sorry, here's how to continue. 03:23.380 --> 03:28.380 It's not only the assignment, but it's also a practical part of the simple MTA. 03:28.380 --> 03:35.380 I have also been working on the eight for the security movement. 03:35.380 --> 03:40.380 That's the same as one of the four journey voyages. 03:40.380 --> 03:43.380 So, to say it is taking a guide on. 03:43.380 --> 03:49.380 And these people can be certified when we find the process of securing this information journey. 03:49.380 --> 03:53.380 We're running a platform that needs to serve standards. 03:53.380 --> 03:58.380 You need to implement Jesus' guidance. 03:58.380 --> 04:03.380 I was given you honor to be also working out there. 04:03.380 --> 04:08.380 I, together with the kind of officer's permission to talk about you, 04:08.380 --> 04:11.380 making the two of our two in the kind of mandatory. 04:11.380 --> 04:17.380 Because there was a meeting with the source implementation of the time of the assignment. 04:17.380 --> 04:19.380 So, we said, it's not an honor job. 04:19.380 --> 04:20.380 You think about it. 04:20.380 --> 04:21.380 It was an action there. 04:21.380 --> 04:23.380 Not that much about this. 04:23.380 --> 04:28.380 But what would be more secure for the two of the music community? 04:28.380 --> 04:29.380 Yeah. 04:29.380 --> 04:30.380 So, it's okay. 04:30.380 --> 04:32.380 That's certainly the best of our life. 04:32.380 --> 04:34.380 And, what is expected? 04:34.380 --> 04:37.380 Many, many providers can say, 04:37.380 --> 04:39.380 but what do we certify about it? 04:39.380 --> 04:41.380 We can't because they have to be certified. 04:41.380 --> 04:42.380 Our engaging is not. 04:42.380 --> 04:45.380 Because I think those communities have two books. 04:46.380 --> 04:47.380 So, yeah. 04:47.380 --> 04:49.380 So, proud of this. 04:49.380 --> 04:50.380 Yes. 04:50.380 --> 04:51.380 It's true. 04:51.380 --> 04:53.380 This is probably because it didn't have any money. 04:53.380 --> 04:54.380 Any other side for it? 04:54.380 --> 04:55.380 Yeah, my first step up in Boston. 04:55.380 --> 04:57.380 But I thought this really had the beginning of the book. 04:57.380 --> 05:00.380 And it's good that you have another side service. 05:00.380 --> 05:01.380 Any other side service? 05:01.380 --> 05:03.380 And you need to open yourself with free, 05:03.380 --> 05:05.380 or you're trying to test it. 05:05.380 --> 05:07.380 So, it's not a simple book. 05:07.380 --> 05:09.380 But it wasn't. 05:09.380 --> 05:13.380 And a certain point, I was very upset. 05:13.380 --> 05:16.380 And I do, in my company, have a budget. 05:16.380 --> 05:18.380 And I'm not a kind of activist here. 05:18.380 --> 05:20.380 And I hope you can say it. 05:20.380 --> 05:21.380 We can answer it. 05:21.380 --> 05:25.380 Also, it's a set of, I'd like to see to this kind of thing. 05:25.380 --> 05:26.380 I'd like to see to this kind of thing. 05:26.380 --> 05:28.380 And you said, it's certainly better than that. 05:28.380 --> 05:30.380 But it's creating an open force. 05:30.380 --> 05:32.380 But we have to see that. 05:32.380 --> 05:34.380 And we have to, of course, 05:34.380 --> 05:36.380 if anyone can move back to the next one. 05:36.380 --> 05:40.380 And again, I will use that library to introduce ourselves. 05:40.380 --> 05:42.380 I'd like to see this kind of library. 05:42.380 --> 05:46.380 So, before I go on, what problems do we do? 05:46.380 --> 05:49.380 So, well, these are routine. 05:49.380 --> 05:52.380 It's not that you can afford to keep that situation. 05:52.380 --> 05:55.380 And, when you try to talk into this, 05:55.380 --> 05:59.380 I mean, you know, when we have a lot of professional, 05:59.380 --> 06:01.380 of course, you might use a lesson here. 06:01.380 --> 06:04.380 You know, why do you choose to critique? 06:04.380 --> 06:07.380 And I was like, yeah, well, why do you choose to critique? 06:07.380 --> 06:11.380 Do you know what the chance of it's a matter of stuff? 06:11.380 --> 06:14.380 You mean, you're too close to yourself, you know? 06:14.380 --> 06:17.380 You know, this is probably what you see. 06:17.380 --> 06:20.380 You don't have to think about it. 06:20.380 --> 06:21.380 Okay. 06:21.380 --> 06:23.380 It's you. 06:23.380 --> 06:24.380 Or. 06:24.380 --> 06:27.380 You can have, but you just have to think of it. 06:27.380 --> 06:29.380 So, you don't have to worry about it. 06:29.380 --> 06:30.380 I mean, it's accurate. 06:30.380 --> 06:34.380 Of course, this is about the future of the communication party. 06:34.380 --> 06:35.380 You can get it. 06:35.380 --> 06:36.380 Any blind spots. 06:36.380 --> 06:39.380 Basically, you will have a piece of outside 06:39.380 --> 06:41.380 of other systems. 06:41.380 --> 06:43.380 You can see the other systems. 06:43.380 --> 06:46.380 You can create three systems. 06:46.380 --> 06:50.380 So, why would you see things? 06:50.380 --> 06:53.380 Are we carrying it about the use? 06:53.380 --> 06:55.380 Sorry. 06:55.380 --> 06:59.380 Well, it was a done by the time. 06:59.380 --> 07:01.380 I'm not going to hold that. 07:01.380 --> 07:03.380 If you could tell, so when you were trying to submit 07:03.380 --> 07:05.380 up the time into the relationships, 07:05.380 --> 07:07.380 something for some of the spirit, 07:07.380 --> 07:09.380 and something has to do with that. 07:09.380 --> 07:11.380 So, what else could happen? 07:11.380 --> 07:13.380 So, right? 07:13.380 --> 07:15.380 If you think about it. 07:15.380 --> 07:17.380 You can have a machine. 07:17.380 --> 07:19.380 So, what's the machine in the middle of that? 07:19.380 --> 07:21.380 You know, you pull it. 07:21.380 --> 07:23.380 You pull it down. 07:23.380 --> 07:25.380 So, what else could happen? 07:25.380 --> 07:26.380 So, right? 07:26.380 --> 07:28.380 You think about it. 07:28.380 --> 07:30.380 You can have a machine in the middle. 07:30.380 --> 07:32.380 So, what's the machine in the middle of that? 07:32.380 --> 07:33.380 You know, you pull it. 07:34.380 --> 07:35.380 You pull it down. 07:35.380 --> 07:38.380 And you have, you pull it down. 07:38.380 --> 07:39.380 Then you pull it. 07:39.380 --> 07:42.380 So, you pull it down. 07:42.380 --> 07:45.380 You see so, right now, 07:45.380 --> 07:47.380 then you make sense just in DVD. 07:47.380 --> 07:49.380 That the actress and Singh moved at the same time 07:49.380 --> 07:50.380 all there about hotel. 07:50.380 --> 07:51.380 And not even rehearsal composition. 07:51.380 --> 07:53.380 And any public representative, 07:53.380 --> 07:55.380 and you can choose everyone and chill around. 07:55.380 --> 07:57.380 But it's simple to run your students. 07:57.380 --> 07:58.380 And be checks. 07:58.380 --> 08:01.380 It can kind of take attention. 08:01.380 --> 08:05.540 Okay, here we go, right one, this is where Jane comes, you know. 08:05.540 --> 08:08.380 And hey, he starts in the way into the room and says, 08:08.380 --> 08:10.940 it's still happening to check her up. 08:10.940 --> 08:13.180 So we're getting her trying to save messages 08:13.180 --> 08:15.100 to the government and the infrastructure. 08:15.100 --> 08:16.980 Suddenly, he has running back in the middle. 08:16.980 --> 08:18.540 I see him in the middle. 08:18.540 --> 08:21.020 So in that area, no, I'm not. 08:21.020 --> 08:22.260 You see him. 08:22.260 --> 08:24.900 So, actually, that's interesting to see. 08:24.900 --> 08:27.100 I would see him, but he's not seeing him 08:27.100 --> 08:29.420 because we would have to go to the party and see him. 08:30.420 --> 08:34.420 Who would benefit from jumping back to his property? 08:34.420 --> 08:38.420 Well, speaking of being self-centered, 08:38.420 --> 08:40.420 obviously, the people running the castle. 08:40.420 --> 08:42.420 You know, they couldn't have to do this properly. 08:42.420 --> 08:43.420 Oh, we have an issue here. 08:43.420 --> 08:45.420 So we can get this updated for. 08:45.420 --> 08:48.420 I'm sorry that it's having problems with other residents. 08:48.420 --> 08:51.420 They can try to get their machines spread to you. 08:51.420 --> 08:53.420 You can guarantee it. 08:53.420 --> 08:55.420 That's an amazing step. 08:55.420 --> 08:57.420 But, of course, you would have to serve together 08:58.420 --> 09:01.420 to carry officers and have to look at it and say, 09:01.420 --> 09:05.420 oh, or bang and go back and down. 09:05.420 --> 09:08.420 We're not always super-minded because we need our policies 09:08.420 --> 09:11.420 to be 100% of all situations. 09:11.420 --> 09:14.420 You know, you couldn't have some numbers from that. 09:14.420 --> 09:15.420 You could have them. 09:15.420 --> 09:17.420 I can even ask this, or if I don't ask this, 09:17.420 --> 09:19.420 I'm pretty sure that custom doesn't bring figures 09:19.420 --> 09:20.420 to help you with that. 09:20.420 --> 09:22.420 So listen, the money's aren't clear. 09:22.420 --> 09:23.420 That's clear. 09:23.420 --> 09:24.420 That's clear. 09:24.420 --> 09:27.420 You can't see what's going on because you took us from the court. 09:27.420 --> 09:30.420 But every single message is out to others to be sent to us. 09:30.420 --> 09:33.420 We can very excited that the definition has a good, 09:33.420 --> 09:34.420 that is the same. 09:34.420 --> 09:37.420 If you need to, we can observe the community 09:37.420 --> 09:39.420 that we've got to respond to. 09:39.420 --> 09:42.420 We have to have to get away our investment. 09:42.420 --> 09:45.420 And very interesting for every sheet that is created 09:45.420 --> 09:47.420 for structure. 09:47.420 --> 09:49.420 The community of structure companies 09:49.420 --> 09:50.420 can communicate problems. 09:50.420 --> 09:53.420 They see it to a government that's covered in the children. 09:54.420 --> 09:56.420 Is it going to happen? 09:56.420 --> 09:58.420 Let me tell you, if you're going to have the data for that, 09:58.420 --> 10:01.420 we're not going to be able to do all this. 10:01.420 --> 10:04.420 So, if you're going to do a picture, 10:04.420 --> 10:06.420 I'm not going to be very careful. 10:06.420 --> 10:07.420 What's in this report? 10:07.420 --> 10:08.420 No. 10:08.420 --> 10:09.420 It's not. 10:09.420 --> 10:10.420 Let's see that. 10:10.420 --> 10:14.420 It's a structure below. 10:14.420 --> 10:16.420 It has to be that data on. 10:16.420 --> 10:17.420 Who is it? 10:17.420 --> 10:18.420 Who is it? 10:18.420 --> 10:19.420 Who is it? 10:19.420 --> 10:21.420 Who is it? 10:21.420 --> 10:22.420 Who is it? 10:22.420 --> 10:26.420 It has overall success and an overall failure. 10:26.420 --> 10:29.420 It has negotiations in this. 10:29.420 --> 10:33.420 I couldn't talk about that machine because reason. 10:33.420 --> 10:35.420 And there's specific reason. 10:35.420 --> 10:38.420 There's one open-fuse rate in case anything in there 10:38.420 --> 10:40.420 that doesn't exist on the rest because 10:40.420 --> 10:44.420 the TSS kind of conflicts that are not so fast. 10:44.420 --> 10:47.420 And the steam I hear did be also helpful in the past. 10:47.420 --> 10:49.420 If we get the main thing, 10:49.420 --> 10:51.420 the reason, for example, of the system, 10:51.420 --> 10:53.420 it's practicing like that, you know, 10:53.420 --> 10:57.420 that everything else goes into the other itself. 10:57.420 --> 10:59.420 And then we have common security. 10:59.420 --> 11:01.420 It's common security that the key here today 11:01.420 --> 11:03.420 is the standard for an engineer's use. 11:03.420 --> 11:06.420 That's the basic rule. 11:06.420 --> 11:08.420 So, we use this here. 11:08.420 --> 11:12.420 Well, the big rule before this, 11:12.420 --> 11:14.420 is I'm going to have a quick task. 11:14.420 --> 11:16.420 My personal approval. 11:17.420 --> 11:19.420 Yeah, there's no it. 11:23.420 --> 11:27.420 So, why don't you have a seat here? 11:27.420 --> 11:30.420 Well, they went there on the gate 11:30.420 --> 11:32.420 and then I told us, 11:32.420 --> 11:36.420 they didn't have to wait for the source to be out there. 11:36.420 --> 11:38.420 Yeah, just like that. 11:38.420 --> 11:41.420 The process is all the way to the computer. 11:41.420 --> 11:43.420 That's it over there. 11:43.420 --> 11:44.420 So. 11:46.420 --> 11:48.420 The few times a minute, the market, 11:48.420 --> 11:50.420 we still don't have to go to the computer. 11:50.420 --> 11:54.420 The best thing was how we did it over the others. 11:54.420 --> 11:56.420 And that comes for a plan. 11:56.420 --> 11:58.420 And the plan was, like, like, 11:58.420 --> 12:00.420 the key here to be set to be set. 12:00.420 --> 12:03.420 The key, the rule that was actually made by library 12:03.420 --> 12:05.420 was going to be updated. 12:05.420 --> 12:07.420 And I really heard that the key was going to be 12:07.420 --> 12:08.420 actually, you know, 12:08.420 --> 12:10.420 and you are interested to also implement it. 12:10.420 --> 12:12.420 And you want me to have a mic. 12:13.420 --> 12:15.420 I'm sorry. 12:21.420 --> 12:23.420 I'm sorry. 12:23.420 --> 12:26.420 Okay, I'm going to start again. 12:28.420 --> 12:30.420 So, I'm sorry. 12:30.420 --> 12:32.420 Just in the camera. 12:32.420 --> 12:35.420 So the idea was to create a library 12:35.420 --> 12:38.420 and then have a good implementation 12:38.420 --> 12:40.420 with that for that, with in post-fix, 12:40.420 --> 12:41.420 how to configure it. 12:41.420 --> 12:43.420 And it's not that complicated. 12:43.420 --> 12:45.420 I heard a few times too often today. 12:45.420 --> 12:48.420 Also, I'm trying to provide a service 12:48.420 --> 12:51.420 that will receive data grams from any MTA. 12:51.420 --> 12:53.420 Aggregate them, 12:53.420 --> 12:54.420 rework them, 12:54.420 --> 12:56.420 and then send off a report. 12:56.420 --> 12:57.420 Okay. 12:57.420 --> 13:01.420 So reference implementation in post-fix is like this. 13:01.420 --> 13:04.420 You enable this in the SMPP client. 13:04.420 --> 13:06.420 That's why the parameter over there, the option 13:06.420 --> 13:07.420 starts with SMPP. 13:07.420 --> 13:08.420 You know? 13:08.420 --> 13:10.420 And then you say, whatever data 13:10.420 --> 13:12.420 you want to send, send it to the socket. 13:12.420 --> 13:14.420 And that's it. 13:14.420 --> 13:20.420 And then, there's a very interesting case. 13:20.420 --> 13:23.420 How do you, if you have a super secure platform 13:23.420 --> 13:26.420 that uses SMPP and start TLS, 13:26.420 --> 13:28.420 whatever possible? 13:28.420 --> 13:31.420 Tell a remote destination 13:31.420 --> 13:33.420 that they're having a TLS problem 13:33.420 --> 13:36.420 when you want to start TLS every time you connect 13:36.420 --> 13:37.420 to them. 13:37.420 --> 13:40.420 And it fails because they have a problem. 13:40.420 --> 13:42.420 You need a way to tell your mid-platform. 13:42.420 --> 13:43.420 Yes, usually you do that, 13:43.420 --> 13:46.420 but in some circumstances you won't do that. 13:46.420 --> 13:50.420 So we'd say implemented the RC8689, 13:50.420 --> 13:52.420 and you can put the TLS required 13:52.420 --> 13:55.420 header in there and it says, no. 13:55.420 --> 13:56.420 Beware. 13:56.420 --> 13:57.420 It's like nuclear power. 13:57.420 --> 13:59.420 You can do the wrong thing. 13:59.420 --> 14:00.420 You know? 14:00.420 --> 14:02.420 If you have it on your default path, 14:02.420 --> 14:03.420 you know? 14:03.420 --> 14:04.420 You can send up messages. 14:04.420 --> 14:06.420 And you won't have TLS, because it's 14:06.420 --> 14:08.420 downgrading everything. 14:08.420 --> 14:09.420 Like it was meant to. 14:09.420 --> 14:11.420 So when you implement it, 14:11.420 --> 14:12.420 when you put it in emails, 14:12.420 --> 14:14.420 think about where you put it in emails. 14:14.420 --> 14:16.420 And that's about it. 14:16.420 --> 14:18.420 The coming release for that, 14:18.420 --> 14:20.420 post-63.10. 14:20.420 --> 14:24.420 The version will be released early March, 14:24.420 --> 14:27.420 and speaking about by catch, 14:27.420 --> 14:29.420 by then, post-6 will also be able 14:29.420 --> 14:31.420 to support MTA-STS. 14:32.420 --> 14:34.420 So. 14:34.420 --> 14:36.420 And then, 14:36.420 --> 14:37.420 they need to be on the, 14:37.420 --> 14:38.420 on the other side of the socket, 14:38.420 --> 14:40.420 needs to be a service that receives all 14:40.420 --> 14:41.420 the dataograms. 14:41.420 --> 14:42.420 It does something about that. 14:42.420 --> 14:44.420 So we wrote a DLS reporter. 14:44.420 --> 14:46.420 It's actually three binaries. 14:46.420 --> 14:47.420 She Python programs. 14:47.420 --> 14:48.420 They do different things, 14:48.420 --> 14:50.420 which allow for different architectures. 14:50.420 --> 14:52.420 You can have it all on one machine. 14:52.420 --> 14:53.420 Or you can have a larger setup, 14:53.420 --> 14:55.420 where you have a bunch of machines, 14:55.420 --> 14:57.420 and send it all to one collector, 14:57.420 --> 14:58.420 and then one generator, 14:58.420 --> 15:00.420 and the generator sends it off. 15:01.420 --> 15:03.420 So it's supposed to rate forward. 15:03.420 --> 15:06.420 It's as simple as possible. 15:06.420 --> 15:09.420 And it doesn't have many dependencies. 15:11.420 --> 15:14.420 Now that I was talking about that you can generate reports. 15:14.420 --> 15:16.420 How do you ask for reports? 15:16.420 --> 15:18.420 That basically two ways to do that. 15:18.420 --> 15:19.420 Either you ask, 15:19.420 --> 15:22.420 it's seen as it's always seen as, isn't it? 15:22.420 --> 15:27.420 So you propagate a record in, 15:28.420 --> 15:29.420 sorry, 15:29.420 --> 15:31.420 in your own CDS. 15:31.420 --> 15:32.420 And you say either, 15:32.420 --> 15:34.420 I want to have an REA, 15:34.420 --> 15:35.420 via a mail to, 15:35.420 --> 15:36.420 and then you say, 15:36.420 --> 15:37.420 what's the designation address for that? 15:37.420 --> 15:39.420 And you get a send via email. 15:39.420 --> 15:42.420 Or you publish an HTTP resource, 15:42.420 --> 15:46.420 and hosting will be sent to the HTTP resource. 15:46.420 --> 15:48.420 If you implement it, 15:48.420 --> 15:50.420 and if you're asking for that, 15:50.420 --> 15:53.420 you probably want to ask for email, 15:53.420 --> 15:54.420 and not for a TDPS. 15:54.420 --> 15:55.420 And the reason is, 15:56.420 --> 15:59.420 if somebody's posts sends you an HTTP S report, 15:59.420 --> 16:01.420 you can't really tell who it comes from. 16:01.420 --> 16:04.420 There's no reputation aligned with that entity 16:04.420 --> 16:06.420 that sends you the report. 16:06.420 --> 16:09.420 And there might be fooling you. 16:09.420 --> 16:13.420 So you might want to have the mail to a variant, 16:13.420 --> 16:15.420 because as far as, 16:15.420 --> 16:19.420 because the RC asks you to add a T-con signature on that, 16:19.420 --> 16:21.420 and you can build a reputation on that 16:21.420 --> 16:23.420 once you know the entity is like that. 16:23.420 --> 16:26.420 So the more secure way is to use email. 16:26.420 --> 16:29.420 It's always email. 16:29.420 --> 16:32.420 So I'm coming to an end. 16:32.420 --> 16:34.420 If you want to stay in the loop, 16:34.420 --> 16:36.420 there's a fresh list out there. 16:36.420 --> 16:37.420 It's called T-ness RPT, 16:37.420 --> 16:39.420 at list.sys4.de. 16:39.420 --> 16:42.420 And I believe there are five people on this list, 16:42.420 --> 16:43.420 by now, 16:43.420 --> 16:45.420 and I hope they're going to be more than five people 16:45.420 --> 16:47.420 after my talk. 16:47.420 --> 16:50.420 And it's going to be an open place for discussion 16:50.420 --> 16:51.420 about T-us RPT in general, 16:51.420 --> 16:54.420 and the implementation we saw, and we did for that. 16:54.420 --> 16:57.420 And what I didn't talk about is 16:57.420 --> 17:00.420 how you would monitor T-less reports. 17:00.420 --> 17:02.420 There are DMACC platforms out there. 17:02.420 --> 17:05.420 I heard about DMACC a rune. 17:05.420 --> 17:07.420 And I'm curious about that. 17:07.420 --> 17:11.420 But I haven't heard about T-us RPT a rune yet. 17:11.420 --> 17:16.420 So it might be one of our customers 17:16.420 --> 17:19.420 as good, which is budget, 17:19.420 --> 17:22.420 that I have the honor to be back again in a year 17:22.420 --> 17:25.420 and speak about T-us RPT monitoring. 17:25.420 --> 17:27.420 So thank you very much. 17:27.420 --> 17:37.420 Thank you. 17:37.420 --> 17:42.420 I don't give you a second. 17:42.420 --> 17:43.420 I have problems with hearing, 17:43.420 --> 17:45.420 so I need them to go out. 17:45.420 --> 17:46.420 It's just me, even. 17:46.420 --> 17:48.420 God. 17:48.420 --> 17:52.420 I'm not being the main to link in the report report. 17:52.420 --> 17:53.420 Yeah. 17:53.420 --> 18:03.420 I guess you recommend you set up a different demand. 18:03.420 --> 18:05.420 Or a subdomain. 18:05.420 --> 18:07.420 Sorry, I need to repeat it. 18:07.420 --> 18:10.420 So the question is, where would I send a report to? 18:10.420 --> 18:13.420 Would I send it to the same zone that is having a problem? 18:13.420 --> 18:16.420 Or would I send it to a different DNS zone? 18:16.420 --> 18:19.420 It should be a different DNS zone. 18:19.420 --> 18:21.420 You can put it into a subdomain of that 18:21.420 --> 18:25.420 and run a certain run a distinct instance for that. 18:25.420 --> 18:27.420 Or different IP machine, whatever. 18:27.420 --> 18:29.420 Or a completely different zone. 18:29.420 --> 18:31.420 Yeah. 18:31.420 --> 18:35.420 You. 18:35.420 --> 18:39.420 You. 18:39.420 --> 18:41.420 Have you ever encountered any issues? 18:41.420 --> 18:42.420 Yes. 18:42.420 --> 18:44.420 In a bit while. 18:44.420 --> 18:46.420 With the implementation? 18:46.420 --> 18:47.420 Yeah, no. 18:47.420 --> 18:49.420 I do lots of reports about things breaking. 18:49.420 --> 18:51.420 Oh, I can look into this. 18:51.420 --> 18:52.420 Yeah. 18:52.420 --> 18:53.420 Yeah. 18:53.420 --> 18:54.420 I remember. 18:54.420 --> 18:56.420 I also run mail up.org. 18:56.420 --> 18:57.420 Hey. 18:57.420 --> 19:00.420 So I get that. 19:00.420 --> 19:05.420 So the question was, did I run or have we run into problems yet? 19:05.420 --> 19:08.420 And we've got notified by using TeamsRPT. 19:08.420 --> 19:10.420 No? 19:10.420 --> 19:11.420 Yes. 19:11.420 --> 19:16.420 I must say that. 19:16.420 --> 19:17.420 Yeah. 19:17.420 --> 19:19.420 I do run the mail-up.org. 19:19.420 --> 19:22.420 Made in this alongside with other guys. 19:22.420 --> 19:24.420 And I had a configuration problem. 19:24.420 --> 19:28.420 The beginning with the Let's Encryption Certificate Rotation. 19:28.420 --> 19:31.420 I ended up, let's say, like that. 19:31.420 --> 19:32.420 And we went. 19:32.420 --> 19:34.420 We went blind because we were proposing. 19:34.420 --> 19:35.420 We were proposing. 19:35.420 --> 19:36.420 Dane. 19:36.420 --> 19:37.420 And people said, sorry. 19:37.420 --> 19:39.420 Your certificate is the wrong fingerprint. 19:39.420 --> 19:40.420 We're not going to center. 19:40.420 --> 19:42.420 And I read the reports. 19:42.420 --> 19:43.420 And yeah. 19:43.420 --> 19:45.420 But I knew also because Victor called me. 19:46.420 --> 19:47.420 So yeah. 19:47.420 --> 19:48.420 Yeah. 19:48.420 --> 19:52.420 Victor is the best reporter in there. 19:52.420 --> 19:55.420 Is there any more questions? 19:55.420 --> 19:56.420 Okay. 19:56.420 --> 19:57.420 Thank you very much. 19:57.420 --> 19:59.420 Thank you.