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

Passcode: 209247

2024 TSC Recordings	2024 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	Andreas Geißler N.K. Shankaranarayanan Byung-Woo Jun	ONAP and O-RAN SC collaboration: O-RAN SC shared their presentation slide deck, Contributions - SMO - Confluence (o-ran-sc.org) https://wiki.o-ran-sc.org/download/attachments/35881444/2024-1-10%20OSC%20IT-DEP%20SMO%20Deployment%20Upgrade.pdf?api=v2 OOM team plans to ask James Li (O-RAN SC) to present their roadmap and to exchange thoughts
	TCC / ONAP Liaison Updates	Amy Zwarico Byung-Woo Jun	SECCOM: Announcement for ONAP releases prior to London: All ONAP releases prior to London are broken because AAF certificate is expired. Users should select London+. Action Point: TSC/DOC/ARCCOM/OOM should publish this on the ONAP wiki, release note, etc.
	Task Force Updates


Operations (40 minutes)	TSC Activities and Deadlines
	Release Status	Byung-Woo Jun	New Delhi release planning: Release Planning: New Delhi New Delhi Project Status: Project Status in New Delhi Release
	RelEng/Infrastructure
	PTL Updates	Byung-Woo Jun	Shared the OOM Helm chart versioning plan for New Delhi with PTLs. OOM (Andreas Geissler) provides Helm chart versioning flexibilities to projects, by following ONAP Streamlining. For more details, PTL 2024-01-22 Rotating hosts for the PTL meeting are needed.
	Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Byung-Woo Jun Andreas Geißler Amy Zwarico	ARCCOM: Huawei (Guanyu Zhu) and CMCC (Keguang He) presented the requirement and architecture for the 'Incident API requirements in R14', 1) collecting incidents from network, 2) analyzing and aggregating based on AI and others and 3) providing uniform and consolidated incident reports. ARCCOM approved this. 2024-01-23 ARCCOM Meeting - (New Delhi Requirement/Architecture Review) for more details For New Delhi requirements and architecture changes, contact ARCCOM for the reviews. OOM: Tata Communication (Mateusz) installed ONAP Montreal/London and made improvements Security enhancements (e.g., Keycloak/OAuthProxy, AuthorizationPolicy...), Logging enhancements OOM Meeting Notes - 2024-01-24 OOM plans to make OOM enhancements including Tata input to New Delhi (TBD) SECCOM: see 2024-01-23 Security Subcommittee Meeting Notes
Events & Meetings (5 minutes)	Upcoming Events & Housekeeping		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

Zoom Chat Log

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:01:41.720 --> 00:01:43.560
Byung-Woo Jun: Hello, Dong Wong! How are you?

2
00:01:44.360 --> 00:01:49.360
Byung-Woo Jun: Hi, Biel? I'm good. How are you? Good! Can you hear? Can you see my screen?

3
00:01:49.510 --> 00:01:51.360
Dong Wang (China Telecom): Yes, yes, I can see it.

4
00:01:51.370 --> 00:01:53.560
Byung-Woo Jun: Okay, let's wait.

5
00:01:53.830 --> 00:01:56.359
Dong Wang (China Telecom): Okay, yeah, that's the weight of your second.

6
00:01:56.480 --> 00:01:59.930
Byung-Woo Jun: Yeah, okay, thank you. And I'm mute.

7
00:02:14.610 --> 00:02:15.970
Byung-Woo Jun: Hi andres.

8
00:02:21.290 --> 00:02:24.689
Andreas Geissler: Hi, I hope you can see my screen, too.

9
00:02:24.870 --> 00:02:27.549
Andreas Geissler: Yes, I can. That's good.

10
00:02:29.850 --> 00:02:39.499
Byung-Woo Jun: I think the Kenny and Sandra in training was submitting today. So they're gonna start joining from next week. So

11
00:02:51.780 --> 00:02:53.060
Byung-Woo Jun: nice. Wait.

12
00:02:55.460 --> 00:02:57.340
Byung-Woo Jun: Hi, Shankar, I liam.

13
00:03:08.660 --> 00:03:14.069
Byung-Woo Jun: hey? Let's wait one more minute, and then we're gonna start. Maybe some more people.

14
00:03:19.340 --> 00:03:20.770
Byung-Woo Jun: Hi, Thomas.

15
00:03:27.750 --> 00:03:30.440
Byung-Woo Jun: I we can

16
00:03:30.560 --> 00:03:32.770
Byung-Woo Jun: stop Sandra

17
00:03:32.950 --> 00:03:43.120
Byung-Woo Jun: and Kenny. They are in some meetings or training, so they told us they cannot attend this meeting so.

