BRIDGE: https://zoom-lfx.platform.linuxfoundation.org/meeting/94501391330?password=c2f4cfa9-d9f5-4156-9ab2-c141fcdf671f

Passcode: 209247

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.

Attendance is taken purely upon #info in Zoom Chat 

Zoom Chat Log 

00:09:30    N.K. Shankaranarayanan:    #info N.K.Shankar, IC
00:14:34    Sandra Jackson:    brb
00:21:11    Sandra Jackson:    I’m back
00:44:24    Lee Anjella Macabuhay:    Thank you Pawel and team, we are looking to hopefully get it before the DTF meet in Budapest 
00:44:58    Pawel Pawlak:    I am sure it will Lee Anjella

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:39.760 --> 00:00:41.630
Sandra Jackson: Hello, Andreas, how are you?

2
00:00:44.800 --> 00:00:51.520
Andreas GEISSLER (DT): Fine? Thank you. The first one. Okay. I see.

3
00:00:54.460 --> 00:00:59.870
Andreas GEISSLER (DT): Yeah, we are have busy days. So all the day planning meetings, and this is

4
00:01:00.190 --> 00:01:03.240
Andreas GEISSLER (DT): the whole week. But it was really exhausting.

5
00:01:06.620 --> 00:01:15.699
Andreas GEISSLER (DT): I know I can totally relate. I'm so happy that we are on the eve of Friday.

6
00:02:36.600 --> 00:02:39.390
Sandra Jackson: Bayonne. Good morning. How are you?

7
00:02:41.190 --> 00:02:44.020
Byung-Woo Jun: How are you? How are you, Sandra? How are Andres?

8
00:02:47.340 --> 00:02:48.190
Andreas GEISSLER (DT): Hi.

9
00:02:49.410 --> 00:02:50.810
Byung-Woo Jun: okay. Good

10
00:02:53.280 --> 00:02:56.939
Pawel Pawlak: good morning. Good afternoon. Good evening.

11
00:02:58.990 --> 00:03:01.730
Pawel Pawlak: Hello! Buying. How are you? Good. Good.

12
00:03:03.110 --> 00:03:04.939
Pawel Pawlak: Okay. Good to hear. Hello.

13
00:03:05.020 --> 00:03:11.139
Andreas GEISSLER (DT): Sandra! Hello, Andress.

14
00:03:13.340 --> 00:03:18.640
Pawel Pawlak: So it's going to be short meeting right? Just 4 of us.

15
00:03:19.270 --> 00:03:20.190
Byung-Woo Jun: Thank you.

16
00:03:20.350 --> 00:03:29.149
Byung-Woo Jun: No, everyone's exhausted.

17
00:03:31.320 --> 00:03:34.909
Byung-Woo Jun: Join? Okay? Work home.

18
00:03:35.440 --> 00:03:37.739
Sandra Jackson: Yeah, we're trickling in. We're getting there.

19
00:04:02.450 --> 00:04:04.830
Sandra Jackson: I'll give it a another minute or so.

20
00:05:03.780 --> 00:05:14.040
Sandra Jackson: Alrighty. Let's go ahead and get started. You can see the regular reminders on the screen here.

21
00:05:14.640 --> 00:05:29.550
Sandra Jackson: That as you come into the meeting you are muted. The meeting is being recorded, and that includes the chat private chat as well. If you're dialed into the meeting, and you need to speak, you can press Star 6 to unmute yourself

22
00:05:30.150 --> 00:05:31.949
Sandra Jackson: and our

23
00:05:32.230 --> 00:05:45.610
Sandra Jackson: antitrust policy. If you have any questions about it, you can reach out to your organization's legal counsel, or if you are a member of the elf you can reach out to Andrew up to grove of the firm Guesser up to Grove, Llp.

24
00:05:46.640 --> 00:05:50.330
Sandra Jackson: All right. Jumping into today's agenda.

