Internet Engineering Task Force Interim Meetings, 6 Dec 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: IETF-CELLAR-20221206-2000

Description

CELLAR meeting session at IETF
2022/12/06 2000

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

A

Good times since the last meeting.

B

Yes, it was a great fun actually.

A

C

A

Hello and how are you.

C

Good sleepy excellent.

A

uh We are, we are still Gathering, so I will uh let people gather for a few more minutes. I mean a couple more minutes. um Just to let people know. uh Michael has been wrestling with a migraine, so uh he will not be joining us today. So uh you have me.

A

C

We never have you both at the same time, lately.

A

I I think we I think we do have uh meet Echo records with both of us all together together.

A

So so uh that's that's the uh that's. The only thing that I would uh uh mention mention about. um Okay, just to make sure everybody has it uh here's the link for our notes for people to uh log into and uh and uh add yourself as a attendee down under roll call. If you look for that- um and we do have a good uh looks like we do- have a good turnout too. So thank you all for that and.

A

B

And you announced yourself as delayed Spencer Dawkins.

A

A

B

Yeah, it's a bit, um I, don't know. What's the right word.

B

D

Have done well as Halloween I.

B

A

Well, I was impressed that one of our documents was submitted on Halloween, but um so they're always inspiring.

B

As long as it's not the first of April, because people can get ideas.

A

Very much so yes, um I am going to if this is okay um share my screen um and that will take just a second to get organized.

A

Just so, we know what we're looking at and.

A

This one uh just so people like I, say just so: people can follow along um I will go ahead and call us to order and uh and uh welcome everyone and uh put up our usual administrivia part of the agenda um and.

A

See uh so as remote like I said, we're we're- and we are talking about uh the proposed virtual interim uh meeting- dates for 2023 later in the agenda, so letting everybody log in and.

A

The draft minutes from the previous meeting, although they are accessible for people who know how to look uh we're only distributed like two hours ago on the mailing list. So uh if it's okay, we will, uh we will uh give give people a chance to look at those before we approve them.

B

Yeah I saw them earlier because they weren't early on a mailing list, but uh they were on the I, don't know where the minutes are, but wait. A minute usually are.

A

Yeah so yeah well, basically, so basically, the best place to look is if uh um Michael and I both take minutes uh in the uh headstock that I'm showing now. So uh you know, if you open up the, if you open up the meeting notes for uh any meeting, uh you see the completed stuff that we submitted as as uh minutes so um but, like I, said I, don't want to necessarily lean too hard on that.

A

A

So one thing I wanted to do at the uh beginning of our our time together was uh talk about the proposed uh 2023 meeting dates.

A

um I sent uh some proposal out on the 29th of November and there were a couple of data errors. Basically, like you know, I had a couple of them that might have been like the the date was Thursday of the right week, but you know instead of Tuesday, but that didn't change the possible conflicts which are uh here um and uh the current plan uh that I wanted to talk about with you all before we requested these is. We would move our March meeting into April 4th because of uh ietf 116.

A

uh that we would cancel our July meeting that we would move our November meeting to uh the 5th of December and cancel our December meeting like we did this past year.

A

um Are there any other uh Steve said, uh looked good to me on the mailing list and uh are there any other things that we should be aware of uh before we uh turn in the list of uh of uh meeting requests.

B

I have no objections.

A

Cool uh I did have I, so this is a Spencer question about uh any plans for in-person uh no time to wait in 2023. That might might change might change. Our plans, like uh has happened a couple of times and then I.

B

A

This I know this may be early for them, but uh people- you know you guys are connected so uh well connected. So.

D

We don't have a date for uh no time to wait next, yeah not yet.

A

D

So we we made challenge, maybe October November, we don't know uh we'll see when we have a the date.

A

Okay, so um oh does this look good for Spencer to turn in the requests and then we'll you know if, if there's any, if there's anything that comes up, we would manage that conflict like we always do.

A

And uh just so, the working group knows when I start typing, like I know what the answer is as I'm asking a question. That's just that! That's not me telling you I, don't care what you think. It's just me trying to get ahead on the notes.

A

So uh if there are objectives on the call, this would be a great time to make them.

C

A

We supposed to.

C

Be good now we change the dates for the ietf, for example,.

A

So, okay, so the ietf, so the ITF dates, uh because those have uh hotel reservations with them. There are contracts with them uh a couple of years in advance, some some of them they're very unlikely to change so um I.

C

Don't know I, don't think, should we change our schedule already for these dates.

A

um Only uh so, if for okay so like for this one, uh which we would usually have as March 28th, is that highlighting okay, um that's mostly because uh that that meeting is in the Japan time zone and uh both Michael and I are likely to be be on site. So um it would. You know it would be the middle of the night for us and we would not be at our best, so that that you are asking a legitimate question about.

