[07:01:25] gurtov joins the room
[07:05:49] gurtov leaves the room
[07:17:23] gurtov leaves the room
[07:41:05] gurtov joins the room
[07:41:06] gurtov leaves the room
[10:42:21] gurtov joins the room
[10:42:21] gurtov leaves the room
[12:46:22] gurtov joins the room
[12:48:41] gurtov joins the room
[12:51:55] gurtov leaves the room
[13:37:33] gurtov leaves the room
[14:44:40] stucard joins the room
[14:47:57] Bob Moskowitz joins the room
[14:54:53] kc2rxo joins the room
[14:57:43] gurtov joins the room
[14:58:00] <Bob Moskowitz> Greeting, Andrei!
[14:58:55] <stucard> I only have 2 points on -reqs & 1 extremely brief one on -arch so there should be lots of time on solutions.
[15:01:21] <stucard> Bob especially, and to a lesser extent I, have been very busy with ICAO, mostly taking DRIP concepts there, primarily for UAS but also manned aviation. Meanwhile Adam especially, and to a lesser extent I, have been very busy testing DRIP prototypes at the NY UAS Test Site (successfully showing them to the FAA).
[15:05:18] mcr joins the room
[15:05:25] <mcr> codimd link?
[15:05:38] <mcr> damn. chrome crashed again.
[15:07:39] <kc2rxo> https://codimd.ietf.org/notes-ietf-interim-2020-drip-06-drip?both
[15:15:20] <kc2rxo> Good catch thanks
[15:22:19] <mcr> It sounds like Stu needs to have some more active co-authors (and github) to help.  Suggest github pull requests.
[15:46:31] <stucard> Understood. We will try to make -arch provide that overview, leave the details of different subsystems to other drafts.
[15:49:10] <stucard> We've seen huge differences in reliable range of BT4 vs BT5. The former requires paging of long messages, so erasure coding can help.
[15:53:22] <mcr> is there a uncorrected mode where frames can be received with errors within them?
[15:53:35] <mcr> that is loss/corruption of less than a  page?
[15:53:46] <stucard> More specifically, with 1 page of23 RS check bytes, we can correct all 23 bytes of payload of 1 dropped page, and can reconstruct the header bytes from other known information.
[15:54:00] <stucard> Nope, BT doesn't let us get raw frames.
[15:54:50] <mcr> so we can correct for one lost frame, but we can't correct for a frame which arrives too corrupted for the internal FEC to fix it.
[15:55:34] <Bob Moskowitz> CRC would drop such a frame.
[15:55:37] <stucard> Correct, as the BT error control is strictly error detection, not error correction.
[16:05:41] mcr leaves the room
[16:06:38] <stucard> Whoever is shuffling papers, please mute.
[16:07:51] <stucard> Yes, the free pre-standard version of ASTM F3411 is listed in the references in -reqs.
[16:14:28] Bob Moskowitz leaves the room
[16:15:41] kc2rxo leaves the room
[16:17:24] gurtov leaves the room
[16:27:02] stucard leaves the room: I'm not here right now
[16:27:04] stucard joins the room
[17:02:23] stucard leaves the room
[17:23:43] gurtov joins the room
[17:29:13] gurtov joins the room
[17:29:18] gurtov leaves the room
[19:34:28] gurtov leaves the room
[19:41:02] gurtov joins the room
[19:56:29] gurtov leaves the room
[19:58:41] gurtov joins the room
[20:23:59] gurtov joins the room
[20:28:17] gurtov leaves the room
[21:44:10] gurtov leaves the room