94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

Passcode: 209247

2024 TSC Recordings	2023 TSC Decisions	Anti-Trust Policy

We will start our meetings by mentioning the project's Antitrust Policy, which you can find linked from the LF and project websites. The policy is important where multiple companies, including potential industry competitors, are participating in meetings. Please review and if you have any questions, please contact your company legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

Attended	Proxy (w/ @name)	Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Andreas Geißler	DT	Keguang He	China Mobile
Byung-Woo Jun	Ericsson	N.K. Shankaranarayanan	Individual
Dan Timoney	AT&T	Paweł Pawlak	Incognito
Dan Xu	Huawei	Seshu Kumar Mudiganti	Windriver
Dong Wang	China Telecom

	Agenda Items	Presented By	Presos/Notes/Links/
Strategy (45 minutes)	ONAP takeaways		We are encouraging ONAP consumers to share with us their feedback, so we could prioritize our activities and make ONAP better suited their needs and requirements.
	LFN Cross-Organization Updates MAC, SPC, TAC, EUAG, LFN Board	Muddasar Ahmed Paweł Pawlak	TAC Update
	TCC / ONAP Liaison Updates
	Task Force Updates


Operations (40 minutes)	TSC Activities and Deadlines		Byung-Woo Jun , plans to present ONAP TSC initiatives - New Delhi and Oslo roadmaps to LFN DTF The first phase of ONAP Streamlining is being done. Next steps would be: Lightweight ONAP under consideration by aggregating core components, e.g., SO, SDC, Policy, CPS, UUI, DCAE, SDNC based on use cases. Component interface normalization / standardization as needed. slide deck draft: ONAPTSCInitiativeRoadmaps-May-v77.pptx
	Release Status	Paweł Pawlak Andreas Geißler	TSC voting for unmaintained project deprecation after going thru the list from Andreas. OOM New Delhi Release Voting approved by TSC DMaaP MR, CLI, VNFSDK, VFC, etsi-catalog deprecation next transition steps; TSC voting is needed
	RelEng/Infrastructure	Jessica Gonzalez	Onboard ONAP to CM / Insights v3 WIP
	PTL Updates	Paweł Pawlak	Recommended packages upgrades are available on the restricted Wiki. Jiras are created per project. New Delhi Package Updates Need to check NG Portal status CLM jobs. Any update? Jessica Gonzalez , ongoing. Fiete Ostkamp to provide an update about implementation progress. Update from Fiete Ostkamp : maven based jobs use the lf-infra-sonatype-clm Jenkins builder that triggers the com.sonatype.clm:clm-maven-plugin for gradle there currently is no such builder available in global-jjb Sonatype officially does not provide an equivalent plugin, but there is the Sonatype Scan Gradle Plugin that could provide similar functionality Ticket opened by Fiete: https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-26527 ongoing; Jessica and Fiete are discussing this.
	PTL Updates	Thomas Kulik Andreas Geißler	Documentation work in progress by Thomas and Andreas. Any update?
	Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Byung-Woo Jun	preparing architecture enhancement plans for Oslo for LFN DTF presentation, based on the TSC initiative consideration. e.g., Lightweight ONAP architecture
	OOM Update	Andreas Geißler	OOM Update for New Delhi; master versioning and project helm chart versioning decoupling and others. Most patches are in. One issue with SDNC, to be consulted with Dan.
	OOM Update
Events & Meetings (5 minutes)	Upcoming Events & Housekeeping	Byung-Woo Jun	ONE Summit : the session agenda for ONE Summit 2024 has been published, https://events.linuxfoundation.org/one-summit-north-america/program/schedule/ . APRIL 29 - MAY 1, 2024 \| IN-PERSON LFN DTF May 2-3 following ONE Summit ONAP programming committee member: Byung-Woo Jun deadline for topic submission is April 12th. The committee members will discuss the LFN DTF schedule based on the finalized topics next Monday need to add presentation topics, https://wiki.lfnetworking.org/display/LN/2024-05+LFN+Developer+Event+Sessions Byung-Woo Jun , LFN DTF presentation sessions have been scheduled at the DTF programming committee this Monday. FYI only, https://teamup.com/ksofwkj4xse7ggyioa

Zoom Chat Log

00:35:00 Paweł Pawlak: We start voting for unmaintained project deprecation as described by Andreas in : OOM New Delhi Release
00:35:03 Byung-Woo Jun: #vote +1
00:35:25 Paweł Pawlak: #vote +1
00:35:25 Andreas GEISSLER (DT): #vote: +1
00:35:27 Keguang He: #vote +1
00:35:31 N.K. Shankaranarayanan: #vote +1
00:35:41 Paweł Pawlak: #Vote end

Zoom auto-transcript service - These are often translated incorrectly and can be misleading. They are NOT Authoritative! Information as to why .
They are included here as a time stamp cross-reference for the recording only! The notes above this line and the actual recordings are authoritative.

WEBVTT

1
00:00:34.880 --> 00:00:35.613
Byung-Woo Jun: Hi Andrew.

2
00:00:40.270 --> 00:00:41.200
Andreas GEISSLER (DT): Have young.

3
00:00:41.620 --> 00:00:42.629
Byung-Woo Jun: Hey! Where are you?

4
00:00:43.650 --> 00:00:44.420
Andreas GEISSLER (DT): You're

5
00:00:44.790 --> 00:00:46.484
Andreas GEISSLER (DT): busy as always.

6
00:00:47.640 --> 00:00:50.000
Byung-Woo Jun: Yeah, I'm busy. Yeah.

7
00:00:50.970 --> 00:00:51.720
Byung-Woo Jun: yep,

8
00:00:53.662 --> 00:00:54.870
Andreas GEISSLER (DT): Fine! So far.

9
00:00:55.130 --> 00:00:56.219
Byung-Woo Jun: I'm busy so.

10
00:01:00.050 --> 00:01:01.860
Byung-Woo Jun: but we'll see how long.

11
00:01:02.970 --> 00:01:08.039
Byung-Woo Jun: So anyway, I in the slide deck I shared with the team.

12
00:01:08.780 --> 00:01:15.799
Byung-Woo Jun: I put the Deutsch telecom section. So anyway, whenever Mark and you have, you know, come up. And then, you know.

13
00:01:16.580 --> 00:01:18.739
Byung-Woo Jun: added more information there.

14
00:01:30.870 --> 00:01:31.670
Byung-Woo Jun: Well.

15
00:01:32.430 --> 00:01:33.300
Byung-Woo Jun: yep, so.

16
00:01:33.300 --> 00:01:39.009
Andreas GEISSLER (DT): Sorry I was I was bit. Can you repeat? Can you repeat? Sorry.

17
00:01:39.390 --> 00:01:42.899
Byung-Woo Jun: So I in I attach to athletic draft.

18
00:01:43.480 --> 00:01:43.850
Andreas GEISSLER (DT): Okay.

19
00:01:43.850 --> 00:01:50.289
Byung-Woo Jun: So in the slide deck later on, if you look at that, and there's teleconception.

20
00:01:50.420 --> 00:01:50.930
Andreas GEISSLER (DT): Okay.

21
00:01:50.930 --> 00:01:58.448
Byung-Woo Jun: And system loading and then Mark and you and provide more detail work because I just for now I put

22
00:02:01.058 --> 00:02:07.119
Byung-Woo Jun: yesterday we did you talk about switch telecom plans to deploy on a call in

23
00:02:07.210 --> 00:02:15.421
Byung-Woo Jun: the production environment next year and based on use cases, some of the only component such as blah blah blah will be selected.

24
00:02:15.750 --> 00:02:16.279
Andreas GEISSLER (DT): Yeah, yeah.

25
00:02:16.280 --> 00:02:28.060
Byung-Woo Jun: And for that on streamlining and oem script announcement for individual own network orchestration, function, build and deployment are in progress. Okay, this more and you can.

26
00:02:28.280 --> 00:02:37.330
Byung-Woo Jun: and the mark and Edmore. So I'm gonna since Mark will be there, I'm gonna give the you know, mark to decide. Okay, that's my friend. Okay.

27
00:02:37.610 --> 00:02:42.250
Andreas GEISSLER (DT): Yeah, that's good. That's good. I will. I will try to catch him in the next days.

28
00:02:42.290 --> 00:02:46.429
Andreas GEISSLER (DT): So either tomorrow or on Monday.

29
00:02:46.430 --> 00:02:50.540
Byung-Woo Jun: Yeah, yeah, yeah, we have a one week. We have a one week to partnership. So.

30
00:02:50.540 --> 00:02:52.920
Andreas GEISSLER (DT): Yeah, yeah, exactly. Exactly. Okay.

31
00:02:52.920 --> 00:02:54.280
Byung-Woo Jun: Okay, thank you.

32
00:02:59.750 --> 00:03:04.304
Byung-Woo Jun: Hi, Shanka! Hi, Ramesh! Let's wait for pabu. And

33
00:03:05.860 --> 00:03:07.010
Byung-Woo Jun: Sandra.

34
00:03:10.270 --> 00:03:11.110
Ramesh Murugan Iyer: Hi! Bean!

35
00:03:11.710 --> 00:03:12.859
Byung-Woo Jun: Hey! How are you?

36
00:03:13.200 --> 00:03:13.880
N.K. Shankaranarayanan: Boom, yeah.

