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

Passcode: 209247

2023 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
	TCC / ONAP Liaison Updates
	Task Force Updates


Operations (40 minutes)	TSC Activities and Deadlines
	Release Status	Byung-Woo Jun	Creating release status pages, by copying the Montreal release status wiki pages, as a start, Project Status in New Delhi Release. It is a WIP
	RelEng/Infrastructure
	PTL Updates	Andreas Geißler Toine Siebelink Byung-Woo Jun	OOM Helm Chart versioning management in New Delhi. Andreas shared his thoughts on this, and the team agreed to update their own version as needed (when Major changes) Andreas Geißler Ask the OSC team to present their work to the OOM meeting for other issues and updates, see PTL 2024-01-15 Toine hosted the PTL meeting this week. Thanks, Toine! Looking for a volunteer among PTLs for hosting the next week PTL meeting
	Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Zhen Li Dong Wang Byung-Woo Jun	ARCCOM Update: China Telecom (Zhen Li Dong Wang )proposed the 'Data Service Enhancements of Intent Driven Networks in R14' requirements. For more details, see ONAPARC-801 - Getting issue details... STATUS and REQ-1589 - Getting issue details... STATUS As TSC approved last week, the REQ subcommittee has been removed. ARCCOM will handle requirement reviews, along with architecture. Byung-Woo Jun Done
	Other Updates	Toine Siebelink Michael Morris	ONAP Zoom Logon issue for changing the meeting schedule, checking attendance report, minutes, etc. Toine: Ask Kenny / Sandra for this Kenny provided the solution and it is working according to Toine SDC is looking for SDC PTL self-nomination
Events & Meetings (5 minutes)	Upcoming Events & Housekeeping

Zoom Chat Log

00:24:54 Toine Siebelink: apologies have to drop
00:34:48 Keguang He: [onap-ptl] New PTL for portal NG project is Fiete Ostkamp

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.

1
00:08:00.480 --> 00:08:03.709
Byung-Woo Jun: Alfandra or Kenny join us today.

2
00:08:06.710 --> 00:08:11.260
Andreas Geissler: Seems they have forgotten us. Forgot those.

3
00:08:11.280 --> 00:08:14.070
Byung-Woo Jun: Hope not. Hope not.

4
00:08:18.600 --> 00:08:20.850
Byung-Woo Jun: Maybe send the email.

5
00:09:22.100 --> 00:09:29.259
Byung-Woo Jun: I sent the E-mail, Sandra and Kenny about their meeting, so hope they can pick up and join hopefully.

6
00:11:12.510 --> 00:11:16.300
Byung-Woo Jun: I'm not sure I can't claim host. Let me try.

7
00:11:25.140 --> 00:11:32.220
Toine Siebelink: So if you. This meeting is using the new system, isn't it? I don't think you need a claim host. I think anybody can.

8
00:11:32.320 --> 00:11:35.100
Byung-Woo Jun: Yeah, okay, let me

9
00:11:35.270 --> 00:11:41.630
Byung-Woo Jun: let me. Then I try to share screen. Yeah, okay, right? Right? Until one day come.

10
00:11:42.150 --> 00:11:43.330
Byung-Woo Jun: So

11
00:11:44.510 --> 00:11:45.560
Byung-Woo Jun: thank you.

12
00:11:46.360 --> 00:11:48.490
Byung-Woo Jun: Can you see my screen?

13
00:11:51.400 --> 00:11:52.540
Toine Siebelink: Yeah, they can.

14
00:11:52.600 --> 00:11:57.350
Byung-Woo Jun: Okay, until Sandra Kenny. Come, miss, start here.

15
00:11:57.960 --> 00:12:17.059
Byung-Woo Jun: So this is agenda, and we have some release status, since David Mcbride is not here. So I copy this his previous re release. Status Wiki pages. I started working in progress. But you know, you can get idea

16
00:12:17.080 --> 00:12:25.240
Byung-Woo Jun: and then pt update, we have pt update from Oem team, and to one he hosted a Ptr. Meeting this week.

17
00:12:25.260 --> 00:12:28.519
Byung-Woo Jun: and then, as a subcommittee, update

18
00:12:28.680 --> 00:12:37.129
Byung-Woo Jun: Akam and Zennie and Donwan, they propose the new the intent driven networking proposed for

19
00:12:37.570 --> 00:12:38.640
Byung-Woo Jun: new tally.

20
00:12:38.820 --> 00:12:44.770
Byung-Woo Jun: Then either update to one he has a problem with the Zoom login

