No, you are not releasing the IPR.
", "time": "2022-07-27T14:01:29Z"}, {"author": "Rick Taylor", "text": "Thanks Carsten - I need to go back and read the Note Well ... a good rule for all of us
", "time": "2022-07-27T14:13:18Z"}, {"author": "Corinna Schmitt", "text": "with us it was around 10 experts
", "time": "2022-07-27T14:25:35Z"}, {"author": "Corinna Schmitt", "text": "reading and reviewing our draft
", "time": "2022-07-27T14:26:35Z"}, {"author": "Nils M\u00e4urer", "text": "Second Corinna's message: during the work in the IETF around 10 experts from various backgrounds - even involved from the very start of LDACS development - reviewed and commented on the document that it depicts an accurate and correct view of LDACS.
", "time": "2022-07-27T14:28:38Z"}, {"author": "Corinna Schmitt", "text": "The cross-reference is in our document
", "time": "2022-07-27T14:32:11Z"}, {"author": "Corinna Schmitt", "text": "Cross-reference at first stage can befound in Section 1 - Motivation: The assumed use cases
\n for LDACS complements the list of use cases stated in [RAW-USE-CASES]
\n and the list of reliable and available wireless technologies
\n presented in [RAW-TECHNOS].
Sorry Section 3.1.
", "time": "2022-07-27T14:34:51Z"}, {"author": "Carsten Bormann", "text": "Comment from a lurker: I have no idea how the references to OODA are helping. We have had protocols that are reactive for half a century now.
", "time": "2022-07-27T14:39:25Z"}, {"author": "Carsten Bormann", "text": "+1
", "time": "2022-07-27T14:52:48Z"}, {"author": "Lou Berger", "text": "@carsten +1
", "time": "2022-07-27T14:54:06Z"}, {"author": "Lou Berger", "text": "but also not sure it matters
", "time": "2022-07-27T14:54:50Z"}, {"author": "Carsten Bormann", "text": "Much of my work is based on Protestant work ethics. I still wouldn't reference this in an RFC.
", "time": "2022-07-27T15:18:42Z"}, {"author": "Lou Berger", "text": "thanks for making me laugh
", "time": "2022-07-27T15:21:41Z"}, {"author": "Lou Berger", "text": "I'll followup on the list
", "time": "2022-07-27T15:23:13Z"}, {"author": "J\u00e1nos Farkas", "text": "We cant hear you Jeroma
", "time": "2022-07-27T15:25:03Z"}, {"author": "Carsten Bormann", "text": "That's why good conferencing systems start with a mandatory audio check...
", "time": "2022-07-27T15:26:44Z"}, {"author": "Lorenzo Miniero", "text": "@Carsten Bormann that's what the preflight window is supposed to do: it will show moving tiles if it can detect audio. It's all explained in the tutorials
", "time": "2022-07-27T15:28:10Z"}, {"author": "Carsten Bormann", "text": "Lorenzo: I have been using Meetecho for a while and never noticed this function. It needs to stand out much more.
", "time": "2022-07-27T15:29:04Z"}, {"author": "Lorenzo Miniero", "text": "We'll try to make it more explicit that you can say something during that preflight to check audio levels, besides just confirming video works
", "time": "2022-07-27T15:30:30Z"}, {"author": "Jan-Frederik Rieckers", "text": "Using BigBlueButton I really enjoyed the echo test, since it allows you to also check the audio quality, so if you have two mics (the good one and the laptop one) you can check that the good one is selected.
", "time": "2022-07-27T15:32:00Z"}, {"author": "Carsten Bormann", "text": "+1 Janfred
", "time": "2022-07-27T15:33:15Z"}, {"author": "Carsten Bormann", "text": "FEC is just an optimized form of RE in PAREO -- is that not there yet?
", "time": "2022-07-27T15:43:16Z"}, {"author": "Carsten Bormann", "text": "(And, yes, MJM will point to tons of documents doing FEC...)
", "time": "2022-07-27T15:43:36Z"}, {"author": "Lou Berger", "text": "is SCHC https://datatracker.ietf.org/doc/html/rfc8824
", "time": "2022-07-27T15:46:54Z"}, {"author": "Carsten Bormann", "text": "SCHC is a great thing, but not very much related to FEC. You are using this as a tunnel protocol? We have lots of those.
", "time": "2022-07-27T15:47:13Z"}, {"author": "Carsten Bormann", "text": "8724 is probably more relevant here
", "time": "2022-07-27T15:47:35Z"}, {"author": "Rick Taylor", "text": "@carsten - join the qeue
", "time": "2022-07-27T15:47:39Z"}, {"author": "Lou Berger", "text": "FEC/Network coding is mentioned as a possible DetNet protection solution in the detnet arch
", "time": "2022-07-27T15:47:47Z"}, {"author": "Carsten Bormann", "text": "I don't want to waste time on the mic
", "time": "2022-07-27T15:47:53Z"}, {"author": "Rick Taylor", "text": "Ok - can someone make sure your comment is in the minutes please
", "time": "2022-07-27T15:48:24Z"}, {"author": "Carsten Bormann", "text": "There is this massive amount of work... RFC 3940 (now RFC 5740) had FEC in 2004...
", "time": "2022-07-27T15:49:56Z"}, {"author": "Carsten Bormann", "text": ":-) MJM
", "time": "2022-07-27T15:50:24Z"}, {"author": "Carsten Bormann", "text": "(NORM = RFC 5740)
", "time": "2022-07-27T15:57:38Z"}, {"author": "Carsten Bormann", "text": "But that raises the question: are we still using the IP service model?
", "time": "2022-07-27T15:58:24Z"}, {"author": "Marie-Jose Montpetit", "text": "FEC at the network layer: beware of IP
", "time": "2022-07-27T15:58:36Z"}, {"author": "Carsten Bormann", "text": "The LDACS discussion also has a service model issue
", "time": "2022-07-27T16:01:39Z"}, {"author": "Nils M\u00e4urer", "text": "Thank you Rick for raising that again! :)
", "time": "2022-07-27T16:02:09Z"}, {"author": "Nils M\u00e4urer", "text": "Bye everyone, see you in London.
", "time": "2022-07-27T16:02:42Z"}, {"author": "Corinna Schmitt", "text": "bye
", "time": "2022-07-27T16:03:01Z"}]