This was a most interesting presentation, agree further dialogue very welcome
", "time": "2023-07-24T23:02:15Z"}, {"author": "Thomas Barrett", "text": "count us in! EnCirca would like to engage further.
", "time": "2023-07-24T23:02:43Z"}, {"author": "Thomas Barrett", "text": "the primary issues to address are:
", "time": "2023-07-24T23:02:59Z"}, {"author": "Thomas Barrett", "text": "these issues need to translate to informational rfc's
", "time": "2023-07-24T23:04:25Z"}, {"author": "Viktor Dukhovni", "text": "Once again cue PHB with the mathematical mesh... :-)
", "time": "2023-07-24T23:04:40Z"}, {"author": "Viktor Dukhovni", "text": "There names are \"forever\"...
", "time": "2023-07-24T23:04:59Z"}, {"author": "Thomas Barrett", "text": "why wouldn't a BOF lead to a working group?
", "time": "2023-07-24T23:05:38Z"}, {"author": "Randy Bush", "text": "i suspect that RG before BOF, as this is still pretty wobbly
", "time": "2023-07-24T23:07:54Z"}, {"author": "John Klensin", "text": "I wonder again if it is time to ask whether adding all this stuff onto the DNS -- treating DNS names as the core of a universal identifier system -- is really a good idea. This presentation, seeing things in terms of \"integration\", seems to presume that the answer is \"no limits to that process and no bad effects from increasing loading of applications onto it.
", "time": "2023-07-24T23:08:34Z"}, {"author": "Thomas Barrett", "text": "the truth is that web3 can't exist without DNS.
", "time": "2023-07-24T23:09:36Z"}, {"author": "Randy Bush", "text": "is that a bug or a feature :)
", "time": "2023-07-24T23:10:02Z"}, {"author": "Thomas Barrett", "text": "hah!
", "time": "2023-07-24T23:10:11Z"}, {"author": "Evan Hunt", "text": "there's a reason \"put it in the DNS\" is such a cliche. it Never Ever Fails
", "time": "2023-07-24T23:17:09Z"}, {"author": "Jim Reid", "text": "@Thomas BoFs don't lead to a WG for all sorts of reasons: no consensus, unclear problem statement, out of scope, lack of interest, overlaps with existing work, etc. If you want to know more, take a look at the list of failed BoFs at past IETF meetings. IMO, an IETF BoF on the DNS Integration stuff Andrew mentioned could be too fuzzy and/or sprawling to get consensus or a new WG.
", "time": "2023-07-24T23:18:36Z"}, {"author": "Dave Plonka", "text": "Historical, but still current, aside: we have this BCP which suggests the use of DNS for service rendezvous: https://www.rfc-editor.org/rfc/rfc4085.html#section-3.3
\nAn intentionally non-working group forming BoF also seems a candidate option to me.
", "time": "2023-07-24T23:20:19Z"}, {"author": "Randy Bush", "text": "one assignment for resurrection of nsrg: collect all the uses of TXT and other escapes to try and get the dimensions of the space.
", "time": "2023-07-24T23:22:05Z"}, {"author": "Jim Reid", "text": "Might as well count all the grains of sand in the Sahara as count all the uses of TXT. :grinning:
", "time": "2023-07-24T23:23:22Z"}, {"author": "Thomas Barrett", "text": "blockchain naming services could certainly benefit from a few best practices (<10) for DNS integration. It would be a great if IETF led the conversation here.
", "time": "2023-07-24T23:25:14Z"}, {"author": "Viktor Dukhovni", "text": "dns.coffee is a precedent for some of the dependency graph construction.
", "time": "2023-07-24T23:28:56Z"}, {"author": "John Levine", "text": "also dnsviz
", "time": "2023-07-24T23:30:45Z"}, {"author": "Allison Mankin", "text": "There still is a working online tool to see dependencies (this views IETF.org): https://trans-trust.verisignlabs.com/?z=IETF.org
", "time": "2023-07-24T23:35:38Z"}, {"author": "Allison Mankin", "text": "Not sure if it's maintained...
", "time": "2023-07-24T23:36:54Z"}, {"author": "Daniel Gillmor", "text": "@Allison Mankin yikes. and that doesn't even show the results for all possible query paths for any given record.
", "time": "2023-07-24T23:40:32Z"}, {"author": "Allison Mankin", "text": "Your term was apt @Daniel Gillmor
", "time": "2023-07-24T23:42:38Z"}, {"author": "Daniel Gillmor", "text": "@Cristian Munteanu what are the actual costs of selecting a \"non-optimal\" edge node from the hypergiant ? who bears those costs?
", "time": "2023-07-24T23:43:51Z"}, {"author": "Randy Bush", "text": "and measure of alpha and beta error as compared to other detection?
", "time": "2023-07-24T23:51:25Z"}, {"author": "Susan Hares", "text": "On what basis are the triangulation done between streams? Is it IP address, 5 tuples, time, client or something else?
", "time": "2023-07-24T23:54:51Z"}, {"author": "Daniel Gillmor", "text": "@Susan Hares do you want me to ask this question at the mic to Alex?
", "time": "2023-07-24T23:56:11Z"}, {"author": "Benno Overeinder", "text": "Interesting presentation \"Enabling Multi-hop ISP-Hypergiant Collaboration\". On server selection, the following presentation might be interesting: \"Addressing IPv6: A CDN Perspective\", by Joao Taveira Araujo, Fastly. It was presented at RIPE 74. See https://ripe74.ripe.net/programme/meeting-plan/plenary/ and https://ripe74.ripe.net/presentations/71-joao-ripe2017.pdf.
", "time": "2023-07-24T23:56:34Z"}]