21
00:12:44.830 --> 00:12:48.639
Byung-Woo Jun: issues for changing the meeting schedule and etc.

22
00:12:48.730 --> 00:12:57.999
Byung-Woo Jun: And then Mike Mori sent email to Tsc previously, and Sdc. Is looking for Sdc. Self nomination.

23
00:12:58.060 --> 00:13:11.079
Byung-Woo Jun: So since dawn you have to leave soon, so I'm going to give you the your topic first. But on a zoom login before we going to release that one.

24
00:13:11.100 --> 00:13:12.909
Byung-Woo Jun: Could you explain what your problem?

25
00:13:13.180 --> 00:13:20.380
Toine Siebelink: So I actually just just had to disconnect that for a minute. But I just got back at the end of that. Yes, thanks for that. To be on

26
00:13:20.430 --> 00:13:35.999
Toine Siebelink: my problem is So up till a couple of months ago I well up to before Christmas I was able to use lastpass to log into zoom for the own up 0 4. And those those other meetings I only used to own up for logon

27
00:13:36.070 --> 00:13:59.029
Toine Siebelink: for my own meeting for cps. although it was always bit tricky. Last Pass did work for me. And then basically log into zoom. You can do things like schedule. Your meeting, cancel it. You can look at reports who attended it, and and you can start meeting, and then when you start meeting automatically, the host. So that's the way I used to start my meetings.

28
00:13:59.220 --> 00:14:13.090
Toine Siebelink: S, now, as we discussed last week I understand, last pass has been abandoned, and I actually uninstalled that for my own system now as well, and Kelly sent a mail before Christmas, saying that he

29
00:14:13.200 --> 00:14:25.949
Toine Siebelink: He canceled some of the owner. I've I've got the numbers. There was something like 14 different accounts, and I think he brought it back to 50604 is is one that was remaining, and in the mail he mentioned the password.

30
00:14:26.100 --> 00:14:29.559
Toine Siebelink: I have tried logging in with that password, but that didn't work

31
00:14:30.280 --> 00:14:43.770
Toine Siebelink: Now, the last time I hosted actually the last 2 times I hosted a meeting. I was able to just start a meeting. It was in the calendar link and then claim the host using the PIN code that's in the same meal that that works.

32
00:14:43.950 --> 00:14:57.669
Toine Siebelink: But that doesn't give me access to the Zoom account itself, so I can't do things like canceling the meeting, rescheduling it, or look at attendance reports, and those are kind of the things we do, the odd time or need to do the odd time.

33
00:14:57.920 --> 00:15:12.390
Toine Siebelink: So at the moment, I because, yeah, last pass was very, very clever. Actually it. It even hit the password. You couldn't see yourself. And then the account. Now I think the call was visible, but I lost the account. So you log into zoom.

34
00:15:12.400 --> 00:15:36.199
Toine Siebelink: It asks you for an email address and a password. And now I don't even know the email address anymore to for on of 0 4 or any of those other zoom accounts to log in. So I'm not sure if anybody is using that at all. Is anybody using zoom log on to to to look at the meeting start meetings that way. Also, everybody is using the claim claim host method now.

35
00:15:37.150 --> 00:15:47.859
Toine Siebelink: But anyway, yeah, that's that's the problem. Last week we asked this as well, I think some that was here last week, and she said she would follow it up. But I haven't heard anything since

36
00:15:50.740 --> 00:15:56.860
Byung-Woo Jun: anyone knows this how to handle to, you know to what someone looking for.

37
00:15:57.240 --> 00:16:01.150
Andreas Geissler: Unfortunately, no, because I'm also using just flaming it

38
00:16:01.170 --> 00:16:17.779
Andreas Geissler: with the PIN, but not not really logging into but I had. I remember that I had also these these last pass once, but they, as my got a new laptop, and my last pass was, let's say, deleted.

39
00:16:17.900 --> 00:16:18.710
Andreas Geissler: I'd

40
00:16:18.880 --> 00:16:43.890
Toine Siebelink: don't have that, but maybe I will check that again. Yeah, no, Andreas, I think the last pass has been abandoned last. Had the old passwords, anyway. So those wouldn't work anymore. There's no point in trying to use last last week that we we're not supposed to use last anymore. They wouldn't work anyway.

41
00:16:45.370 --> 00:16:58.490
Byung-Woo Jun: Okay. So Duan, is it possible for you to send the email to Kenny and Sandra and CC me don't want. And then so power, too.

42
00:16:58.650 --> 00:17:02.969
Byung-Woo Jun: Okay. So then I'll give you this task to you.

