[{"author": "Richard Barnes", "text": "<p>what's the deal with t-shirts?</p>", "time": "2023-07-27T22:31:01Z"}, {"author": "Ted Hardie", "text": "<p>The secretariat emptied their stores of old, unclaimed t-shirts.  They are downstairs at the registration table.</p>", "time": "2023-07-27T22:31:58Z"}, {"author": "Shivan Sahib", "text": "<p>You can be a document Shepherd without being the WG chair?</p>", "time": "2023-07-27T22:34:28Z"}, {"author": "Stephen Farrell", "text": "<p>yep</p>", "time": "2023-07-27T22:34:38Z"}, {"author": "Paul Wouters", "text": "<p>it is supposed to be NOT the chair :P</p>", "time": "2023-07-27T22:34:51Z"}, {"author": "Jim Fenton", "text": "<p>That's a challenge for some small WGs.</p>", "time": "2023-07-27T22:36:01Z"}, {"author": "Shivan Sahib", "text": "<p><a href=\"https://www.ietf.org/about/groups/iesg/statements/document-shepherds/\">https://www.ietf.org/about/groups/iesg/statements/document-shepherds/</a></p>", "time": "2023-07-27T22:36:25Z"}, {"author": "Benjamin Kaduk", "text": "<p>What about things that will happen later today, Roman?</p>", "time": "2023-07-27T22:36:38Z"}, {"author": "Richard Barnes", "text": "<p><span class=\"user-mention\" data-user-id=\"499\">@Benjamin Kaduk</span> you can just say \"MLS\" :)</p>", "time": "2023-07-27T22:37:41Z"}, {"author": "Benjamin Kaduk", "text": "<p>Also TIGRESS, I think</p>", "time": "2023-07-27T22:38:04Z"}, {"author": "Jonathan Lennox", "text": "<p>While I'm proofreading slides, this one says \"Please sent\".</p>", "time": "2023-07-27T22:38:46Z"}, {"author": "Cory Myers", "text": "<p><a href=\"https://www.washingtonpost.com/technology/2023/07/25/captchas-hate-privacy-pass/\">https://www.washingtonpost.com/technology/2023/07/25/captchas-hate-privacy-pass/</a></p>", "time": "2023-07-27T22:39:24Z"}, {"author": "Greg Wood", "text": "<p>ICYM, WaPo article mentioning privacy pass <a href=\"https://wapo.st/3DyyHWU\">https://wapo.st/3DyyHWU</a></p>", "time": "2023-07-27T22:39:36Z"}, {"author": "Stephen Farrell", "text": "<p>we ufmrg chairs know what our group is:-)</p>", "time": "2023-07-27T22:41:48Z"}, {"author": "Benjamin Kaduk", "text": "<p>I guess this is the time to uphold the reputation of the security area for close attention to detail in written material...</p>", "time": "2023-07-27T22:42:24Z"}, {"author": "Roman Danyliw", "text": "<p>Sorry about that.</p>", "time": "2023-07-27T22:43:01Z"}, {"author": "Ira McDonald", "text": "<p><a href=\"https://csrc.nist.gov/Events/2023/lightweight-cryptography-workshop-2023\">https://csrc.nist.gov/Events/2023/lightweight-cryptography-workshop-2023</a> - all recordings and slides are posted here</p>", "time": "2023-07-27T22:43:50Z"}, {"author": "Daniel Gillmor", "text": "<p>It might help to advertise the workflow for how to vet the errata, for folks who don't know how to do it.</p>", "time": "2023-07-27T22:49:09Z"}, {"author": "Bernie Hoeneisen", "text": "<p><a href=\"https://www.rfc-editor.org/errata.php\">https://www.rfc-editor.org/errata.php</a></p>", "time": "2023-07-27T22:50:04Z"}, {"author": "Daniel Gillmor", "text": "<p>it would really help if we could see the breakdown by WG -- i'm not going to do a good review of, say, OAUTH errata.</p>", "time": "2023-07-27T22:50:21Z"}, {"author": "Bernie Hoeneisen", "text": "<p>only sec related errata: <a href=\"https://www.rfc-editor.org/errata_search.php?rec_status=15&amp;area_acronym=sec&amp;presentation=table\">https://www.rfc-editor.org/errata_search.php?rec_status=15&amp;area_acronym=sec&amp;presentation=table</a></p>", "time": "2023-07-27T22:50:51Z"}, {"author": "Deb Cooley", "text": "<p>On the WG documents page, there is an errata button.  clicking on that for whatever RFC will bring up the list of errata for that RFC.</p>", "time": "2023-07-27T22:51:38Z"}, {"author": "Daniel Gillmor", "text": "<p>right, that page lets you sort and filter in these ways, but it's still not super easy to do, and there's no pretty graph that names the outstanding groups/rfcs/etc.  I have to search to find them.  Gamify it if you want nerds to drive the number down to zero.</p>", "time": "2023-07-27T22:52:05Z"}, {"author": "Dave Thaler", "text": "<p>see RFC 5218</p>", "time": "2023-07-27T22:52:52Z"}, {"author": "Samuel Weiler", "text": "<p>is anyone from GoDaddy in the room?</p>", "time": "2023-07-27T22:52:59Z"}, {"author": "Daniel Gillmor", "text": "<p>\"ship it right away\" is easier to do when your protocol is online and it has a clear migration schedule from version to version.</p>\n<p>It's a lot harder when your protocol is generating static objects with indefinite lifetimes.</p>", "time": "2023-07-27T22:57:37Z"}, {"author": "Michael StJohns", "text": "<p><a href=\"https://www.rfc-editor.org/errata_search.php?rec_status=2&amp;area_acronym=sec&amp;presentation=table\">https://www.rfc-editor.org/errata_search.php?rec_status=2&amp;area_acronym=sec&amp;presentation=table</a> = status=15 is verified and reported, while 2 appears to be just \"reported\"</p>", "time": "2023-07-27T22:57:46Z"}, {"author": "Florence D", "text": "<p>Really interesting presentation, thanks.</p>", "time": "2023-07-27T23:03:19Z"}, {"author": "Jonathan Hoyland", "text": "<p>If only clocks were sufficiently well synchronised on the web to allow for 24 hour certs</p>", "time": "2023-07-27T23:03:49Z"}, {"author": "Jonathan Hoyland", "text": "<p>Also if only CAs had good enough uptime</p>", "time": "2023-07-27T23:04:07Z"}, {"author": "Daniel Gillmor", "text": "<p><span class=\"user-mention\" data-user-id=\"453\">@Jonathan Hoyland</span> we've all been burned by bad clocks, but i wonder what would happen if we started to be stricter about rejecting out-of-sync machines</p>", "time": "2023-07-27T23:06:12Z"}, {"author": "Yoav Nir", "text": "<p>@Jonathan Maybe we should have a working group to make some protocol for synchronizing computer clocks.</p>", "time": "2023-07-27T23:06:35Z"}, {"author": "Daniel Gillmor", "text": "<p>and in ACME we talked about ACME clients being configured with CA rollover, so that CA downtime isn't so painful to the client.</p>", "time": "2023-07-27T23:06:41Z"}, {"author": "Jonathan Hoyland", "text": "<p>So I would say two things 1. DCs and 2. NTS has a dependency on TLS which has a dependency on synchronised clocks ...</p>", "time": "2023-07-27T23:07:43Z"}, {"author": "Deb Cooley", "text": "<p>wait like NTP?</p>", "time": "2023-07-27T23:09:08Z"}, {"author": "Jonathan Hoyland", "text": "<p>520 slides at 30 Hz takes under 20 seconds</p>", "time": "2023-07-27T23:10:25Z"}, {"author": "Thomas Hardjono", "text": "<p>FYI.  SAML2.0 WG in OASIS is being closed, after 20 yrs almost.</p>", "time": "2023-07-27T23:10:55Z"}, {"author": "Jim Fenton", "text": "<p>identity-discuss mailing list archives are 404</p>", "time": "2023-07-27T23:11:17Z"}, {"author": "Uri Blumenthal", "text": "<p>Well, an authenticated identity is the key (no pun intended) input to everything else, like authorization, etc.</p>", "time": "2023-07-27T23:11:45Z"}, {"author": "Jim Fenton", "text": "<p>...and the words they choose overlap with each other</p>", "time": "2023-07-27T23:13:20Z"}, {"author": "Richard Barnes", "text": "<p>Slides are still wrong.  Correct email address is <a href=\"mailto:identity-discuss@iab.org\">identity-discuss@iab.org</a></p>", "time": "2023-07-27T23:14:11Z"}, {"author": "Ned Smith", "text": "<p>@Uri Blumenthal - true but if as privacy trackers, identifiers don't need to be authenticatable</p>", "time": "2023-07-27T23:14:45Z"}, {"author": "Benjamin Kaduk", "text": "<p>The slides up at the datatracker look good to me :)</p>", "time": "2023-07-27T23:14:48Z"}, {"author": "Roman Danyliw", "text": "<p><a href=\"https://www.ietf.org/mailman/listinfo/Identity-discuss\">https://www.ietf.org/mailman/listinfo/Identity-discuss</a></p>", "time": "2023-07-27T23:14:49Z"}, {"author": "Watson Ladd", "text": "<p>Come to NTP tomorrow if you want time for security!</p>", "time": "2023-07-27T23:15:21Z"}, {"author": "Jim Fenton", "text": "<p>Pun intended?</p>", "time": "2023-07-27T23:15:42Z"}, {"author": "Watson Ladd", "text": "<p>Of course</p>", "time": "2023-07-27T23:16:08Z"}, {"author": "Benjamin Kaduk", "text": "<p>There are still some terms in the DNS glossary that you don't even try to define yet!</p>", "time": "2023-07-27T23:16:43Z"}, {"author": "Stephen Farrell", "text": "<p>DNS vocab is lame:-)</p>", "time": "2023-07-27T23:16:45Z"}, {"author": "Ned Smith", "text": "<p>RFC4949 hasn't been updated since 2013</p>", "time": "2023-07-27T23:17:26Z"}, {"author": "Mohammad Al Abbadi", "text": "<p>Two definitions enter, three definitions leave!</p>", "time": "2023-07-27T23:17:55Z"}, {"author": "Yoav Nir", "text": "<p>PHB is not a number</p>", "time": "2023-07-27T23:19:49Z"}, {"author": "Watson Ladd", "text": "<p>Next up, IAB program on what it is like to be a bat</p>", "time": "2023-07-27T23:19:59Z"}, {"author": "Stephen Farrell", "text": "<p>IRTF doesn't do programmes</p>", "time": "2023-07-27T23:20:57Z"}, {"author": "Stephen Farrell", "text": "<p>answer: yes (or no:-)</p>", "time": "2023-07-27T23:21:36Z"}, {"author": "Aaron Parecki", "text": "<p>I mean, sounds like PHB is coming at it with his own idea of the identity space, just like Dick described</p>", "time": "2023-07-27T23:21:51Z"}, {"author": "Nick Doty", "text": "<p>focusing on user-driven use cases, or principles for how to avoid harm to people and maintain benefits for people, might be a way to narrow the scope</p>", "time": "2023-07-27T23:23:07Z"}, {"author": "Benjamin Kaduk", "text": "<p>Just so long as we are not hurling identity discuses at each other...</p>", "time": "2023-07-27T23:23:55Z"}]