37
00:03:14.500 --> 00:03:15.909
Byung-Woo Jun: I'm okay.

38
00:03:18.850 --> 00:03:20.389
Paweł Pawlak: Hello! Good morning. Everyone.

39
00:03:21.110 --> 00:03:21.823
Byung-Woo Jun: Hi, Pablo!

40
00:03:22.950 --> 00:03:24.079
Paweł Pawlak: Hello, Bjorn.

41
00:03:33.950 --> 00:03:36.240
Paweł Pawlak: how come? There's just 5 of us.

42
00:03:38.040 --> 00:03:38.820
Paweł Pawlak: 10.

43
00:03:39.722 --> 00:03:41.910
Byung-Woo Jun: We need them more to approve the.

44
00:03:42.120 --> 00:03:44.000
Byung-Woo Jun: And do you see.

45
00:03:44.470 --> 00:03:47.709
Paweł Pawlak: Exactly. We need more. Tsc, members.

46
00:03:47.920 --> 00:03:48.930
Paweł Pawlak: Yeah, yeah.

47
00:03:49.130 --> 00:03:49.760
Byung-Woo Jun: So.

48
00:03:52.900 --> 00:03:56.360
Paweł Pawlak: Okay, let's wait minute or 2. Maybe maybe

49
00:03:56.630 --> 00:03:57.710
Paweł Pawlak: they are coming.

50
00:03:58.330 --> 00:03:59.180
Byung-Woo Jun: Okay.

51
00:04:02.260 --> 00:04:04.199
Byung-Woo Jun: we need to send dry taste right?

52
00:04:05.960 --> 00:04:08.499
Paweł Pawlak: Yeah. By the way, where is Sandra? Yeah, you're right.

53
00:04:09.890 --> 00:04:11.039
Paweł Pawlak: What happens.

54
00:04:12.780 --> 00:04:14.829
Byung-Woo Jun: Soft this week, and.

55
00:04:36.370 --> 00:04:37.940
Paweł Pawlak: Let me check my emails.

56
00:04:38.550 --> 00:04:41.370
Paweł Pawlak: Maybe maybe she dropped some information.

57
00:04:42.440 --> 00:04:43.829
Paweł Pawlak: Let's see if.

58
00:05:06.690 --> 00:05:08.279
Byung-Woo Jun: she put the

59
00:05:08.630 --> 00:05:11.819
Byung-Woo Jun: cheap with the the slack channel.

60
00:05:12.340 --> 00:05:18.540
Byung-Woo Jun: Is that? I have an appointment this morning. I don't think I'll be bad in time to join the Tsc. Meeting.

61
00:05:19.020 --> 00:05:20.940
Paweł Pawlak: Okay. Okay, okay, okay.

62
00:05:20.940 --> 00:05:24.185
Byung-Woo Jun: She's gonna join. So I mean, maybe we can go ahead.

63
00:05:25.322 --> 00:05:28.060
Byung-Woo Jun: How about can you share the screen or

64
00:05:28.100 --> 00:05:29.590
Byung-Woo Jun: your agenda?

65
00:05:29.590 --> 00:05:31.599
Paweł Pawlak: Yeah, yeah. J, give me a sec.

66
00:05:52.710 --> 00:05:55.979
Paweł Pawlak: Okay? So I'm gonna share my screen.

67
00:05:56.450 --> 00:05:57.220
Paweł Pawlak: Okay.

68
00:06:04.050 --> 00:06:06.100
Paweł Pawlak: guys, please confirm, you can see it.

69
00:06:06.210 --> 00:06:06.690
Paweł Pawlak: Yeah.

70
00:06:06.690 --> 00:06:07.740
Byung-Woo Jun: I can see.

71
00:06:08.090 --> 00:06:09.790
Paweł Pawlak: Alright. So

72
00:06:10.580 --> 00:06:11.980
Paweł Pawlak: just before

73
00:06:12.620 --> 00:06:16.069
Paweł Pawlak: we move on, I will mark myself as present.

74
00:06:28.070 --> 00:06:28.850
Paweł Pawlak: Okay.

75
00:06:29.475 --> 00:06:31.900
Paweł Pawlak: being, I think what our

76
00:06:32.230 --> 00:06:33.609
Paweł Pawlak: green color is

77
00:06:34.280 --> 00:06:37.406
Paweł Pawlak: sometimes more green, sometimes with more blue.

78
00:06:38.300 --> 00:06:39.582
Byung-Woo Jun: To fix it.

79
00:06:40.010 --> 00:06:43.830
Paweł Pawlak: Okay, it's okay. It's okay. Okay. Guys, let's let's move on.

80
00:06:44.430 --> 00:06:45.460
Paweł Pawlak: though.

81
00:06:46.550 --> 00:06:49.130
Paweł Pawlak: I propose we start with

82
00:06:49.390 --> 00:06:55.089
Paweł Pawlak: with some updates from tech update. If Mundasa is with us.

83
00:06:55.810 --> 00:06:58.390
Paweł Pawlak: Let me check. No, no, I don't see on the cell.

84
00:06:58.390 --> 00:07:01.735
Byung-Woo Jun: He he sent email. He's not gonna join today. So.

85
00:07:02.070 --> 00:07:04.509
Paweł Pawlak: Okay, okay, so let's move on. So

86
00:07:04.790 --> 00:07:10.159
Paweł Pawlak: sorry for that, maybe next week we, we could have this this update. So moving.

87
00:07:10.160 --> 00:07:18.339
Byung-Woo Jun: Maybe sorry. Maybe there's he report to second, maybe the as a second update. Maybe we can introduce. It's up to you.

88
00:07:18.540 --> 00:07:19.290
Byung-Woo Jun: Hubble.

89
00:07:19.760 --> 00:07:22.570
Paweł Pawlak: Hmm, yeah. Yeah. Well, this is

90
00:07:23.190 --> 00:07:34.049
Paweł Pawlak: mudosa has has many hats in on app so or in in Lfn, so I think this tech update would come from his head as a vice chair of tech right? So.

91
00:07:34.050 --> 00:07:35.570
Byung-Woo Jun: Okay. Okay. Hmm.

92
00:07:35.570 --> 00:07:37.709
Paweł Pawlak: But yeah, okay, hmm.

93
00:07:38.880 --> 00:07:42.819
Paweł Pawlak: we can, we can try to to have this update next time.

94
00:07:44.008 --> 00:07:47.150
Paweł Pawlak: Moving forward, moving forward.

95
00:07:47.250 --> 00:07:49.069
Paweł Pawlak: Okay, beyond, we have this.

96
00:07:50.730 --> 00:07:52.849
Paweł Pawlak: Would you like to refer to this point?

97
00:07:52.850 --> 00:08:08.039
Byung-Woo Jun: Yeah, we are going to add the you know, you know. Tsc, chair, Baro and vice Chance, me and Doman and Taguang. We work on this on your Tsc initiatives for new daily, and also roadmap to full elephant.

98
00:08:08.050 --> 00:08:16.299
Byung-Woo Jun: So we are going to. I'm going to present what we have done so far as a draft, so we can, you know, give you information.

99
00:08:16.370 --> 00:08:30.240
Byung-Woo Jun: and then go through quickly, and then we put the slide deck in the draft so you can take a look at the offline. But I'm gonna give you a very quick overview today, and then take a look. And then we have a one more week to review.

100
00:08:30.480 --> 00:08:43.840
Byung-Woo Jun: So that means so by next week let us know your opinion. So all your company has additional input. And there's some reason China, mobile China telecom and voice telecom here the region.

101
00:08:44.080 --> 00:08:51.632
Byung-Woo Jun: And then so if you, your company, has some other reason please share, but we don't have many tf.

102
00:08:52.010 --> 00:08:54.460
Paweł Pawlak: Hey, young? So I stopped sharing to give you the floor.

103
00:08:54.460 --> 00:08:56.490
Byung-Woo Jun: Okay, let me do that. Okay.

104
00:08:56.870 --> 00:08:58.680
Byung-Woo Jun: me share screen.

105
00:09:02.150 --> 00:09:04.460
Byung-Woo Jun: Let me know if you see my screen.

106
00:09:04.920 --> 00:09:06.103
Paweł Pawlak: Yes, we can see it.

107
00:09:06.520 --> 00:09:07.060
Paweł Pawlak: okay, yeah.

108
00:09:07.060 --> 00:09:24.950
Byung-Woo Jun: As I mentioned, and myself and Kang Wong, we prepared for this for Ts initiatives and the new Delhi. And also so this is agenda. We're gonna present to elephant. Dtf, background challenges action points, human next plan, focus area and Cicd

109
00:09:25.070 --> 00:09:43.019
Byung-Woo Jun: also architecture focus lightweight on app and the Aiml intend and get and on maintain project plan, and then also collaboration between on app or and nephew collaboration plan and also on app and orn collaboration in progress. I I copy the chunk of report.

110
00:09:43.070 --> 00:09:54.425
Byung-Woo Jun: and then China, mobile China telecom, and how we voice telecom. They share the visions. And then we're gonna do questions. So anyway, this is the background. So out of 9 is

111
00:09:55.480 --> 00:10:06.790
Byung-Woo Jun: we create the owner. And then for a telecom community. And we created many used cases and now own it is not platform any longer one of these collection of network automation functions.

