Kudos for appropriate use of \"scarfed\".
", "time": "2023-11-09T14:01:48Z"}, {"author": "Andrew Newton", "text": "XML eye chart
", "time": "2023-11-09T14:10:15Z"}, {"author": "Murray Kucherawy", "text": "Interesting new approach for eye charts.
", "time": "2023-11-09T14:11:31Z"}, {"author": "Murray Kucherawy", "text": "At a distance of 20 feet, spot the XML error.
", "time": "2023-11-09T14:11:39Z"}, {"author": "Pete Resnick", "text": "The question of more than one contact format is all about need for interoperability, isn't it?
", "time": "2023-11-09T14:34:29Z"}, {"author": "Pete Resnick", "text": "If it needs interoperability, standards track makes sense.
", "time": "2023-11-09T14:36:19Z"}, {"author": "Murray Kucherawy", "text": "My main concern is about who's planning to switch and what that transition will look lke.
", "time": "2023-11-09T14:37:24Z"}, {"author": "Pawe\u0142 Kowalik", "text": "I think right now it is in the context of RDAP, but this will also surface if we discuss JSON representations of EPP artefacts (later agenda point)
", "time": "2023-11-09T14:40:57Z"}, {"author": "Jody Kolker", "text": "+1 Scott.
", "time": "2023-11-09T14:42:01Z"}, {"author": "Pawe\u0142 Kowalik", "text": "+1 for both experimental
", "time": "2023-11-09T14:43:41Z"}, {"author": "Murray Kucherawy", "text": "If you go with experimental, think about what sort of structure you might want to put on the experiment (e.g., is anyone tracking the experiment? is there a target date to decide? etc.).
", "time": "2023-11-09T14:44:31Z"}, {"author": "Pawe\u0142 Kowalik", "text": "+1
", "time": "2023-11-09T14:46:11Z"}, {"author": "Murray Kucherawy", "text": "Please remember to depart the queue after you're done at the mic.
", "time": "2023-11-09T14:50:06Z"}, {"author": "James Galvin", "text": "Noting for the record that the Chairs have noted Jody, Pete's, and Murray's comments regarding \"contact\" here in the chat.
", "time": "2023-11-09T14:55:36Z"}, {"author": "Edmon Chung", "text": "the IDN policy development process is expected to complete most of the main principles wtihin the year
", "time": "2023-11-09T15:05:56Z"}, {"author": "Jim Reid", "text": "Which year Edmon?
", "time": "2023-11-09T15:06:22Z"}, {"author": "Edmon Chung", "text": "and that includes behaviours of IDN variants and certainly provisioning implications as well as rdap
", "time": "2023-11-09T15:06:34Z"}, {"author": "Edmon Chung", "text": "there will be a f2f special working group meeting in december and most of the issues are expected to be completed
", "time": "2023-11-09T15:06:56Z"}, {"author": "Edmon Chung", "text": "so 2023 :-)
", "time": "2023-11-09T15:07:06Z"}, {"author": "James Galvin", "text": "To expand a bit on the \"issues completed this year\" comment, the Policy Process then moves to a public comment period and then there's review of comments and then there's a final report.
", "time": "2023-11-09T15:09:33Z"}, {"author": "Edmon Chung", "text": "for ccTLDs, the ccNSO policy development process is also abuot to complete and will have some implications on IDN ccTLDs as well although less of an impact because 2nd level registrations are not dealt with there
", "time": "2023-11-09T15:10:00Z"}, {"author": "James Galvin", "text": "So the \"happy path\" for that could still be as short as a few months, although the reality is that \"DONE\" will be sometime in the latter half of next year. So, soon regardless.
", "time": "2023-11-09T15:10:14Z"}, {"author": "Edmon Chung", "text": "ya cause after completing the first round of discussion there will be a draft out for public comments and then further discussion before finalization, so it will take a few months and into the 2nd half of next year, that said, the issues pertinent to considering EPP IDN extension should be complete wtihin this year
", "time": "2023-11-09T15:11:58Z"}, {"author": "James Galvin", "text": "And as Edmon says, within ICANN there are some differences between ccTLDs versus gTLDs that we have to track and make sure are covered.
", "time": "2023-11-09T15:12:00Z"}, {"author": "Edmon Chung", "text": "the longer discussion will probably be future policy changes, particularly the IDN Implementation Guidelines update process
", "time": "2023-11-09T15:12:21Z"}, {"author": "Andrew Newton", "text": "I support this too.
", "time": "2023-11-09T15:15:55Z"}, {"author": "Andrew Newton", "text": "Links have a \"rel\" which specifies the relationship.
", "time": "2023-11-09T15:17:23Z"}, {"author": "Andrew Newton", "text": "I think the big question here is gonna be one of scope.
", "time": "2023-11-09T15:26:05Z"}, {"author": "Gavin Brown", "text": "let's start with application/epp+xml, application/epp+json can come later
", "time": "2023-11-09T15:27:07Z"}, {"author": "Andrew Newton", "text": "what about an openApi version of EPP?
", "time": "2023-11-09T15:27:25Z"}, {"author": "Ties de Kock", "text": "YANG? /s
", "time": "2023-11-09T15:27:41Z"}, {"author": "Andrew Newton", "text": "CBOR
", "time": "2023-11-09T15:28:38Z"}, {"author": "Jody Kolker", "text": "Any concerns on how rate limiting would be implemented?
", "time": "2023-11-09T15:28:41Z"}, {"author": "Andrew Newton", "text": "I think using REST is the point. People using clouds can use web-app firewalls, etc... to do rate limiting... and they can do it per endpoint too
", "time": "2023-11-09T15:29:38Z"}, {"author": "Gavin Brown", "text": "EPP over HTTP would also lower the barrier to entry for registries
", "time": "2023-11-09T15:31:59Z"}, {"author": "Jody Kolker", "text": "Any concerns regarding response times?
", "time": "2023-11-09T15:32:10Z"}, {"author": "Pawe\u0142 Kowalik", "text": "thanks
", "time": "2023-11-09T15:33:11Z"}]