25
00:05:52.930 --> 00:06:03.560
Sandra Jackson:  we have some updates wait is shanker on. I don't remember. Anyway, I'll check in a minute. But we have some updates.

26
00:06:03.750 --> 00:06:23.570
Sandra Jackson: there was a nefio I think, developer Conference this week, Monday and Tuesday. and then we had a Tac meeting yesterday. and then we'll talk about nomination. Sorry nominations. I need to fix that. Actually, we're in the voting stage. So I'll I'll talk about that a little bit.

27
00:06:24.490 --> 00:06:31.740
Sandra Jackson: Our release updates. ptole updates and subcommittee updates, and then our regular

28
00:06:32.200 --> 00:06:34.040
Sandra Jackson: housecleaning.

29
00:06:38.440 --> 00:06:39.240
Sandra Jackson: Okay.

30
00:06:40.830 --> 00:06:46.619
Sandra Jackson: let's jump into it. Bai bayon, do you need me to share, or are you gonna share?

31
00:06:47.700 --> 00:06:49.450
Byung-Woo Jun: Me? Yeah, I can share.

32
00:06:50.070 --> 00:06:59.689
Byung-Woo Jun: Okay, let me stop sharing. Can you give me the host? Okay, good.

33
00:07:02.440 --> 00:07:04.280
Byung-Woo Jun: Let me know if you see my screen.

34
00:07:06.110 --> 00:07:17.760
Byung-Woo Jun: Okay, this is kind of a by presentation to nephew events at Silicon Valley are remotely presented. Basically.

35
00:07:17.880 --> 00:07:23.190
Byung-Woo Jun: we share what's the owner perspective toward nephew.

36
00:07:23.220 --> 00:07:32.940
Byung-Woo Jun: And so I'm just to or in or in on it, or in a few together. So there, I just share my thoughts. And also

37
00:07:33.010 --> 00:07:34.609
Byung-Woo Jun: some of the the

38
00:07:34.760 --> 00:07:39.789
Byung-Woo Jun: community owner community. I got some input from them, too. So

39
00:07:40.120 --> 00:07:50.900
Byung-Woo Jun: so basically, Onfc's nephew is as a good showcase for decorated intent with the continuous reconciliation they have that mechanism and architecture.

40
00:07:51.980 --> 00:08:00.950
Byung-Woo Jun: and since the beginning one of has been looking for his delegation integration point for nephew. and initially we saw.

41
00:08:01.170 --> 00:08:07.290
Byung-Woo Jun: excuse me, nephew, could be a good candidate for infra cnf management delegation. So.

42
00:08:08.510 --> 00:08:16.089
Byung-Woo Jun: But we realize nephew is not just for implementation. I can consider it as architecture pattern.

43
00:08:16.190 --> 00:08:27.829
Byung-Woo Jun: So if you can be applied to every layer. So some of the discussion they said, maybe they can build smo leveraging if you, too, if you basically

44
00:08:28.100 --> 00:08:36.639
Byung-Woo Jun: decorative, the package, decorative intent, coming into Gdp 3 and then hydrate, and they customize it and then

45
00:08:36.770 --> 00:08:42.080
Byung-Woo Jun: distribute to another the git deposit in the each workforce center.

46
00:08:42.270 --> 00:08:47.619
Byung-Woo Jun: then the using CD, and they could pick up the the intent. And then they just

47
00:08:47.660 --> 00:08:51.030
Byung-Woo Jun: using the customized operator and then

48
00:08:51.270 --> 00:08:59.780
Byung-Woo Jun: execute the action. So this concept is high level, not just for the Cnf implementation. So, yeah, thinking about

49
00:08:59.910 --> 00:09:19.909
Byung-Woo Jun: nephew can be applied to every layer. And then some owner company even apply this pattern. I think that's my view, too. And this is long tango so, or in some of the people seeing the old or Nsmo Farcom, and can apply. And if your pattern framework so