112
00:10:06.860 --> 00:10:12.529
Byung-Woo Jun: and that allows operator vendors to pick and choose and desired function.

113
00:10:12.570 --> 00:10:26.339
Byung-Woo Jun: and these are on a streamlining, and then also on. It has a line of the many industry, standard and de facto, and then recently, aiml 3 Gpp. Tm. Forum, sc and 2 Gpp for Netflix license.

114
00:10:26.380 --> 00:10:31.230
Byung-Woo Jun: and also we do de facto ingress. I am a service man, she still

115
00:10:31.420 --> 00:10:40.120
Byung-Woo Jun: cognitive, and then also as the alignment. So we found. And what olive strength this is the what we see English Strength

116
00:10:40.810 --> 00:10:47.510
Byung-Woo Jun: weekly is a large. So it's complexity and learning curve. And then it's just some problem. The integration.

117
00:10:47.980 --> 00:10:49.739
Dan Timoney (AT&T): Challenges the way they are.

118
00:10:53.480 --> 00:10:54.830
Andreas GEISSLER (DT): Your voice, disappears.

119
00:10:56.850 --> 00:10:58.100
Byung-Woo Jun: You know. Can you hear me?

120
00:10:58.100 --> 00:10:58.830
Andreas GEISSLER (DT): Yeah. Now again.

121
00:10:58.830 --> 00:11:00.619
Paweł Pawlak: Young now is better. Yeah.

122
00:11:00.620 --> 00:11:02.020
Byung-Woo Jun: Okay, sorry about that.

123
00:11:02.090 --> 00:11:16.812
Byung-Woo Jun: I don't know something wrong. So performance and scalability challenges. And we put the challenges here, competing standard and technologies and the some vendor lock, and we getting me moved to Af is gone, and then also some vendor specific configuration is gone.

124
00:11:17.818 --> 00:11:23.099
Byung-Woo Jun: But still not completely so. Implementation challenges and opportunity.

125
00:11:23.260 --> 00:11:30.619
Byung-Woo Jun: We are seeking emerging technologies, service, innovation, intent and secure Ci City

126
00:11:30.640 --> 00:11:38.659
Byung-Woo Jun: and part of the Oem Andreas team doing and also adding second, doing. And we try to make a Cq Cicd

127
00:11:38.730 --> 00:12:08.339
Byung-Woo Jun: and also network automation function capital. I'm gonna explain it a bit another community adoption. That's why. So this is the current issues, and not many new feature being implemented in New Jersey contribution having decreased significantly collaboration activity. Other companies are not strong yet, and several on a component being deprecated. So anyway, this is Action point we we come up and the setting on it. Authorization roadmap for on a, for future focus area and release

128
00:12:08.450 --> 00:12:14.979
Byung-Woo Jun: and evaluate alternate solution technology to ensure that only remains the best fit.

129
00:12:15.160 --> 00:12:17.549
Byung-Woo Jun: So we want to be relevant

130
00:12:18.180 --> 00:12:26.280
Byung-Woo Jun: and then collaborate to other community and standardization organization. So especially focus on the the Oran and the nephew.

131
00:12:26.360 --> 00:12:29.799
Byung-Woo Jun: And that's the kind of a 3 main action point we are.

132
00:12:29.820 --> 00:12:30.910
Byung-Woo Jun: am I with?

133
00:12:31.280 --> 00:12:48.800
Byung-Woo Jun: And then I'm gonna introduce about the what on it achieved so far. And then what's the next plan so and describe. Own it. Built as a platform, and through the owner streamlining, we achieved the individual component build and deployment. Thanks to all your effort and Ngos leading.

134
00:12:49.160 --> 00:12:51.170
Byung-Woo Jun: And then what's the next?

135
00:12:51.190 --> 00:13:03.939
Byung-Woo Jun: So China telecom channel mobile they're thinking, what if we compose existing on it? Individual component, and then creating some kind of a lightweight on it.

136
00:13:04.140 --> 00:13:11.960
Byung-Woo Jun: So for the some handling, some new feature or the the focus on the so do I enhance the feature.

137
00:13:11.990 --> 00:13:16.670
Byung-Woo Jun: This is one of the example. China, mobile China telecom intend to even close loop.

138
00:13:16.710 --> 00:13:38.070
Byung-Woo Jun: and they select this field to the the own app component, and then the creating complete their solution. So we are moving from platform to individual the catalog concept. And then we tried the building building with showcase, how to aggregate own app component for greater solutions. That's the one thing

139
00:13:38.160 --> 00:13:49.490
Byung-Woo Jun: and then focus radio manage the right size and focus function. This is what the owner streamlining. And then oem enabled these features.

140
00:13:49.520 --> 00:13:57.870
Byung-Woo Jun: So we can control size and focus function. And as I mentioned, we're gonna build some the lightweight on it.

141
00:13:58.847 --> 00:14:06.490
Byung-Woo Jun: Component, it won't have function solutions. So then we can we need that. So and then also see collaboration with other community

142
00:14:06.690 --> 00:14:10.820
Byung-Woo Jun: and then become valuable. Reference implementation choice.

143
00:14:11.330 --> 00:14:17.500
Byung-Woo Jun: Understand the organization, such as ft. 3 Gpt and portal and operator and vendors.

144
00:14:17.540 --> 00:14:27.660
Byung-Woo Jun: And then we continue a technology advanced and unique and value added feature to the telecom industry to make it relevant, otherwise only gonna disappear

145
00:14:28.100 --> 00:14:36.999
Byung-Woo Jun: and then continue enhancement on a component build and deployment security. That's what the Oem team is doing, and also other on a streamlining team

146
00:14:37.280 --> 00:14:41.200
Byung-Woo Jun: doing this and also secure cic progress.

147
00:14:41.580 --> 00:14:53.920
Byung-Woo Jun: So anyway, architecture, I think we share this one I mentioned. This is we building the the Icd pipeline creating owner in in the individual component, and then putting into artifacts

148
00:14:53.980 --> 00:15:06.540
Byung-Woo Jun: and then also using Jenkin and the philosophy and then using Deutsch telecom, using August city to deploy to our individual components. So we are seeing this as a first phase of the own funds.

149
00:15:07.350 --> 00:15:23.680
Byung-Woo Jun: and then this is, I share this one before. At the Budapest. Anyway, this is once you achieve that, we can support generic capacity based vendor, only a operator they can use delivery pipeline. They can mix to their their component in their own environments.

150
00:15:23.710 --> 00:15:24.760
Byung-Woo Jun: And

151
00:15:25.160 --> 00:15:29.220
Byung-Woo Jun: this is kind of also I talked to China, mobile China telecom.

152
00:15:29.520 --> 00:15:33.730
Byung-Woo Jun: and probably this is a good use case for Oslo.

153
00:15:33.920 --> 00:15:45.170
Byung-Woo Jun: and then connection to Oran and nephew. That's the one of the the also focus area, we think. But if you have any suggestion, other and objection, please let us know.

154
00:15:45.490 --> 00:15:52.170
Byung-Woo Jun: So here for the continuing streamlining and via the right way on a core network automation.

155
00:15:52.380 --> 00:16:13.529
Byung-Woo Jun: and then for the we normalize and standardize the core component interface. We want the more standard based, and then, or the flexible based interfaces intended to expand the important and then decorative is important to communicate the nephew, and then possibly Oran, because Oran is leveraging nephew frame of architecture.

156
00:16:13.930 --> 00:16:16.130
Byung-Woo Jun: And then we want to offer

157
00:16:16.180 --> 00:16:23.860
Byung-Woo Jun: own an individual component function for building or an smanko. I already have some plan

158
00:16:23.910 --> 00:16:47.945
Byung-Woo Jun: and some architectural join for that. So and that's what we trying to focus. So we're gonna discuss more detail, a policy based and secure announcement and logging design implementation. I think Tata communication Andrews, they mentioned about the logging implementation design you know. Probably possibly they can contribute to also Tata communications through the.

159
00:16:48.360 --> 00:16:48.750
Andreas GEISSLER (DT): No

160
00:16:49.330 --> 00:16:50.400
Andreas GEISSLER (DT): minutes.

161
00:16:50.850 --> 00:17:00.680
Byung-Woo Jun: So that's the one I put and sec. Pipeline. We are adding the security secure. C. Id. Pipeline. We have some study case how to make a security Icd.

162
00:17:01.070 --> 00:17:08.360
Byung-Woo Jun: And signing verification as from some of them signing, and Som is already doing it. But we want to secure side seating.

163
00:17:08.380 --> 00:17:09.890
Byung-Woo Jun: So there's the one.

164
00:17:09.920 --> 00:17:24.220
Byung-Woo Jun: And I mentioned about the only one maintained project management. So we remove the Msp. And Cts. Temporal from the Montreal. But we are removing today. Andrea is gonna discuss further. But after that we're gonna add more. But for now

165
00:17:24.329 --> 00:17:36.310
Byung-Woo Jun: Cri university email, Ml, and then pass free Vfc and scatter which can be moved. Let's, you know, wait for the Andrews to report and our boarding tomorrow today.