18
00:03:43.410 --> 00:03:49.900
Byung-Woo Jun: and Donwong, Kaguan and Mars said, we are going to host meeting today. So

19
00:03:50.030 --> 00:04:04.640
Byung-Woo Jun: as a start, I so this is january 20 fifth Tsc. Year, 2,024. I'm going to start our meeting, and then don't want and Kegwan please the.

20
00:04:04.980 --> 00:04:08.100
Byung-Woo Jun: you know, jump in any time you want to,

21
00:04:09.350 --> 00:04:11.690
Byung-Woo Jun: update. So

22
00:04:12.480 --> 00:04:33.230
Byung-Woo Jun: Andrews. So this agenda is 11 cross organization update. We are talking about briefly about own sc collaboration. I see Nk. Shanku I mentioned. But there is some follow up and between Orange and OMT. And Andress can. Briefly,

23
00:04:33.240 --> 00:04:36.580
Byung-Woo Jun: you know. Talk about this and

24
00:04:36.790 --> 00:04:44.000
Byung-Woo Jun: Tsc. I'm not sure any going to join today? At the second we want to

25
00:04:44.350 --> 00:04:47.060
Byung-Woo Jun: make announcements for onap

26
00:04:47.200 --> 00:04:51.339
Byung-Woo Jun: releases prior to London and saying all on it.

27
00:04:51.450 --> 00:04:54.549
releases prior to London are broken

28
00:04:54.560 --> 00:04:57.179
Byung-Woo Jun: because aaf certificate is

29
00:04:57.530 --> 00:05:10.219
Byung-Woo Jun: expired. So you just should select London, plus. That's the kind of the current announcement we want to propose. So we need to some agreement from Tsc member today.

30
00:05:10.510 --> 00:05:18.250
Byung-Woo Jun: Then we are going to change documentation and other Wikis release notes based on that

31
00:05:18.310 --> 00:05:29.709
Byung-Woo Jun: and release status I'm going to share briefly about the project status in new daily releases. And I sent email to Ptl for the key updates benefit

32
00:05:30.040 --> 00:05:42.540
Byung-Woo Jun: and the Pt update. I'm gonna share a brief debrief to what happened this Monday. Not much. And and also we're gonna report our com and oem and the

33
00:05:42.630 --> 00:05:44.530
Byung-Woo Jun: second dates.

34
00:05:44.610 --> 00:05:47.910
Byung-Woo Jun: And then there's some updated.

35
00:05:47.960 --> 00:05:51.120
Byung-Woo Jun: and the event coming

36
00:05:51.480 --> 00:05:57.059
Byung-Woo Jun: on on any summit is scheduled and the session topic agenda

37
00:05:57.180 --> 00:05:58.980
Byung-Woo Jun: has been published.

38
00:05:59.290 --> 00:06:16.810
Byung-Woo Jun: and also Kenny confirmed elephant Dtf. Will follow when he summit. I think it will be same time like last year, and May second and third. So that's the basic agenda. If you have any any additional agenda, just let me know, and let's start from the beginning.

39
00:06:18.130 --> 00:06:31.520
Byung-Woo Jun: So there's some collaboration as Nk. Shankar mentioned last week. and James Lee, and then Luis from Orn, Sc. Team contact OM. And others.

40
00:06:31.580 --> 00:06:37.189
Byung-Woo Jun: and they share their their presentation slide deck. How they gonna wants to use the

41
00:06:37.700 --> 00:06:45.000
Byung-Woo Jun: on it. And Andres, do you have any update for this? You want to and talk about briefly about this?

42
00:06:45.380 --> 00:06:53.749
Andreas Geissler: Yeah, I don't know that the the presentation, and wanted actually, and this week to go

43
00:06:53.840 --> 00:06:59.439
Andreas Geissler: through the slides to give some comments or some feedback to

44
00:06:59.450 --> 00:07:25.429
Andreas Geissler: the let's say, conclusions and the changes which would propose and and we're done so we. Unfortunately, as some colleagues from Tata wanted to present their enhancements, or they change changes and questions, and even want to. Let's say, contribute to OM. We postpone this discussion, maybe to next week.

45
00:07:25.520 --> 00:07:51.170
Andreas Geissler: But in the meantime we will. I will definitely go through the slides and make some notes so that we have. let's say some let's say, Pre, that I have some some pre notes here. What would be done? Or what is the plan? For example, here? Yeah. So there is a plan to deprecate the the message.

46
00:07:51.170 --> 00:08:01.620
Andreas Geissler: So that's something what? Of course we can. We can stay. And all of these these other

47
00:08:01.880 --> 00:08:10.830
Andreas Geissler: thoughts. Yeah. yeah. So I will definitely give that a feedback or collect this feedback, and then we can go next week

