[{"author": "Ari Ker\u00e4nen", "text": "<p>MCR there's noise from your mic</p>", "time": "2025-12-03T07:07:35.000Z"}, {"author": "Carsten Bormann", "text": "<p>MCR: fan noise</p>", "time": "2025-12-03T07:07:39.000Z"}, {"author": "Lorenzo Corneo", "text": "<p>MCR I muted your mic with chair's superpower</p>", "time": "2025-12-03T07:09:44.000Z"}, {"author": "Carsten Bormann", "text": "<p><a href=\"https://www.ietf.org/archive/id/draft-bormann-asdf-instance-information-07.html#name-axioms-for-instance-related\">https://www.ietf.org/archive/id/draft-bormann-asdf-instance-information-07.html#name-axioms-for-instance-related</a></p>", "time": "2025-12-03T07:15:38.000Z"}, {"author": "Michael Richardson", "text": "<p>sorry, chat wasn't on top.  The fan helps keep the air fresh...</p>", "time": "2025-12-03T07:18:23.000Z"}, {"author": "Michael Richardson", "text": "<p>okay, so I'm gonna push the manage adoption button... with a objections by 2025-12-19, or 2026-01-03?</p>", "time": "2025-12-03T07:26:57.000Z"}, {"author": "Carsten Bormann", "text": "<p>-12-19 is still in range, I think</p>", "time": "2025-12-03T07:28:04.000Z"}, {"author": "Carsten Bormann", "text": "<p>Right.  Slim this one down so we don't run into IESG blockers.  We can start the next draft now!</p>", "time": "2025-12-03T07:31:16.000Z"}, {"author": "Carsten Bormann", "text": "<p>sdfProtocolInformation +1</p>", "time": "2025-12-03T07:34:56.000Z"}, {"author": "Michael Richardson", "text": "<p>Do we need GATT clue here?<br>\nChristian A has that...</p>", "time": "2025-12-03T07:34:58.000Z"}, {"author": "Carsten Bormann", "text": "<p>We definitely should keep some synchronization between the CoRE GATT work and this</p>", "time": "2025-12-03T07:35:45.000Z"}, {"author": "Carsten Bormann", "text": "<p>NIPC is a code-heavy spec, I have some editorial comments on code in specs</p>", "time": "2025-12-03T07:38:21.000Z"}, {"author": "Carsten Bormann", "text": "<p>Yep, we'll all forgetthe new name</p>", "time": "2025-12-03T07:39:17.000Z"}, {"author": "Michael Richardson", "text": "<p>An Application Layer Interface for Non-Internet-Connected Physical<br>\nComponents (NIPC)</p>", "time": "2025-12-03T07:39:28.000Z"}, {"author": "Ari Ker\u00e4nen", "text": "<p>BTW; I have a hard stop at the top of the hour so will unfortunately miss the last 15 mins of the meeting.</p>", "time": "2025-12-03T07:40:57.000Z"}, {"author": "Carsten Bormann", "text": "<p>The meeting actually is from 8 to 9 with some overflow time possible (but not planned)</p>", "time": "2025-12-03T07:41:30.000Z"}, {"author": "Carsten Bormann", "text": "<p>(CET, sorry)</p>", "time": "2025-12-03T07:41:44.000Z"}, {"author": "Ari Ker\u00e4nen", "text": "<p>OK, thanks! So I'll miss overflow, if any :-)</p>", "time": "2025-12-03T07:42:05.000Z"}, {"author": "Michael Richardson", "text": "<p>We have a meeting set for Jan 7.   Do we add another one for Feb?    Did we decide we aren't meeting at 125?</p>", "time": "2025-12-03T07:44:09.000Z"}, {"author": "Carsten Bormann", "text": "<blockquote>\n<p>Do we add another one for Feb? \u2794  yes<br>\nDid we decide we aren't meeting at 125? \u2794 not sure decided, but given the set of people who want to go there, I would argue not to have one</p>\n</blockquote>", "time": "2025-12-03T07:45:38.000Z"}, {"author": "Michael Richardson", "text": "<p>Feb. 4 would  match the pattern. Hmm. Just after FOSDEM.  Calendar says \"book train to ski hill\"...   Any objections to that date?</p>", "time": "2025-12-03T07:49:36.000Z"}]