166
00:17:36.970 --> 00:17:49.209
Byung-Woo Jun: And this is the collaboration I mentioned before. And then this is so what junk input I'm gonna briefly introduce to what owner the individual component can contribute to, or in a similar build.

167
00:17:49.260 --> 00:17:50.390
Byung-Woo Jun: And then

168
00:17:50.440 --> 00:17:54.770
Byung-Woo Jun: this is China mobile. I'm not sure how the China mobile team is here.

169
00:17:56.290 --> 00:17:57.510
Byung-Woo Jun: Kate.

170
00:17:58.010 --> 00:18:08.209
Byung-Woo Jun: no, not here. The okay channel telecom team is using. Okay, anyway. So I'm gonna go over quickly and the the channel over keg one he shared with his view.

171
00:18:08.910 --> 00:18:14.309
Byung-Woo Jun: There will continue, carry out work, related the larger, moderate, and autonomous networking on it.

172
00:18:14.340 --> 00:18:25.419
Byung-Woo Jun: They are doing something for New Delhi, and then they believe the owner is relevant for 5G. And coming. 6 g. Based on the AI based architecture.

173
00:18:25.460 --> 00:18:33.690
Byung-Woo Jun: And in oh, any summit Huai and China Mobile. They are introducing the cloud native AI plan for 60,

174
00:18:33.750 --> 00:18:41.490
Byung-Woo Jun: and then we I just put up, you know, Mark. There, I think, though, this after already Summit, probably they're gonna already know about this.

175
00:18:41.800 --> 00:18:46.989
Byung-Woo Jun: And then one of the other suggestion from tag one, and then to a mobile.

176
00:18:47.310 --> 00:18:50.990
Byung-Woo Jun: its owner component can be released, and independently. That's

177
00:18:51.040 --> 00:19:00.500
Byung-Woo Jun: already we have it. And but there is lack of official guidance on how to combine existing audio functionality to achieve, to create next level solution.

178
00:19:00.530 --> 00:19:11.089
Byung-Woo Jun: So this is what we focus. Also, initially, I was thinking, we can do for our new daily, but we have no chance to handle that. But this is a lot of documentation

179
00:19:11.130 --> 00:19:14.889
Byung-Woo Jun: and guidance for users. So

180
00:19:15.690 --> 00:19:17.500
Byung-Woo Jun: why are we doing quote

181
00:19:17.840 --> 00:19:27.970
Byung-Woo Jun: lightweight? Call on it the solution, maybe you can, creating some kind of documentation catalog and guidance for that. That's my think their way.

182
00:19:28.190 --> 00:19:33.829
Byung-Woo Jun: and then they won't decide to release a streamlined a version of on it. And

183
00:19:34.261 --> 00:19:53.929
Byung-Woo Jun: Aka a lightweight on it to include this call network automation function. This is the kind of you know, example. But it can be so Sbc Eps was to mention policy, uui etc. And we are reducing the deployment, complexity and resource consumption. So that's the what channel mobile focus.

184
00:19:54.500 --> 00:20:22.270
Byung-Woo Jun: And they explain about the Ui intent based network automation and those. So they envision how owner can talking to nephew so. And this is their first phase and owner. Ui going through the own app, the you know, the core the components, and talking to owner, the nephew and or or N, and based on standard. And then this is next division. It's possible.

185
00:20:22.300 --> 00:20:27.650
Byung-Woo Jun: Intend on. Now, analysis server can talking injector intend to

186
00:20:27.790 --> 00:20:33.359
Byung-Woo Jun: nephew directly. So anyway, this is intense. Okay? Going to see. I'm gonna move on to.

187
00:20:33.780 --> 00:20:42.539
Byung-Woo Jun: And this is challenging. So telecom don't want to share this key function deployment intent based network. They're gonna continue

188
00:20:43.043 --> 00:20:51.090
Byung-Woo Jun: intent driven automation continue to collaborate and generate outcome and poc with etho, and if they are doing it

189
00:20:51.110 --> 00:21:00.410
Byung-Woo Jun: and then current progress are in the requirements. Some of the requirement data service enhancement of intend driven network in ui that start doing in

190
00:21:00.490 --> 00:21:02.590
Byung-Woo Jun: you daily and then

191
00:21:02.680 --> 00:21:05.939
Byung-Woo Jun: challenges is they have a difficulty

192
00:21:06.030 --> 00:21:32.609
Byung-Woo Jun: to to deploy on a release prior to London. I think them basically aft expiry. But we got removed that issue and OM. Already to enhance that, we will apply the new security architecture without Af. That's a good thing. We don't have that many challenges, actually, or in Sm, where they have a similar challenges problem. So we already inform Andrews, informed that we don't have, they don't have to use af any longer.

193
00:21:32.670 --> 00:21:38.570
Byung-Woo Jun: and future will keep collaborate on a community. And AI ml, that's predicting and 60,

194
00:21:38.640 --> 00:21:44.510
Byung-Woo Jun: and then out in the and then intend to. Even so, I actually just on a mobile channel telecom their focus,

195
00:21:44.830 --> 00:21:47.330
Byung-Woo Jun: intangible natural automation works.

196
00:21:47.699 --> 00:21:56.789
Byung-Woo Jun: This is then, then disappeared. Okay, anyway. So anyway, I'm gonna collect additional input, from China, mobile or or simplify, this is what they done.

197
00:21:56.880 --> 00:22:07.300
Byung-Woo Jun: And this is today thinking about the candidate for a lightweight call on it and then additional they already mentioned about cps. Right? So anyway, they're going to do.

198
00:22:07.580 --> 00:22:14.250
Byung-Woo Jun: And this is how they are the conform to the industry standard and the Stos.

199
00:22:14.580 --> 00:22:26.992
Byung-Woo Jun: and then how we vision. They are focusing on the incident. Api enhancement to unify instant management as so we can simplify portal

200
00:22:27.610 --> 00:22:39.349
Byung-Woo Jun: close loop handling. So that's we're gonna briefly introduce that one and those telecom and Ngs here, those telecom plans deploy only a call in

201
00:22:39.430 --> 00:22:42.669
Byung-Woo Jun: your production environment next year, which is great news

202
00:22:42.750 --> 00:22:43.769
Byung-Woo Jun: or on it

203
00:22:43.890 --> 00:22:56.050
Byung-Woo Jun: and then based on on it, based on the used case, some of the owner component, not all owner component, some of the selected owner components, such as it AI and Cps, Dvs, and a policy

204
00:22:56.070 --> 00:23:06.849
Byung-Woo Jun: can be selected and to use for their production environment. That's the next year. So that's why Andrew's team, and owing, they built on a stream learning and the owners

205
00:23:06.890 --> 00:23:22.989
Byung-Woo Jun: oem script enhancement for individual owner orchestration build and deployment progress. So this is the what we think Tsc and Pablo and 3 tears vice. We talk about this, and then we collect the operators. Input

206
00:23:23.080 --> 00:23:52.899
Byung-Woo Jun: and then we going to introduce our plan and our problem, our challenges to our elephant community. At the elephant. Dt, that's the current the plan. So I share the this slide that draft. And so if you have any company the input, please send to me and to send to us. And then the Pablo and Kevin, and don't want me. And then we gonna you know, enhance the the slide it before on the

207
00:23:52.950 --> 00:23:56.580
Byung-Woo Jun: refund. Dtf, okay, I'm gonna stop share.

208
00:23:56.590 --> 00:24:03.969
Byung-Woo Jun: And then any questions you can send me email. And then we're gonna discuss. And then next, Tsc, we're gonna have some feedback session.

209
00:24:04.020 --> 00:24:09.519
Byung-Woo Jun: If you have anything feel free to contact 4 of us. I'll stop sharing here.

210
00:24:11.170 --> 00:24:11.960
Byung-Woo Jun: Okay.

211
00:24:11.960 --> 00:24:14.589
Paweł Pawlak: Thank you. Okay, let me

212
00:24:15.110 --> 00:24:16.460
Paweł Pawlak: come back to

213
00:24:17.670 --> 00:24:19.100
Paweł Pawlak: the screen

214
00:24:19.220 --> 00:24:20.750
Paweł Pawlak: within the agenda.

215
00:24:23.310 --> 00:24:26.049
Paweł Pawlak: Okay, so for voting.

216
00:24:27.730 --> 00:24:31.319
Paweł Pawlak: I'm not sure we have a quorum to vote today.

217
00:24:34.570 --> 00:24:36.570
Byung-Woo Jun: Cool. I've only seen 4.

218
00:24:37.180 --> 00:24:40.210
Paweł Pawlak: Yeah, keep going. He's here. Ishanka is here.

219
00:24:40.210 --> 00:24:41.580
Keguang He: Alright for leads. Yes.

220
00:24:42.030 --> 00:24:43.849
Paweł Pawlak: Yeah, no problem. So.

221
00:24:44.600 --> 00:24:45.009
Byung-Woo Jun: One more.

222
00:24:45.010 --> 00:24:47.420
Paweł Pawlak: So we have 5. We are no, we have 5. Right?

223
00:24:47.420 --> 00:24:48.549
Byung-Woo Jun: You're fine. Okay?

224
00:24:48.740 --> 00:24:49.689
Byung-Woo Jun: But this is.

225
00:24:49.690 --> 00:24:52.829
Paweł Pawlak: Good good one is here, and and Shankar is here.