43
00:17:04.180 --> 00:17:12.639
Byung-Woo Jun: then hopefully, they can response back to you for this. Okay, okay, and I'll follow up to okay with your CC, me, that email.

44
00:17:13.010 --> 00:17:21.149
Byung-Woo Jun: Thank you. Thank you. I don't. The fancy work we did, zoom. And I can just use it. So okay.

45
00:17:21.170 --> 00:17:27.250
Byung-Woo Jun: Michael. If your issue is quick rest finish it before moving to other Michael

46
00:17:32.560 --> 00:17:35.249
Byung-Woo Jun: Michael, I cannot hear you, Michael Morris.

47
00:17:36.910 --> 00:17:52.519
Byung-Woo Jun: Okay, yeah. So I put some looking for SP. Tsf nomination. You send the email to Tsc, but no response. So anything to say here or

48
00:17:52.980 --> 00:18:13.239
Michael Morris: no, just like, guess basically what I said. An email there, I I'm stepping down as Ptl. Now. I've looked see if there's anyone else in the existing Ptl. Team wants to take over, and there isn't any candidates there, so it looks like Sc. Will have no Ptl. Going forward unless somebody else from somewhere else in the one of community wants to.

49
00:18:13.530 --> 00:18:14.879
Michael Morris: once they're taken on board.

50
00:18:15.120 --> 00:18:27.690
Byung-Woo Jun: Okay? So I hope that there's some candid nomination. team. So otherwise let us know. And then I'm not sure how Ts can help you

51
00:18:27.760 --> 00:18:32.899
Byung-Woo Jun: in here. But anyway, thank you for your service for pto. Thank you very much.

52
00:18:34.400 --> 00:18:49.779
Byung-Woo Jun: Okay. And I'll if you have the Tse a member, if you have any. Suggestion, and anybody who can do this. Sdc Pto. And please do so. Otherwise Sdc will be

53
00:18:50.120 --> 00:18:54.810
headless project again. And then, if you don't maintain you would be.

54
00:18:55.540 --> 00:19:04.239
Byung-Woo Jun: you will become unmaintained projects. So that's not a good thing. So since as this is important, you know, project. So okay, so

55
00:19:04.640 --> 00:19:08.609
Byung-Woo Jun: okay. And then, we're gonna go to

56
00:19:08.990 --> 00:19:12.789
Byung-Woo Jun: any other questions so far here, then, I'm gonna move to

57
00:19:13.110 --> 00:19:14.550
Byung-Woo Jun: previous status.

58
00:19:16.460 --> 00:19:17.850
Byung-Woo Jun: Okay?

59
00:19:18.910 --> 00:19:29.169
Byung-Woo Jun: So the David the Mcbride used to handle this project status to Montreal, since he's not here temporarily, I,

60
00:19:29.260 --> 00:19:31.280
Byung-Woo Jun: you know, copy the

61
00:19:32.030 --> 00:19:39.600
Byung-Woo Jun: the initial, the release from Montreal, and I create the 3 subsections, the Wikipedia pages.

62
00:19:39.640 --> 00:19:48.670
Byung-Woo Jun: So anyway, this is a template. So I put key update. I empty the older key update. And then Pto, I just put the

63
00:19:48.870 --> 00:20:06.950
Byung-Woo Jun: price order for Ptr to add a key update and benefit for new daily release, and also milestone status. I need to Update Sanjira the link. So you will be hooking to New Delhi

64
00:20:07.230 --> 00:20:10.000
Byung-Woo Jun: and then documentation.

65
00:20:10.640 --> 00:20:15.160
Byung-Woo Jun: for now the just just modify a little bit. But I'm gonna look at Folder.

66
00:20:15.310 --> 00:20:28.490
Byung-Woo Jun: and I don't know, Thomas, we can have here, but anyway, so I copied it, and then I put some additional information on some changes. For example. I think the

67
00:20:28.560 --> 00:20:39.750
Byung-Woo Jun: Pcie. No Pto, and also Dmap. And I have to ask Piakra. I think that he's he stepped down, too. I think so. I'm gonna in that case no Pto

68
00:20:39.900 --> 00:20:43.189
Byung-Woo Jun: since Muncho. and then

69
00:20:44.380 --> 00:20:51.120
Byung-Woo Jun: the Msb. Is unmaintained. Project no, Pta. I think the

70
00:20:51.130 --> 00:21:02.740
Byung-Woo Jun: we decide to retire. Msp. And then also the Stc. I put I put up with Mike Motor's name, but he's stepping down