A

uh Why that you know why we would why we would change the our dates to accommodate that.

C

Another question is: do we already change the dates like it seems? The 28th of March won't be okay, so we.

A

C

Now, to put it on the 4th of April.

A

Yeah, that's that's what I'm that's yeah I'm I'm go I'm going with this. uh You know with the uh current plan that I had in the minutes so yeah. So yes uh moving Marsh to April 4th and uh moving the November meeting to uh the first week of December, but uh and canceling cancel canceling our July meeting, so I will I will uh I will I will I will turn it.

A

I will turn in the right set of of uh requests before before uh uh we get going so yeah excellent, and thank you for correcting the uh boxing day thing I like I, say: I, don't know how I managed to pick the wrong date. Number uh the the wrong day number out of the week that.

C

I was looking at if inbox in days and leave a thing in the UK. We've never heard.

A

C

A

uh Canada also so so that so uh so Michael would be uh affected, but yeah, that's where it comes from um so cool, so uh Spitzer will submit the request, yes, excellent um and uh for the working group status uh update, we have a lot of drafts that were expiring and have now been submitted. You know with a you know, with update with that.

A

You know have been resubmitted so that they are active in the data tracker and thank everybody for that and, uh let's see um and this one here yeah the Flack one uh is actually uh Spencer needs to correct this. I'll do that well, I will not do that. While you are watching.

A

This uh the the thing with the thing with that slack is uh that we have uh finished working group last call and uh Spencer just needs to do the the shepherd write-up on the on the document, uh so that should be happening that should be happening soon. It just wasn't going to happen this week so uh so uh and matroska. We are also waiting for uh ad evaluation.

A

uh So um those two documents we are uh waiting on the next step in the publication process um and, like I, said thanks for everybody. For um for posting, the updated uh working group drafts I wanted to ask people. What are we focusing on next now that petroska and flacker, leaving the the base matroskus back and Flacco, are leaving the working group.

C

Well, my trust care. We have two options: either the codec document or the tag documents I think the codec documents is more important, but it will also be a lot longer. So I would actually appreciate.

D

The attack parties are so long because there will be a lot of discussions about attack, meanings and uh the details about tech and for me, the codec part is more important.

C

Yes, I think the codec is more important, but I think it will take less time for the tag because there's like I, don't know 30 codex and we have to go through each of them. uh While tag is mostly done, we're not going to rewrite them. If anything, we have to just change the documentation, so I would rather focus on that because it should be faster and.

C

B

C

And, of course, we can do both at the same time, because I don't expect actually to have a lot of work on text, but I know maybe BJ omia, but other ideas on that. Well, anyway, that's my opinion.

D

We do both at the same time, in parallel.

C

Yeah, like we did dbml and Metro scale at the same time, and it worked fine, yes,.

D

We are totally independent, so we we do well yeah.

D

So for f everyone, it is still um yeah. I have a lot of people, that is, they are very happy with uh ffv1 version 3.. So for the moment uh there is no uh not a lot of work on before, but we still want to to focus on V4. At some point, foreign.

D

Stable about what already exists.

A

Yeah just to test another urgent right now, right.

D

Yeah, sorry, we just we still want to to work on ffv1.

A

D

Is a matter of time.

A

Okay, cool and that and that's helpful for me and Michael and uh for our area director, just to know what uh what to expect uh we probably we. We probably should be updating uh uh the uh dates. The dates on on these.

C

A

And which we can do by email.

A

uh And I'd like to have, uh uh when Michael's available also.

A

Okay, cool um Steve, you you had asked the question about uh a document that would handle ebml, lorata and uh um and uh so for for people who are following along. We have five reported irada, including six technical. uh We have proposed texts for all nine Narada. Thank you for that, uh and we did have. uh You know, like I, said just the one question from Chris about uh whether onearada should be uh combined with another erotic or not that that question would be interesting if we did not do another document at some point.

A

But uh if we do another document we'll have to you know we'll have to make we'll have to decide what to do that anyway.

A

So um Michael Michael's suggestion on Halloween was uh yes, we should start the uh 79, uh sorry 8794 Abyss uh now, but not rush um and so I wanted to ask the question: um do we have a sense of when we would be likely to uncover more errata uh I'm, assuming I'm, assuming that part of the process of uncovering the nine we found so far uh has been people using using uh ebml and then uh having questions.

C

I I, don't think we can say when, because basically the win before was when we finished the matrosca document. If we find something that is a problem that didn't happen, so there was some reports from the ebml RFC from people who read the document and tried to implement and saw some things.

C

