[{"author": "Pete Resnick", "text": "<p>More important to check for us <em>unusual</em> suspects.</p>", "time": "2024-12-03T16:01:10Z"}, {"author": "Alexey Melnikov", "text": "<p>I can't possibly know what I don't know ;-)</p>", "time": "2024-12-03T16:01:45Z"}, {"author": "Murray Kucherawy", "text": "<p>My first ever interim.  No wise cracks, please.</p>", "time": "2024-12-03T16:06:11Z"}, {"author": "Pete Resnick", "text": "<p><a href=\"https://author-tools.ietf.org/iddiff?url2=draft-ietf-emailcore-rfc5321bis-36\">https://author-tools.ietf.org/iddiff?url2=draft-ietf-emailcore-rfc5321bis-36</a> makes life easy</p>", "time": "2024-12-03T16:07:30Z"}, {"author": "Pete Resnick", "text": "<p>The differences between our lists were due to human error AFAICT, not because there was something obscure going on. That points to leaving them alone.</p>", "time": "2024-12-03T16:11:06Z"}, {"author": "Dave Crocker", "text": "<p>an alternative is to introduce a construct like xHLO and declare it to map to both.</p>", "time": "2024-12-03T16:11:32Z"}, {"author": "Pete Resnick", "text": "<p>@Dave: I think that leads to the same problem: We might screw up where we introduce that.</p>", "time": "2024-12-03T16:12:59Z"}, {"author": "Dave Crocker", "text": "<p><span aria-label=\"sunglasses\" class=\"emoji emoji-1f60e\" role=\"img\" title=\"sunglasses\">:sunglasses:</span></p>", "time": "2024-12-03T16:13:17Z"}, {"author": "John Klensin", "text": "<p>My goal, going back to the first interaction with Donald, was that we not do anything that makes things worse -- by human error or otherwise.</p>", "time": "2024-12-03T16:13:19Z"}, {"author": "Murray Kucherawy", "text": "<p>Is it time to inject \"It's worse than you think?\"</p>", "time": "2024-12-03T16:13:34Z"}, {"author": "Murray Kucherawy", "text": "<p>Agree with \"riskier\", not worth it.</p>", "time": "2024-12-03T16:14:57Z"}, {"author": "Pete Resnick", "text": "<p>Meh. Leave it alone.</p>", "time": "2024-12-03T16:15:03Z"}, {"author": "Murray Kucherawy", "text": "<p>+1 LGTM</p>", "time": "2024-12-03T16:19:15Z"}, {"author": "Murray Kucherawy", "text": "<p>(as a participant)</p>", "time": "2024-12-03T16:19:27Z"}, {"author": "Murray Kucherawy", "text": "<p>I slightly prefer Dave's, though change \"piece of mail\" to \"message\" to be consistent with the rest of the paragraph.</p>", "time": "2024-12-03T16:21:49Z"}, {"author": "John Klensin", "text": "<p>Barry +1 but very slightly)</p>", "time": "2024-12-03T16:26:13Z"}, {"author": "Pete Resnick", "text": "<p>I vaguely remember the discussion from 1999 that introduced that sentence, but cannot find anything in the DRUMS archive about when it happened.</p>", "time": "2024-12-03T16:26:54Z"}, {"author": "Murray Kucherawy", "text": "<p>How many versions of the DRUMS draft were there?</p>", "time": "2024-12-03T16:27:40Z"}, {"author": "Murray Kucherawy", "text": "<p>Probably a pain to check all of them.</p>", "time": "2024-12-03T16:27:47Z"}, {"author": "Murray Kucherawy", "text": "<p>The datatracker might do well with a \"blame\".</p>", "time": "2024-12-03T16:27:53Z"}, {"author": "Murray Kucherawy", "text": "<p>Yep.</p>", "time": "2024-12-03T16:28:31Z"}, {"author": "John Klensin", "text": "<p>Murray: a bunch.  And my notes about specific controversies in putting what became 2821 together do not identify any arguments about it.</p>", "time": "2024-12-03T16:28:58Z"}, {"author": "Murray Kucherawy", "text": "<p>I think I prefer (2) because (1) and the original have a dangling \"if\".  What if the content does not conform to ...?  What alternatives are there?</p>", "time": "2024-12-03T16:35:01Z"}, {"author": "Pete Resnick", "text": "<p>\"complete or for\" in the last line seems like a typo.</p>", "time": "2024-12-03T16:36:22Z"}, {"author": "Pete Resnick", "text": "<p>completely or for</p>", "time": "2024-12-03T16:36:30Z"}, {"author": "Pete Resnick", "text": "<p>I think strike the \"or\"</p>", "time": "2024-12-03T16:36:41Z"}, {"author": "Murray Kucherawy", "text": "<p>I think it's right as is, or maybe add a comma after \"completely\"</p>", "time": "2024-12-03T16:37:13Z"}, {"author": "Pete Resnick", "text": "<p>\"Whatevah\", as my NY friends would say.</p>", "time": "2024-12-03T16:38:31Z"}, {"author": "Murray Kucherawy", "text": "<p>Missing commas can be very important.</p>\n<p>Pete finds inspiration in cooking his family and his dog.</p>", "time": "2024-12-03T16:39:24Z"}, {"author": "Pete Resnick", "text": "<p>\"completely or, specifically, for...\"</p>", "time": "2024-12-03T16:39:28Z"}, {"author": "Pete Resnick", "text": "<p>Yes, that works for my soft brain which misread it the first time.</p>", "time": "2024-12-03T16:40:01Z"}, {"author": "Murray Kucherawy", "text": "<p>I'd be fine with being explicit about STARTTLS and maybe AUTH, and kicking DKIM and SPF to the AS.</p>", "time": "2024-12-03T16:42:58Z"}, {"author": "Pete Resnick", "text": "<p>@Murray: +1</p>", "time": "2024-12-03T16:43:18Z"}, {"author": "Todd Herr", "text": "<p>starting to???</p>", "time": "2024-12-03T16:44:58Z"}, {"author": "Murray Kucherawy", "text": "<p>The \"Extensions ...\" sentence is incomplete.  Did I write that?  ugh.</p>", "time": "2024-12-03T16:47:33Z"}, {"author": "Murray Kucherawy", "text": "<p>There's an \"are\" missing, I think.</p>", "time": "2024-12-03T16:47:37Z"}, {"author": "John Klensin", "text": "<p>Replace bolded text with an explicit \"There is additional discussion of this in the applicability statement\" or something like that?</p>", "time": "2024-12-03T16:47:50Z"}, {"author": "John Klensin", "text": "<p>I agree with Dave.</p>", "time": "2024-12-03T16:49:20Z"}, {"author": "Murray Kucherawy", "text": "<p>That's a good point.  Then I suggest we try without, but be willing to add STARTTLS if cornered.</p>", "time": "2024-12-03T16:49:34Z"}, {"author": "Murray Kucherawy", "text": "<p>Shipping a protocol document from ART that has no transport security capability will draw ire from UTA too. :)</p>", "time": "2024-12-03T16:51:41Z"}, {"author": "Murray Kucherawy", "text": "<p>Can we get away with making allusions to \"a future applicability statement\" without making it a normative reference?</p>", "time": "2024-12-03T16:52:32Z"}, {"author": "Pete Resnick", "text": "<p>@Murray: As John said, already mentioned.</p>", "time": "2024-12-03T16:52:47Z"}, {"author": "Barry Leiba", "text": "<p>I think it doesn't need to be normative.</p>", "time": "2024-12-03T16:52:48Z"}, {"author": "Murray Kucherawy", "text": "<p>Works for me.</p>", "time": "2024-12-03T16:52:57Z"}, {"author": "Barry Leiba", "text": "<p>Happy to go in the direction JCK just said.</p>", "time": "2024-12-03T16:53:13Z"}, {"author": "Murray Kucherawy", "text": "<p>+1</p>", "time": "2024-12-03T16:53:48Z"}, {"author": "Murray Kucherawy", "text": "<p>Who did John say is pushing DKIM?  Karl?</p>", "time": "2024-12-03T16:54:01Z"}, {"author": "Barry Leiba", "text": "<p>Nooooooooooo</p>", "time": "2024-12-03T16:54:05Z"}, {"author": "Kenneth Murchison", "text": "<p>our charter says the following about the A/S: \"5321bis and 5322bis will be submitted for<br>\npublication before this document is finalized\"</p>", "time": "2024-12-03T16:57:20Z"}, {"author": "Murray Kucherawy", "text": "<p>I'm fine with defending our preferred text to the IESG.</p>\n<p>I also suggest we should think about a backup plan we can live with in case that doesn't work.</p>", "time": "2024-12-03T16:58:52Z"}, {"author": "Todd Herr", "text": "<p>@pete - Did you say \"MUST use STARTTLS is a a hill we want to die on\"?</p>", "time": "2024-12-03T16:59:02Z"}, {"author": "Pete Resnick", "text": "<p>@Todd: Yes, we do <em>not</em> want to add that to the document.</p>", "time": "2024-12-03T16:59:35Z"}, {"author": "Murray Kucherawy", "text": "<p>I think this is another case where we can talk about end-to-end security being a common concern for which solutions exist, go do your homework.</p>", "time": "2024-12-03T17:00:57Z"}, {"author": "Murray Kucherawy", "text": "<p>+1 to \"punt to AS\"</p>", "time": "2024-12-03T17:02:29Z"}, {"author": "Murray Kucherawy", "text": "<p>+1 to this plan</p>", "time": "2024-12-03T17:06:16Z"}, {"author": "Pete Resnick", "text": "<p>+1 to John's suggestion for 5321bis and interim only for the a/s.</p>", "time": "2024-12-03T17:06:36Z"}, {"author": "Murray Kucherawy", "text": "<p>Could we even do the AS-focused interim later in December?</p>", "time": "2024-12-03T17:06:43Z"}, {"author": "Pete Resnick", "text": "<p>We may need the interim to deal with IESG pushback on 5321bis.</p>", "time": "2024-12-03T17:09:09Z"}, {"author": "Barry Leiba", "text": "<p>Getting a January interim on our calendars now... might be best.</p>", "time": "2024-12-03T17:11:28Z"}, {"author": "Pete Resnick", "text": "<p>@Alexey: Fair. An a/s interim sounds good.</p>", "time": "2024-12-03T17:11:45Z"}, {"author": "Pete Resnick", "text": "<p>+1 for cluster</p>", "time": "2024-12-03T17:12:02Z"}, {"author": "Murray Kucherawy", "text": "<p>Two interims might be necessary (one AS, one bis).</p>", "time": "2024-12-03T17:12:14Z"}, {"author": "Murray Kucherawy", "text": "<p>Both in January is fine.</p>", "time": "2024-12-03T17:12:22Z"}, {"author": "Pete Resnick", "text": "<p>ack</p>", "time": "2024-12-03T17:12:23Z"}, {"author": "Murray Kucherawy", "text": "<p>I would love to get all three of these done (in the RFC Editor queue) before I step down, but that's certainly not a hard requirement.</p>", "time": "2024-12-03T17:12:45Z"}, {"author": "Pete Resnick", "text": "<p>I love happy thoughts!</p>", "time": "2024-12-03T17:15:32Z"}, {"author": "Murray Kucherawy", "text": "<p>I'll have what he's having.</p>", "time": "2024-12-03T17:15:39Z"}, {"author": "Pete Resnick", "text": "<p>@Murray: Now <em>that's</em> a good reference!</p>", "time": "2024-12-03T17:16:03Z"}, {"author": "Kenneth Murchison", "text": "<p>Bye all.  Enjoy your holidays!</p>", "time": "2024-12-03T17:18:25Z"}]