[{"author": "Steve Lasker", "text": "<p>Hi folks</p>", "time": "2023-05-22T15:04:38Z"}, {"author": "Jon Geater", "text": "<p>OK, I'll grab better headphones</p>", "time": "2023-05-22T15:05:11Z"}, {"author": "Cedric Fournet", "text": "<p>Do you have a pointer to the discussion on key vs SCITT  transparency?</p>", "time": "2023-05-22T15:05:14Z"}, {"author": "Hannes Tschofenig", "text": "<p>Current issue: <a href=\"https://github.com/ietf-wg-scitt/draft-ietf-scitt-architecture/issues/69\">https://github.com/ietf-wg-scitt/draft-ietf-scitt-architecture/issues/69</a></p>", "time": "2023-05-22T15:11:00Z"}, {"author": "Jon Geater", "text": "<p><a href=\"https://docs.google.com/document/d/12NMFA0P1OYtE6_QoqP3J80tDr0z2-FEm2ZdiWeauAHE/editAdded\">https://docs.google.com/document/d/12NMFA0P1OYtE6_QoqP3J80tDr0z2-FEm2ZdiWeauAHE/editAdded</a> to the notes too</p>", "time": "2023-05-22T15:12:07Z"}, {"author": "Steve Lasker", "text": "<p>Jon, the link above got merged with your comment:<br>\n<a href=\"https://docs.google.com/document/d/12NMFA0P1OYtE6_QoqP3J80tDr0z2-FEm2ZdiWeauAHE/edit\">https://docs.google.com/document/d/12NMFA0P1OYtE6_QoqP3J80tDr0z2-FEm2ZdiWeauAHE/edit</a></p>", "time": "2023-05-22T15:16:02Z"}, {"author": "Jon Geater", "text": "<p>Thanks Steve</p>", "time": "2023-05-22T15:16:47Z"}, {"author": "Jon Geater", "text": "<p>FYI all I'm travelling today and my network is unreliable. I keep falling off and have to leave at the bottom of the hour. Apologies.</p>", "time": "2023-05-22T15:17:32Z"}, {"author": "Steve Lasker", "text": "<p>Vacation return overload. I have to drop at 30 past the hour. </p>\n<p>My main comment on the URL for statements to assure they're not tied to a location, so users can copy statements from one SCITT instance to another, and maintain the link to the ID, independent of the instance. <br>\nSee: Separating Identity From Location (<a href=\"https://stevelasker.blog/2021/09/24/separating-identity-from-location/\">https://stevelasker.blog/2021/09/24/separating-identity-from-location/</a>)</p>", "time": "2023-05-22T15:20:23Z"}, {"author": "Orie Steele", "text": "<p>you want content id references</p>", "time": "2023-05-22T15:33:35Z"}, {"author": "Orie Steele", "text": "<p>where content id is a hash based identifier for binary.</p>", "time": "2023-05-22T15:33:56Z"}, {"author": "Orie Steele", "text": "<p>registration policy is up the the TS, we don't control that.</p>", "time": "2023-05-22T15:41:47Z"}, {"author": "Orie Steele", "text": "<p>if an operator wants to allow registrations for something, that is their choice.</p>", "time": "2023-05-22T15:42:12Z"}, {"author": "Orie Steele", "text": "<p>we don't limit registration policies as part of our work.</p>", "time": "2023-05-22T15:42:28Z"}, {"author": "Orie Steele", "text": "<p>we do define the shape of signed statements and transparent statments</p>", "time": "2023-05-22T15:43:01Z"}, {"author": "Raymond Lutz", "text": "<p>I'm against compactness.</p>", "time": "2023-05-22T15:47:44Z"}, {"author": "Raymond Lutz", "text": "<p>I think we can have a simple machine with optional metadata that can be used for lookups. Otherwise, it becomes almost worthless pile of obscured data.</p>", "time": "2023-05-22T15:50:04Z"}, {"author": "Raymond Lutz", "text": "<p>Let me say that we definitely need to have the transparency service responsible for providing as list of entries that are associated. Or the submitter can lie about what is submitted.</p>", "time": "2023-05-22T15:54:30Z"}, {"author": "Raymond Lutz", "text": "<p>Historicity is a good word! Thank you</p>", "time": "2023-05-22T15:57:18Z"}]