48
00:08:10.890 --> 00:08:24.589
Andreas Geissler: in the Om meeting through my notes, and then, maybe, if others would have some other notes from our team, that would do, we conclude that and and give that back to Louise

49
00:08:24.820 --> 00:08:31.000
Andreas Geissler: or James Lee so, and that, that will be done. Yup. And

50
00:08:31.180 --> 00:08:41.510
Byung-Woo Jun: to make some kind of conclusion out of that. Sure, thank you, Andreas, I think you know, maybe next week we can work something from all an Sc team.

51
00:08:41.679 --> 00:08:51.509
N.K. Shankaranarayanan: And as Andress mentioned about Tata communication. Yeah, yeah, just just a comment to Andreas and yourself.

52
00:08:51.750 --> 00:09:01.279
N.K. Shankaranarayanan: when you look, look at the presentation and look at the questions from Louise. Just keep in mind. If if

53
00:09:01.570 --> 00:09:04.660
N.K. Shankaranarayanan: if you think that is a good

54
00:09:04.990 --> 00:09:16.199
N.K. Shankaranarayanan: sort of reference implementation or default method of using own app and OS components for for the Smo.

55
00:09:16.540 --> 00:09:20.610
N.K. Shankaranarayanan: because that's the discussion is going in that direction. And

56
00:09:20.880 --> 00:09:24.620
N.K. Shankaranarayanan: and I would be interested in. If if you think, for example.

57
00:09:24.710 --> 00:09:36.869
N.K. Shankaranarayanan: you might have one conclusion, saying, This is the right thing to do, let him do it, and we'll make that the standard implementation for other people to follow. or he might come to a conclusion, saying, what he's doing is right. But

58
00:09:37.120 --> 00:09:57.670
N.K. Shankaranarayanan: there are other ways of doing it. And so there are multiple options. And so it it'll it will be good to know which way you are thinking that that's the plan. We you know, when we have a meeting with the at the Oem team we test. We gonna discuss about that. We're gonna review the their presentation side.

59
00:09:57.730 --> 00:10:09.300
Byung-Woo Jun: And good thing I found from the slide deck his state. I think that they are moving on to latest on it, frozen because we they had experience with the aaf

60
00:10:09.360 --> 00:10:25.129
Byung-Woo Jun: aaf under certificate. So they, we convince them to to move on to London, plus. So I think the one of the slides that they are doing it. And also, yeah. Also, I think they interest me. Select us. You know

61
00:10:25.300 --> 00:10:38.650
Byung-Woo Jun: the select own app functions, not every owner platform that's a good thing, and conforming to streamlining. And not only the Orient team. We're gonna talk about more tata communication.

62
00:10:38.650 --> 00:10:59.699
Byung-Woo Jun: They are interested in taking some of the owner function. That's a good thing. So Andro's team already supporting the individual project in selection based on the owners streamlining. So I think there's good synergy between owner and the orange and the Tata communication. So anyway, we're not talking about. So, okay, that's the thing.

63
00:10:59.990 --> 00:11:03.559
Byung-Woo Jun: Andrews, do you have any additional comments? Well, we're gonna move on.

64
00:11:04.080 --> 00:11:06.120
Andreas Geissler: No, you can move on. That's fine.

65
00:11:06.560 --> 00:11:11.020
Byung-Woo Jun: Thank you. Desk. Update any question. Stop us.

66
00:11:11.340 --> 00:11:15.560
Byung-Woo Jun: And Amy is not here today. So second

67
00:11:15.950 --> 00:11:20.829
Byung-Woo Jun: we are. We have some discussion this week, and so we know

68
00:11:20.890 --> 00:11:39.290
Byung-Woo Jun: aaf certificate ex expired. And then so we need to tell our customers, and then some participant companies. We need to tell them, all owner releases prior to London are broken because of the af certificate issues.

69
00:11:39.470 --> 00:11:50.450
Byung-Woo Jun: So they should select. You know, London plus. So is that okay, to send this announcement to public. So

70
00:11:51.170 --> 00:11:59.070
Byung-Woo Jun: you know, I like to get some content from Tsc, any objection. Yeah, I'm not sure we're gonna do both, because not enough. But

71
00:11:59.250 --> 00:12:04.590
Byung-Woo Jun: do you have any objection telling the customer we're going to go this path

72
00:12:06.310 --> 00:12:11.910
Andreas Geissler: if you have any objection just wanted me on that. I fully agree with that to do that.

73
00:12:12.170 --> 00:12:13.670
Byung-Woo Jun: Yeah, so great

74
00:12:13.720 --> 00:12:38.149
Byung-Woo Jun: and so this is action point. And then tsc documentation. Thomas, I'm not sure what which document section you need to put that in. And then I'm going to change outcome and also walking with Pablo and Dongwong and Kegwan. We're gonna push some Tsc, Wiki and some release notes. We're gonna announce that. So when