226
00:24:53.230 --> 00:24:54.229
Andreas GEISSLER (DT): Yeah, good guys.

227
00:24:54.230 --> 00:24:57.330
Paweł Pawlak: I will make you make make you beautiful. Color.

228
00:24:58.240 --> 00:24:58.810
Andreas GEISSLER (DT): Just.

229
00:24:59.843 --> 00:25:00.876
Byung-Woo Jun: Okay.

230
00:25:02.171 --> 00:25:04.000
Paweł Pawlak: Thank you. Thank you of you.

231
00:25:04.000 --> 00:25:04.890
Byung-Woo Jun: Cheers! Oh.

232
00:25:04.890 --> 00:25:05.910
Paweł Pawlak: Okay? Hmm.

233
00:25:07.310 --> 00:25:08.920
Paweł Pawlak: so in this case.

234
00:25:08.980 --> 00:25:11.609
Paweł Pawlak: I think we could vote right.

235
00:25:14.180 --> 00:25:15.700
Byung-Woo Jun: Yeah, we can. Book, yes.

236
00:25:18.635 --> 00:25:19.680
Paweł Pawlak: Okay.

237
00:25:19.950 --> 00:25:21.729
Paweł Pawlak: So the voting

238
00:25:22.230 --> 00:25:25.350
Paweł Pawlak: is for the unmenting projects deprecation.

239
00:25:25.740 --> 00:25:27.580
Paweł Pawlak: After going through the

240
00:25:27.660 --> 00:25:31.339
Paweł Pawlak: list from, and Jess and Jess, would you like to refer the list.

241
00:25:31.340 --> 00:25:32.828
Andreas GEISSLER (DT): Yes, I can do

242
00:25:34.010 --> 00:25:35.350
Paweł Pawlak: So this is a new.

243
00:25:35.350 --> 00:25:38.500
Andreas GEISSLER (DT): I think that you can open it. Yeah, you can open that.

244
00:25:38.500 --> 00:25:39.120
Paweł Pawlak: Yes.

245
00:25:39.120 --> 00:26:03.234
Andreas GEISSLER (DT): So yeah, we had the list which I created. Based on, let's say, on one hand, the deprecation of the maintenance of the message router where we have to select certain components which we cannot per default. Deploy anymore when the message router is removed

246
00:26:03.770 --> 00:26:10.680
Andreas GEISSLER (DT): and we had some components which are, let's say, not maintained since a couple of releases. And

247
00:26:11.074 --> 00:26:14.350
Andreas GEISSLER (DT): that's the question whether we have to. We should

248
00:26:14.928 --> 00:26:35.960
Andreas GEISSLER (DT): remove them or not remove them, but we disable it from the default deployment in owner. Yeah, the removal from charts. It's not the case now at the moment. But the they still in are in there, but in the default setup they will be just set to off so that it's not deployed in the, in the, in the field.

249
00:26:36.310 --> 00:26:51.159
Andreas GEISSLER (DT): So this is cli. So it was already discussed, I think, with thanks you from so so young. That did that, and he agreed that it's that it could can be removed. We have

250
00:26:51.570 --> 00:27:00.819
Andreas GEISSLER (DT): of DC gen components which are depending on the the message router.

251
00:27:00.920 --> 00:27:09.999
Andreas GEISSLER (DT): They would need to be disabled as long as they are not needed, so that means when they are would be needed, they would need to be patched

252
00:27:10.110 --> 00:27:22.100
Andreas GEISSLER (DT): to be let's say, compatible with a native Kafka. So that means we can enable that again. But then it has a bit to be. Some implementation changes to be done on these components. Yeah.

253
00:27:22.896 --> 00:27:31.760
Andreas GEISSLER (DT): Then, of course, the d map itself. There, when we deprecate or we remove the message router.

254
00:27:32.050 --> 00:27:58.079
Andreas GEISSLER (DT): we also deprecate the components which are using the message. Router sorry that which are using the data router, which would be the data file collector actually, and the Pm. Mapper, which is depending on a data file collector itself. So then it would make sense to completely disable the the the d map. Actually. So that would be the

255
00:27:58.080 --> 00:28:07.379
Andreas GEISSLER (DT): the consequence. So if there is no user of of the data router also, then we can also disable the the map completely from deployment. Yeah.

256
00:28:07.780 --> 00:28:08.660
Andreas GEISSLER (DT): And

257
00:28:09.250 --> 00:28:30.730
Andreas GEISSLER (DT): yeah, then, Holmes, I think it's not maintained, since whatever releases, I don't think that we we would need that. The modeling, which is only the Etsy catalog chart. Is not changed and then dengue was I think we was agreeing with that.

258
00:28:31.170 --> 00:28:51.989
Andreas GEISSLER (DT): The Msb, we have already decided one or 2 releases before that. As we have now the issue ingress, we don't need that anymore. It will be. Anyway, it can be disabled the Nbi, which is at the moment depending on the message router. We would also need to disable

259
00:28:51.990 --> 00:29:13.266
Andreas GEISSLER (DT): for the time being, if no one is using it. And of course, as I said, we have some patches here, but we have to to, let's say, extract them from our implementation, then to make it available for Ndi if it's needed later, the of as well. So I don't see any use case currently, which is providing that

260
00:29:13.800 --> 00:29:18.389
Andreas GEISSLER (DT): in the Sdnc. The the D Map listener

261
00:29:18.670 --> 00:29:41.569
Andreas GEISSLER (DT): would be affected, so that would mean we would then disable it from deployment. And I have not seen any any issues. The I think, just for some use cases they have. This was implemented. But from the core functionality the map listener in Sdc's Sdnc. Is not needed.

262
00:29:42.110 --> 00:30:00.920
Andreas GEISSLER (DT): and the Vfc it was correctly. Also agreed with Kejuan, so that as there are no let's say, further developments ongoing on that we also should disable it. And the Vnf. SDK. This is also just, let's say, agreed with

263
00:30:01.826 --> 00:30:05.709
Andreas GEISSLER (DT): dung su. That could also be disabled in that way.

264
00:30:07.390 --> 00:30:10.426
Paweł Pawlak: Okay? And we have. And we have those comments here.

265
00:30:10.730 --> 00:30:11.380
Andreas GEISSLER (DT): You know great.

266
00:30:11.380 --> 00:30:15.892
Byung-Woo Jun: Yeah, just to, you know, collection input from them, you know. So.

267
00:30:16.470 --> 00:30:20.000
Paweł Pawlak: Okay? Questions from the Tst members

268
00:30:20.330 --> 00:30:21.690
Paweł Pawlak: before voting.

269
00:30:22.250 --> 00:30:24.658
N.K. Shankaranarayanan: Yeah, I just have one clarification.

270
00:30:25.650 --> 00:30:31.839
N.K. Shankaranarayanan: So, Andreas, if this is, if I understand, this is about not being part of the standard OM.

271
00:30:32.190 --> 00:30:38.650
N.K. Shankaranarayanan: But in some sense the code will be still available if somebody still using the message Router.

272
00:30:39.450 --> 00:30:40.150
Andreas GEISSLER (DT): Hmm.

273
00:30:40.850 --> 00:30:41.999
N.K. Shankaranarayanan: Is that correct? Yeah.

274
00:30:42.000 --> 00:30:58.430
Andreas GEISSLER (DT): Yes, you could. You could enable it, of course, from the standard deploy. So in the in the hound chart, so it will not disappear from the hound charts at the moment. Yeah, so you could just enable it. So they are still in there. But we we won't do not want to.

275
00:30:58.470 --> 00:31:03.860
Andreas GEISSLER (DT): Let's say this, or let's say, yeah, deploy it from any.

276
00:31:03.860 --> 00:31:05.610
Paweł Pawlak: So we commented, kind of right?

277
00:31:05.610 --> 00:31:06.270
N.K. Shankaranarayanan: This.

278
00:31:06.530 --> 00:31:07.679
Paweł Pawlak: Is still, you know.

279
00:31:07.680 --> 00:31:08.310
N.K. Shankaranarayanan: And the charts.

280
00:31:08.310 --> 00:31:13.251
Paweł Pawlak: It's commented. If somebody is willing to use it, then must uncomment it right kind of.

281
00:31:13.560 --> 00:31:15.889
N.K. Shankaranarayanan: I think, thanks. Yeah. Got it because that.

282
00:31:15.890 --> 00:31:16.340
Byung-Woo Jun: So, and.

283
00:31:16.340 --> 00:31:16.940
N.K. Shankaranarayanan: Yeah, are.

284
00:31:18.380 --> 00:31:19.680
Byung-Woo Jun: Go ahead, go ahead, please.

285
00:31:20.540 --> 00:31:21.230
Byung-Woo Jun: Bro.

286
00:31:22.100 --> 00:31:23.430
Paweł Pawlak: Just send that out. Yes.

287
00:31:23.430 --> 00:31:27.199
N.K. Shankaranarayanan: Yeah, I said, there are some projects which are might be still using

288
00:31:27.380 --> 00:31:34.499
N.K. Shankaranarayanan: remap. I don't know if they'll switch to Kafka, but as long, but they're not using Om in this manner. So.

289
00:31:34.800 --> 00:31:36.499
Andreas GEISSLER (DT): Yeah, yeah. Yeah, yeah.