We reached these two steps and I think from now it's one it's less likely to have Errata now.

A

Okay, cool: um do we do we want to go ahead and um and this I I? This is a question probably for uh me and Michael, but uh um but basically the Spencer will uh discuss uh adding a milestone for this.

A

With Michael and with uh with Murray uh rid.

A

Oh so cool, um and then thank you for that. That's very hopeful for me.

A

um I wanted to uh ask what people's Impressions were uh about the in-person in-person meeting um at the at the uh had no time to wait, but uh because I was the only person who I think I was the only person who wasn't on site. um Well, uh let's, let's defer that until uh Michael's available. If that's okay.

A

A

um So, like I said, uh matroska we're waiting for Murray's 80 evaluation. uh The last time Michael and I talked with him.

A

um We were Mike Murray said that this was like the next document that he has to do any evaluation. For so we we are at the top of his list and uh we need the. We need the shepherd right up for the Flack uh draft, which is at the top of my list, so uh for both of these uh I don't know that we have anything to talk about on the call um are there we said we said we're uh deferring uh V4, uh ffe, ffv1, uh V4 4-bit.

D

A

Here and uh do we have any other business.

B

uh Well, I do have one question: okay,.

A

B

There are two PRS against the flux specification document still on the GitHub they're. Only small and little minor things: okay and I didn't publish a new, um a new document, because I thought, what's only only small changes and uh but well we haven't had any more changes since then, when do you want to meet to publish a new document? I, don't know whether you already started reading or whether you can look at them and well what.

C

B

A

um Okay, so Spencer's Spencer's opinion on this is: uh if these are small changes, uh I'm fine uh with you uh with you, you know with you waiting to do the submission, um just in case I, just in case I, see anything that I have questions about.

A

You know that that way, that way, you'd only have to do the submission once, uh but we will need. We will need to do an update uh when we request publication. You know the next step. Basically, so after after you see my uh Shepherd report and if there's anything, we need to talk about there and we resolve anything. We need to talk about uh at that point. It would be good to do her vision. Okay,.

B

Yes, I was just wondering whether it would be uh is a workable situation for you when there are these two changes that aren't in the documents- and there are only really minor, gotcha yeah, so.

B

Okay, that was all.

A

Cool, so uh is there anything else we need to talk about.

D

um About matroska I feel an issue about the time code. Part Steve. Can you check it a bit more uh a bit when you have some time, but there is one pull request, but it is an addition. So it is a bit different and there is the the Issue Number 682 I would like, but Steve can review if Steve can review it. It would be a great because uh it is not clear about the example uh provided in the mattress aspect.

D

Yeah six eight two.

D

uh I put it in the chart, so there's maybe a small focus on that. uh It is a bit per bit, I think to focus on so not something we could do now, I think, but just yeah Steve. If you can check it.

C

Yeah, okay, I will.

A

And and so the question is, does this need to happen before the response back is published.

D

It would be great because the example seems weird to me so um I would like to have uh to be sure about the example in The. Matrix spec is fine.

A

A

So you just say that this is not blocking.

B

A

uh It would be good, it would be good to our resolve.

A

That right is that right.

A

Cool and uh Steve is that, okay for you to uh to take a look at that yeah.

C

A

A

Ready, oh excellent: is there anything else we need to talk about.

C

Remember the way that document is part of the codec document, not the microscale document, so um yeah.

D

Is that blocking for the current documentary yeah.

A

Oh, you were saying that is 682 on the codec or on the mains back.

D

A

D

Mappings so yeah, not the main spec too. Okay, so not blocking.

A

Okay and I'm- sorry I'm, sorry I'm. Sorry I'm misunderstood that. So that's on the Codex pack.

D

No, no, it is uh it is me.

D

So it is on uh on the uh addition, uh the additional mappings, so not the codec. It is another one.

A

D

I, don't know uh this one we it will be in inside the codec uh document.

D

So it is less urgent.

A

C

The link on where it's uh it's integrated in the document, that's in the codec file, okay,.

A

Okay, excellent excellent and thank you guys for walking me through that.

A

Just to make sure just make sure that uh everybody understands what we're you know, what we're talking about.

A

That, maybe just Spencer understands what we're talking about you guys know you can uh type corrections in the minutes too right, I'm.

C

Not offended you should do it so well,.

A

A

um Is there anything else we need to talk about.

C

A

Are we all good, yes cool? So, like the other good news I have for you all is I, don't think I gave Michael the migraine so uh I'm expecting to see him back in January.

C

A

But uh I hope you all have a wondrous winter holidays of whatever flavor you might celebrate, and a wonderful beginning of your New Year, we'll see. We will see you all on the mailing list.

C

B

A

C

Excellent, all right.

A

A