661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Passcode: 209247

2022 TSC Recordings	2022 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)	Gov. Holiday	Did Not Attend

Attendance is taken purely upon #info in Zoom Chat

Alla.Goldner	AMDOCS	Fernando Oliveira	Individual Contributor
Andreas Geißler	DT	Magnus Buhrgard (Unlicensed) proxy Byung-Woo Jun	Ericsson
Bin Yang	WindRiver	N.K. Shankaranarayanan	STL
Former user (Deleted)	Bell Canada	Ranny Haiby	Samsung
cl664y@att.com	AT&T	Seshu Kumar Mudiganti	Huawei
Dong Wang	China Telecom	Timo Perala	Nokia
Eric Debeau	Orange	Yuanhong Deng	China Mobile

Agenda Items	Presented By	Presos/Notes/Links/
Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements		Log4j bug SECCOM will file a CVE on ONAP's behalf (as soon as the list of projects are all confirmed at a minimum SECCOM will create the JIRA tickets for the impacted projects in order to solve it as part of the Istanbul maintenance release and the Jakarta release. They will track to completion, supported by our release manager, David McBride and the Integration Team (through the Docker Scan) Another problem has been discovered after 2.17.0 was released. - minor - fixed in 2.17.1 This should be the version we move to now. CII Badging formally rebranded - https://github.com/coreinfrastructure/best-practices-badge/issues/1515 We will be referring to this as simply the Best Practices Badging Program
Release Status	David McBride	Release Status Weekly Update (Dec 14) Note: M2 is scheduled for Jan 27 Reminder that TSC agreed to Log4j fix to Istanbul is the priority
RelEng/Infrastructure	Jessica Gonzalez	Tickets- Open showstoppers: Tickets- Waiting on Community: Migration Status / Upcoming Changes Assistance Needed with the LF-IT RelEng Hiring in the EU
PTL Updates		VVP & VNFRQTs No PTL. No Volunteers: Where do we move 3GPP VES specification ownership? option: ONAP DCAE project can be a placeholder for '3GPP VES specification' Final call email is sent and a decision to move to unmaintained after the Jan. DTF event - FINAL CALL to support the ONAP VNFREQS, VVP Projects - Deadline: Jan 20th, 2022 E2E Network Slicing leadership vacancy N.K. Shankaranarayanan has been reaching out to help establish new leadership for the use case. Kevin Tang from STL is joining the community and is ramping up on the E2E Network Slicing
Subcommittee Updates Arch, Lab, Modeling, Seccom, Requirements	Kenny Paul	Update on Lab HW from Intel HW shipped to Santa Clara in error. - currently being re-routed to UNH
Task Force Updates CNF, Wiki 2.0, ONAP Enterprise		Several presentations organized by CNF/Enterprise Task Forces - Check it out Any update from the Wiki 2.0 Task Force? (Catherine) E-mail to be sent "Call for volunteers to review/re-organise wiki.onap.org"
TSC Activities and Deadlines	cl664y@att.com	TSC Vice Chair Election Kick-off Istanbul Award Nomination Kick Off TSC 2.0 - Project Life Cycle: 2021 Project Lifecycle Proposed Edits - tight to the Unmaintained project discussions - see action items from TSC 2021-12-09 Weekly meeting resumes on Monday, Jan 17 (let David McBride know if you'd like to be added to the invitation) LFN Board follow-up actions - will resume after the LFN DDF January 11th at 3.30pm UTC - ONAP: 2022 TSC priorities and Action Plan - TSC Members - please attend this session - thank you! https://teamup.com/event/show/id/Hm4xpwwdoh872yV9XYjBpwdVt9rddc
Upcoming Events & Housekeeping	Kenny Paul	PTL meeting on 1/17 will be canceled LFN Developer and Testing Forum, Jan. 10-13, 2022 (4h topics + 30 mins break)/day , Virtual Event Registration: https://community.lfnetworking.org/events/details/linux-foundation-lfn-developer-testing-forums-presents-lfn-developer-testing-forum-january-2022/ Sessions Page ONAP Community Program Committee Leads: Ranny Haiby , Timo Perala - Thank you Open Networking & Edge Executive Forum (ONEEF) Q1/Q2 Virtual LFN Developer & Testing Forum, Week of June 13th 2022 Physical Event Porto, Portugal

Zoom Chat Log

06:00:01 From bin.yang@windriver.com to Everyone:
#info Bin Yang, Wind River
06:00:08 From Ranny HAIBY (Samsung) to Everyone:
#info Ranny Haiby, Samsung
06:00:20 From Alla Goldner to Everyone:
#info Alla Goldner, Amdocs
06:00:25 From Bruno Sakoto to Everyone:
#info Bruno Sakoto, Bell Canada
06:00:34 From Byung-Woo Jun (Ericsson) to Everyone:
#info proxy Byung-Woo Jun, Ericsson
06:00:57 From Dong Wang (China Telecom) to Everyone:
#info Dong Wang, China Telecom
06:02:12 From Andreas GEISSLER (DT) to Everyone:
#info Andreas Geissler, DT
06:02:41 From Yuanhong Deng (China Mobile) to Everyone:
#info Yuanhong Deng, China Mobile
06:02:59 From Timo Perala (Nokia) to Everyone:
#info Timo Perala, Nokia
06:03:16 From N.K. Shankaranarayanan to Everyone:
#info N.K.Shankar, STL
06:03:21 From Eric Debeau to Everyone:
#info Eric Debeau, Orange
06:05:56 From Catherine Lefevre to Everyone:
#info, Catherine Lefevre AT&T
06:15:42 From Catherine Lefevre to Everyone:
Thanks Tony

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.

06:03:59 Okay.
06:04:11 recording is started, everybody's needs when you come in please stay muted unless you're talking.
06:04:18 If you're on a phone line you can use star six to unmute yourself. If you happen to send me a private message.
06:04:25 It'll become part of the public record when I cut and paste them into the minutes and we'll start the meeting by mentioning our projects antitrust policy.
06:04:36 You can find this linked from the lF and all of the project websites, its policies important where we have multiple companies including potential industry competitors, participating in these meetings.
06:04:47 Please review if you have any questions please contact companies legal counsel.
06:05:12 and welcome to 2022 everyone.
06:05:17 Hopefully this turns out to be a stellar year for every one, and everything is
06:05:28 a bit better than it was in 2021, and a ton better than it was in 2020.
06:05:38 As far as the agenda topics go today.
06:05:44 Talk a little bit about sitcom although I don't think I see anyone from set Come on the call at the moment.
06:05:54 They would send out release status so probably not much to talk about their
06:06:01 do a check in with Roland.
06:06:05 Talk about what we want to do for a couple of projects without PT else, give an update on the lab hardware.
06:06:19 Got some presentations, we're going to talk about TLC Karen feeding, and then next week's event is there anything else that anyone needs to add.
06:06:38 Okay.
06:06:42 We're Catherine there if I could get someone to assist with gate keeping.
06:06:59 I can do that unless. Thank you undress.
06:07:05 Good morning, good afternoon, good evening everybody. I hope you can hear me now.
06:07:10 Yes, I just wanted to see the opportunity before we go deeper to these tsp meeting to just wish you the best for 2022 to you to your team to your family.
06:07:25 I hope you come back, reenergize you have a fantastic time with them. And you have also time to relax as well I could see some activities during the holiday season.
06:07:37 So some people stay connected as a hobby, I don't know.
06:07:42 But I'm really happy to to kick off the year with all of you.
06:07:47 We have a lot of interesting topics today but I think it would be also an interesting year.
06:07:55 And I just hope that your brain will make it through. So, and thank you again to continuously be engaged with us. don't hesitate, as you said, we, we try to prepare the agenda on a weekly basis with Kenny and also David, but it's not only the agenda of
06:08:17 the TLC. It's also your agenda. So if there is any items you want to bring never easy to do it.
06:08:29 So I'm wishing you a great 2022.
06:08:34 Thank you.
06:08:36 Thanks Catherine, and the quick.
06:08:41 Just a quick blurb about the agenda.
06:08:46 A lot of times folks will reach out to either David Ryan asked if something can be added to the agenda.
06:08:56 The, the planning session that Catherine mentioned, we have on Wednesday prior to the meeting. So, if anyone wants to go in and add items to the agenda themselves, please do so in advance of about noontime when noontime Pacific Wednesday, which is giving
06:09:20 away one moment.
06:09:25 20 hundred and UTC so it's before then if you'd like to add it to the agenda, please do.
06:09:33 Just go in and do the edit and stick a line in there.
06:09:40 Okay.
06:09:42 I saw, Tony. Join
06:09:48 Katherine's joining again Did we lose her.
06:09:53 I'm still there I'm coming in from the other computer okay.
06:10:01 Yeah.
06:10:01 So I guess the first thing that we should talk about, um, although I think Tony may be the only one from the sitcom team on the call is the log for Jay stuff.
06:10:16 Okay.
06:10:18 Would you like to talk about
06:10:23 the current recommendation is that well that they keep finding additional problems with log for J.
06:10:50 Most recent problem is considered minor. But, yeah, compared to the previous two problems.
06:10:46 a month ago, when all the issues were found. They recommended the remote execution command execution problems, they came out with a 2016 version very quickly day later, they came out with two that are not a short shortly thereafter they came out with
06:11:23 dot 70, and then week ago, about, they came out with two dots 17 dot one.
06:11:26 So,
06:11:26 the current recommendation from sec com is that we get everybody up to date 17 dot one.
06:11:38 And
06:11:38 hopefully that's the last one we have to do for log for j for now.
06:11:53 So, we had.
06:11:58 What do you know if CV CV was filed
06:12:09 for own app.
06:12:13 In this regard, CPE own apps.
06:12:35 There were there definitely were CVS filed against log for Ji, not familiar with that particular statement right there about filing one on FB. Ah. So, In the current text.
06:12:40 Someone was talking.
06:12:42 I was going to just mention that this is the thing that Christoph brought up, I think, I think it was actually at the ptl meeting on the 20th.
06:13:14 It was or was it that it was at the TLC meeting and and the the issue here was because own app is being used in production as a, as a critical resource.
06:13:13 There was a feeling that we should probably have a CV filed.
06:13:18 Due to log for j against own app itself.
06:13:25 Yeah, Christoph had volunteered to file it, but at the same time you'll recall that he said that he was going to be taking a hiatus, to work on his
06:13:41 PhD program, and.
06:13:50 And that's where we kind of lost the trail so anyway we thought maybe Christophe had been in touch with CENTCOM about this.
06:13:57 So we were, we wanted to get feedback from CENTCOM about whether there had been any progress on this.
06:14:04 And if not, we're gonna have to see if we can figure out how to follow up with her stuff.
06:14:12 Okay. Yeah, I'm.
06:14:17 I missed the first part of the second meeting this week, because
06:14:24 some various issues.
06:14:29 And so, if the if that was discussed I missed that discussion.
06:14:39 I can circle back.
06:14:44 Yeah, I can circle back with the second and verify
06:14:51 know if that was done or is being planned to being done.
06:14:55 I didn't, I did not see it in the notes from the part of the meeting that I missed. So, okay, that that would be helpful, because we didn't want to bother Christophe since he's taking some time off.
06:15:10 But since it's an important issue.
06:15:14 We, we will follow up with him.
06:15:18 separately if if he has not been in touch with CENTCOM so if you could let us know about that, then we'll proceed accordingly.
06:15:29 Sure thing.
06:15:34 Yeah, I'm not seeing anything.
06:15:37 Yeah, it looks like most of the CV ease that had been filed, I guess I could share this one I'm looking at here.
06:15:47 I just did a search for own app and it looks like most of the stuff here is
06:15:59 applied.
06:16:00 When we did the major effort in Dublin.
06:16:07 So I don't think there's been anything since then.
06:16:16 Quick question why you were sharing that that it was clinging my mind.
06:16:22 So it's good that we are opening. Some items, but all do we are we following on them and then explaining the focus that we have been doing or.
06:16:35 If you click on that one is there a resolution at one point or.
06:16:48 You see,
06:16:48 There is a problem to the lzi and then I guess if we click on the OCI is a province.
06:17:06 Yeah. Okay.
06:17:07 Okay.
06:17:11 Thank you. Yeah, and that the CV explicitly says before Dublin so implying that after Dublin that's not an issue.
06:17:24 Okay.
06:18:00 Kenny Are you on mute.
06:18:04 Indeed, I was because
06:18:07 I had muted myself.
06:18:11 It's amazing how this technology works.
06:18:16 So then, the other thing was
06:18:21 getting jerks getting JIRA has opened against the projects that are going to need to fix something
06:18:33 and getting open as well so that needs to be done.
06:18:39 Anything else to discuss on this topic
06:18:50 is the sibling items I guess it's in progress. The tickets have been created so you know there was a similar one.
06:19:02 Yes, this one I don't know, I think it's still in progress, right.
06:19:10 So, You know that a variety of JIRA tickets, get created.
06:19:32 We get
06:19:25 here because we will need them for the PCs call the Tonys you can follow up offline that will be great with the second
06:19:39 already.
06:19:41 Yeah.
06:19:44 As mentioned in the note on the agenda, I'd like to track those as we move forward.
06:19:53 So if I get a list of those that would be helpful.
06:20:11 Alright, so.
06:20:15 Any other questions from anybody before we move to the next topic.
06:20:20 Everything is good.
06:20:24 Yeah, I'm not seeing that.
06:20:28 I assume it would be no sJi bug.
06:20:32 No, I think, I think these were tickets that were filed against individual projects for, for work that they need to do to mediate the log for Jay issue.
06:20:46 So I think they would be actually be in the individual projects.
06:20:52 Maybe not.
06:20:55 Tony, do you know where they will, would they be filed with projects or no GSA
06:21:02 is assumption is oj si.
06:21:04 Okay,
06:21:07 that would need to be verified.
06:21:10 Okay, well I guess we can just wait to hear back from Tony, and Kenny, with a list of the tickets.
06:21:23 Okay, thank you, Tony, maybe we can action.
06:21:28 Tony to provide a list. Well I'll we've got today then.
06:21:34 Is that not the action item trip. Yeah. Fair enough.
06:21:42 Okie doke Catherine UK to move on.
06:21:48 Yes, if anybody have any questions we can go to the next item. Thank you.
06:21:54 Okay. David sent out an update.
06:22:06 Unless there's anything, David you want to mention regarding the update will skip along. Um, yeah just that I didn't send out a new update this week because due to the holiday thanks haven't, you know, nothing's really changed since my last update.
06:22:16 I just want to remind everyone that m two is scheduled for January 27, and those issues have been published.
06:22:25 And then just a reminder that for our discussion about log for j prior to the holiday. The priority is on the maintenance release for a standard bowl.
06:22:40 So far we have not decided to slip the Jakarta schedule.
06:22:46 But depending on what happens with the maintenance release that that may ultimately affect the schedule.
06:22:57 And that's why it's important that we get that list of tickets, as soon as possible.
06:23:02 That's it for me.
06:23:15 Thank you, David. Any questions from the CFC.
06:23:21 We keep going there for the date.
06:23:28 This temple not Jakarta.
06:23:39 Yes.
06:23:39 Okay, don't see anyone from Roland on the call.
06:23:52 Last I know we still needed assistance with hiring.
06:23:57 The link is there, if you know have somebody who is a good tool Smith, who would like to work for the Linux Foundation.
06:24:12 Please take a look at.
06:24:17 open.
06:24:18 Go to link.
06:24:23 Please take a look at this message, and
06:24:28 go there and direct, share it with your with what the folks you think might be qualified for the jobs so they can apply for it.
06:24:39 Please and thank you.
06:24:46 Did you. Yes. can you did you communicate on LinkedIn for example.
06:24:56 Thank you. I had.
06:25:00 I am and go take a look.
06:25:03 If not, I certainly intended to and if it's not Harrison.
06:25:09 Yeah.
06:25:11 Yeah, I'll go look.
06:25:15 That was certainly my intent.
06:25:20 I don't have any Well, yeah, I really don't have any contacts anymore.
06:25:28 The, the, the different tools and EU but have a lot of, lot of folks that I've worked with in the past so we'll see.
06:25:36 I'll go take a look.
06:25:43 So moving along
06:25:50 the VP, and the NF requirements.
06:25:54 Where do we go from here.
06:26:00 So, I think the email, Watson before the vacation, you have the link here is the final call before we move this to project under and maintain the remaining question was about the specification.
06:26:22 In there is that I don't see Magnus because Magnus was also all liaison for the PGP, and we have an agreement with PGP to notify them when, when the specification
06:26:40 is changed.
06:26:42 So, if we have to unmaintained Vp NVNF requirements. We need to find the old for the vest itself. And I think vj if I say something wrong. The idea was maybe potentially to bring it under the vz umbrella.
06:27:03 So, at least we can continue to update the vest.
06:27:09 If there is a need.
06:27:10 Am I right, or concerning this BJ, because like yeah yeah that that's an offense Sure, I think this is one of the major client for a specification. But yeah, it's the specification with us broadly beyond DC as I mentioned the trees up and also the aura
06:27:29 and on our pretty faces. So, yeah, wherever we want to I mean I think DC could be one placeholder. I think the last few releases though we didn't have any major aspect changes the last version we approved was seven to one which is, which is, I think,
06:27:45 pretty bad conference, we have a place of an easy way to absolve us, please up specs without involving specification itself so i think that's that's more flexibility so we'll have to see if there's any further division data, or recommendation coming from
06:28:02 that going forward.
06:28:07 going forward. So I would read again the topics when Magnus will be back on the 20 just to be sure that is fine with that or maybe have
06:28:16 another opinion about Wonderlich.
06:28:20 But for the moment is a project that has to be a placeholder on the see probably the best position, or if it's something that the requirements of committee want to own their option that what is clear we cannot live in Google so I will bring again this
06:28:45 Okay.
06:28:49 Thank you, any difficult when you are interested.
06:28:52 The deadline is on the 20 so the DC on the 20th we do some conclusion about DNS DNS equipment and bvp. As a reminder, the DNS requirements will never focus on the CNS requirement, the CNS requirement under by undercut, which is the other, which is do
06:29:15 by default or requirement open source community if I can see so.
06:29:22 All right.
06:29:34 Shall we move on.
06:29:40 Yes. So
06:29:44 really see already to provide an update.
06:29:47 Concerning the Mitchell slicing all weekend courses so if you need another week.
06:29:56 To conclude, Oh.
06:30:00 So, actually, I just sent you an email Catholic.
06:30:04 So I can do a short update.
06:30:08 One and because this has already happened in the slicing use case mailing threads. So I Hilla from Wipro has been leading this and she's still playing quite an important role, doing managing the release planning and just to remind everyone she had said,
06:30:29 you know, she, she could not keep doing that.
06:30:33 And I reached out and I found that the pro team is still involved and she would be involved supporting it by leading the use case and all the other work and and the architecture and all that was getting a little bit out of hand.
06:30:49 So one thing I did and discuss with folks, and so there's a, he founded a good resource from steel. That's my company.
06:30:59 Kevin Tang, and I talked to I ILA, and we had a call with Kevin and then she sent an email to the slicing team mailing list, introducing him and we thought we would just take it one step at a time.
06:31:14 So the slicing use case team called was on Tuesday this week.
06:31:20 And I'm happy to say I think the team was welcoming.
06:31:26 And just to introduce Kevin Tang, he is, he's actually coming in bringing in an Orion perspective and that's, I think it's a good compliment, because he's used to win and he's using he's used to architecture and through gap and slicing.
06:31:42 One thing is not that used to his own app procedures and so I said I would.
06:31:48 I'm helping him get used to that all of that and so he will need a lot of help, and but he's committed.
06:31:55 And so it's, I think, I think we have a reasonably good solution.
06:32:00 And if you need more help, we can reach out, we can see how it goes.
06:32:05 So, David and Kenny this exactly three weeks to them too.
06:32:09 And I think I realized dunno.
06:32:13 You know, a lot of the heavy lifting already looks like things will be okay.
06:32:18 There is a demo next week at the DTF that you live in.
06:32:24 Henry and Duncan when you're also on this call. You could also comment, and then then the architectural review for slicing use cases.
06:32:34 The week after that.
06:32:36 So, it's it's it's it's going along.
06:32:42 And so I think we could just let it just proceed as is and see how it goes.
06:32:49 So I don't know exactly what the precise steps need to happen. minutes it's not a.
06:32:55 It's not a,
06:32:58 like a PDL kind of project right it's a use case lead and I think that we have a little bit more flexibility there, but.
06:33:06 And, but as as interact for as things go along and as the use case needs to interact with all the different projects I think that's when we will see more of that transition.
06:33:18 So, for example, in the DCA call this week with I think Kevin was there, and I wanted to just, it was all very new. I didn't want to even say he's taking over we will just see how you go one step at a time.
06:33:32 Yeah.
06:33:32 So that's, that's the update and welcome input and support and help other people are also interested, please let us know.
06:33:42 Well that's excellent news.
06:33:45 Oh, good. thank you.
06:33:49 And in your right with a with a use case somebody that's that's helping to wrangle the use case.
06:34:01 There's not an official
06:34:06 or a specific process for that.
06:34:11 Right, yeah. And, and I think people are flexible there's a lot of work, especially the slicing use case touches many many different parts, and so it doesn't have to be one lead I I told I'm already thinking of her as they are colleagues.
06:34:29 And so I think from our perspective we have to make sure, and I think this point was brought up before my number that our transitions.
06:34:39 People are committed, and there's a lot of people doing I my observation was a lot of people in the team doing the work, but it's.
06:34:49 When we say leading it there's all the requirements of presentation and interaction and phone calls and it is a burden for many people. So, what we observed was there are people who could have work candidates who have the experience and everyone has has
06:35:08 constraints. So, so anything we can do overall as a community to just make it easier for the whole world steps up is always good.
06:35:20 These are excellent news Shanker and thank you for the full of work. I think I'm the same I was speaking to receive your emails to to to bring this great news to the owner community and I will definitely follow up with you with additional support.
06:35:41 But that's great for us that we can have some hypnotism that the people who we continue to the hive and make it happen because it's a very crucial use case that the needle slicing is required for anything we do.
06:36:03 And it was so really useful for the work we do with Johan community.
06:36:08 So thank you so much.
06:36:10 And let's, let's keep going. Right. Let's keep going. So thank you so much. Thank you You're welcome and he's by the way is in California and so I think the, the reevaluate it all the time zones, that's a challenge.
06:36:26 Especially the slicing excuses, is covers all time zones more than
06:36:34 from Europe as well.
06:36:35 ya know, so maybe you can tell Kevin, you should join these calls also.
06:36:44 It's 6am there.
06:36:48 We find a way to follow up with him. So, okay, okay, that's really great. Thank you and if anyone has comments please, please, just let me know or let the slicing come to the slicing use case calls and.
06:37:04 And just to add.
06:37:07 I think that particular focus I think my advice to Kevin was, to, to, to build that connection with Orion, because Orion slicing is a supported use case in Oregon, and there were meetings between on app and Orion but they sort of stopped around March
06:37:22 of last year.
06:37:24 And so I think there is a wider and and and this these topics are bubbling up as to even in the way see deals he calls his top topics are bubbling up as to what are the northbound interfaces from the SMS and he's an SMS inside the SMS or not and how and,
06:37:41 you know, there's this. There's there is. It's a good, it's a it's a good time for the slicing use case to be even more aware of what's happening in the community.
06:37:53 So I think that's why I feel good about is bringing in that particular value and you can learn all the owner stuff procedures and.
06:38:05 Okay. And there is another point you bring Shanker if there is anything we can improve and remove the load, things that from a process perspective.
06:38:19 You will not define as a burner, and we can improve without impacting the deliverables of any CDs prefer you also to share your experience, or to ask Kevin to share his experience as a newbies
06:38:38 week because we, I believe we offer and definitely for any new suggestion, but we are running a little bit of ideas about what is still the major concern because we were suggesting that we can have a coup ptl leadership, would there be no concrete
06:39:04 solution or suggestion, and I know I want to bridge to the Ddf, I know David you have a session, also to continue to seek. What can we do better.
06:39:20 To improve. Cool.
06:39:24 That's that's a very good point I'll tell them, because you're absolutely right. When someone is first learning the ropes that's when they realized what was easy what was difficult, and some things have gotten much better and.
06:39:37 So, for example, I know, David, since these reminders, just before the release deadlines and that David that helps.
06:39:46 About a week you know you sort of know what, even though yes we can go look it up and sometimes things fall behind and after so that's good to hear a lot of times I feel like everyone gets my emails like oh no not that guy again.
06:39:59 But so that's good to hear. It was like that first for me and then I thought, Oh okay, then it's like, you know, you immediately address that when you get an email from David so that you don't have to worry about it.
06:40:14 A week later, yeah.
06:40:14 Yeah, that.
06:40:14 Yeah. So, yeah, that's it's a good point I will be can use this also as alone as two, and then and Kevin.
06:40:24 Sorry Kenny and I are happy to get together with Kevin to if he you know wants to understand the process better. That's would be that would be very good.
06:40:50 Yeah, maybe you can pass that on to him and, and if he's interested he can reach out to us. Yes.
06:40:44 Thank you.
06:40:59 So I think if there is any other questions regarding defeat the end of date, we can move to the lab update Kenny.
06:41:10 Okay. So the good news is that the hardware has shipped.
06:41:16 The bad news is that rather than shipping it to University of New Hampshire, through a snafu. It was shipped to Intel Santa Clara.
06:41:29 So, Bob Monkman is currently working on kitty cat Reeve rerouted and sent, but the, the, the good news here is that the, the, the hardware has officially been procured, and is at least in transit so that's where we are.
06:41:52 Hopefully we will have an update better update next week.
06:41:57 But that was it.
06:42:02 So sorry for Bob that it got messed up.
06:42:07 In Santa, Santa Clara so there you have it.
06:42:11 That's the update.
06:42:14 I know everybody's looking forward to having that up and running.
06:42:24 Yep.
06:42:26 Okay, so that's great and then I believe the anyway the coupon when he will remain available for the fullness change, and they would be a concrete plan to, to the PDL one we stuck to do the transition right.
06:42:45 Yep.
06:43:11 I'm moving along then to
06:43:18 CF
06:43:23 Task Force. There's several presentations.
06:43:33 Someone would like to talk mentioned that. Yeah, I just wanted to promote
06:43:41 I think we have a full presentation scheduled by the CNS task force to promote, not only what we have been doing in the past and the requirement of Jocasta, but also to promote the as the model, and I'm just looking beyond is on the call, maybe you can
06:44:03 share a little bit more about what you intend to do because you have to presentation with the other companies, maybe you can give some more some older.
06:44:16 Sure. Okay. For as the specification package specification perspective, we have a presentation plan.
06:44:22 one by Marion, and Zoo and myself, and also a theme from Nokia, So that's the plan from specification.
06:44:43 And we continue to communicate with all in community, and second part is that is the PRC roadmap so which is onboarding to STC and Orchestration by two so and other sub components.
06:44:58 So that's what we have now, and the.
06:45:03 I think the specification pretty well received and that we need to some minor adjustments need to be done with the origin and the Nokia, and that's probably sort by.
06:45:14 So anyway, that's the plan for next week presentation.
06:45:21 Thank you, man.
06:45:23 Thank you so much beyond and then we also some presentation.
06:45:28 Thank you. And we thank you so much beyond and then we also some presentation, we have home Lucas, and also see shoe and Deimos, so it's not only about a theory, it's also to demonstrate older older cnn orchestrator have evolved in the last release and
06:45:44 and with some concrete demo that the team is planning to share. Ronnie anything you have in mind as well. Did I cover everything with Bianca.
06:45:57 On the full presentation that the Senate stuff for them to do.
06:46:06 I don't think I have anything to add to the moment.
06:46:10 Okay, we also seize the opportunity to do the work is to in progress to prison. The, the landing page, not to prison the landing page the new landing page of the center, but we will ask and beyond.
06:46:24 I know you have some constraints I wants to give you an address. We will find the CNS Task Force presenter have to also add the link to the new CNS landing page.
06:46:37 In the meanwhile within two days to finalize it.
06:46:41 But we have been working and thanks again for all the effort put in this.
06:46:51 To change a little bit.
06:46:51 The, the wiki entry of the center stuff for us to be more practice and more relevant.
06:47:00 With the new, CNN, landing page.
06:47:03 Okay. And then for the enterprise.
06:47:10 It just to recap of what has been done last year, and also what we intend to do this year and open forum, if there is any new under fair use case we should consider.
06:47:34 I guess you were trying to go to the landing page, give me.
06:47:39 Yeah, I'm a bit lines are trying to keep up Sorry, no issue.
06:47:56 We can add the link. Here we go, here it is. Working progress. If you have any comments, suggestions to improve it.
06:48:04 Feel free to write to the CNS task of this call is to reach directly honey.
06:48:09 Honey has been driving this new landing page, which is great.
06:48:19 Oh yeah, just to clarify, I think technically what we will do once this page is ready for publication, we will just replace the existing main page so there is no link need to link a new punch.
06:48:43 Thank you, Danny. Okay. Yep.
06:48:48 Yep. And then on the price of already cover quickly, and then find any.
06:48:56 I know at one point we kicked off the wiki to the tour de force.
06:49:04 Pink t mo honey you were trying to drive that but I'm not sure if we have been able to progress in this domain you to order priority. Is it something you would like to resume this year, what is your feeling about this.
06:49:33 Sorry, what are we talking about I was the the the wiki task force that that we talked about getting.
06:49:43 Oh.
06:49:47 To be honest, I think due to other priorities we didn't have much of a chance to go into that last year. So I think what might help is maybe if there are more volunteers that will help us get this thing going.
06:50:08 And then, let's see if there is any, maybe send the weekend send the cold football on TV mail
06:50:18 is nobody stand up that nobody December, but it will stay as it is.
06:50:26 So, we can send an email to us go vote on the.
06:50:57 Okay,
06:51:01 Back to you can eat.
06:51:03 I'm finishing my notes here.
06:51:11 Okay, I'm coming up.
06:51:15 I will be now that we're in the new year.
06:51:18 I will kick off the TASC Vice Chair election.
06:51:22 Also I will kick off the award nominations for the demo release.
06:51:30 And today and tomorrow and probably my priority is going to be prep for the event next week.
06:51:37 So I may not get that kicked off until early next week.
06:51:43 But those are coming up, and on my list of priorities to do.
06:51:52 So be watching for that.
06:51:58 The next big thing here is the discussion of the
06:52:07 project lifecycle, and how that
06:52:14 the unmaintained projects there let's open that in a new tab.
06:52:27 And
06:52:33 these were the things that that had been discussed
06:52:38 the need for joint session between set calm and the architecture subcommittee and the requirements subcommittees.
06:52:51 To address these bullets, I don't know that anything has happened in that regard.
06:53:01 Since, since the meeting. On the ninth. Does anyone have any updates there.
06:53:19 No, I think that maybe we can look at the action I, but what I would like to suggest is that maybe David one you will resume the meeting on the 17th, maybe also review the action items, but we can ever quickly look at if we look at the link now, but it
06:53:37 will be probably more appropriate to review the different action items.
06:53:44 Doing your specific goal. And by action items.
06:53:49 There was a list of listener, and I don't know still mind on the bridge, but there's still an action on my side to review what you sent me before the only day.
06:54:01 So, but there is a section on the TC from the December 9, where we were defining the songs that like project team to define functional dependency with a maintain that's already covered as part of the release management process so these different action
06:54:21 items which is the one that can you start to highlight it, if, if you could give you a day with, with the working team, and and give us an update at one point, because I don't know if we can do it to the right.
06:54:40 So, I know item one is cover item two, I don't know, and so on and so on. You see what I mean.
06:54:48 Yeah.
06:54:50 Okay, I will put it on the agenda for our meeting on the 17th.
06:54:57 Okay.
06:55:03 But thank you.
06:55:15 I was waiting for the new year to Easter, with a fresh mind so I have two, three action items ongoing that I need to complete.
06:55:25 These were from the elephant both from last year into fall.
06:55:30 So you will see the Mohawk safe. After the PDF, working on that and providing update to the TASC as well.
06:55:40 So I believe we have captured all the GSB activities and the blind, anything else.
06:55:48 The only thing I wanted to also bring up the DDS event.
06:56:03 I forget to add that to the agenda. We have a review of the 2022 TLC priorities. So I want to be sure that the TLC members. notice the session.
06:56:08 Because I want to be sure that what we determined at one point.
06:56:16 In September, October, as priority for this year, which was done with the former tsp board is also a key with the new to the board, and the session is plan.
06:56:29 I'm just looking at the schedule for next week.
06:56:37 I hope I will find it quickly.
06:56:40 The to see prioritization speech or session is on noise and the
06:56:54 second half of the first day.
06:57:03 Yes,
06:57:00 you are.
06:57:06 January, 11.
06:57:06 So I would like to have the GC to join it.
06:57:09 Because I want to reconfirm, the priority, which was defined with the former tsp.
06:57:19 In.
06:57:39 Thank you.
06:57:51 And I will also send a note
06:57:55 to be.
06:58:02 January.
06:58:03 11.
06:58:03 Is it the 2pm UTC, honey.
06:58:14 Or is it 3pm 730 Pacific is
06:58:22 330 UTC.
06:58:28 Okay.
06:58:31 Thanks a lot.
06:58:33 Thank you.
06:58:50 Okay. Oh, and speaking of which, hey we have this little developer event next week,
06:58:58 and
06:59:01 Randy Timo thoughts on that I saw the demo just a note that I did see the email about the link from Martin I will take a look at that.
06:59:14 Okay.
06:59:20 So anything you guys would like to mention.
06:59:27 Nothing in particular, as you can see the agenda is very packed, but on the other hand I think everybody's got to to the hang of things and it's going to be very similar to previous events so you can always all sessions will be recorded if you can't attend
06:59:45 the session.
06:59:46 There will be a recording available and meeting notes.
06:59:52 So yeah, again, it's the same format we've grown accustomed to.
06:59:58 In recent events.
07:00:03 And I seize the opportunity to thank you on the MC mo to be all the presenters at first, at the program community and helping to build these agenda based on the
07:00:18 content submitted by the team to thank you so much, because we need you.
07:00:23 We need people like you to make it happen as well so thank you.
07:00:35 And that's it.
07:00:36 We've got something that will be coming up.
07:00:41 The end of q1 or q2 and then our next developer event is scheduled in Portugal, the week of June 13.
07:00:50 That's it for the things on the agenda today.
07:00:55 New York, only thing because we have a little bit of time and sucker is still on the breakthrough sector is anything you want to share about the architecture review that you're performing in the context of the Jacka and to any special request any update.
07:01:16 Everything is going well, you have all the appointment.
07:01:30 Okay.
07:01:31 Okay. So, we are finishing quite early today. Any other particular topic so question or anything that any of you would like to bring before we close.
07:01:47 I just want to mention for those that are interested, a new kit completed the locales release this week. I think it'll be announced at the DTFX week.
07:02:08 And what was the school but I level of this release.
07:02:14 Well, the, the main thing was, it was basically just updates to the primarily the reference architecture. But there are also significant updates to reference conformance, including updates to fog test.
07:02:39 And also this was the first release to fully deployed the new release process that was developed last year.
07:02:53 Okay, so I wonder if it is, is it also related to.
07:02:58 I'm just going to the disco list. I know civic was sending a notification concerning your front desk eternities.
07:03:10 One was 23.
07:03:12 Yeah, that was, that was specific to fuck tests, it's not directly related to a new kid okay.
07:03:21 Although I new kid does leverage front desk. Yes, yes, yes, yes.
07:03:27 Yeah. And there, there will be an announcement, and, you know, Brandon will be coming out with
07:03:35 you the marketing, which will include detailed information about the accomplishments, for the release.
07:03:49 Okay.
07:03:52 Well, thank you for promoting the work done by an open source community because it's also interested to learn from them and to see how we can benefit with your community of what has been developed by them.
07:04:09 Anything else from anybody.
07:04:20 Okey doke.
07:04:22 Happy New Year everyone. I have one node.
07:04:27 One note.
07:04:29 In case you haven't heard Civ badging has been rebranded. Oh yeah.
07:04:35 As the Open.
07:04:38 Open Source security, foundations, best practices badging program.
07:04:46 So, the open ssF best practices badging or for shorter. For our purposes I think we just go with best practices bantering program.
07:05:01 So
07:05:04 maybe we should take a note, and it's still the same wiki page and so on its own.
07:05:12 Yep. There's just a rebranding for now, the wiki page, or the.
07:05:20 Their website will add a nother domain name at some point, but there will be redirects from the old domain name.
07:05:30 So, but that hasn't happened yet.
07:05:34 It's strictly a rebranding at this point.
07:05:44 That's good to know.
07:05:45 Thank you so much to me to share that with us as one.
07:05:58 Nothing else changes under the hood. Just.
07:06:03 so will, and all the things that we do, be referring to it as just best practices managing program.
07:06:17 Okay, that's good.
07:06:19 And anybody have any other comments so.
07:06:24 Even so, to share before we close.

BRIDGE: https://zoom.us/j/661303200?pwd=TFdRd0c2MTJUem8xa252UGJHTE1Mdz09

Agenda Items

Subcommittee Updates

Release Status

RelEng/Infrastructure

PTL Updates

Subcommittee Updates

Task Force UpdatesCNF, Wiki 2.0, ONAP Enterprise

TSC Activities and Deadlines

Upcoming Events & Housekeeping

Sessions Page

Task Force Updates
CNF, Wiki 2.0, ONAP Enterprise

Browser not supported