290
00:31:36.870 --> 00:31:42.809
Andreas GEISSLER (DT): that's right. So they can use it still. But as I said so

291
00:31:43.635 --> 00:31:50.729
Andreas GEISSLER (DT): it is not maintained any longer. But if if they want to use it still, that that can be still done. Yeah, yeah.

292
00:31:52.620 --> 00:31:55.300
Byung-Woo Jun: Andrea's question, so

293
00:31:55.810 --> 00:31:59.789
Byung-Woo Jun: so on. Maintain project. There is the process, we

294
00:32:00.250 --> 00:32:21.990
Byung-Woo Jun: not just the mark for not deploying. And also, you know, we totally archive it. So many of the project, for example, we archive. So that means not part of that. So the current today, what you see, although you know, cli homes sic catalog. Msp, you know Nbi Vnfs gave

295
00:32:22.020 --> 00:32:28.119
Byung-Woo Jun: you wanna just to put this you you wanna disable, or you wanna go for archive.

296
00:32:28.500 --> 00:32:32.540
Byung-Woo Jun: Those things looks like Oshanko. You want to

297
00:32:32.630 --> 00:32:34.270
Byung-Woo Jun: email email

298
00:32:34.350 --> 00:32:37.899
Byung-Woo Jun: in the hand chart and then not archiving.

299
00:32:38.440 --> 00:33:02.879
Andreas GEISSLER (DT): A at the end. It is the decision of the of the of of us, or or so of all of us. If we archive this as well, that's that's that's completely. Also, I would be fine with that. If there's no no, no project using it or update updating it. We can archive that as well. But then we can maybe in the next release remove even the helm charts. Basically, yeah.

300
00:33:03.030 --> 00:33:10.729
Byung-Woo Jun: Okay, okay, so that's fine. That's fine. We just wanna which you want to archive. Which one to completely move from it.

301
00:33:10.970 --> 00:33:11.740
Byung-Woo Jun: Yep.

302
00:33:12.770 --> 00:33:14.660
Byung-Woo Jun: alright. Fine.

303
00:33:16.980 --> 00:33:18.100
Paweł Pawlak: Okay.

304
00:33:18.360 --> 00:33:19.370
Paweł Pawlak: so

305
00:33:19.960 --> 00:33:23.749
Paweł Pawlak: last, call for questions, guys, if you have any

306
00:33:24.060 --> 00:33:27.749
Paweł Pawlak: for this proposal, is it clear for everyone what we want to

307
00:33:28.440 --> 00:33:32.260
Paweł Pawlak: hold on. I'm removing those unmandined

308
00:33:33.970 --> 00:33:35.980
Paweł Pawlak: projects from the core.

309
00:33:37.700 --> 00:33:38.660
Byung-Woo Jun: I'm fine.

310
00:33:39.430 --> 00:33:40.499
Byung-Woo Jun: Okay, we will.

311
00:33:40.500 --> 00:33:52.700
Andreas GEISSLER (DT): To do at least the integration team. Or that's basically as well, me or Mike. We would need them to, let's say, change the current.

312
00:33:52.750 --> 00:34:17.220
Andreas GEISSLER (DT): let's say checks. Right? So so the all the hell, the all the the health checks and so on, and and and and smoke tests which con, which include these components would need to be disabled at least from the gating, because if we don't deploy them, of course we cannot use them in in in certain tests, so that has to be still done. But that's the second step.

313
00:34:22.440 --> 00:34:27.410
Paweł Pawlak: Okay. So I'm crafting some some message in chat. Sorry, guys, it's my first time I'm

314
00:34:27.460 --> 00:34:30.250
Paweł Pawlak: doing this kind of exercise. So

315
00:34:56.719 --> 00:34:57.590
Paweł Pawlak: buckets.

316
00:34:58.180 --> 00:34:59.290
Paweł Pawlak: So

317
00:34:59.590 --> 00:35:04.210
Paweł Pawlak: we start the voting process for the UN. Maintained project deprecation

318
00:35:04.600 --> 00:35:05.940
Paweł Pawlak: pay.

319
00:35:07.290 --> 00:35:13.039
Paweł Pawlak: as described by Andreas in in, in the In the link, right that you can see. So, please.

320
00:35:13.670 --> 00:35:19.950
Paweł Pawlak: and maybe I should do start votes. But okay, I I I know that we start voting. So I hope this is still in line

321
00:35:20.340 --> 00:35:23.340
Paweł Pawlak: with the with the process. So please.

322
00:35:23.600 --> 00:35:25.190
Paweł Pawlak: now it's time to vote.

323
00:35:29.560 --> 00:35:31.560
Byung-Woo Jun: One more, one more.

324
00:35:32.430 --> 00:35:32.800
Paweł Pawlak: A

325
00:35:36.060 --> 00:35:41.220
Paweł Pawlak: okay, I will now officially stop voting by vote end.

326
00:35:43.130 --> 00:35:46.499
Paweł Pawlak: So thank you very much. So I will put the comment here

327
00:35:46.990 --> 00:35:49.260
Paweł Pawlak: that Tsc. Agreed to.

328
00:35:50.550 --> 00:35:50.960
Byung-Woo Jun: Yep.

329
00:35:50.960 --> 00:35:53.900
Paweł Pawlak: Approved, approved by Tsc. Or something like this, right.

330
00:35:54.140 --> 00:35:55.000
Byung-Woo Jun: Hang.

331
00:35:55.000 --> 00:35:56.080
Paweł Pawlak: Okay.

332
00:35:57.080 --> 00:35:58.230
Paweł Pawlak: votes.

333
00:35:58.330 --> 00:35:59.510
Paweł Pawlak: Voting

334
00:36:00.070 --> 00:36:00.970
Paweł Pawlak: approved

335
00:36:02.340 --> 00:36:04.229
Paweł Pawlak: by Tsc.

336
00:36:05.790 --> 00:36:08.260
Paweł Pawlak: okay, so this is our.

337
00:36:10.480 --> 00:36:11.900
Paweł Pawlak: thank you very much.

338
00:36:12.480 --> 00:36:13.860
Byung-Woo Jun: Oh, G.

339
00:36:14.000 --> 00:36:14.920
Byung-Woo Jun: Yes. Bmw.

340
00:36:14.920 --> 00:36:15.730
Paweł Pawlak: Documents.

341
00:36:16.020 --> 00:36:44.419
Byung-Woo Jun: Next one. I you know, I just put that, but I don't think we are deported. But this one we have a tradition step so after Tsc, both, what are you gonna do? So we're gonna follow on this step, one through you know, 13 or 14. So anyway, I'm gonna book it, I'm gonna follow that. So since we approve that Tsc approving, I'm gonna which, you know, after Andreas and decide, we're gonna go through that transition to make it official. That's all.

342
00:36:44.820 --> 00:36:47.200
Paweł Pawlak: Okay, okay, thank you, Bill.

343
00:36:47.600 --> 00:36:52.889
Paweł Pawlak: Okay, guys, moving forward. I'm not sure if Jess joined.

344
00:36:54.220 --> 00:37:01.489
Paweł Pawlak: But maybe, Kevin, you are off on board on up to Cm. Inside. V. 3. What is the topic here?

345
00:37:03.630 --> 00:37:04.890
Kevin Sandi: Yeah, there was some questions

346
00:37:04.900 --> 00:37:14.331
Kevin Sandi: in the past meetings about a not, seeing data for own up on the new version of insights. So Jessica was,

347
00:37:15.270 --> 00:37:18.360
Kevin Sandi: Trying to work on that? But she figured out that

348
00:37:18.480 --> 00:37:33.049
Kevin Sandi: it's more complicated does that than expected, because it has to be like e every the way the new version of insights works. The onboarding is like a more, time time consuming a task.

349
00:37:33.160 --> 00:37:39.339
Kevin Sandi: So I believe she's still working on that, I I haven't heard of any updates on that.

350
00:37:39.510 --> 00:37:45.929
Kevin Sandi: But the the last time I hear about it is that, she's coordinating with with on boarding team, how to

351
00:37:46.110 --> 00:37:55.490
Kevin Sandi: how to tackle on up for the onboarding, because there are many projects so apparently each project will have to be on boarded, one by one.

352
00:37:55.780 --> 00:38:00.850
Paweł Pawlak: Okay, okay, so I'll put the work in progress. Mark, right? And we can check next next time

353
00:38:01.270 --> 00:38:02.590
Paweł Pawlak: for the update.

354
00:38:02.610 --> 00:38:04.280
Paweł Pawlak: Okay, thank you. Kevin.

355
00:38:05.270 --> 00:38:08.779
Paweł Pawlak: Okay, we have the section for the Ptl updates.

356
00:38:09.160 --> 00:38:15.689
Paweł Pawlak: So just a reminder recommended packages upgrades available on the restricted wiki

357
00:38:15.720 --> 00:38:21.580
Paweł Pawlak: plus jiras created. We haven't seen too much progress here, so, please.

358
00:38:22.650 --> 00:38:27.780
Paweł Pawlak: it's more for the details to to plan accordingly and and work on those upgrades

359
00:38:29.670 --> 00:38:31.449
Toine Siebelink: So for the 10 years.