50
00:09:20.160 --> 00:09:27.630
Byung-Woo Jun:  So a nephew has the possibility to change existing orchestration. Apis there. Yet

51
00:09:27.680 --> 00:09:32.230
Byung-Woo Jun: network automation architecture is possible. So they share.

52
00:09:32.580 --> 00:09:43.479
Byung-Woo Jun: Sorry about that. Second. they share about their view of how to connect, and that to external community like service, orchestrator, and

53
00:09:44.240 --> 00:09:46.060
Byung-Woo Jun: Lauren Smo.

54
00:09:46.150 --> 00:09:54.329
Byung-Woo Jun: But current. It is a work in progress, and it's not too clear, and their architecture they share. I'm not too

55
00:09:54.400 --> 00:10:04.460
Byung-Woo Jun: satisfied yet. But, anyway, are we willing to work together to sort out. And so, from own perspective, I ask on it, need their

56
00:10:04.500 --> 00:10:09.710
Byung-Woo Jun: clear, well-defined interaction. Mechanisms. So onap can

57
00:10:09.940 --> 00:10:16.869
Byung-Woo Jun: can design how to delegate the Cnf. And infra management, otherwise we cannot. So

58
00:10:16.900 --> 00:10:30.610
Byung-Woo Jun: bottom 9 is that the interface should be decorative and intent based, and then with active reconciliation. So that's the what I told them kind of requirement to them. So I'm Jo. I joined the

59
00:10:31.210 --> 00:10:40.389
Byung-Woo Jun: since the beginning of nephew I joined the nephew Sikk network architecture and just to contribute to some of the idea of the

60
00:10:40.590 --> 00:10:46.280
Byung-Woo Jun: interfaces. So I think that we're gonna continue to work on that. So I think the more

61
00:10:46.430 --> 00:10:59.929
Byung-Woo Jun: owner community members. They, you know, probably contribute to more additional thought, too. So I introduced the only streamlining which support the patent, choose facilitation to others.

62
00:11:00.080 --> 00:11:06.910
Byung-Woo Jun: So some of the discussion with the Oecd Smo. Or Nmo. They are checking.

63
00:11:06.980 --> 00:11:15.699
Byung-Woo Jun: If they can reuse the owner component functions to build their smo Falcom and Nfo. Something like that.

64
00:11:15.770 --> 00:11:31.280
Byung-Woo Jun: So II told them on app streaming will facilitate, and that pick and choose. They don't have to bring whole own app into osc, but they can pick and choose the owner component, thanks to Andres and the

65
00:11:31.370 --> 00:11:51.870
Byung-Woo Jun: which telecom they supporting this capability during material, so they can build on a component individually and then using CD, they can pick and choose the component they need. So that's what the collaboration effort. We can. So I share the owner. Streamlining roadmap

66
00:11:51.910 --> 00:11:59.710
Byung-Woo Jun: So through onf streaming on, it is no longer platform. We already decided this way, changing logo to.

67
00:11:59.820 --> 00:12:03.739
Byung-Woo Jun: Rather it provides various network automation functions

68
00:12:03.870 --> 00:12:10.720
Byung-Woo Jun: and security reference configuration in elephant. That's our we are doing through on app stream running

69
00:12:11.590 --> 00:12:12.500
Byung-Woo Jun: so

70
00:12:13.090 --> 00:12:24.550
Byung-Woo Jun: based on that owner enables individual owner function, build and component deployment through city. I just mentioned about the Andres and Ddt and the Oem team effort.

71
00:12:24.860 --> 00:12:26.080
Byung-Woo Jun: And

72
00:12:26.800 --> 00:12:39.450
Byung-Woo Jun: for elephant. yeah. And tf, we plan to share the use cases for repository based and twin services network service and Cnf, and

73
00:12:39.590 --> 00:12:46.770
Byung-Woo Jun: I made type of C and a application such as the ran application on boarding

