[{"author": "Alexey Melnikov", "text": "My apologies, I am a few minutes late as well<br/>", "time": "2022-03-25T11:30:40Z"}, {"author": "Francesca Palombini", "text": "hello! I'm here too (outside of camera view)<br/>", "time": "2022-03-25T11:31:58Z"}, {"author": "Todd Herr", "text": "I can do the note taking<br/>", "time": "2022-03-25T11:33:12Z"}, {"author": "Bron Gondwana", "text": "my network is too unreliable to volunteer sorry<br/>", "time": "2022-03-25T11:33:16Z"}, {"author": "Todd Herr", "text": "Also could you please move the microphone closer to yourself?<br/>", "time": "2022-03-25T11:33:30Z"}, {"author": "Bron Gondwana", "text": "much clearer<br/>", "time": "2022-03-25T11:33:49Z"}, {"author": "Murray Kucherawy", "text": "My technical issue is that it's 4:30am.<br/>", "time": "2022-03-25T11:35:29Z"}, {"author": "Murray Kucherawy", "text": ":)<br/>", "time": "2022-03-25T11:35:47Z"}, {"author": "John Levine", "text": "want to try the small point I brought up?<br/>", "time": "2022-03-25T11:38:37Z"}, {"author": "John Levine", "text": "points<br/>", "time": "2022-03-25T11:38:41Z"}, {"author": "Alexey Melnikov", "text": "Which ones?<br/>", "time": "2022-03-25T11:38:49Z"}, {"author": "John Levine", "text": "vrfy, and so forth<br/>", "time": "2022-03-25T11:39:12Z"}, {"author": "Alexey Melnikov", "text": "We will start with ENHANCEDSTATUSCODES, then we will see<br/>", "time": "2022-03-25T11:39:38Z"}, {"author": "John Levine", "text": "looks reasonable<br/>", "time": "2022-03-25T11:41:52Z"}, {"author": "Murray Kucherawy", "text": "+1<br/>", "time": "2022-03-25T11:42:12Z"}, {"author": "Dave Crocker", "text": "Using registration as a quality control mechanism makes sense when the registration namespace is limited, or the operational dangers of registering 'poor' entries is dangerous.&nbsp;&nbsp;Neither seem to apply here.<br/>", "time": "2022-03-25T11:48:56Z"}, {"author": "Dave Crocker", "text": "Spec Required ensure a single reference, but does not get into the game of quality control on the work.<br/>", "time": "2022-03-25T11:50:59Z"}, {"author": "Pete Resnick", "text": "I think the concern is that Spec Required requires an expert to approve.<br/>", "time": "2022-03-25T11:54:01Z"}, {"author": "Dave Crocker", "text": "//sorry. I mis-remembered spec required. Given the choices, FCFS should apply.&nbsp;&nbsp;Yes, that can produce useless registration.&nbsp;&nbsp;That is too bad for what is being registered, but doesn't hurt general SMTP use.<br/>", "time": "2022-03-25T11:54:15Z"}, {"author": "Murray Kucherawy", "text": "Pete: Why's that bad?<br/>", "time": "2022-03-25T11:54:33Z"}, {"author": "Todd Herr", "text": "@Pete - True, but Barry just volunteered to be that expert<br/>", "time": "2022-03-25T11:54:37Z"}, {"author": "John Levine", "text": "I'll be co-expert if people want<br/>", "time": "2022-03-25T11:54:58Z"}, {"author": "Dave Crocker", "text": "@murray, it's bad because it imposes a significantly higher barrier in effort and time.<br/>", "time": "2022-03-25T11:55:07Z"}, {"author": "Pete Resnick", "text": "I tend to agree with Dave on this. Expert review takes time and some justification<br/>", "time": "2022-03-25T11:55:42Z"}, {"author": "Dave Crocker", "text": "I don't understand what 'mess' John is concerned about.<br/>", "time": "2022-03-25T11:58:12Z"}, {"author": "Dave Crocker", "text": "Someone registers a name that is, for whatever reason, ultimately useless.&nbsp;&nbsp;So what?<br/>", "time": "2022-03-25T11:59:35Z"}, {"author": "Murray Kucherawy", "text": "I agree with the point about media types.&nbsp;&nbsp;We'd rather have some crazy idea registered with documentation than not registered.<br/>", "time": "2022-03-25T12:01:14Z"}, {"author": "Pete Resnick", "text": "People can be dopes if they want to. We only want to make sure they have the opportunity not to be dopes.<br/>", "time": "2022-03-25T12:01:27Z"}, {"author": "Pete Resnick", "text": "04:30. Ugh.<br/>", "time": "2022-03-25T12:03:16Z"}, {"author": "Murray Kucherawy", "text": "How is he a half hour behind me?<br/>", "time": "2022-03-25T12:03:42Z"}, {"author": "Todd Herr", "text": "California is a big state<br/>", "time": "2022-03-25T12:03:55Z"}, {"author": "Pete Resnick", "text": "heh<br/>", "time": "2022-03-25T12:03:59Z"}, {"author": "John C Klensin", "text": "Then one provides provisional registration that gets the name into the registry and allows the registrant 60 days to listen to discussion and amend things before the registration semi-automatically becomes permanent<br/>", "time": "2022-03-25T12:05:34Z"}, {"author": "Dave Crocker", "text": "@murray, my body isn't a half-hour behind.&nbsp;&nbsp;My brain is.&nbsp;&nbsp;You referenced 4:30, so I did too.&nbsp;&nbsp;I'll probably still say 4:30 later this morning.<br/>", "time": "2022-03-25T12:06:42Z"}, {"author": "Murray Kucherawy", "text": "I sympathize.&nbsp;&nbsp;I just had to get three different ADs to explain to me the concept of network ossification.<br/>", "time": "2022-03-25T12:07:53Z"}, {"author": "Bron Gondwana", "text": "we can always fix this later right?&nbsp;&nbsp;If the registry gets filled with shit, we can do an IETF consensus document to change the registry and clean out the nonsense<br/>", "time": "2022-03-25T12:10:59Z"}, {"author": "Dave Crocker", "text": "@bron: +1<br/>", "time": "2022-03-25T12:11:23Z"}, {"author": "Bron Gondwana", "text": "and if it doesn't, we've avoided red tape and extra work for IANA<br/>", "time": "2022-03-25T12:11:27Z"}, {"author": "John C Klensin", "text": "I'm having trouble hearing barry<br/>", "time": "2022-03-25T12:11:59Z"}, {"author": "Bron Gondwana", "text": "asking IANA to post to the list makes sense to me<br/>", "time": "2022-03-25T12:12:22Z"}, {"author": "Pete Resnick", "text": "My apologies for being overly loud to interrupt Barry. Unintentional, but no good nonetheless.<br/>", "time": "2022-03-25T12:12:50Z"}, {"author": "Bron Gondwana", "text": "IANA are competent and reliable<br/>", "time": "2022-03-25T12:13:04Z"}, {"author": "Dave Crocker", "text": "The nature of FCFS is well-understood.&nbsp;&nbsp;Although perhaps a 'bigger' change, it fixes the problem.&nbsp;&nbsp;Anything else doesn't.<br/>", "time": "2022-03-25T12:13:55Z"}, {"author": "Pete Resnick", "text": "Specification Required is less change than FCFS, which would lean in favor of that. But I still favor FCFS.<br/>", "time": "2022-03-25T12:15:29Z"}, {"author": "Bron Gondwana", "text": "I can't reliably talk, but I'm right here with Dave.&nbsp;&nbsp;Let's just FCFS<br/>", "time": "2022-03-25T12:15:39Z"}, {"author": "John C Klensin", "text": "@Bron: if our goal is to be sure that a given keyword is not used in different ways by different actors (except maliciously),&nbsp;&nbsp;thjere is no cleaning.<br/>", "time": "2022-03-25T12:16:21Z"}, {"author": "John C Klensin", "text": "@meetecho: volume coming from room seems to be very low compared to remote participants.&nbsp;&nbsp;I can hear, but just barely<br/>", "time": "2022-03-25T12:17:18Z"}, {"author": "Meetecho", "text": "We're monitoring but they seem comparable to us, maybe it's some specific speakers?<br/>", "time": "2022-03-25T12:17:42Z"}, {"author": "Pete Resnick", "text": "I'm so proud of my mentee for feeling he can go to the mic. :slightly_smiling_face:<br/>", "time": "2022-03-25T12:17:47Z"}, {"author": "Dave Crocker", "text": "@meetecho, the issue is the room mic.&nbsp;&nbsp;The leader table mic seems loud enough.<br/>", "time": "2022-03-25T12:17:57Z"}, {"author": "Meetecho", "text": "That said, we're trying not to boost local mics too much as they may generate feedback when remotes speak<br/>", "time": "2022-03-25T12:18:00Z"}, {"author": "Meetecho", "text": "Mh maybe it's running out of juice?<br/>", "time": "2022-03-25T12:18:18Z"}, {"author": "Dave Crocker", "text": "@meetech, well, yeah, there's that.<br/>", "time": "2022-03-25T12:18:25Z"}, {"author": "Joris Baum", "text": "@meetecho: everything seems fine to me<br/>", "time": "2022-03-25T12:18:43Z"}, {"author": "Murray Kucherawy", "text": "I am so tempted to register the BADIDEA extension now.<br/>", "time": "2022-03-25T12:18:44Z"}, {"author": "Meetecho", "text": "Heading there to check<br/>", "time": "2022-03-25T12:18:56Z"}, {"author": "Francesca Palombini", "text": "or just switch the queue mic with the presenter mic?<br/>", "time": "2022-03-25T12:19:39Z"}, {"author": "Dave Crocker", "text": "@murray, please do.&nbsp;&nbsp;A reliable way to reduce excessive fear is 'mere exposure' (which is actually a formal psych term.)<br/>", "time": "2022-03-25T12:19:58Z"}, {"author": "Meetecho", "text": "We're going to the room to see if we can boost just the queue line mic for remotes a bit<br/>", "time": "2022-03-25T12:20:10Z"}, {"author": "Murray Kucherawy", "text": "@Dave: You won't like what the extension does. ;)<br/>", "time": "2022-03-25T12:21:23Z"}, {"author": "Meetecho", "text": "Barry sounded fine to us<br/>", "time": "2022-03-25T12:21:48Z"}, {"author": "John C Klensin", "text": "Alexey +1<br/>", "time": "2022-03-25T12:21:52Z"}, {"author": "Dave Crocker", "text": "@murray, it will be a trivial addition to the list of what I don't like.<br/>", "time": "2022-03-25T12:22:01Z"}, {"author": "Dave Crocker", "text": "@murray, and yes, I'm fine with your treating that as a challenge.<br/>", "time": "2022-03-25T12:22:21Z"}, {"author": "Murray Kucherawy", "text": "451 Your first reply can't be trusted; please try again.<br/>", "time": "2022-03-25T12:22:49Z"}, {"author": "Bron Gondwana", "text": "sorry I lost network for a while<br/>", "time": "2022-03-25T12:22:53Z"}, {"author": "Murray Kucherawy", "text": "Anyone remember why VRFY was mandatory originally?<br/>", "time": "2022-03-25T12:23:22Z"}, {"author": "Pete Resnick", "text": "Easiest to move discussion to A/S. I'm OK with minimal change.<br/>", "time": "2022-03-25T12:23:59Z"}, {"author": "John C Klensin", "text": "Murray: yes, I remember.&nbsp;&nbsp;Don't want to take time today<br/>", "time": "2022-03-25T12:24:30Z"}, {"author": "Murray Kucherawy", "text": "John: Don't need the whole history, but is that logic still valid?<br/>", "time": "2022-03-25T12:24:57Z"}, {"author": "Dave Crocker", "text": "Do we know of current operational problems involving VRFY?&nbsp;&nbsp;If not, then the concern is for 'improvement' rather than 'repair' to the spec.<br/>", "time": "2022-03-25T12:25:26Z"}, {"author": "Bron Gondwana", "text": "Dave: argument for removal of something not used is \"less work for implementing\"<br/>", "time": "2022-03-25T12:27:06Z"}, {"author": "Dave Crocker", "text": "@todd: +1<br/>", "time": "2022-03-25T12:27:41Z"}, {"author": "Pete Resnick", "text": "I prefer no change in the doc and move any new discussion needed to A/S.<br/>", "time": "2022-03-25T12:27:51Z"}, {"author": "Dave Crocker", "text": "@bron, yes, but... that's a reasonable 'improvement' line of argument, but risks unintended consequences.&nbsp;&nbsp;The nature of the current effort is supposed to be more constrained than that.<br/>", "time": "2022-03-25T12:29:15Z"}, {"author": "Dave Crocker", "text": "Does this 3.3 text cause known problems?<br/>", "time": "2022-03-25T12:30:39Z"}, {"author": "Dave Crocker", "text": "That said, what does it mean for software to 'assume' anything?<br/>", "time": "2022-03-25T12:31:09Z"}, {"author": "John C Klensin", "text": "I don't know any such problems<br/>", "time": "2022-03-25T12:34:03Z"}, {"author": "John C Klensin", "text": "I think we have consensus that this is a lousy piece of text<br/>", "time": "2022-03-25T12:34:41Z"}, {"author": "Pete Resnick", "text": "heh<br/>", "time": "2022-03-25T12:34:48Z"}, {"author": "Pete Resnick", "text": "Yeah, it's not clear that the sentences in this paragraph have much to do with eachother.<br/>", "time": "2022-03-25T12:35:27Z"}, {"author": "John Levine", "text": "ok with dropping it<br/>", "time": "2022-03-25T12:35:33Z"}, {"author": "Kenneth Murchison", "text": "+1 to dropping it<br/>", "time": "2022-03-25T12:35:36Z"}, {"author": "Pete Resnick", "text": "@John: If we can't figure out what it was meant to do, do you prefer drop or just leave it?<br/>", "time": "2022-03-25T12:36:33Z"}, {"author": "Dave Crocker", "text": "Clarification invites new problems.&nbsp;&nbsp;Dropping /might/ invite problems, but we don't know what problem the text is fixing AND we don't like the current text.<br/>", "time": "2022-03-25T12:36:38Z"}, {"author": "Dave Crocker", "text": "+1 to dropping.<br/>", "time": "2022-03-25T12:36:50Z"}, {"author": "Murray Kucherawy", "text": "You know, I'd like to capture the discussion about registry rules someplace and apply it if we update 6838.&nbsp;&nbsp;How many other WGs have had that same discussion?<br/>", "time": "2022-03-25T12:37:13Z"}, {"author": "Murray Kucherawy", "text": "wait that's media types, make that 8126<br/>", "time": "2022-03-25T12:37:24Z"}, {"author": "Bron Gondwana", "text": "Murray: +1, I'm sure many WGs have had this disucssion<br/>", "time": "2022-03-25T12:38:17Z"}, {"author": "John Levine", "text": "ok<br/>", "time": "2022-03-25T12:38:40Z"}, {"author": "John Levine", "text": "rhymes with green, not with whine<br/>", "time": "2022-03-25T12:38:57Z"}, {"author": "John Levine", "text": "The paragraph suggests it's about source routes<br/>", "time": "2022-03-25T12:39:52Z"}, {"author": "John C Klensin", "text": "@John lhanks.<br/>", "time": "2022-03-25T12:41:17Z"}, {"author": "Pete Resnick", "text": "So \"leave it alone\" lands on 550?<br/>", "time": "2022-03-25T12:43:39Z"}, {"author": "John Levine", "text": "yes<br/>", "time": "2022-03-25T12:43:44Z"}, {"author": "Pete Resnick", "text": "Cool.<br/>", "time": "2022-03-25T12:43:52Z"}, {"author": "Pete Resnick", "text": "Sounds like no change it is.<br/>", "time": "2022-03-25T12:44:06Z"}, {"author": "Murray Kucherawy", "text": "Can a \"FOR\" clause include multiple addresses?<br/>", "time": "2022-03-25T12:47:13Z"}, {"author": "Pete Resnick", "text": "I think text for A/S is more likely than really needing a change in base.<br/>", "time": "2022-03-25T12:47:47Z"}, {"author": "Pete Resnick", "text": "Happy to help either way.<br/>", "time": "2022-03-25T12:47:52Z"}, {"author": "Kenneth Murchison", "text": "Pete is you have suggested text for A/S that would be great<br/>", "time": "2022-03-25T12:48:28Z"}, {"author": "John Levine", "text": "@murray allows only one address<br/>", "time": "2022-03-25T12:48:31Z"}, {"author": "Pete Resnick", "text": "Yeah, this part people have actually had trouble with. We need to clarify.<br/>", "time": "2022-03-25T12:50:56Z"}, {"author": "Dave Crocker", "text": "1. SMTP does not get to dictate what list exploder do, since their activity is quite long after message delivery.<br/>", "time": "2022-03-25T12:51:54Z"}, {"author": "Dave Crocker", "text": "2. Do we have documentation of a significant operation problem that making a change here will fix?<br/>", "time": "2022-03-25T12:52:16Z"}, {"author": "Pete Resnick", "text": "+1 to Barry.<br/>", "time": "2022-03-25T12:54:00Z"}, {"author": "John C Klensin", "text": "The problem is not exploders in the post-delivery context that Dave is talking about.&nbsp;&nbsp; It is far more important for alias-type changes.<br/>", "time": "2022-03-25T12:55:01Z"}, {"author": "Pete Resnick", "text": "@Dave: But that *would* be a significant change to text that people do use.<br/>", "time": "2022-03-25T12:55:57Z"}, {"author": "John C Klensin", "text": "@Pete +1<br/>", "time": "2022-03-25T12:56:14Z"}, {"author": "Pete Resnick", "text": "If we're going to discuss aliases/lists at all (and that is a separate discussion), I'm inclined to clarify the text.<br/>", "time": "2022-03-25T12:56:31Z"}, {"author": "Dave Crocker", "text": "@pete, any change is... change.&nbsp;&nbsp;Dropping bad text is arguably less change than replacing it with new (and therefore untested) text that might create new problems, especially here where it is far beyond SMTP's scope.<br/>", "time": "2022-03-25T12:57:02Z"}, {"author": "Pete Resnick", "text": "(The result of the other ticket might be to rip this and other text out, but as I said, that's separate.)<br/>", "time": "2022-03-25T12:57:30Z"}, {"author": "Pete Resnick", "text": "Dropping bad text is sometimes better, sometimes not. *That* is something that we have to make a judgement on.<br/>", "time": "2022-03-25T12:58:26Z"}, {"author": "John C Klensin", "text": "But, Dave, the assertion that it is beyond SMTP's scope when it has been considered within scope for 30 years, is, itself, a rather significant change.<br/>", "time": "2022-03-25T12:58:36Z"}, {"author": "Pete Resnick", "text": "(Sorry, I leave myself standing in line too often.)<br/>", "time": "2022-03-25T12:59:11Z"}, {"author": "John C Klensin", "text": "Agree with Pete that further discussion may lead to talking it out, but I don't think an out of scope argument is helpful here.<br/>", "time": "2022-03-25T12:59:54Z"}, {"author": "Joris Baum", "text": ":grinning_face_with_star_eyes:<br/>", "time": "2022-03-25T13:00:06Z"}, {"author": "Pete Resnick", "text": "Pete groans loudly.<br/>", "time": "2022-03-25T13:00:47Z"}, {"author": "Murray Kucherawy", "text": "You could add a sentence near the top that indicates this document uses \"sender-SMTP\" and \"SMTP client\" interchangeably, and change nothing else.<br/>", "time": "2022-03-25T13:02:28Z"}, {"author": "Barry Leiba", "text": "The Crocker Principle!<br/>", "time": "2022-03-25T13:02:44Z"}, {"author": "John C Klensin", "text": "+1 to Pete and, yes, I would personally favor that sentence.<br/>", "time": "2022-03-25T13:02:57Z"}, {"author": "John C Klensin", "text": "but I'm obviously willing to go a bit further in the direction of clarification than some others.<br/>", "time": "2022-03-25T13:03:27Z"}, {"author": "Murray Kucherawy", "text": "How did this get less discussion than FCFS?<br/>", "time": "2022-03-25T13:03:36Z"}, {"author": "Barry Leiba", "text": "FCFS = For C*s*ing F*'s Sake, no?<br/>", "time": "2022-03-25T13:04:18Z"}, {"author": "Alexey Melnikov", "text": "Murray: we are tired :-)<br/>", "time": "2022-03-25T13:04:37Z"}, {"author": "Alexey Melnikov", "text": "Which sometimes helps<br/>", "time": "2022-03-25T13:04:43Z"}, {"author": "Dave Crocker", "text": "Since 'server' seems to have become a socially insensitive term, sender/receiver is the socially safer choice.<br/>", "time": "2022-03-25T13:05:52Z"}, {"author": "Pete Resnick", "text": "@Dave: I like that as a good argument for the A/S to commit to sender/receiver.<br/>", "time": "2022-03-25T13:06:20Z"}, {"author": "Pete Resnick", "text": "I have no objection to a simple clarification like Murray's suggestion.<br/>", "time": "2022-03-25T13:07:33Z"}, {"author": "Murray Kucherawy", "text": "Is it still 4:30, Dave?<br/>", "time": "2022-03-25T13:07:53Z"}, {"author": "John Levine", "text": "It's always 4:30 somewhere<br/>", "time": "2022-03-25T13:08:06Z"}, {"author": "Dave Crocker", "text": "@murray, after two triple espressos, I think it is at least 4:45.<br/>", "time": "2022-03-25T13:09:47Z"}, {"author": "Murray Kucherawy", "text": "How's the view from the ceiling?<br/>", "time": "2022-03-25T13:10:05Z"}, {"author": "Pete Resnick", "text": "Does time speed up or slow down with triple espressos?<br/>", "time": "2022-03-25T13:10:09Z"}, {"author": "Murray Kucherawy", "text": "I think it causes Doppler shifts.<br/>", "time": "2022-03-25T13:10:19Z"}, {"author": "Dave Crocker", "text": "@murray, you are assuming a degree of effect that is not assured -- and did not happen -- at 4:30, nor at 4:45.<br/>", "time": "2022-03-25T13:11:14Z"}, {"author": "John C Klensin", "text": "@Alexey:&nbsp;&nbsp;ROFL<br/>", "time": "2022-03-25T13:12:07Z"}, {"author": "Pete Resnick", "text": "(Murray, who hasn't turned on his video, must still be in his PJs.)<br/>", "time": "2022-03-25T13:12:28Z"}, {"author": "Barry Leiba", "text": "You assume he wars them...<br/>", "time": "2022-03-25T13:12:43Z"}, {"author": "Murray Kucherawy", "text": "Yeah, you don't get my camera on when I've been in meetings since 2am.<br/>", "time": "2022-03-25T13:12:45Z"}, {"author": "Barry Leiba", "text": "wears<br/>", "time": "2022-03-25T13:12:47Z"}, {"author": "Pete Resnick", "text": "It's Hans-J\u00f6rg at the mic.<br/>", "time": "2022-03-25T13:12:51Z"}, {"author": "Benson Muite", "text": "Thanks for the educational discussion.<br/>", "time": "2022-03-25T13:12:59Z"}, {"author": "Murray Kucherawy", "text": "It's a local... right.<br/>", "time": "2022-03-25T13:13:49Z"}, {"author": "Dave Crocker", "text": "SMTP is not supposed to interpret the left-hand side.<br/>", "time": "2022-03-25T13:13:57Z"}, {"author": "Todd Herr", "text": "\"sub addressing\"?<br/>", "time": "2022-03-25T13:13:58Z"}, {"author": "Murray Kucherawy", "text": "On the other hand it might be helpful to document someplace.<br/>", "time": "2022-03-25T13:14:00Z"}, {"author": "John Levine", "text": "todd+ietf@example.com<br/>", "time": "2022-03-25T13:14:10Z"}, {"author": "Todd Herr", "text": "thanks<br/>", "time": "2022-03-25T13:14:15Z"}, {"author": "Murray Kucherawy", "text": "Thanks all.<br/>", "time": "2022-03-25T13:14:24Z"}, {"author": "Joris Baum", "text": "thanks!<br/>", "time": "2022-03-25T13:14:35Z"}, {"author": "John C Klensin", "text": "Barry +1<br/>", "time": "2022-03-25T13:14:47Z"}, {"author": "Pete Resnick", "text": "Travel well all who are traveling. Good rest to all the rest.<br/>", "time": "2022-03-25T13:14:48Z"}, {"author": "John Levine", "text": "zzzzzzzzz<br/>", "time": "2022-03-25T13:14:56Z"}, {"author": "Alexey Melnikov", "text": "Thank you all<br/>", "time": "2022-03-25T13:15:22Z"}, {"author": "John C Klensin", "text": "zzzzzz indeed.&nbsp;&nbsp;And good travels to those of you who are in vienna<br/>", "time": "2022-03-25T13:15:46Z"}, {"author": "John C Klensin", "text": "And I'd love to know what Barry is discussing with some animation :-)<br/>", "time": "2022-03-25T13:16:32Z"}]