71
00:21:02.870 --> 00:21:07.610
Byung-Woo Jun: as Pto of the munshi. So in new dairy and no Pto.

72
00:21:07.720 --> 00:21:14.630
Byung-Woo Jun: okay, so I update these pages for now. So you can feel free to change and put your input.

73
00:21:14.990 --> 00:21:21.239
Byung-Woo Jun: Okay, so I just creating 2, 3 new Wiki pages copying the

74
00:21:22.540 --> 00:21:34.709
Byung-Woo Jun: and David style. But anyway, we're gonna modify. So one of them is, for example, who was that? Not this? Okay?

75
00:21:35.740 --> 00:21:36.930
This one.

76
00:21:37.100 --> 00:21:44.060
Byung-Woo Jun: these pages. Okay. I change a little bit, and I'm still working in progress. And

77
00:21:44.370 --> 00:22:02.120
Byung-Woo Jun: this is the Montreal Lumchad version. And for this older project and the new dairy I copy as is. But, Pto, you can feel free to changes. I think the one of the report from Oem team today, Andreas, he will explain the what our discussion in Ktf.

78
00:22:02.140 --> 00:22:24.349
Byung-Woo Jun: so you can. No, you can address about the strategy for how to handle helm chat version, for now I put the pages, and then after Andres he described what we our discussion and decision. Then Pto feel free to change to this Helen chat, and then communicate to

79
00:22:24.370 --> 00:22:49.579
Byung-Woo Jun: the oem team. Then you can, you know. Change it, you know. I think they can use this pages for changing or still talking to the android on. So this is kind of a release status. For now until we find some other volunteer handling and release manager. But temporary. I'm handling this. Okay? So, okay, any questions here.

80
00:22:51.920 --> 00:22:52.850
Byung-Woo Jun: Okay?

81
00:22:54.250 --> 00:22:57.869
Byung-Woo Jun: And the Pt, update. So

82
00:22:58.010 --> 00:23:18.199
Byung-Woo Jun: do I host you the Pta meeting this week. Thank you. It was great. It was very good technical discussion by Andrews and other Pto teams, I think, was very good. And then so that's why we have a separate Pta meeting for now shrunk to a 30 min. But we're gonna focus on technical discussion.

83
00:23:18.430 --> 00:23:27.959
Byung-Woo Jun: And then we summarize and report to Tse. That's you know, current structure. So anyway, so and for next week we're looking for

84
00:23:28.020 --> 00:23:37.939
Byung-Woo Jun: host for this meeting and for any Ptl. Wants to host the next Monday meeting. Please, send us email

85
00:23:38.060 --> 00:23:55.210
Byung-Woo Jun: and your intention for next week. And before Monday. Okay, so that one and then, now I'm gonna delete the keep. The Andrea's the you know the talking about oem chat version, Andreas, do you need to the share this?

86
00:23:55.320 --> 00:24:03.289
Andreas Geissler: No, I don't need to share actually. So I think you can also go back to the project status page. So

87
00:24:03.330 --> 00:24:10.790
Andreas Geissler: what you had. I think you have an open dialing left. Yeah? So basically, yeah, what we agreed on Monday was

88
00:24:10.920 --> 00:24:20.600
Andreas Geissler: since, or for new Delhi daily. And the future releases basically, the components would be free to choose their

89
00:24:20.700 --> 00:24:28.989
Andreas Geissler: release version. We will start all with the 13 dot whatever we had.

90
00:24:29.180 --> 00:24:34.440
Andreas Geissler: But of course it makes sense for any change coming to

91
00:24:34.740 --> 00:24:46.490
Andreas Geissler: new daily, which is not, let's say, which is different from, or successor for Montreal child versions should update

92
00:24:46.500 --> 00:24:56.759
Andreas Geissler: their your your release versions in the helm charts so, and as long as you are using

93
00:24:56.780 --> 00:25:12.830
Andreas Geissler: the 13 dot 0. So the major 13 version there is no other thing to be changed. If you are updating also the major version. So from to 14, or whatever version you would like

94
00:25:13.080 --> 00:25:21.510
Andreas Geissler: there has to be a change done in the umbrella ownup chart, basically, which is.

95
00:25:22.260 --> 00:25:24.969
Andreas Geissler: let's say, having

96
00:25:25.620 --> 00:25:55.489
Andreas Geissler: which is containing a chart yaml file, which has dependencies to the different sub charts, basically the component charts. And the at the moment we are using wildcard with 13 dot x, so anything which is, has the major version, 13 would be included. So whenever a component would decide to change it, to change the version, for example, to 14 or something. The this