75
00:12:38.150 --> 00:12:56.380
Byung-Woo Jun: they customer look at the own app, and they try to download the own app function. They should know they should select the London plus. Okay, this is kinda done. We're gonna do this. And we're gonna talk separately about how you gonna publish this on it, Wiki? And then

76
00:12:57.530 --> 00:13:03.509
Byung-Woo Jun: Rtd, Thomas, okay, so, Thomas, do you have any suggestion here?

77
00:13:05.140 --> 00:13:15.810
Thomas Kulik: Yeah, just thinking about it. But definitely, put it in the we should put it in the release note in the the composite release note of Umhm

78
00:13:16.260 --> 00:13:21.300
Thomas Kulik: of the the latest release. Yeah.

79
00:13:21.490 --> 00:13:23.260
Byung-Woo Jun: yeah, that's the.

80
00:13:25.860 --> 00:13:36.630
Byung-Woo Jun: And then I look at the David Mcbride previous release note. And then I'm gonna squeeze him. And then I'm gonna talk to you before we publish it. Okay.

81
00:13:36.730 --> 00:13:37.590
Byung-Woo Jun: okay.

82
00:13:38.130 --> 00:13:44.659
Byung-Woo Jun: okay, 2 down. And I'm gonna share this project. Status.

83
00:13:44.900 --> 00:13:58.339
Byung-Woo Jun: okay, this is what we created. I actually, I created copying the David Mcbride. And then we are trying to update the update this page related information. So anything I,

84
00:13:58.600 --> 00:14:11.660
Byung-Woo Jun: and you know, change the orange, you know. So service design. Sdc, we don't have active Pta any longer. Vfc. And the unhong, she confirmed. She's not Pta any longer.

85
00:14:11.680 --> 00:14:41.259
Byung-Woo Jun: So we're not sure. And then so, Thomas, we have a project lead for some of the components, even though they don't have a ptl, but they have a stay, active commuters. So the project is the active. So, okay, we, we have a separate column for New Delhi, and this project is active, even though, we don't have. Ptl, so this is the additional column we're gonna indicate. So this is responsible for the Ptl.

86
00:14:41.330 --> 00:14:48.309
Byung-Woo Jun: And then they have to update the Harlem Chart version, and they want to use for New Delhi.

87
00:14:48.730 --> 00:15:06.409
Byung-Woo Jun: And the good thing is Andrew's Om days is he supports flexibility on the Halem chat versioning. So, Pto, if you don't have any major changes, you don't have to change the major version so. But let Andrews knows about this.

88
00:15:06.410 --> 00:15:23.160
Byung-Woo Jun: Because she need to manage it to umbrella. Helen chat so that as as long as this of some communication between Andrews and the Pto. It should be fine. And then yes, it will be flexible, Andrews, you said, is that my understanding. Is that correct?

89
00:15:25.440 --> 00:15:27.759
Andreas Geissler: Yes, that's right, that's right.

90
00:15:28.030 --> 00:15:49.739
Byung-Woo Jun: So whatever you see. And whatever I get anyway, I know when there's a patch that I will anyway take into consideration for the updates. That's fine. I put the voluntary active. Ui. We know how this really active anyway, and project status new daily. This is the same thing and the key update.

91
00:15:49.780 --> 00:16:01.519
Byung-Woo Jun: So I can't take a few the ptos to update their feature putting key update benefits. So you know, Pto, please the

92
00:16:01.860 --> 00:16:20.800
Byung-Woo Jun: or the Tsc Inquis, Pto to put the information. I think. I ui! They were gonna put the the key benefit, you know, and then update 2 updates one from China mobile, one from China telecom. So this is kind of a changes. Okay?

93
00:16:21.020 --> 00:16:24.840
Byung-Woo Jun: So that's the one I'm back to here.

94
00:16:26.040 --> 00:16:44.990
Byung-Woo Jun: So Etl and the this week, just the we share the information about the how oem helm chart versioning, as you know, supported in the new daily. So we just share this new the plan and handling with the ptl.

95
00:16:45.270 --> 00:17:00.539
Byung-Woo Jun: so that's the good thing. So anyway, if you want to see more detail, you can go to this pages. But that's the basic updates. okay this week. So I think it's a good thing we have a burgeoning flexibility. So okay?

96
00:17:00.940 --> 00:17:04.790
Byung-Woo Jun: And then, yeah, go ahead. Yeah, I have a question

97
00:17:04.940 --> 00:17:09.670
N.K. Shankaranarayanan: we used to. We used to track the use case work

