Where are you going, Hannes, also Hawaii?
", "time": "2023-10-16T15:03:47Z"}, {"author": "Hannes Tschofenig", "text": "I will just step down as a chair
", "time": "2023-10-16T15:04:15Z"}, {"author": "Hannes Tschofenig", "text": "No Hawaii for me
", "time": "2023-10-16T15:04:26Z"}, {"author": "Hannes Tschofenig", "text": "Deadline for draft submission is next Monday!!!
", "time": "2023-10-16T15:04:52Z"}, {"author": "Cedric Fournet", "text": "We could also start discussing the agenda for our 118 session.
", "time": "2023-10-16T15:06:37Z"}, {"author": "Orie Steele", "text": "I can summarize, but Steve and I had already planned to share some context on the list.
", "time": "2023-10-16T15:07:15Z"}, {"author": "Orie Steele", "text": "(re SCITT <> SPICE)
", "time": "2023-10-16T15:07:25Z"}, {"author": "A.J. Stein", "text": "(I was teasing, I saw the email about you stepping down from chair. I am pretty new here, but I enjoyed meeting you and your contributions, Hannes. Thanks again.)
", "time": "2023-10-16T15:07:57Z"}, {"author": "Hannes Tschofenig", "text": "I will still be around - just in a different role.
", "time": "2023-10-16T15:10:02Z"}, {"author": "Orie Steele", "text": "endorsement: I looked at your transparent statement, and I counter sign on it?
", "time": "2023-10-16T15:10:54Z"}, {"author": "Raymond Lutz", "text": "I can't go to the 118 in person, and it is is a critical time window for me as the November election is occurring at the same time. I'm going to try to participate esp. with document submissions prior to the meeting as I think I will have time between now and then.
", "time": "2023-10-16T15:10:57Z"}, {"author": "Dick Brooks", "text": "100% agree Roy. KISS...
", "time": "2023-10-16T15:11:21Z"}, {"author": "Orie Steele", "text": ": )
", "time": "2023-10-16T15:13:31Z"}, {"author": "Henk Birkholz", "text": "https://datatracker.ietf.org/doc/charter-ietf-keytrans/ballot/
", "time": "2023-10-16T15:14:35Z"}, {"author": "Dick Brooks", "text": "+1 @Ray the API is key for adoption by consumers.
", "time": "2023-10-16T15:19:54Z"}, {"author": "Steve Lasker", "text": "+1 for adding SCRAPI
", "time": "2023-10-16T15:21:02Z"}, {"author": "A.J. Stein", "text": "Since I am more recent here, it would be great if the notes or elsewhere on the mailing list about what is wanted in the Hackathon with the CLI and SCRAPI work (if not in issues already), I would love to be more focused on that than when I started in 117.
", "time": "2023-10-16T15:25:51Z"}, {"author": "Raymond Lutz", "text": "I see essentially what we need to define is the concrete set of name-value pairs that can be used in reg-info or other places, and then show how these are used in various uses functions.
", "time": "2023-10-16T15:25:57Z"}, {"author": "Dick Brooks", "text": "QR codes are just an alternative representation of an API call; here is a QR code example of a cybersecurity label lookup API call: https://reliableenergyanalytics.com/products
", "time": "2023-10-16T15:26:11Z"}, {"author": "Orie Steele", "text": "I will be there (in person, and the command line stuff I have been working on is in line with the fundamental operations), I think its good to \"show how to use\" / \"make usable software that implements the IETF specs\".
", "time": "2023-10-16T15:28:13Z"}, {"author": "Raymond Lutz", "text": "Although we are using the term scrapi here, I don't think it is a viable name because it is already in heavy use, usually for web scrapers. Is there a repo already started on the api for scitt?
", "time": "2023-10-16T15:29:04Z"}, {"author": "Cedric Fournet", "text": "I'll be in Prague
", "time": "2023-10-16T15:29:48Z"}, {"author": "A.J. Stein", "text": "I will be in attendance in Prague.
", "time": "2023-10-16T15:29:49Z"}, {"author": "Roy Williams", "text": "Not sure if Antoine will make it? Kristina will be there but it may be post Hackathon.
", "time": "2023-10-16T15:30:14Z"}, {"author": "A.J. Stein", "text": "(Henk, it will be easy, I am planning for Australia for IETF 119 to float on a raft there to save on transport costs.)
", "time": "2023-10-16T15:30:28Z"}, {"author": "Roy Williams", "text": "A.J. Is there room on the raft for a few more?
", "time": "2023-10-16T15:32:56Z"}, {"author": "Raymond Lutz", "text": "Yes, just to clarify, I will be putting forward a higher-level API which will sit on top of this lower level.
", "time": "2023-10-16T15:32:57Z"}, {"author": "Steve Lasker", "text": "100% running code is very convincing.
", "time": "2023-10-16T15:33:13Z"}, {"author": "Steve Lasker", "text": "AJ - awesome!
\nEntry awareness is great to give new perspective experience
I'll also be at the hackathon, will prioritize working on the drafts and the session.
", "time": "2023-10-16T15:34:12Z"}, {"author": "Hannes Tschofenig", "text": "AJ. That's great. Your help will be appreciated!
", "time": "2023-10-16T15:34:23Z"}, {"author": "Hannes Tschofenig", "text": "We actually have a very good representation at the hackathon. I am impressed!
", "time": "2023-10-16T15:36:06Z"}, {"author": "Raymond Lutz", "text": "I don't know if we need two sets of attributes in both reg-info and feed. Seems like reg-info is flexible enough.
", "time": "2023-10-16T15:47:46Z"}, {"author": "Orie Steele", "text": "Here is a registry that issuer's use to convey their intention to make claims
", "time": "2023-10-16T15:48:53Z"}, {"author": "Orie Steele", "text": "https://www.iana.org/assignments/cwt/cwt.xhtml
", "time": "2023-10-16T15:48:54Z"}, {"author": "Orie Steele", "text": "this includes \"sub\" which is the identifier the issuer uses to refer to the \"topic\" /\"purpose\".
", "time": "2023-10-16T15:49:20Z"}, {"author": "Orie Steele", "text": "reinventing \"sub\" is pointless and breaks interoperability.
", "time": "2023-10-16T15:49:38Z"}, {"author": "Orie Steele", "text": "\"sub\" replaces \"feed:,
", "time": "2023-10-16T15:49:59Z"}, {"author": "Neal McBurnett", "text": "I think the verifier point of view is also important, and I thing verifiers in general will perceive that many statements have multiple \"purposes\"
", "time": "2023-10-16T15:52:08Z"}, {"author": "Hannes Tschofenig", "text": "Question: Dick & Ray - - are you guys going to submit a VRF for the next IETF meeting?
", "time": "2023-10-16T15:53:32Z"}, {"author": "Cedric Fournet", "text": "I believe we agree on the joint purpose of \"feed + reg_info\", but not on how we would separate their purpose if we keep a separate feed.
", "time": "2023-10-16T15:55:23Z"}, {"author": "Neal McBurnett", "text": "\"Purpose\" seems like a problematic term. Feed or Topic are better.
", "time": "2023-10-16T15:55:43Z"}, {"author": "Cedric Fournet", "text": "\"Purpose\" becomes problematic only if we try to define it once for all in the spec. Not if it is left to the supply chain actors.
", "time": "2023-10-16T15:56:58Z"}, {"author": "Steve Lasker", "text": "a feed, as a bstr can be a set of name/value pairs.
\nKeeping name/value pairs separate opens up the ambiguity where another issuer can submit a statement on a subset of the properties, making it unclear which feed they're talking about.
Are we going to have a discussion on this interactively in 2 three minutes? Won't the session automatically close again?
", "time": "2023-10-16T15:58:25Z"}, {"author": "Raymond Lutz", "text": "Yes, Charlie, feed is a bad name, in my opinion.
", "time": "2023-10-16T15:58:29Z"}, {"author": "Jon Geater", "text": "+1 Sylvan - this is exactly the property I was trying to represent in my PR talking about 'pre-commitment' and themes like that. Sylvan just said it better than me.
\nSeems like the group will be much happier if we just change the name...?
", "time": "2023-10-16T15:58:34Z"}, {"author": "Andrew Reiter", "text": "Must drop for conflict.
", "time": "2023-10-16T15:58:41Z"}, {"author": "Cedric Fournet", "text": "We have been arguing about feed name and its content format for weeks, without clear consensus. Hence the simplifying proposal to move it to reg_info, where the issuer can pick any names and contents as part of its map.
", "time": "2023-10-16T16:02:31Z"}]