360
00:38:31.650 --> 00:38:38.690
Toine Siebelink: Hi, yeah, maybe I've missed something. So what we have these say, I'm actually not quite sure where you're on the screen.

361
00:38:38.810 --> 00:38:41.382
Toine Siebelink: Which way have these be communicated? Is

362
00:38:42.110 --> 00:38:43.210
Toine Siebelink: updates.

363
00:38:46.320 --> 00:38:53.509
Paweł Pawlak: Well, we do on our side. We do every month kind of review of the of the Progress. Right? So

364
00:38:54.110 --> 00:38:57.049
Paweł Pawlak: time it was done beginning of the of the April.

365
00:38:57.150 --> 00:38:58.780
Paweł Pawlak: So it was

366
00:38:59.140 --> 00:39:01.410
Paweł Pawlak: highlighting that they were not.

367
00:39:01.450 --> 00:39:06.250
Paweł Pawlak: When when we are checking the outputs of the Clm. Jobs, right.

368
00:39:06.712 --> 00:39:09.190
Paweł Pawlak: We are comparing number of vulnerabilities

369
00:39:09.350 --> 00:39:11.200
Paweł Pawlak: from the previous scan.

370
00:39:11.560 --> 00:39:14.699
Paweł Pawlak: and then we see if some something happened or not.

371
00:39:14.930 --> 00:39:15.390
Toine Siebelink: That's fine.

372
00:39:16.870 --> 00:39:17.680
Toine Siebelink: Yeah.

373
00:39:18.303 --> 00:39:28.546
Toine Siebelink: But are you communicating? Sorry about what I'm wondering about? What we yeah, previously, I think, what's the name she used to create tickets for.

374
00:39:28.940 --> 00:39:32.320
Paweł Pawlak: Tickets were created for each project. Amy, Amy created tickets.

375
00:39:32.320 --> 00:39:42.682
Toine Siebelink: Oh, okay, yes. I was wondering about. I'm not aware, maybe just simple. No tickets for for cps, so I'll I'll double check it again. But

376
00:39:43.480 --> 00:39:48.890
Paweł Pawlak: Every project, but I can double check and and send you some more details. Offline if you want.

377
00:39:49.150 --> 00:39:56.079
Toine Siebelink: Yeah, yeah, I'm just not aware of a ticket for cps. But maybe if we miss it somehow, I'll I'll double check it again. Anyway. Thanks, Pablo.

378
00:39:56.080 --> 00:39:59.166
Paweł Pawlak: Okay, okay, thank you for for raising this point.

379
00:40:00.150 --> 00:40:01.659
Paweł Pawlak: Juan, okay, thanks

380
00:40:04.210 --> 00:40:08.610
Paweł Pawlak: I don't know, if there is progress for Mg portal,

381
00:40:09.910 --> 00:40:16.899
Paweł Pawlak: I I had the impression that the meeting is needed with Matt and with Jessica and Fita.

382
00:40:17.470 --> 00:40:19.990
Paweł Pawlak: But I'm not sure if it happened.

383
00:40:20.470 --> 00:40:25.720
Andreas GEISSLER (DT): I'm not also not sure because we have this week complete the complete

384
00:40:26.620 --> 00:40:29.040
Andreas GEISSLER (DT): of a planning week.

385
00:40:29.040 --> 00:40:29.689
Paweł Pawlak: Yeah, okay.

386
00:40:29.690 --> 00:40:34.462
Andreas GEISSLER (DT): So, therefore maybe this week it will not or wouldn't.

387
00:40:34.940 --> 00:40:38.259
Paweł Pawlak: We will check on Monday in this.

388
00:40:38.260 --> 00:40:39.099
Byung-Woo Jun: Yeah, nice thing.

389
00:40:39.100 --> 00:40:40.269
Paweł Pawlak: Thank you at your fiance.

390
00:40:40.270 --> 00:40:41.999
Byung-Woo Jun: Yeah. Good. Good. Good.

391
00:40:42.000 --> 00:40:46.419
Paweł Pawlak: Okay, so this is already covered. Hmm.

392
00:40:46.670 --> 00:40:54.940
Paweł Pawlak: we have this one more item for the Pts update. So documentation work. There were 2 items remaining. Right address.

393
00:40:54.940 --> 00:41:11.439
Andreas GEISSLER (DT): Yes, there were 2 2 items of May remaining also here. We have to check. So whether whokash will will provide or help us for that, at least for the, for the my for the multi cloud component.

394
00:41:11.440 --> 00:41:24.965
Andreas GEISSLER (DT): The other one, maybe, is not this relevant? This was from of I don't think that we will manage or will use that at all, so let's see so. But to be the the multi cloud one. I I we will check with with

395
00:41:25.587 --> 00:41:29.459
Andreas GEISSLER (DT): with Wukash, but he's also on that on that planning. That's the the.

396
00:41:29.460 --> 00:41:33.880
Paweł Pawlak: Yeah, okay, next week. Next week. I I I hear you, okay, no problem.

397
00:41:34.230 --> 00:41:37.010
Paweł Pawlak: And then subcommittee update view.

398
00:41:37.786 --> 00:41:46.810
Byung-Woo Jun: It's already presented there. This, my slide. The so any comment please contact outcome. And then we're gonna modify. Okay.

399
00:41:46.960 --> 00:41:47.830
Byung-Woo Jun: yes, thank.

400
00:41:47.830 --> 00:41:48.520
Paweł Pawlak: Thank you

401
00:41:48.990 --> 00:41:51.129
Paweł Pawlak: or M. Update, address.

402
00:41:53.043 --> 00:42:03.616
Andreas GEISSLER (DT): Well, we have so far most of these most of the patches are are in. We have one issue.

403
00:42:04.924 --> 00:42:11.029
Andreas GEISSLER (DT): as Dan is here. Then are you checking the

404
00:42:12.990 --> 00:42:30.639
Andreas GEISSLER (DT): The slack channel of the CC. SDK, because a sunket has a couple of issues found on the Sdnc during his his changes for the Rfc update for the So.

405
00:42:30.820 --> 00:42:34.950
Andreas GEISSLER (DT): And he wanted to get some confirmation from you.

406
00:42:35.590 --> 00:42:37.179
Andreas GEISSLER (DT): Because I think?

407
00:42:37.758 --> 00:42:58.379
Andreas GEISSLER (DT): Yeah, he will. He's he has updated the Sso. Accordingly. But still has issues, and he thinks that. And he found some issues in the Sdnc. Code which he doesn't know whether there was someone working? Or is someone working on that or not

408
00:42:58.630 --> 00:43:08.669
Andreas GEISSLER (DT): to to make this or to get this ready? Otherwise we still we will still have then issues when the Sdnc update is done for new daily.

409
00:43:09.320 --> 00:43:10.140
Andreas GEISSLER (DT): and the S always.

410
00:43:10.140 --> 00:43:10.880
Dan Timoney (AT&T): Yeah. Ready.

411
00:43:10.880 --> 00:43:12.249
Andreas GEISSLER (DT): For for that. Yeah.

412
00:43:13.380 --> 00:43:17.259
Dan Timoney (AT&T): Yeah, I see his comments now. I have missed them before. I'll I'll take a look at them.

413
00:43:17.450 --> 00:43:18.210
Andreas GEISSLER (DT): Yeah, okay.

414
00:43:18.210 --> 00:43:23.770
Dan Timoney (AT&T): I do know there are updates we have to make internally, some, some of them complete changes, and some of them might be code changes.

415
00:43:24.240 --> 00:43:25.360
Dan Timoney (AT&T): Yeah, right?

416
00:43:25.750 --> 00:43:26.440
Andreas GEISSLER (DT): That would be great.

417
00:43:28.380 --> 00:43:30.980
Dan Timoney (AT&T): Yes. Okay.

418
00:43:30.980 --> 00:43:34.543
Paweł Pawlak: So done, please please check and and come back to to us.

419
00:43:35.453 --> 00:43:38.459
Paweł Pawlak: what's more specifically to to Andreas and the team.

420
00:43:38.770 --> 00:43:39.390
Byung-Woo Jun: I'm just.

421
00:43:39.920 --> 00:43:40.606
Paweł Pawlak: Thank you

422
00:43:42.350 --> 00:43:50.289
Paweł Pawlak: alright. Just a reminder we have. We have upcoming events right in in the end of April beginning of May.

423
00:43:50.802 --> 00:43:56.089
Paweł Pawlak: Being. Would you like to give an update for the for the agenda for Friday?

424
00:43:56.350 --> 00:43:58.280
Byung-Woo Jun: Sure. Can you? Can you hear me.

425
00:43:59.027 --> 00:43:59.679
Paweł Pawlak: We hear you.

426
00:44:00.170 --> 00:44:03.370
Byung-Woo Jun: Yeah. Okay. So if you click the last link.

427
00:44:03.680 --> 00:44:05.089
Paweł Pawlak: Last thing. Of course.

428
00:44:05.090 --> 00:44:06.330
Byung-Woo Jun: Yeah, their one, yeah.

429
00:44:07.760 --> 00:44:08.380
Dan Timoney (AT&T): Okay.

430
00:44:08.826 --> 00:44:16.860
Byung-Woo Jun: Go to delegate to May. Keep going. May second, second and third, yeah. Yeah. Second.