97
00:25:55.830 --> 00:26:00.630
Andreas Geissler: additional file needs to be changed, so that in the daily

98
00:26:00.640 --> 00:26:21.569
Andreas Geissler: and the gating runs, then this new major version is used for the component. But that's then the exception for the case. If, whenever you would like to change only the second number or the third number. So having new features or bug fixes

99
00:26:21.570 --> 00:26:31.509
Andreas Geissler: feel free to do that, this would be automatically included in the new daily. Let's say in the in the in the daily runs and in the integration. Yeah.

100
00:26:31.780 --> 00:26:32.870
so that's

101
00:26:33.260 --> 00:26:36.040
Andreas Geissler: what we had discussed on Monday.

102
00:26:36.820 --> 00:26:55.020
Byung-Woo Jun: That's great. This is the improvement. Thank you Andreas? So last time when we started on app streamlining, so we had a short term the you know the short term and long term the goal, the short term for Montreal everyone jumping into 13, starting the 13 or off.

103
00:26:55.250 --> 00:27:07.450
Byung-Woo Jun: And then Andrea is providing the nice system and the umbrella system, and then we decide the Ptr. The Ptm. As Andrea said, has, you know, flexibility. So Pto

104
00:27:07.690 --> 00:27:14.630
Byung-Woo Jun: have did some flexibility. They can choose. So anyway. Thank you so much, I think, though from New Delhi

105
00:27:14.680 --> 00:27:24.959
Byung-Woo Jun: own app has a more flexible. So the you know way of the handling of the helm chart and following their own app streaming. That's great. Thank you. Thank you. Andres.

106
00:27:25.660 --> 00:27:28.110
Byung-Woo Jun: Any question here. Any?

107
00:27:28.970 --> 00:27:30.779
Byung-Woo Jun: I think this is a very good thing.

108
00:27:32.960 --> 00:27:35.629
Byung-Woo Jun: Okay, thank you very much. Andrews.

109
00:27:35.810 --> 00:27:40.580
Byung-Woo Jun: Okay, so otherwise common. Yeah, yeah.

110
00:27:41.040 --> 00:27:55.690
N.K. Shankaranarayanan: So I just wanted to. You're familiar with this, this whole topic of the student, Louis from China working with our own helm charts

111
00:27:55.850 --> 00:27:59.100
N.K. Shankaranarayanan: for, but he is focused on the SMO.

112
00:27:59.320 --> 00:28:05.159
N.K. Shankaranarayanan: Right about the outgo. CD installation right of

113
00:28:05.370 --> 00:28:07.469
N.K. Shankaranarayanan: right? No, it's so easily. Yeah.

114
00:28:08.190 --> 00:28:16.970
N.K. Shankaranarayanan: yeah, I'm I'm just giving an update. It's very timely because he in in Oscar gave a detailed presentation.

115
00:28:17.110 --> 00:28:23.350
N.K. Shankaranarayanan: And I'll I'll find that and forward it, and I'll encourage him to to also be in touch with you.

116
00:28:23.460 --> 00:28:27.030
N.K. Shankaranarayanan: But he's putting a lot of effort. and

117
00:28:27.520 --> 00:28:31.690
N.K. Shankaranarayanan: I don't know anyone else outside. So who who came in

118
00:28:31.720 --> 00:28:38.500
N.K. Shankaranarayanan: after all this work was done and went in detail with all the helm charts, and he's looking on the Osi side and the own app side.

119
00:28:38.820 --> 00:28:46.709
N.K. Shankaranarayanan: Yeah, and asking this dependency, that dependency, this doesn't work that doesn't work. And he's asking, you know, really important and detailed questions about

120
00:28:46.860 --> 00:28:56.200
N.K. Shankaranarayanan: the map message. Router seems to be duplicated and slimsy. Kafka is being used. And why is this in this helm chart? And so I think we should

121
00:28:56.390 --> 00:29:04.700
N.K. Shankaranarayanan: pay attention to the fact that someone is really using and trying to make everything work. And and he's been sending email. And and I'm just reporting that

122
00:29:04.970 --> 00:29:09.040
N.K. Shankaranarayanan: he's not lost interest. He's continuing his work. And he's actually making more progress.

123
00:29:09.250 --> 00:29:11.979
N.K. Shankaranarayanan: Yeah, pointing out

124
00:29:12.150 --> 00:29:13.370
N.K. Shankaranarayanan: things that