98
00:17:10.109 --> 00:17:12.009
N.K. Shankaranarayanan: book. And before

99
00:17:12.119 --> 00:17:16.349
N.K. Shankaranarayanan: now it's become more autonomous. But there is still

100
00:17:16.670 --> 00:17:21.339
N.K. Shankaranarayanan: activity going on. For example, the Sun use case. We are continuing.

101
00:17:21.560 --> 00:17:34.810
N.K. Shankaranarayanan: It's all Oran focused. Or in this case Oran and Cps focused. And there is. And and II don't. I know the work that is happening, and some of it is overseas. Some of it is on app.

102
00:17:35.780 --> 00:17:42.140
N.K. Shankaranarayanan: Do you have any thoughts about whether you want to track it on the own app side, or is it the Benchong is doing it?

103
00:17:42.950 --> 00:17:43.700
N.K. Shankaranarayanan: Pardon.

104
00:17:43.900 --> 00:17:47.400
Byung-Woo Jun: Gan Chung. he used to handle use cases.

105
00:17:47.450 --> 00:17:51.660
N.K. Shankaranarayanan: Yeah, yeah, but I

106
00:17:51.690 --> 00:17:56.009
N.K. Shankaranarayanan: I don't. I don't see anything on the

107
00:17:56.560 --> 00:17:57.930
N.K. Shankaranarayanan: on the wiki.

108
00:17:58.140 --> 00:18:03.150
N.K. Shankaranarayanan: Okay. for example, the Sun use case there used to be.

109
00:18:03.270 --> 00:18:06.550
N.K. Shankaranarayanan: We used to just keep track it under

110
00:18:06.580 --> 00:18:12.690
N.K. Shankaranarayanan: the architecture, because there used to be use cases. And

111
00:18:13.000 --> 00:18:14.520
N.K. Shankaranarayanan: I am not actually

112
00:18:14.710 --> 00:18:22.000
N.K. Shankaranarayanan: created a I can last time I copied the page from London to Montreal. So I've not done that for New Delhi yet. Okay.

113
00:18:22.660 --> 00:18:34.219
Byung-Woo Jun: if if you can, I yeah, definitely want to track that. Okay. So I'm gonna socialize you and Ben Chong about how you know. Handle if you can create the the new daily the pages.

114
00:18:34.280 --> 00:19:04.010
Byung-Woo Jun: and then you can send me the link. I'll I'll try to track. Because currently Arctic just subcommittee we tracked the requirement several requirement already reviewed at the outcome. And I'm going to once you send the link. Then I'm gonna track the used cases and working with you and the benchm. Okay, benchmark, but definitely some use cases and other requirements it affects cps, it affects Sdn, C,

115
00:19:04.210 --> 00:19:08.999
N.K. Shankaranarayanan: and I put in the requirements marked it in the Jira. It's marked as New Delhi.

116
00:19:09.190 --> 00:19:15.290
N.K. Shankaranarayanan: I have to do a review with Architecture committee. I'm essentially waiting just to

117
00:19:15.540 --> 00:19:17.249
N.K. Shankaranarayanan: make sure the

118
00:19:17.260 --> 00:19:22.469
N.K. Shankaranarayanan: there is commitment to do the work. And so that makes the presentation that much more.

119
00:19:22.500 --> 00:19:34.769
N.K. Shankaranarayanan: Okay, once you have a commitment just content me scaling to update to come review and we create a jitter every single review, and we track their way.

120
00:19:34.770 --> 00:19:59.740
Byung-Woo Jun: and that the only jitter were linked to your requirement and other, you know, information. So once you you have commitment, please contact me, and then I'll arrange to on review schedule. Okay? So you're still following the same process. Yes, just we actually come they can. We can handle many things. Okay. So anyway, just contact me, send me email

121
00:19:59.740 --> 00:20:04.349
Byung-Woo Jun: title. I allow the time slot. Okay, good. Sounds good. Thank you.

122
00:20:05.090 --> 00:20:06.510
Byung-Woo Jun: And

123
00:20:07.090 --> 00:20:13.490
Byung-Woo Jun: okay, pto, we decide to shrink it to 30 min. And then also,

124
00:20:13.940 --> 00:20:21.090
Byung-Woo Jun: mainly focus on the technical discussion among the Ptl, so that's why we like to some Ptl.

125
00:20:21.430 --> 00:20:28.769
Byung-Woo Jun: one of the Ptl. Or, you know, rotating. You know we need some rotating host for Ptl. So

126
00:20:28.910 --> 00:20:40.220
Byung-Woo Jun: first week from Alexand he volunteer to host the meeting. and then the this week this Monday no volunteer. So I temporarily handle that.