431
00:44:16.970 --> 00:44:18.139
Byung-Woo Jun: see if you scroll down.

432
00:44:18.970 --> 00:44:19.540
Dan Timoney (AT&T): Close.

433
00:44:19.540 --> 00:44:20.609
Byung-Woo Jun: Yeah, there you go.

434
00:44:20.890 --> 00:44:22.200
Byung-Woo Jun: And so

435
00:44:22.540 --> 00:44:30.590
Byung-Woo Jun: dtf, programming committee this Monday have decided we're going to schedule this way. So they said.

436
00:44:30.650 --> 00:44:40.269
Byung-Woo Jun: Thursday, may second is all the nephew Day, dedicated nephew in a day. So we're going to all attend the nephew today, so they are.

437
00:44:40.940 --> 00:44:47.110
Byung-Woo Jun: Have a several agenda. If you scroll down. You can see agenda. So they have up to whole day.

438
00:44:47.210 --> 00:44:51.590
Byung-Woo Jun: and they gonna describe to see sick ones

439
00:44:51.710 --> 00:44:55.850
Byung-Woo Jun: 2, 3, 4. Keep. If you keep scroll down there. 4,

440
00:44:56.010 --> 00:45:06.150
Byung-Woo Jun: so they're gonna do it. And then Friday, if you scroll back up Friday, since many people are leaving afternoon. So we squeeze the

441
00:45:06.440 --> 00:45:15.839
Byung-Woo Jun: the schedule. So anyway, for own app, I'm gonna start with the New Daily Release status. I'm preparing another slide and I can share next Tsc, briefly.

442
00:45:16.210 --> 00:45:32.099
Byung-Woo Jun: and followed by the Onts initiative for all the roadmap and strategy that I just did it, and then oem enhancement oops you going too fast. Om enhancement Andreas Geisel and all his colleague, and talk about the oem enhancement.

443
00:45:32.360 --> 00:45:34.200
Byung-Woo Jun: Then the

444
00:45:34.430 --> 00:45:41.189
Byung-Woo Jun: the quality, assurance, and security in software development. Modessa from second will present that.

445
00:45:41.280 --> 00:45:50.960
Byung-Woo Jun: and then, followed by Maggie from Nsa. Will provide operation security and open source. 5G mobile network. They're going to do.

446
00:45:51.010 --> 00:45:57.449
Byung-Woo Jun: And then, Sess, you're going to present a cross community collaboration case study.

447
00:45:57.630 --> 00:46:01.700
Byung-Woo Jun: and the last one is cps, demo twine

448
00:46:01.800 --> 00:46:07.580
Byung-Woo Jun: and twine. Sorry for the late one, but this is still before 2 o'clock. So so anyway.

449
00:46:07.580 --> 00:46:19.070
Toine Siebelink: No, yeah. I was just gonna ask you, can you? Because you're showing I'm not sure what time zone you're currently showing so it's ending at 2 2 pm. In the afternoon. Right? So.

450
00:46:19.390 --> 00:46:20.820
Byung-Woo Jun: Pm. Will end it.

451
00:46:21.570 --> 00:46:23.350
Toine Siebelink: It's gonna be.

452
00:46:23.350 --> 00:46:24.509
Byung-Woo Jun: Yeah, yeah, yeah. So you.

453
00:46:24.510 --> 00:46:27.590
Toine Siebelink: Yeah, no particular like being the last one. But okay.

454
00:46:27.590 --> 00:46:35.910
Byung-Woo Jun: I know, but you know people leaving like Maggie leaving Friday, many people leaving. So we tried to. Sorry about that. But

455
00:46:36.270 --> 00:46:37.669
Byung-Woo Jun: that's the only the.

456
00:46:37.770 --> 00:46:38.390
Dan Timoney (AT&T): So.

457
00:46:38.390 --> 00:46:43.630
Byung-Woo Jun: So that's the schedule, and don't confuse by this timeline, because

458
00:46:43.840 --> 00:46:46.120
Byung-Woo Jun: Pablo is in Europe now. So.

459
00:46:46.120 --> 00:46:47.690
Toine Siebelink: What's Pavel? Sorry it's pavil screen.

460
00:46:47.690 --> 00:46:49.249
Paweł Pawlak: So it is. It's it's.

461
00:46:49.250 --> 00:46:49.750
Toine Siebelink: See what.

462
00:46:49.750 --> 00:46:51.779
Paweł Pawlak: So we're so time, time zone, so good.

463
00:46:51.780 --> 00:46:53.359
Toine Siebelink: 5. Okay? Yeah, that's one.

464
00:46:53.360 --> 00:46:58.890
Paweł Pawlak: To you to you. One. Right? You are in Ireland. So yeah, and plus one.

465
00:46:58.890 --> 00:47:08.810
Byung-Woo Jun: This one, I think, though, everything will be finished before 2 o'clock. So I mean, there's some session closing session, brief one. But you know, we target everything done by 2

466
00:47:09.280 --> 00:47:14.069
Byung-Woo Jun: Pm. And local. You know the California time. So that's the.

467
00:47:14.496 --> 00:47:19.609
Paweł Pawlak: Quarter past 1 one Pm. Should finish here or not. Maybe no.

468
00:47:19.780 --> 00:47:20.300
Byung-Woo Jun: Something.

469
00:47:20.300 --> 00:47:23.219
Paweł Pawlak: 9 h. You need to. The, you know

470
00:47:25.180 --> 00:47:26.160
Paweł Pawlak: I'm wasted.

471
00:47:26.160 --> 00:47:26.690
Byung-Woo Jun: Times, like.

472
00:47:26.690 --> 00:47:29.789
Paweł Pawlak: An hour is plus. So it should be

473
00:47:30.350 --> 00:47:31.750
Paweł Pawlak: before 2. Yeah.

474
00:47:32.140 --> 00:47:33.840
Byung-Woo Jun: Yeah, before 2, yeah, so.

475
00:47:34.430 --> 00:47:36.150
Paweł Pawlak: Maybe quarter to 2. Yeah.

476
00:47:36.150 --> 00:47:45.309
Byung-Woo Jun: Yeah, yeah, something like that. So anyway, people can leave Friday. That's that's why. So we have a very busy schedule. But you know.

477
00:47:45.360 --> 00:48:12.580
Byung-Woo Jun: so he's gonna work. And then so Andreas, you, you know, talk to Mark or somebody else who can present in person. And then, or do I can connect the link. But you are not gonna be here anyway. So yeah, right? So okay, that's the things. I'm not sure tag one. And then don't. One can remotely join that time. In that case I give you a chance to present to your sections. Okay, if if you, if you want.

478
00:48:15.180 --> 00:48:15.900
Dan Timoney (AT&T): Okay.

479
00:48:16.390 --> 00:48:17.680
Keguang He: Have a note to.

480
00:48:17.770 --> 00:48:19.960
Keguang He: I'm not approved here for

481
00:48:20.170 --> 00:48:21.420
Keguang He: the partition.

482
00:48:22.020 --> 00:48:26.980
Byung-Woo Jun: Okay, then I'll cover no problem. I cover China, Mobile and China

483
00:48:27.040 --> 00:48:35.620
Byung-Woo Jun: telecom section. And then, okay, mark will cover the Deutsch telecom if he comes. And then, Howie, I'm going to talk to Don, we?

484
00:48:35.650 --> 00:48:47.469
Byung-Woo Jun: And if he wants to doing it. But anyway, so okay, so I send the email to them. And then if you have any comment, they can come back to me. So okay, this is schedule the we you know.

485
00:48:47.690 --> 00:48:48.380
Byung-Woo Jun: mate.

486
00:48:48.870 --> 00:48:52.610
Paweł Pawlak: Thank you for sharing, and thank you for being our representative beyond here

487
00:48:52.840 --> 00:48:55.410
Paweł Pawlak: in the in this, in the committee.

488
00:48:55.830 --> 00:49:04.800
Paweł Pawlak: Alright, I think we ran out of the topics unless some of you would like to add some. Add some additional topic for today or for the next week.

489
00:49:08.020 --> 00:49:09.530
Paweł Pawlak: I'm fine. Okay.

490
00:49:10.000 --> 00:49:14.559
Paweł Pawlak: hearing none. Thank you very much, guys, for for attending today. Thank you for

491
00:49:15.950 --> 00:49:16.899
Paweł Pawlak: voting

492
00:49:17.370 --> 00:49:19.609
Paweł Pawlak: and hear you next week.

493
00:49:20.280 --> 00:49:20.740
Byung-Woo Jun: Thank you.

494
00:49:21.630 --> 00:49:23.210
Paweł Pawlak: You, everybody! Bye.

495
00:49:23.990 --> 00:49:24.319
Keguang He: Bang!

496
00:49:24.654 --> 00:49:24.990
Paweł Pawlak: Bye.

497
00:49:28.270 --> 00:49:29.000
N.K. Shankaranarayanan: And cube.

Agenda Items

ONAP takeaways

LFN Cross-Organization Updates

TCC / ONAP Liaison Updates

Task Force Updates

TSC Activities and Deadlines

Release Status

RelEng/Infrastructure

PTL Updates

PTL Updates

Subcommittee Updates

OOM Update

OOM Update

Upcoming Events & Housekeeping

Zoom Chat Log

Browser not supported