125
00:29:13.720 --> 00:29:19.510
N.K. Shankaranarayanan: that he's he is asking for guidance also as to what to drop, what to keep.

126
00:29:19.930 --> 00:29:28.440
N.K. Shankaranarayanan: so that you have a working system. And so he doesn't know, for example, of that.

127
00:29:28.610 --> 00:29:35.169
N.K. Shankaranarayanan: the fact that all the modules are more autonomous. Now, he's just going based on what's available in the documentation.

128
00:29:36.260 --> 00:29:37.270
N.K. Shankaranarayanan: And yep.

129
00:29:37.670 --> 00:29:38.949
N.K. Shankaranarayanan: yeah, just

130
00:29:39.250 --> 00:30:00.730
Andreas Geissler: I was. I was not, let's say, following this too closely. So II wanted I think we will. I will have to get in touch with him more deeply, and and to discuss with him, make some things more clear. But in mind. But

131
00:30:00.930 --> 00:30:08.720
N.K. Shankaranarayanan: so he's bringing this discussion to oversee, because he's trying to use also the way, non real-time. Rick and John Kinney is there, and we are.

132
00:30:08.780 --> 00:30:10.279
N.K. Shankaranarayanan: People are engaging with them.

133
00:30:10.480 --> 00:30:14.819
N.K. Shankaranarayanan: But we'll also. That's why I'm telling you this this like an update. Yeah.

134
00:30:14.850 --> 00:30:22.360
Byung-Woo Jun: good good shank. Actually, the funny thing is at the Oem meeting this week and Andreas and discussed about the

135
00:30:22.510 --> 00:30:27.480
Byung-Woo Jun: there was teams of, you know, presentations because we they supposed to come back to us

136
00:30:27.510 --> 00:30:49.050
Byung-Woo Jun: oem team, and they give us more detail. But I think that good. So maybe we can. You know, Andrews? Maybe you can contact them and then give share the their, you know work and what just Sunshanka provided. So we can have some arrangements. So that's good thing. They are still continue to work on the at the Oc. So then we just need to sync up the cell.

137
00:30:50.600 --> 00:30:57.019
N.K. Shankaranarayanan: And we actually, you know, Angus actually talk about that yesterday? Yeah, yeah, so yeah.

138
00:30:57.060 --> 00:31:08.830
N.K. Shankaranarayanan: it is really not common that we find someone so motivated and actually cleaning things up by saying, You know, this works. This doesn't work. This is this is the way to move forward, and

139
00:31:09.260 --> 00:31:25.890
N.K. Shankaranarayanan: so I'll ask his latest presentation yesterday. I don't. I couldn't find it. I'll ask him okay to to make sure, he sends it to us, yeah, that's good information. By the way, Ashanka. Do they use a London version or Montfield?

140
00:31:26.080 --> 00:31:39.049
N.K. Shankaranarayanan: He was actually no sorry London, and he was asking questions like, Is Montreal release available? Is it signed off. And so we said, You know it's the release is not the same as what it was before.

141
00:31:39.430 --> 00:31:43.370
N.K. Shankaranarayanan: you know. He signed up. He's signed up.

142
00:31:43.420 --> 00:31:56.669
Byung-Woo Jun: and the reason I ask him was thi before they use the the older than London. So they don't have, you know, they using stay using, you know, A and I. So we had some certificates at issue

143
00:31:56.670 --> 00:32:16.270
Byung-Woo Jun: a aab. So yeah. But if they use it beyond that, he's not using af he knows that's good. Then, Andreas, he he presented to us team about how to gonna use August city, and then how you know, O owner, improve. So I think the it will be good, Andreas, you have anything to say.

144
00:32:16.950 --> 00:32:18.729
Andreas Geissler: No, no, so

145
00:32:18.840 --> 00:32:33.739
Andreas Geissler: II will have to check, so that either louis will might join our our own meeting, or we would need to arrange some, maybe separate meeting for discussing. So our our findings and defi his findings.

146
00:32:33.790 --> 00:32:45.760
Andreas Geissler: And yeah, definitely would look more into more detail if I when I have time. So maybe I could check in the next week, so we can have have a joint meeting together and present what we have done.

147
00:32:45.800 --> 00:33:02.200
Byung-Woo Jun: Good chunk. This isn't a good synergy, because they are looking for new way, and then Andrea's and oem team. They already provide new way and how they change it. And I think if we we sync up they will be good learning posts.

148
00:33:02.320 --> 00:33:08.979
Byung-Woo Jun: Okay, thank you. Thank you very much. Okay, so any I gave you this task. Andrews. Okay, so.

