Internet Engineering Task Force Interim Meetings, 10 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: IETF-UUIDREV-20230510-1800

Description

UUIDREV meeting session at IETF
2023/05/10 1800

https://datatracker.ietf.org/meeting//proceedings/

A

We can hear you.

A

Well, it's almost 1101 or equivalent.

A

um Should we get started or do we want to allow a little bit more late arrival time.

A

B

Two another two minutes, maybe.

A

A

ah Brad's, here too, that's good.

B

B

Chat logs materials, but nothing else, I, don't think we have any other slides at this point.

A

uh I think that's I think that's it. It was.

B

A

And look at the repository right now.

C

A

um Yeah I I, the I, think the problem I had last time was finding the uh um the link to the the link to the minutes and so forth. Okay, on that, this time.

B

I reposted that.

B

C

Minutes before I hope that was useful.

A

The only place that I found the link to the meat Echo was in the on on data tracker was in the um uh uh the the calendar, invite it.

B

Must be somewhere if you go under meetings under meeting materials for today, then you'll find the links all the links.

A

B

I wish it was under the agenda.

A

Okay, well, it's the same thing and we're at 1105 or 205.. Let's start East Coasters. Let's go.

A

So who's talking Michael, you were me, I, don't know. I'll.

C

Run it yeah, so there you go well right, yeah.

B

So I'll just put up the note well for for the purposes of the uh recording. uh That is not the note. Well.

B

But you know, if you have any IPR need to tell us about it and if you have any questions, please ask the chairs or your area directors and we'll straighten you out and aside from that, um please be nice to each other, uh speak slowly and um address the issues rather than the people.

B

Okay, so uh I think we just need to jump into uh the issues that are open.

C

Yeah issues open are that there are no issues open, um there's one request: without changes, a grammatical error and I simply, you know I think it's fine I just didn't know if it was worth a whole new version.

B

Just pull it in and next time, you'll we'll get discussed comments from uh at some point and it will just show up, as I can do that even here yeah you.

C

Want me to do that right here, just yeah. We can just merge it.

A

My point was, if.

B

C

Was if there was no other changes to make, then is it? Is it worth a whole nother Draft before we send it to the next folks, or do last call.

B

Okay, do we do we? Do we get all of this things about our Shaw One issues? I? Think, is everyone happy with with the results we're there? I am.

A

I think so I I honestly uh need to need to go through the whole. The whole thing again, but um I I think we're probably you know. I can probably do that overlap with the working group last call, and so maybe that's what we should do next is kick off a working group last call and then uh I would suggest. Maybe you know we incorporate whatever. Whatever changes result from that, including this seconds thing push out another push out another version and do ietf last call with that.

B

Yeah, so the isg will do the ietf last call um uh once our 80 pluses it. um So we don't have to worry about that. um So uh should we we push the buttons for the last call at this point.

B

What is how do we is two weeks enough? Do we should we go to the end of.

C

I think we said one month is what we wanted to do.

B

C

But yeah I agree I, think based on what we have. We just use draft three, as the last last call version sure there's a double seconds in there, but you know we know it's there. Otherwise I've got zero feedback on my other forms. Okay, so this one is I think we're in that state.

B

So um who, which one of us Jim you or I, are going to do the shepherd write-up.

A

Or anybody else I mean it does not.

B

Or anybody else other than Kaiser.

A

Yeah or probably other than Kaiser or Brad, actually, which.

B

A

Leave many uh doesn't leave many uh options open, but.

A

I'm about to leave on some travels, so I'm I'm not anxious to do the last call right up.

B

Okay, well, let me push the buttons to saying: let's go to the ink working group last call- um and we said four weeks right and.

A

Actually, we don't need the shepherd right up until last call is.

B

Over we don't need that. That's right, exactly uh I, don't think we not pulled group blah blah blah.

B

None of those things matter.

B

And we are now in working group last call good, okay! Well, that might be all for today, then shortest virtual interim ever broad Peter, any comments. Mr un Duke.

C

B

Guys I'm just here to learn. If this is always this easy, then it's great.

C

Oh we've worked hard to make it.

B

This easy fair enough yeah. Sometimes we just need a deadline to get everything done with bye and I. Think that was the point of today's meeting was to to make sure that we're all on the same page we uh check in and we're good okay. So uh that puts our last call date.

B

uh I'm gonna put it in my calendar um that puts our last call codes up to um one two: three June 7th we'll make it June 9th, that's a Friday, maybe the Thursday, hey I'm, just putting an entry in my calendar to remind me to uh follow up with the last call.

B

uh Working group last call.

C

Now that the only the only thing that would comment is I think at some point one of our interns, we discussed uh making sure that the itu and the iso folks had a chance to weigh in on the last call, since they have Upstream documents that depend or tie back to us. So I think at this moment we would be good to at least get this in front of those Liaisons.

C

They'll, you know blast it out there everywhere, just say: hey last call speak now or forever hold your peace type situation to the internet.

B

Itu T and what was it was IEEE no ISO about.

B

All right I'll do that um I um I, just think I knew who are iq2. We got, Scott um liaison is and I'll figure out who the, if there's this different ISO liaison.

B

um But of course, uh if you had no people tell them as well uh I let the lib you ID people which turns out to be Steven, um um so um um is one of them in a more or less the Linux world that happened at whatever February, and they think they had some comments already and I'll. Just let them know that it's a last. It's we're in working group last call and if they have any other comments, that would be great.

C

um Yeah I had comments into the to the prototypers, who have really helped us out: six: seven and eight I kind of added and cc'd everybody out there and and ask them to really look at draft zero three and give some feedback. So I didn't get anything from that on draft zero. Three, so you know I'll just read comments on that thread. Saying: hey! It's! It's Lads, officially last call: okay.

B

uh Well, there's nothing else. We can close the meeting, we're not having another meeting uh unless we need to somehow for some. We may need to have some conversation based on some discuss, but hopefully we'll we'll know with this. If we, if we get into our, if we get into a problem with comments from the iesg, then uh we'll know at that point if we need some other effort, uh but at this point I don't see any reason to uh have that.

B

Wonderful, thank you Kaiser. Thank you, Peter. Thank you. Brad!

B

That's good yeah I wanted to say thanks to everybody, this has been a whole yeah whole.

C

Adventure here, so this is great awesome. It's finally happening good.

A

B

All right, I'm.

A

Sure I'm, sorry, we haven't had a little bit more activity. Just in terms of you know getting uh you know, kind of a wider, wider range of of comments, and that sort of thing- but uh this is a this- is a pretty small working group. So.

C

I'd say: Jim I'm glad that we didn't, because we had all that hashed out before we even came to the ietf, so we Brad and I were able to to work through all of that I'm actually really glad that it was quiet. So I'm just glad we're here near the end. I see I see the end in sight, cool all.

B

Right good, thank you. Everyone all.

A

Right have a beer.

B

C