[{"author": "Tim Wicinski", "text": "<p>I for one welcome our new Kitten TLD Overlords</p>", "time": "2025-11-07T16:38:01.000Z"}, {"author": "Matt Green", "text": "<p>I'm just glad the puppies are secure</p>", "time": "2025-11-07T16:39:00.000Z"}, {"author": "Ted Hardie", "text": "<p>For .internal, what's the DNSSEC story?</p>", "time": "2025-11-07T16:40:25.000Z"}, {"author": "Ted Hardie", "text": "<p>If you use this, I mean.</p>", "time": "2025-11-07T16:40:44.000Z"}, {"author": "Peter Thomassen", "text": "<p>Florian, the DS record on slide 3 is for \"puppy\" in the \"<a href=\"http://example.org\">example.org</a>\" zone (not the root)</p>", "time": "2025-11-07T16:42:15.000Z"}, {"author": "Florian Obser", "text": "<p>Peter, yeah, it sounded like you would also put a DS in the root and I was curious how that would look like.</p>", "time": "2025-11-07T16:44:05.000Z"}, {"author": "Florian Obser", "text": "<p>I wondered if the proposal is to put 'internal 86000 IN DS .'</p>", "time": "2025-11-07T16:44:40.000Z"}, {"author": "Peter Thomassen", "text": "<p>got it</p>", "time": "2025-11-07T16:44:55.000Z"}, {"author": "Suzanne Woolf", "text": "<p>This discussion is an interesting demonstration of the kind of work that happens in DNSOP. For those who want to re-organize how DNS work is done in the IETF, how would you handle this draft? Kick it? See if the WG wants to adopt, but don't take up f2f meeting time? Kick out protocol work (maybe to DNSDEV) so there's room for it in DNSOP? Something else?</p>", "time": "2025-11-07T16:45:13.000Z"}, {"author": "Paul Hoffman", "text": "<p>\"Something else?\" Your list isn't long enough? :-)</p>", "time": "2025-11-07T16:46:40.000Z"}, {"author": "Florian Obser", "text": "<p>but this is 90% operations work. and 10% rubberstamp from the protocol wonks that this does not break stuff...</p>", "time": "2025-11-07T16:48:11.000Z"}, {"author": "Florian Obser", "text": "<p>(zonecut to nowhere I mean)</p>", "time": "2025-11-07T16:48:20.000Z"}, {"author": "Suzanne Woolf", "text": "<p>@Paul I never assume I've thought of everything, or even everything relevant ;-)</p>", "time": "2025-11-07T16:49:45.000Z"}, {"author": "Suzanne Woolf", "text": "<p>The current topic is an even better example, but I won't belabor the point.</p>", "time": "2025-11-07T16:50:57.000Z"}, {"author": "\u00c9ric Vyncke", "text": "<p>Early allocation is always possible</p>", "time": "2025-11-07T16:54:16.000Z"}, {"author": "Shumon Huque", "text": "<p>FYI, the new draft that I mentioned that defines Q and Meta-Types division for private use is: <a href=\"https://datatracker.ietf.org/doc/html/draft-huque-dnsop-private-metatypes-00\">https://datatracker.ietf.org/doc/html/draft-huque-dnsop-private-metatypes-00</a></p>", "time": "2025-11-07T16:55:07.000Z"}, {"author": "Tim Wicinski", "text": "<p>I have always been a fan of Early Allocation for work which folks are implementing</p>", "time": "2025-11-07T16:58:57.000Z"}, {"author": "Tim Wicinski", "text": "<p>but I am just me</p>", "time": "2025-11-07T16:59:04.000Z"}, {"author": "David Lawrence", "text": "<p>What's wrong with wanting my pony</p>", "time": "2025-11-07T17:06:48.000Z"}, {"author": "Ond\u0159ej Sur\u00fd", "text": "<p>Isn't that what we do here all the time?</p>", "time": "2025-11-07T17:07:10.000Z"}, {"author": "Suzanne Woolf", "text": "<p>Nothing, as long as you don't complain about not getting it ;-)</p>", "time": "2025-11-07T17:07:13.000Z"}, {"author": "Shumon Huque", "text": "<p>Mark's comment about pony refers to the Redhat situation. Does he have any comment on the other use cases? multi-signer, and provider transition across disjoint algs, and pre-publication of TAs for alg rollover?</p>", "time": "2025-11-07T17:08:52.000Z"}, {"author": "Paul Hoffman", "text": "<p>@David: Mark is arguing that not only do you want a pony, but you expect it to be alive.</p>", "time": "2025-11-07T17:12:42.000Z"}, {"author": "Paul Hoffman", "text": "<p>(Is it Friday? Did I just make a dead pony joke?)</p>", "time": "2025-11-07T17:13:12.000Z"}, {"author": "Philip Homburg", "text": "<p>In my opinion the draft goes overboard in supporting setups that don't implement all mandatory to implement algorithms.</p>", "time": "2025-11-07T17:15:26.000Z"}, {"author": "Shumon Huque", "text": "<p>Not having a way to specify private algs in DS records seems to be a protocol gap, that we should close.</p>", "time": "2025-11-07T17:20:03.000Z"}, {"author": "David Blacka", "text": "<p>Philip is describing the original reasoning for NOT including the DNS or OID in the DS in that RFC.</p>\n<p>Mark is saying that this reasoning wasn't good enough, and we should fix this.</p>\n<p>My question is: do we need backwards compatibility? Wouldn't it be possible just to update how the PrivateDNS and PrivateOID types work going forward?</p>", "time": "2025-11-07T17:21:55.000Z"}, {"author": "Philip Homburg", "text": "<p>The draft is weak on arguing what goes wrong with how it currently works. If this is a thing that only bind implements then backward compatibility is not an issue.</p>", "time": "2025-11-07T17:26:35.000Z"}, {"author": "David Blacka", "text": "<p>Sorry, Phil, I was responding your Mic comments, not chat</p>", "time": "2025-11-07T17:26:56.000Z"}, {"author": "Jim Reid", "text": "<p>why bother with _forsale in the DNS when there are platforms like ebay that specialise in selling tat?</p>", "time": "2025-11-07T17:37:38.000Z"}, {"author": "Philip Homburg", "text": "<p>That would be 'marktplaats' in .nl :-)</p>", "time": "2025-11-07T17:38:16.000Z"}, {"author": "Mike Blanche", "text": "<p>can we also have _not-forsale ?</p>", "time": "2025-11-07T17:38:19.000Z"}, {"author": "David Lawrence", "text": "<p>I'd still really, REALLY like a way to mark my domains as NOT for sale.   Marco has suggested that the way to accomplish this was to set an extremely high price and give the admonission in the draft, \"don't contact us unless you're prepapred to pay this much\" but I'd really prefer an explicit signal to brokers to just not bother (which I then expect they would ignore if they had a crazy high offer).</p>", "time": "2025-11-07T17:39:05.000Z"}, {"author": "Ted Hardie", "text": "<p>Reserving this domain name via dnsop would be a bad precedent, iin my opinion.</p>", "time": "2025-11-07T17:39:20.000Z"}, {"author": "Vicky Risk", "text": "<p>No opinion about where this belongs, but it seems like the kind of useful information that could help attract more engagement from operators. So this is like, IETF marketing....</p>", "time": "2025-11-07T17:39:20.000Z"}, {"author": "Vicky Risk", "text": "<p>which I realize does not make it attractive to a lot of people...</p>", "time": "2025-11-07T17:39:52.000Z"}, {"author": "Philip Homburg", "text": "<p>underscore labels are expert review.</p>", "time": "2025-11-07T17:44:04.000Z"}, {"author": "Ted Hardie", "text": "<p>Weirdly, that example is not traditional for the character \"xue\", even though the initial two are. \u6e05\u83ef\u5927\u5b78 is the traditional version.</p>", "time": "2025-11-07T17:44:48.000Z"}, {"author": "Marco Davids", "text": "<p>@Jim These platforms each use their own merthods, that is wat this draft is trying to address; a more universal way of selling domains names (for free, because any owner can put it up withou having to pay those companies).</p>", "time": "2025-11-07T17:45:34.000Z"}, {"author": "Marco Davids", "text": "<p>@Mike I actually had that request but decided against it - when someone wants to buy a good, even if the owener says it is for not for sale, they will probably do it anyway. But there is a hack: put if for sale for a figure with 239 digits in USD ;-)</p>", "time": "2025-11-07T17:46:31.000Z"}, {"author": "Paul Hoffman", "text": "<p>Just noting that the DBOUND WG failed a decade ago after considering this idea</p>", "time": "2025-11-07T17:47:53.000Z"}, {"author": "Philip Homburg", "text": "<p>I think (but I'm not a lawyer) that putting for sale a domain that is also a trademark could cause problems. As long as it is not for sale and just private/hobby use, it falls in a different category.</p>", "time": "2025-11-07T17:48:06.000Z"}, {"author": "Paul Hoffman", "text": "<p>s/a decade/almost a decade/   <a href=\"https://datatracker.ietf.org/group/dbound/history/\">https://datatracker.ietf.org/group/dbound/history/</a></p>", "time": "2025-11-07T17:48:37.000Z"}, {"author": "David Lawrence", "text": "<p>Yes, cold callers will do what cold callers do, which sucks.  I still think that being explicit in indicating that you are in general not interested is still useful.</p>", "time": "2025-11-07T17:48:55.000Z"}, {"author": "John Levine", "text": "<p>+2 Ondrej</p>", "time": "2025-11-07T17:50:24.000Z"}, {"author": "John Levine", "text": "<p>For years I have pointed out that it would be possible for web and mail servers to autoconfigure to handle variant domain names, but nobody has done it</p>", "time": "2025-11-07T17:51:02.000Z"}, {"author": "Marco Davids", "text": "<p>@Philip interesting, I wouldn't know but in that cae, better stick to the law and don't try to sell it.</p>", "time": "2025-11-07T17:51:10.000Z"}, {"author": "Shumon Huque", "text": "<p>I think Viktor meant DNAME, not DS</p>", "time": "2025-11-07T17:51:50.000Z"}, {"author": "John Levine", "text": "<p>DNAME, not DS</p>", "time": "2025-11-07T17:51:51.000Z"}, {"author": "Mike Blanche", "text": "<p>an \"administrative\" link is also unclear...</p>", "time": "2025-11-07T17:52:19.000Z"}, {"author": "Marco Davids", "text": "<p>@Vicky, interesting angle ;-)</p>", "time": "2025-11-07T17:52:27.000Z"}, {"author": "Ted Hardie", "text": "<p>SECDISPATCH this?</p>", "time": "2025-11-07T17:58:58.000Z"}, {"author": "Peter Thomassen", "text": "<p>The problem statement / work to be done is written down here: <a href=\"https://datatracker.ietf.org/doc/draft-fregly-research-agenda-for-pqc-dnssec/\">https://datatracker.ietf.org/doc/draft-fregly-research-agenda-for-pqc-dnssec/</a></p>", "time": "2025-11-07T18:01:04.000Z"}, {"author": "Marco Davids", "text": "<p>@David thanks</p>", "time": "2025-11-07T18:01:36.000Z"}, {"author": "Florian Obser", "text": "<p>thanks Peter, now I remember there was a thing. So I guess my feedback is, try again to get a WG</p>", "time": "2025-11-07T18:01:43.000Z"}]