127
00:20:40.350 --> 00:20:57.749
Byung-Woo Jun: And then so if any ptl, I send the email to a Pto on a Ptl, if any volunteer for a meeting for next week, host, also a top discussion topic, and let us know. Then we can arrange the you know the agenda.

128
00:20:57.790 --> 00:21:14.729
Byung-Woo Jun: And then well, anyway, we're gonna have meeting, anyway. So we'll see how it goes. Okay. But I hope to Pto more active. And then provide the more other volunteer for hosting. It's a rotating one. So anyway, that's the information already. Information sent to Pto, so okay?

129
00:21:15.970 --> 00:21:32.330
Byung-Woo Jun: And the this week I'll come under Howway. And I think Cmcc also involved this one. But Kanye she presented the requirement and architecture for incident Api requirement for a new Deli.

130
00:21:32.370 --> 00:21:45.630
Byung-Woo Jun: basically collecting instant analyzing, aggregating and then provide uniform collaborates, consolidate incident reports. So I think, mainly they have a 2 step. And to for

131
00:21:46.210 --> 00:21:57.429
Byung-Woo Jun: R 14 they're gonna handle for only the collecting and then handling through Sdn Ccc. SDK, and then the R. 15, they plan to

132
00:21:57.480 --> 00:22:03.169
Byung-Woo Jun: handle more control loop. But anyway she presented for requirements

133
00:22:03.190 --> 00:22:12.900
Byung-Woo Jun: for new daily. And we reviewed. And then we approved. So anyway, so you can see more detail about this. And

134
00:22:13.200 --> 00:22:22.930
Byung-Woo Jun: any comment you, you involve this one, too last last last release you are. You are part of that right?

135
00:22:23.130 --> 00:22:24.510
Keguang He: Yes, the

136
00:22:24.530 --> 00:22:35.740
Keguang He: we have a requirement about it. But maybe we have some challenge to finish this work. So we divided

137
00:22:35.750 --> 00:22:39.680
Keguang He: this requirements into a several small requirements.

138
00:22:39.830 --> 00:22:45.760
Keguang He: and the in New Jersey. They will finish that some part of the requirements.

139
00:22:45.800 --> 00:22:50.070
Keguang He: and I think in the next 2 days

140
00:22:50.330 --> 00:22:52.939
Keguang He: we will do more work

141
00:22:53.020 --> 00:22:58.140
Keguang He: to to to do the insight incident management

142
00:22:58.300 --> 00:23:06.640
Keguang He: with intern with the intent drive in so I think for new dirty release.

143
00:23:06.680 --> 00:23:09.320
Keguang He: They may do some some worker

144
00:23:09.330 --> 00:23:27.969
Keguang He: folks on folks on the incident management, and in next release after New Derby release. We will do more work with intended driven. So this is our plan. Thank you.

145
00:23:28.090 --> 00:23:46.220
Byung-Woo Jun: Okay, yeah. Positive part of it. Okay, I added. And the if you. Look at the optic to a meeting link, and that is a link for requirement. And then, this is some slide deck. So you can. Actually look at the what they plan. Okay, I think III I think this is very important requirement, too.

146
00:23:46.380 --> 00:24:06.310
Byung-Woo Jun: So in so far new daily. 3 important requirements one from China, mobile generative AI and China telecom, or data service, and then Howway and Cmcc, for instance, the Api requirement for new daily. So take a look at that, and probably we can.

147
00:24:06.330 --> 00:24:09.200
Byung-Woo Jun: you know, run many things from there.

148
00:24:09.380 --> 00:24:10.220
Byung-Woo Jun: Okay.

149
00:24:10.380 --> 00:24:19.780
Byung-Woo Jun: And this the deck next one at the OM. Maybe. Andress you can. Debrief this one Andres.

150
00:24:23.300 --> 00:24:24.690
Andreas Geissler: Oh, yeah, I was unmuted.

151
00:24:25.140 --> 00:24:54.209
Andreas Geissler: That was sorry for what? What's that? Right? So we had a presentation from to tata colleagues? Which are using in there? Let's say, own solution. Let's say or

152
00:24:54.350 --> 00:25:01.310
Andreas Geissler: projects part of own up. So they have installed ownup. They had added a couple of

153
00:25:01.370 --> 00:25:05.490
Andreas Geissler: components and

154
00:25:05.510 --> 00:25:22.410
Andreas Geissler: enhanced a couple of functionalities, especially regarding locking especially regarding authorization policies and so on. And they are thinking

155
00:25:22.440 --> 00:25:43.259
Andreas Geissler: to they presented this to us. In that meeting, and they have, or will clarify whether they are can maybe upstream these parts, which were very interesting, and would basically

