[{"author": "Steve Lasker", "text": "<p>Feeds: <a href=\"https://github.com/ietf-wg-scitt/draft-ietf-scitt-architecture/pulls\">https://github.com/ietf-wg-scitt/draft-ietf-scitt-architecture/pulls</a><br>\nEmulator Update: <a href=\"https://github.com/scitt-community/scitt-api-emulator/pull/31\">https://github.com/scitt-community/scitt-api-emulator/pull/31</a></p>", "time": "2023-10-09T15:08:39Z"}, {"author": "A.J. Stein", "text": "<p>My review isn't thoughtful with the OAS pull request, but lazily testing it out with the OpenAPI Editor/Viewer had issues with the relative paths (of OAS specs referencing one another). This coming week, I wanted to examine if that is a major issue or not just reviewer error on my part. (Nothing deep or constructive yet.)</p>", "time": "2023-10-09T15:10:48Z"}, {"author": "A.J. Stein", "text": "<p>If metadata without more structure for sequencing and relationships is sufficient and why not feeds (in concept, even without a name), I ask rhetorically: why even SCITT at all?</p>", "time": "2023-10-09T15:20:54Z"}, {"author": "Raymond Lutz", "text": "<p><a href=\"https://itu.dk/people/debois/papers/podc20.pdf\">https://itu.dk/people/debois/papers/podc20.pdf</a></p>", "time": "2023-10-09T15:22:04Z"}, {"author": "Raymond Lutz", "text": "<p>On the Subject of Non-Equivocation</p>", "time": "2023-10-09T15:22:32Z"}, {"author": "Raymond Lutz", "text": "<p>I don't think feeds can (by themselves) non-equivocation. The only way in the end to know if something else was said is to have the log and review it.</p>", "time": "2023-10-09T15:23:59Z"}, {"author": "Raymond Lutz", "text": "<p>Probably can support the issue of metadata for searching without supporting it with nonequivocation criteria.</p>", "time": "2023-10-09T15:24:51Z"}, {"author": "Dick Brooks", "text": "<p>I feel like we're trying to slay the hydra before we even know how to slay one dragon.</p>", "time": "2023-10-09T15:31:13Z"}, {"author": "Raymond Lutz", "text": "<p>Now that issue brought up by Roy I think might be a good reason for a feed identifier.</p>", "time": "2023-10-09T15:33:43Z"}, {"author": "Orie Steele", "text": "<p>Sry I am late</p>", "time": "2023-10-09T15:34:37Z"}, {"author": "Raymond Lutz", "text": "<p>Yes, Dick, for many use cases we don't need to have absolute security and not also the ability to span over different data stores. I noted in DBOM that they had the idea of multiple instances but one single data store for each one, and the concept of a channel.</p>", "time": "2023-10-09T15:35:08Z"}, {"author": "Raymond Lutz", "text": "<p>I do think reg_info is just fine for metadata, bc we need to have those attributes of artifacts so we can find them.</p>", "time": "2023-10-09T15:37:04Z"}, {"author": "Dick Brooks", "text": "<p>Ray, I would feel like we've made good progress if we can create a \"foundational solution\" that would enable a single software vendor to host a SCITT Trust Registry for their own products. I don't think we have defined a protocol adequately to do this foundational function yet.</p>", "time": "2023-10-09T15:37:59Z"}, {"author": "A.J. Stein", "text": "<p>Do we know of a single software vendor that works completely in isolation and has no external software/hardware dependencies they must communicate with/through SCITT? Your point stands, but foundational is far away from simple with completely independent vendors, even for the simplest solutions. The \"walk, crawl, run\" theme of your comment still resonates with me, Dick.</p>", "time": "2023-10-09T15:40:10Z"}, {"author": "Dick Brooks", "text": "<p>:thumbsup:</p>", "time": "2023-10-09T15:41:09Z"}, {"author": "Orie Steele", "text": "<p>I'm fine merging PRs that improve the document, there will be plenty of chances to object when the document is more mature.</p>", "time": "2023-10-09T15:45:11Z"}, {"author": "Orie Steele", "text": "<p>im ready</p>", "time": "2023-10-09T15:46:36Z"}, {"author": "Dick Brooks", "text": "<p>I agree with Orie, distinguish a \"registration action\" from a \"broadcast feed\". Very different concepts and protocols incovled, IMO.</p>", "time": "2023-10-09T15:50:48Z"}, {"author": "Raymond Lutz", "text": "<p>Yes, love using subject</p>", "time": "2023-10-09T15:52:57Z"}, {"author": "Dick Brooks", "text": "<p>+1 for use of subject to identify \"artifact\" being registered.</p>", "time": "2023-10-09T15:53:35Z"}, {"author": "Raymond Lutz", "text": "<p>I'm for changing feed to subject when ever appropriate.</p>", "time": "2023-10-09T15:54:40Z"}, {"author": "Raymond Lutz", "text": "<p>I notice 'feed' is not in the iana list.</p>", "time": "2023-10-09T15:55:03Z"}, {"author": "Dick Brooks", "text": "<p>IMO \"feed\" refers to the inter-registry communications that take place between SCITT Trust Registries.</p>", "time": "2023-10-09T15:55:33Z"}, {"author": "Raymond Lutz", "text": "<p>that's correct because feed is a concept from the standpoint of the viewer, as Orie says. Good job Orie.</p>", "time": "2023-10-09T15:55:36Z"}, {"author": "Raymond Lutz", "text": "<p>I consider this a breakthru.</p>", "time": "2023-10-09T15:56:11Z"}, {"author": "A.J. Stein", "text": "<p>Can you have a feed or anything in this IANA registration before it is not documented in an endorsed spec? I assume this is a \"we need to agree to this, then request that from IANA\" situation.</p>", "time": "2023-10-09T15:56:26Z"}, {"author": "A.J. Stein", "text": "<p>(My only experience is for MIME filetype registration, others can correct me.)</p>", "time": "2023-10-09T15:56:26Z"}, {"author": "Dick Brooks", "text": "<p>IANA also registers DNS tags that are used in DNS operations to ensure uniqueness of dns names.</p>", "time": "2023-10-09T15:57:39Z"}, {"author": "Raymond Lutz", "text": "<p>Orie going into repeat mode again.</p>", "time": "2023-10-09T15:59:10Z"}, {"author": "A.J. Stein", "text": "<p>So it isn't only me? I thought my WiFi wasn't working or the coffee I drank is working a little too well.</p>", "time": "2023-10-09T15:59:32Z"}, {"author": "Steve Lasker", "text": "<p>--Time Check--</p>", "time": "2023-10-09T15:59:56Z"}, {"author": "Orie Steele", "text": "<p>the base architecture already prescribes header paramters.</p>", "time": "2023-10-09T16:00:32Z"}, {"author": "Orie Steele", "text": "<p>and you are yet again, conflating queries, and header parameters.</p>", "time": "2023-10-09T16:00:48Z"}, {"author": "Orie Steele", "text": "<p>can't solve the name collision issue, with header parameters</p>", "time": "2023-10-09T16:01:15Z"}, {"author": "Orie Steele", "text": "<p>you need the TS to help with that.</p>", "time": "2023-10-09T16:01:22Z"}, {"author": "Steve Lasker", "text": "<p>thanks folks</p>", "time": "2023-10-09T16:01:38Z"}]