149
00:33:09.250 --> 00:33:10.450
Andreas Geissler: and

150
00:33:10.580 --> 00:33:19.729
Byung-Woo Jun: Pto under, as I mentioned the main discussion about the Oem helm charts. Okay, let me try to open. Okay?

151
00:33:20.530 --> 00:33:31.829
Byung-Woo Jun: So pity you. So basically, the Monday we discuss about the Lfid support, I'm not sure. Is there any Lfid team here

152
00:33:32.130 --> 00:33:37.000
Byung-Woo Jun: and dashboard? And Jessica, you are familiar with this?

153
00:33:41.380 --> 00:33:44.529
Jessica Wagantall: No! Was it discussed in the particular meeting

154
00:33:44.640 --> 00:34:07.229
Byung-Woo Jun: dashboard? The It 0 issue review some job. Okay, okay, if you're not, Matt, Matt is working. Okay. So anyway, okay, so we ask Matt, so 44. So then you you talk about the robot. You know, frame of 7 has some issues and also mainly discuss about the what andress we just mentioned.

155
00:34:07.470 --> 00:34:11.130
Byung-Woo Jun: And then, okay, so that's the one okay.

156
00:34:11.650 --> 00:34:14.999
Byung-Woo Jun: already already to talk about this. I'm not gonna repeat. So

157
00:34:16.350 --> 00:34:25.090
Byung-Woo Jun: so the stop committee update So at the outcome. somebody's questions.

158
00:34:26.580 --> 00:34:27.940
Byung-Woo Jun: we can hear you.

159
00:34:28.239 --> 00:34:37.180
Keguang He: Okay. Yes, yes. I received an email that maybe we have a new Ptr for Portal and G projector.

160
00:34:38.070 --> 00:34:38.790
Byung-Woo Jun: Oh.

161
00:34:40.139 --> 00:34:42.060
Byung-Woo Jun: could you? Yeah, some 30.

162
00:34:42.179 --> 00:34:49.480
Andreas Geissler: Yeah. Feature features, I think. Elected for the Ptl. Also for the as a Ptl. For

163
00:34:49.550 --> 00:34:50.949
Andreas Geissler: the

164
00:34:51.760 --> 00:34:58.140
Keguang He: for the portal and G project. That's right. You can choose information from the head box.

165
00:34:58.250 --> 00:35:11.339
Byung-Woo Jun: Okay, I'll change the update. The for Portal engine. Great. Thank you. Thank you. Oh, great!

166
00:35:11.770 --> 00:35:13.000
Byung-Woo Jun: And

167
00:35:13.260 --> 00:35:26.729
Byung-Woo Jun: plus this third Tuesday, and it's outcome. There is some presentation from China telecom. They propose to data service enhancement we intend driven network for New Delhi.

168
00:35:26.880 --> 00:35:28.890
Byung-Woo Jun: This is the

169
00:35:29.000 --> 00:35:44.390
Byung-Woo Jun: one of the the important enhancement to New daily about the AI based the intent driven networking one from China telecom, one from China mobile Kegon already, you know, to mention about it.

170
00:35:44.400 --> 00:35:50.839
Byung-Woo Jun: So this one Zen, or don't can you provide some more detail about this if you can

171
00:35:51.310 --> 00:35:53.390
Byung-Woo Jun: just just summarize it.

172
00:35:53.930 --> 00:36:16.959
Dong Wang: Yeah, yeah, thank you so much. I think we are continuing our research and development with all that most of force on the autonomous networks, including the intended services so I think that in 3 release we will continue our research focus on

173
00:36:16.960 --> 00:36:26.650
Dong Wang: the service with Onac. Actually, our team currently focused on the research of Sikkimobi networks

174
00:36:26.650 --> 00:36:44.359
Dong Wang: and the way in last year in recent time. Way, build lightweight platform. Based on all that architecture. And I think, maybe 2 weeks later, we can deal

175
00:36:44.360 --> 00:37:05.219
Dong Wang: demo in meeting to show our new platform architecture and show some further roadmap and plan, or our research and development with on app

176
00:37:05.220 --> 00:37:14.110
Dong Wang: so that works. And I think that maybe 2 weeks later, we we can provide more information about our research. With all that.

177
00:37:14.850 --> 00:37:33.459
Byung-Woo Jun: Okay, sounds good whenever you have something for us. And you can schedule a meeting. And we can participate. Okay? Great, that's great. There's yeah. Basically, this is an intent-driven network. And then I think the general purpose on the Raj data model Raj language model.