156
00:25:43.280 --> 00:25:51.520
Andreas Geissler: fit to the open tickets or the open issues we are not yet we were not able to solve yet

157
00:25:51.600 --> 00:26:01.599
Andreas Geissler: because of time and resource limits, and maybe but so they they are. They think of up streaming the components, but have to clarify that within the organization.

158
00:26:01.720 --> 00:26:05.619
Andreas Geissler: and especially, of course, for their own

159
00:26:05.690 --> 00:26:18.050
Andreas Geissler: benefit, because they don't need then in each, let's say, release upgrade to maintain their changes again. So it makes that totally sense for them, of course, to

160
00:26:18.250 --> 00:26:20.619
Andreas Geissler: upstream the work to our

161
00:26:21.240 --> 00:26:31.300
Andreas Geissler: component, also to our projects here, especially to the Om project. So and this looks very promising.

162
00:26:31.340 --> 00:26:38.290
Andreas Geissler: But they will still clarify what and how they can contribute to our

163
00:26:38.300 --> 00:26:41.690
Andreas Geissler: project or the Om project

164
00:26:41.790 --> 00:26:49.080
Andreas Geissler: but looking forward to if they are really that would be a big help for us also, as we are

165
00:26:49.100 --> 00:26:53.539
Andreas Geissler: only a few people working on the OM. Parts at the moment.

166
00:26:53.880 --> 00:26:59.059
Andreas Geissler: So that is, of course, something which would be appreciated definitely.

167
00:27:00.190 --> 00:27:23.840
Byung-Woo Jun: I think that I think some of the slide, but they not allowed to present, you know, the share with the publicly yet, but once they have some permission we can share. Well, I think the good, you know, you know, achievement. They made so still following the owner security architecture and logging enhancement architecture. But they made it the more

168
00:27:23.950 --> 00:27:37.389
Byung-Woo Jun: you know, they put additional effort. We they went for the I think it would be good benefit is beneficial. Once they upstream they are output into the own app oem. I think it would be very nice.

169
00:27:37.560 --> 00:27:54.939
Byung-Woo Jun: and the and also logging enhancement we provide architecture contribution. But we have not. We did prototype we made in. It's gonna work. And then so global concept. But the code is not there. But I think Tata communication. They are tackling same you know.

170
00:27:54.950 --> 00:28:02.860
Byung-Woo Jun: the area following the architecture we provided. And then, one thing is we share the common.

171
00:28:02.860 --> 00:28:27.830
Byung-Woo Jun: the issues and front bit they need the root access privilege. We had the same problem. But Nsa, they suggest a certain method. And so we are discussing with Top that once they engage those I think, gonna discuss additional. The you know point, I think you will be very nice, I think, thank you. And they gonna contact andress additional information. Then, once, then, we can

172
00:28:27.960 --> 00:28:36.709
Byung-Woo Jun: andress, you know, and myself can share with information here. Okay, okay, thank you. Thank you. Andress. And

173
00:28:37.200 --> 00:28:51.519
Byung-Woo Jun: since Emmy is not here. And then I mentioned about second major discussion about this. The release, the notes. So this she will talk about. If you want to see the meeting this week meeting, you can see.

174
00:28:52.390 --> 00:29:00.090
Byung-Woo Jun: and the last one is the upcoming event. Housekeeping summit. This

175
00:29:00.190 --> 00:29:04.319
Byung-Woo Jun: session agenda for only summit for this year has been published.

176
00:29:04.540 --> 00:29:19.309
Byung-Woo Jun: and I was part of the programming Committee and also Emmy and then other so, and based on several people's common recommendation. They selected this topic will be very interesting.

177
00:29:19.740 --> 00:29:32.560
Byung-Woo Jun: And then many of them is AI and based on the optimization security. I think the many advanced topic. They also intend, of course, and advanced topic. So

178
00:29:32.620 --> 00:29:45.079
Byung-Woo Jun: I seen China mobile. Ii sort of their presentation, I think China telecom, too, and several are very the AI base intent based. Their plan will be very interesting.

179
00:29:45.460 --> 00:29:49.360
Byung-Woo Jun: And then Kenny confirmed last night.

180
00:29:49.880 --> 00:30:12.410
Byung-Woo Jun: then, like last year, and this on at the same week, are we gonna have Elef and Dtf, this is a date may second and third following only summit. So like last year, only summit first and then followed by the elephant. Dtf, this is the upcoming event. Okay? And don't want Kegwan. Do you have any additional topic? And then common

181
00:30:12.600 --> 00:30:14.179
Byung-Woo Jun: before we close meeting?

182
00:30:14.790 --> 00:30:22.400
Keguang He: Sorry. Hello, Bill, I have question. And for the one summit. And