74
00:12:46.970 --> 00:12:51.509
Byung-Woo Jun: and CD based owner component triggering mechanisms. So we don't

75
00:12:51.810 --> 00:13:13.939
Byung-Woo Jun: abstract interface for choreograph. And so we we plan to share this at the Dntf. Camille, Adia and I. Well, I'll present plan to present this use cases at the Elephant Dntf. And come here, and I working on this. And anybody wants to contribute to idea that please contact me

76
00:13:14.150 --> 00:13:20.190
Byung-Woo Jun: and base, basically standard-based after interface with the creative Api.

77
00:13:20.200 --> 00:13:25.100
Byung-Woo Jun: and each component is autonomous and invoked from any level of the network automation

78
00:13:25.120 --> 00:13:31.470
Byung-Woo Jun: by leveraging CD mechanism and Kamel. He tried to create a package, can

79
00:13:31.670 --> 00:13:39.160
Byung-Woo Jun: be loaded into Github Paste early pass 3, and then some of the owner component can triggered by

80
00:13:39.230 --> 00:13:42.649
Byung-Woo Jun: CD, so anyway, that's the use case you're gonna share.

81
00:13:42.730 --> 00:13:57.380
Byung-Woo Jun: And then the future roadmap or network more intent, based and decorative, and putting in more AI conforming to standards such as 3 GPTM. Form, sc, and ITON. Etcetera.

82
00:13:57.410 --> 00:14:04.139
Byung-Woo Jun: This is what China telecom the proposed. They are working on this during Montreal.

83
00:14:04.460 --> 00:14:08.109
Byung-Woo Jun: I told Nephew Community we are doing this

84
00:14:08.130 --> 00:14:18.519
Byung-Woo Jun: and China telecom, doing this for now and then, also China mobile they are, and you know, wants to promote the Threegpp Tm. Program Api model.

85
00:14:18.530 --> 00:14:30.470
Byung-Woo Jun: I seem last time China, Mobile, China, Telecom, Nokia, and Addix. And we met together. And then we talk about this. So I think that we have a good plan for intent-based handling. So

86
00:14:30.590 --> 00:14:42.000
Byung-Woo Jun: so currently, you know, extend the Ui supporting user intense support. And an AI based natural language translation. That's what China telecom doing it.

87
00:14:42.250 --> 00:14:46.650
Byung-Woo Jun: and then delegate the resource level orchestration to nephew. So

88
00:14:46.780 --> 00:14:52.800
Byung-Woo Jun: I think the one the day I interested in how to link to a nephew, but

89
00:14:52.810 --> 00:15:02.020
Byung-Woo Jun: for intent. But I think the once nephew sort out how to expose their capability through their no Spa interface, then we can

90
00:15:02.120 --> 00:15:06.980
Byung-Woo Jun: achieve this goal. But for now they are still working on this. and

91
00:15:07.360 --> 00:15:16.119
Byung-Woo Jun: for security I mentioned a security owner continues to support the service mesh ingress. O, 2 item based authentication, authorization

92
00:15:16.970 --> 00:15:17.870
Byung-Woo Jun: and

93
00:15:18.040 --> 00:15:24.470
Byung-Woo Jun: consider a sitecare less solution, such as qom for function, security.

94
00:15:24.750 --> 00:15:34.959
Byung-Woo Jun: and aligned with the nephew and others. Nephew, currently they proposed you to cube which is kind of a side car less mesh and using the Linux kernel.

95
00:15:36.140 --> 00:15:51.550
Byung-Woo Jun: So for own app component itself, we are continuing to use what Andrews and oem team does. That's a good name for our application. But network function there could be thousands network functions. So I think the

96
00:15:51.890 --> 00:16:01.680
Byung-Woo Jun: side call less solutions much better for performance and simplicity perspective. So that's why we are studying. And we plan to collaborate