178
00:37:33.570 --> 00:37:42.010
Byung-Woo Jun: It's not really good. The accuracy provide accuracy for the, you know, some use cases they are using a Ccbn.

179
00:37:42.060 --> 00:37:57.450
Byung-Woo Jun: But by adding the Domain specific data service, and they can combine it that they can provide more accurate the the, you know the calculation. You know more based on AI, that's my understanding. Is that right? Glen? Then don't want.

180
00:37:57.800 --> 00:37:59.140
Dong Wang: yeah, yeah, yeah.

181
00:37:59.440 --> 00:38:21.230
Byung-Woo Jun: Okay, okay, on. Yeah. Thank you. Thank you. Yeah, you can. Yeah. So you can see the the own app. 801. And then also their requirement, 1589, for more detail, they uploaded their presentation slide deck. You can see more detail from there. Thank you very much, Zen, and the one, and then thank you very much.

182
00:38:21.310 --> 00:38:23.570
Byung-Woo Jun: and also for information.

183
00:38:23.580 --> 00:38:32.469
Byung-Woo Jun: and another side, as I mentioned, this is one on the track the China telecom provider, you know, AI based intent-driven networking.

184
00:38:32.630 --> 00:38:51.020
Byung-Woo Jun: and then also China Mobile. They have a generative AI which Kagan he presented, I think, shared information with us last time. So this is a 2 major track. You know, on the intent driven networking based on AI and MF. And then the Lm.

185
00:38:51.020 --> 00:39:07.589
Byung-Woo Jun: so you will be really good enhancement to new daily, you know, from my side, for we really interesting the their outcome during the new daily. And then I'm very excited about this. Okay, thank you. Both the companies. Thank you.

186
00:39:08.140 --> 00:39:09.550
And

187
00:39:10.570 --> 00:39:20.249
Byung-Woo Jun: I think, okay, one is the Tsc. Approved last week the Requirements Subcommittee is officially removed, I think

188
00:39:20.390 --> 00:39:36.599
Byung-Woo Jun: probably Team only deleted the archived and requirements subcommittee wiki pages. And I change the outcome description. And I'm gonna add more detail about the what outcome they're gonna hand. How outcome going to handle the requirement?

189
00:39:36.730 --> 00:39:55.730
Byung-Woo Jun: The in our review. And we already did 2 decline review from China, Mobile and China telecom China telecom China mobile. And we did. And then, so anybody wants to have requirement and architecture on review and please contact us outcome. So we're gonna handle that. So

190
00:39:56.240 --> 00:40:12.850
Byung-Woo Jun: I think that's all I put here and any other. The discussion are one thing. one, some question about the unip spum, Jessica and team. They provide the good spam generation

191
00:40:13.000 --> 00:40:23.640
Byung-Woo Jun: and some. Yes, we are onap supporting it, and, for all you know, report and one question from the colleague as a what onap

192
00:40:23.850 --> 00:40:37.139
Byung-Woo Jun: depths the the Sba level of the supporting. So currently it is using default. So if any request and I'm going to discuss at the second.

193
00:40:37.140 --> 00:41:02.500
Byung-Woo Jun: and what only are going to provide whichever owner going to provide. Okay. So you know, never top level, and 1, 2, 3 or all. So it depends. But we are just providing reference implementation. So maybe default is fine but I'll discuss with the second next Tuesday, and then that Jessica and team knows about that. Okay, Jessica, is that okay with you?

194
00:41:02.750 --> 00:41:18.179
Byung-Woo Jun: Yeah, that's a good way to thank you so much. Thank you very much for generation. Really? Good. So okay, that's so, I have any other information you want to discuss today.

195
00:41:22.720 --> 00:41:23.530
Byung-Woo Jun: Okay.

196
00:41:24.300 --> 00:41:30.759
Byung-Woo Jun: then, I'm going to. Probably this is the we can. You know, we can stop here.

197
00:41:31.210 --> 00:41:56.729
Byung-Woo Jun: So okay, thank you very much. Okay. So I just, you know, have. By the way, I'll see. Okay, she's I was sick. That's why just Kenny just sent email. She sticks. So anyway. So next week she will return. So anyway. So okay, for now I just temporarily handle this. Thank you very much. Thank you.

198
00:41:57.620 --> 00:41:59.960
Dong Wang: Thank you.

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

Subcommittee Updates

Other Updates

Upcoming Events & Housekeeping

Zoom Chat Log

Browser not supported