183
00:30:22.550 --> 00:30:24.609
Keguang He: I find dtf, Michigan

184
00:30:24.690 --> 00:30:31.919
Keguang He: to do. Do they provide online meeting? Or we can only join this meeting in person.

185
00:30:32.550 --> 00:30:40.910
Byung-Woo Jun: We have to ask how we're gonna work last year we selectively, you know, to participate. You said this old end meeting, too.

186
00:30:42.280 --> 00:30:45.360
Keguang He: No due for one summit.

187
00:30:45.580 --> 00:30:47.609
Keguang He: and lf, and dtf.

188
00:30:48.850 --> 00:31:01.640
Keguang He: for this meeting, because I can't. Maybe I can't join this person this meeting in person. So II I'm not sure whether they provide a online meeting

189
00:31:02.820 --> 00:31:04.820
Byung-Woo Jun: where they provide owner meeting

190
00:31:05.440 --> 00:31:06.589
Keguang He: the online.

191
00:31:06.960 --> 00:31:10.639
Byung-Woo Jun: Oh, no, I believe. Sorry. Sorry. Sorry. I think the

192
00:31:10.970 --> 00:31:26.470
Byung-Woo Jun: I'm not sure currently they indicate in person. But previously last year, I think they shared some of the information online. So you can, you know, hear that. So we can ask Kenny for more detail. He's the one problem, I think the I think

193
00:31:26.540 --> 00:31:46.880
Byung-Woo Jun: last year I think the only few people they joined away meeting and elephant Dtf, and then I don't think I'm not sure. But anyway, I I'm sure there will be some kind of online plan. But anyway, so but the one thing is only summit is the

194
00:31:46.930 --> 00:31:55.290
Byung-Woo Jun: is to not free. So that's I'm not sure. Okay, so not it's not free. You have to register with this and pay some money. So

195
00:31:55.420 --> 00:32:03.110
Byung-Woo Jun: I'm not sure. Okay. So maybe we're gonna answer Kenny about that. You know, next week. So okay, I'll I'll ask. I'll follow up that.

196
00:32:03.310 --> 00:32:17.390
Keguang He: Okay, okay, maybe I can send the email to, can you, too, online. But I'm not sure about the only summit. Okay.

197
00:32:17.450 --> 00:32:19.529
Keguang He: Okay. Okay. Alright. Okay. Thank you.

198
00:32:19.930 --> 00:32:22.999
Byung-Woo Jun: You can send it. Don't want you have any any.

199
00:32:24.520 --> 00:32:27.570
Dong Wang (China Telecom): Yeah, no, no more information. Thank you so much.

200
00:32:27.750 --> 00:32:34.880
Byung-Woo Jun: Okay, before we close meeting. Do you have any comment? And then any suggestions here before close meeting

201
00:32:35.740 --> 00:32:36.680
Byung-Woo Jun: anybody

202
00:32:37.210 --> 00:32:55.599
ONAP Meeting 4: I beyond here. Sorry I was. I only joined you in the last few minutes. Something else just on the the cost. I noticed already registered for it because I'm presenting it to one so much. If there is actually $50. No sorry $100 charge for the

203
00:32:55.710 --> 00:33:10.000
Byung-Woo Jun: myself today. Charge.

204
00:33:11.320 --> 00:33:12.110
ONAP Meeting 4: Yep.

205
00:33:12.230 --> 00:33:17.410
ONAP Meeting 4: I think they probably did that to prevent a lot of people register and then not showing up.

206
00:33:17.620 --> 00:33:22.529
ONAP Meeting 4: Okay, I just guessing. I just guessing. Maybe maybe Kenny can explain it to us better.

207
00:33:22.640 --> 00:33:44.830
Byung-Woo Jun: Yeah, yeah, yeah, Kenny. You know, like that last meeting and 50 people didn't show up, even though they registered. That's why we want. I think that that's the good plan. Okay, thank you. Thank you for letting us know. Okay, alright, thank you. That's about it. And today, and I'm gonna put this recording into this web pages. Okay.

208
00:33:44.900 --> 00:33:46.150
Byung-Woo Jun: thank you so much.

209
00:33:46.490 --> 00:33:49.550
ONAP Meeting 4: Thanks to you. Bye, bye, have a good day, everybody.

210
00:33:49.890 --> 00:33:51.029
Keguang He: Thank you. Bye.

211
00:33:51.240 --> 00:33:52.020
Byung-Woo Jun: right.

Agenda Items

ONAP takeaways

LFN Cross-Organization Updates

TCC / ONAP Liaison Updates

TSC Activities and Deadlines

Release Status

RelEng/Infrastructure

PTL Updates

Subcommittee Updates

Upcoming Events & Housekeeping

Zoom Chat Log

Browser not supported