[{"author": "Carsten Bormann", "text": "

Monitor speakers would be like it

", "time": "2024-03-19T23:30:10Z"}, {"author": "Martine Lenders", "text": "

I also always have trouble hearing remote speakers when I am a speaker in the room.

", "time": "2024-03-19T23:30:22Z"}, {"author": "Francesca Palombini", "text": "

awwwww

", "time": "2024-03-19T23:30:33Z"}, {"author": "Christian Ams\u00fcss", "text": "

Oh, awesome, congratulations!

", "time": "2024-03-19T23:30:41Z"}, {"author": "Martine Lenders", "text": "

Best wishes and congratulation, Jaime!

", "time": "2024-03-19T23:30:55Z"}, {"author": "Jaime Jimenez", "text": "

Thank you all!

", "time": "2024-03-19T23:31:48Z"}, {"author": "Christian Ams\u00fcss", "text": "

Thanks all for pushing SID through

", "time": "2024-03-19T23:34:56Z"}, {"author": "Christian Ams\u00fcss", "text": "

Francesca, note takers disagree about which document you mentioned, please clarify (groupcomm-bis v oscore-groupcomm)

", "time": "2024-03-19T23:37:33Z"}, {"author": "Carsten Bormann", "text": "

groupcomm-bis

", "time": "2024-03-19T23:37:48Z"}, {"author": "Christian Ams\u00fcss", "text": "

OK, then my \"will do\" was wrong.

", "time": "2024-03-19T23:38:14Z"}, {"author": "Carsten Bormann", "text": "

My \"will do\"

", "time": "2024-03-19T23:38:23Z"}, {"author": "Francesca Palombini", "text": "

groupcomm bis should be prioritized, oscore-groupcomm + ace docs depend on it

", "time": "2024-03-19T23:38:37Z"}, {"author": "Francesca Palombini", "text": "

and note that ace docs are progressing faster (one has passed IESG processing, the other is pre ietf LC)

", "time": "2024-03-19T23:39:12Z"}, {"author": "Christian Ams\u00fcss", "text": "

@meetecho, please pivot to speaker

", "time": "2024-03-19T23:41:52Z"}, {"author": "Christian Ams\u00fcss", "text": "

thx

", "time": "2024-03-19T23:41:58Z"}, {"author": "Christian Ams\u00fcss", "text": "

Brief side note: The uint encoding also makes the PRoxy-Scheme option very short (0 data).

", "time": "2024-03-19T23:54:42Z"}, {"author": "Carsten Bormann", "text": "

Maybe sort the implementations by client vs. server

", "time": "2024-03-19T23:57:32Z"}, {"author": "Francesca Palombini", "text": "

https://datatracker.ietf.org/dir/

", "time": "2024-03-20T00:06:45Z"}, {"author": "Marco Tiloca", "text": "

@Francesca, you mentioned both IOTDIR and DNSDIR, right?

", "time": "2024-03-20T00:08:24Z"}, {"author": "Martine Lenders", "text": "

BTW, there was already an early review from DNSDIR.

", "time": "2024-03-20T00:09:37Z"}, {"author": "Carsten Bormann", "text": "

Martine: Is it worth to ask for an update of that?

", "time": "2024-03-20T00:10:08Z"}, {"author": "Martine Lenders", "text": "

Sure!

", "time": "2024-03-20T00:10:37Z"}, {"author": "Francesca Palombini", "text": "

@Marco: I only mentioned dnsdir, but if you think iotdir would be useful do request it! we should be using early reviews :)

", "time": "2024-03-20T00:20:07Z"}, {"author": "Francesca Palombini", "text": "

to directorates

", "time": "2024-03-20T00:20:22Z"}, {"author": "Marco Tiloca", "text": "

Right, thanks!

", "time": "2024-03-20T00:21:02Z"}, {"author": "Christian Ams\u00fcss", "text": "

Reply-To sounds weird, assuming that \"reply\" and \"response\" are synonymous (Reply-From?)

", "time": "2024-03-20T00:24:29Z"}, {"author": "Carsten Bormann", "text": "

Yep

", "time": "2024-03-20T00:24:35Z"}, {"author": "Marco Tiloca", "text": "

Yes, \"Reply-From\" is nice and also avoids possible confusion with \"Response-For\" in https://datatracker.ietf.org/doc/html/draft-bormann-core-responses-02#section-4

", "time": "2024-03-20T00:28:47Z"}, {"author": "Carsten Bormann", "text": "

You may want to use sf for HTTP (also base64url, but with some decoration)

", "time": "2024-03-20T00:31:36Z"}, {"author": "Carsten Bormann", "text": "

(sf: https://datatracker.ietf.org/doc/draft-ietf-httpbis-sfbis/ )

", "time": "2024-03-20T00:36:17Z"}, {"author": "Marco Tiloca", "text": "

Thanks

", "time": "2024-03-20T00:36:54Z"}, {"author": "Christian Ams\u00fcss", "text": "

That sounds like good general guidance for HTTP encoding of CoAP options unless there is an obvious better way in an existing HTTP header

", "time": "2024-03-20T00:37:11Z"}, {"author": "Carsten Bormann", "text": "

Indeed

", "time": "2024-03-20T00:37:33Z"}, {"author": "Marco Tiloca", "text": "

The papers that G\u00f6ran mentioned:

\n", "time": "2024-03-20T00:59:11Z"}, {"author": "G\u00f6ran Selander", "text": "

I referred to the second.

", "time": "2024-03-20T00:59:42Z"}, {"author": "G\u00f6ran Selander", "text": "

+1 Marco

", "time": "2024-03-20T01:06:39Z"}, {"author": "Christian Ams\u00fcss", "text": "

/me is looking forward to seeing CoAP-over-BP :-)

", "time": "2024-03-20T01:14:45Z"}, {"author": "Christian Ams\u00fcss", "text": "

@meetecho: please pivot to upcoming speaker

", "time": "2024-03-20T01:15:05Z"}, {"author": "Christian Ams\u00fcss", "text": "

thanks

", "time": "2024-03-20T01:15:16Z"}, {"author": "Christian Ams\u00fcss", "text": "

See also mail thread.

", "time": "2024-03-20T01:25:07Z"}, {"author": "Christian Ams\u00fcss", "text": "

(started coap+bp topic there too)

", "time": "2024-03-20T01:25:20Z"}, {"author": "Carsten Bormann", "text": "

Thanks

", "time": "2024-03-20T01:26:12Z"}, {"author": "Christian Ams\u00fcss", "text": "

Please expand NTN acronym.

", "time": "2024-03-20T01:28:15Z"}, {"author": "G\u00f6ran Selander", "text": "

Non-Terrestrial Network

", "time": "2024-03-20T01:28:33Z"}, {"author": "Christian Ams\u00fcss", "text": "

Thanks, that's interesting work!

", "time": "2024-03-20T01:32:18Z"}, {"author": "Carsten Bormann", "text": "

+1

", "time": "2024-03-20T01:32:27Z"}, {"author": "Martine Lenders", "text": "

Thank you everyone! Have a nice day.

", "time": "2024-03-20T01:32:34Z"}, {"author": "Rikard H\u00f6glund", "text": "

Thank you!

", "time": "2024-03-20T01:32:38Z"}, {"author": "Jaime Jimenez", "text": "

Non-Terrestrial Networks an NB-IoT flavour done by sat and telco vendors.

", "time": "2024-03-20T01:32:58Z"}]