I went through the same thing in Brussels in November, Warren :(
", "time": "2023-03-30T00:32:11Z"}, {"author": "Warren Kumari", "text": "Yah. Actually I've been in Japan since March 15th....
", "time": "2023-03-30T00:34:14Z"}, {"author": "Warren Kumari", "text": "I'm now very familiar with this hotel room... I haven't disassembled any furniture yet though...
", "time": "2023-03-30T00:35:03Z"}, {"author": "Nigel Hickson", "text": "good evening
", "time": "2023-03-30T00:37:58Z"}, {"author": "John Woodworth", "text": "Hope you feel better
", "time": "2023-03-30T00:39:06Z"}, {"author": "Warren Kumari", "text": "Thanks. I'm feeling 99% fine - that this point mostly tired of being in this room (especially because 750 of my friends are just down the road and I cannot play with them :-))
", "time": "2023-03-30T00:41:06Z"}, {"author": "Robert Wilton", "text": "Re: I haven't disassembled any furniture yet though...
\nMissed opportunity?
We do miss you Warren :-)
", "time": "2023-03-30T00:45:06Z"}, {"author": "David Lawrence", "text": "I miss Japan
", "time": "2023-03-30T00:45:17Z"}, {"author": "David Lawrence", "text": "oh and Warren I guess
", "time": "2023-03-30T00:45:22Z"}, {"author": "Warren Kumari", "text": "Gee, thanks David, I really feel the love with that comment :-P
", "time": "2023-03-30T00:46:41Z"}, {"author": "Tim Wicinski", "text": "I miss Warren and Japan. Dave, well less so
", "time": "2023-03-30T00:46:47Z"}, {"author": "Tim Wicinski", "text": "I was very excited to write up our comments into the datatracker warren, until I could not find them easily.
", "time": "2023-03-30T00:47:32Z"}, {"author": "Warren Kumari", "text": "I'm in the queue for at the end of the presentation (not a clarifying question).
", "time": "2023-03-30T00:48:22Z"}, {"author": "Suzanne Woolf", "text": "ack warren
", "time": "2023-03-30T00:49:27Z"}, {"author": "Tommy Jensen", "text": "DNS is obsolete?
", "time": "2023-03-30T00:51:16Z"}, {"author": "Tim Wicinski", "text": "Olafur told me this many times
", "time": "2023-03-30T00:51:46Z"}, {"author": "Nigel Hickson", "text": "Thought we were using DNS to connect?
", "time": "2023-03-30T00:51:56Z"}, {"author": "Tim Wicinski", "text": "Understood!
", "time": "2023-03-30T00:53:12Z"}, {"author": "Warren Kumari", "text": "Oh. Also thank you very much from me - the authors and ISE have been very patient. Also thank you to the WG for all of their time on this..
", "time": "2023-03-30T00:54:14Z"}, {"author": "Warren Kumari", "text": "The IETF decided that we didn't want to run this registry...
", "time": "2023-03-30T00:56:41Z"}, {"author": "Warren Kumari", "text": "(which I think is the right outcome)
", "time": "2023-03-30T00:56:59Z"}, {"author": "Warren Kumari", "text": "If GNU is willing to deal the legal and drama under the label, that's fine...
", "time": "2023-03-30T00:58:33Z"}, {"author": "George Michaelson", "text": "Apologies to Elliot for usurping his queue position I did not check
", "time": "2023-03-30T00:59:22Z"}, {"author": "Eliot Lear", "text": "No worries, George.
", "time": "2023-03-30T01:00:14Z"}, {"author": "Andrew Campling", "text": "The assertion on the conclusion slide that the \".alt draft would address name space conflict for use-cases
\nwhere it is a problem\" seems to be incorrect
if the PDUs are being aligned and the PDUs include unique typecodes then refusing to combine the registry is a recipe for disaster.
", "time": "2023-03-30T01:02:03Z"}, {"author": "George Michaelson", "text": "it would be increadibly helpful if IANA blocked out some window of RR types to try and prevent collision while things are worked out, or all the PDUs could have the top bit set or something? I just think this is heading to on-the-wire worst of both worlds
", "time": "2023-03-30T01:03:02Z"}, {"author": "Tim Wicinski", "text": "Well we could just ask IANA
", "time": "2023-03-30T01:04:13Z"}, {"author": "Tim Wicinski", "text": "They seem to be decent folks
", "time": "2023-03-30T01:04:21Z"}, {"author": "Anthony Somerset", "text": "Ben check your headset
", "time": "2023-03-30T01:04:33Z"}, {"author": "Daniel Migault", "text": "good!
", "time": "2023-03-30T01:04:50Z"}, {"author": "Benjamin Schwartz", "text": "MUST but we know you won't.
", "time": "2023-03-30T01:06:59Z"}, {"author": "Tim Wicinski", "text": "does anyone know the latency between a slide deck added to the meeting materials and it shows up in the meetecho materials?
", "time": "2023-03-30T01:08:09Z"}, {"author": "Benjamin Schwartz", "text": "There's a refresh button at the top of the meeting materials pane
", "time": "2023-03-30T01:08:36Z"}, {"author": "Tim Wicinski", "text": "yes but there seems to be some lag (asking for an author who just sent updates)
", "time": "2023-03-30T01:08:59Z"}, {"author": "Anthony Somerset", "text": "we can hear you
", "time": "2023-03-30T01:10:27Z"}, {"author": "Lorenzo Miniero", "text": "@Tim Wicinski when you hit refresh, the materials pane should be updated right away, as we pull changes from the datatracker. Notice that this doesn't mean we'll import the deck for sharing too: that only happens automatically before the session starts, when we convert them automatically. Decks added after the session starts must be imported manually to be used in the meeting session
", "time": "2023-03-30T01:11:52Z"}, {"author": "Tim Wicinski", "text": "Oh Thanks Lorenzo ! I will alert my co-chairs to this
", "time": "2023-03-30T01:12:58Z"}, {"author": "Andrew Campling", "text": "This seems like a great way to improve the end-user experience
", "time": "2023-03-30T01:14:53Z"}, {"author": "Anthony Somerset", "text": "there was a concern raised previously (last meeting) about ech causing headaches for filtering for schools - this looks like a good alternative solution for the problem
", "time": "2023-03-30T01:14:56Z"}, {"author": "Anthony Somerset", "text": "content filters can rather use DNS instead of HTTPS/SNI
", "time": "2023-03-30T01:15:26Z"}, {"author": "Andrew Campling", "text": "@Anthony there are downsides to using DNS rather than SNI for content filtering
", "time": "2023-03-30T01:15:47Z"}, {"author": "Anthony Somerset", "text": "especially if the browsers could directly process the EDE data without extensions etc
", "time": "2023-03-30T01:16:22Z"}, {"author": "Tommy Jensen", "text": "DNS is certainly more reliable than SNI by quite a bit... does the browser-provided hook allow interception of queries for both the browser's own DNS client and when it calls the OS resolver, or only one or the other?
", "time": "2023-03-30T01:16:44Z"}, {"author": "Benjamin Schwartz", "text": "Neither DNS nor SNI contains content, so neither can be used for _content_ filtering. They can only be used for _service_ blocking.
", "time": "2023-03-30T01:16:46Z"}, {"author": "Tommy Jensen", "text": "I'm unfamiliar with what extensions can do
", "time": "2023-03-30T01:16:58Z"}, {"author": "Benjamin Schwartz", "text": "(@Wes the buzzword is \"subresources\".)
", "time": "2023-03-30T01:18:02Z"}, {"author": "Andrew Campling", "text": "@Tommy J security s/w that uses SNI typically takes steps to verify its accuracy before using it - see our latest draft for more on this :-)
", "time": "2023-03-30T01:18:10Z"}, {"author": "Peter Thomassen", "text": "When subresources has blocked this way, the browser may opt to show whatever notification they like, e.g. around the TLS lock icon
", "time": "2023-03-30T01:18:55Z"}, {"author": "Andrew Campling", "text": "https://datatracker.ietf.org/doc/draft-campling-ech-deployment-considerations/
", "time": "2023-03-30T01:18:56Z"}, {"author": "\u00c9ric Vyncke", "text": "Interesting to see how many people are not complying with the IETF mask policy in this room :-o
", "time": "2023-03-30T01:20:27Z"}, {"author": "Anthony Somerset", "text": "@Suzanne Woolf can you give us a \"friendly\" reminder :)
", "time": "2023-03-30T01:20:55Z"}, {"author": "Tim Wicinski", "text": "\"Testy Exchanges\"
", "time": "2023-03-30T01:27:14Z"}, {"author": "Suzanne Woolf", "text": "@\u00c9ric Vyncke thanks, it's hard to see from up here.
", "time": "2023-03-30T01:27:43Z"}, {"author": "Chris Box", "text": "Isn't it common to send A and AAAA queries in parallel from a dual stack client?
", "time": "2023-03-30T01:34:27Z"}, {"author": "Tommy Jensen", "text": "Yes, at least we do for sure.
", "time": "2023-03-30T01:34:48Z"}, {"author": "David Lawrence", "text": "Common, yes, but not universal. \"Happy eyeballs.\"
", "time": "2023-03-30T01:34:54Z"}, {"author": "Yoshiro Yoneya", "text": "For the trouble shooting, people tend to refer WHOIS rather than DNS.
", "time": "2023-03-30T01:35:08Z"}, {"author": "David Lawrence", "text": "Anyway, I am 100% + extra credit in favor of my DNS not lying to me and giving me real nxd.
", "time": "2023-03-30T01:35:11Z"}, {"author": "Tommy Jensen", "text": "Oh same
", "time": "2023-03-30T01:35:36Z"}, {"author": "Mark Andrews", "text": "NXDOMAIN rcode is signed.
", "time": "2023-03-30T01:35:42Z"}, {"author": "Mark Andrews", "text": "ENT and NXDOMAIN have different responses in DNSSEC
", "time": "2023-03-30T01:36:12Z"}, {"author": "John Levine", "text": "How does he feel about RFC 8020:?
", "time": "2023-03-30T01:38:29Z"}, {"author": "Tim Wicinski", "text": "The document does not mention RFC8020
", "time": "2023-03-30T01:39:28Z"}, {"author": "David Lawrence", "text": "Adopt!
", "time": "2023-03-30T01:40:19Z"}, {"author": "Tim Wicinski", "text": "I am always of the opinion of make Shumon do more work.
", "time": "2023-03-30T01:40:54Z"}, {"author": "Yoshitaka Aharen", "text": "would be better to mention RFC8198 (Aggressive Use of DNSSEC-Validated Cache)?
", "time": "2023-03-30T01:41:20Z"}, {"author": "Shane Kerr", "text": "We (NS1) can quickly change our implementation, for some definition of \"quickly\". ;-)
", "time": "2023-03-30T01:46:01Z"}, {"author": "Wataru Ohgai", "text": "How can resolvers cache these types of answers? All abide by negative cache TTL?
", "time": "2023-03-30T01:47:39Z"}, {"author": "Andrew Fregly", "text": "It is not just a few bytes. For signed DNSSEC responses with PQC algorithms, it could be thousands of bytes.
", "time": "2023-03-30T01:48:21Z"}, {"author": "Anthony Somerset", "text": "is the benefit saving data in the response or reduced signing operations?
", "time": "2023-03-30T01:48:29Z"}, {"author": "David Lawrence", "text": "YUP. But the vendors gonna vend so.
", "time": "2023-03-30T01:48:44Z"}, {"author": "David Lawrence", "text": "Either way, some one is coding to deal with it, and currently the burden is on the larger set of clients
", "time": "2023-03-30T01:51:58Z"}, {"author": "Andrew Fregly", "text": "Since it has been implemented already, it seems the coding issue has been solved.
", "time": "2023-03-30T01:52:45Z"}, {"author": "Jim Reid", "text": "Andrew by the time PQC DNSSEC becomes a thing, queries will mostly be over DoQH => few fragmentation or truncation issues.
", "time": "2023-03-30T01:55:01Z"}, {"author": "Jim Reid", "text": "Faking a signed response on the fly opens a new vector for DOS attacks. I'm not sure that's worth the benefit of slimmer responses to some queries. YMMV.
", "time": "2023-03-30T01:57:15Z"}, {"author": "Andrew Fregly", "text": "Jim, we should discuss offline. I have been pushing back in various public forums that we don't know enough to state that queries will mostly be over OoQH, particularly for resolver to authoritative queries.
", "time": "2023-03-30T01:59:03Z"}, {"author": "Andrew Fregly", "text": "See my talks at the PQNET Workshop in November and DNS-OARC 40
", "time": "2023-03-30T01:59:37Z"}, {"author": "Jim Reid", "text": "OK Andrew.
", "time": "2023-03-30T02:03:49Z"}, {"author": "David Lawrence", "text": "Hmmm, the assertion that all zones use notify is overstated. Not to detract from the overall point tho.
", "time": "2023-03-30T02:11:17Z"}, {"author": "Shane Kerr", "text": "We use a \"service\" not a name server for our XFR stuff too, so that is not necessarily new.
", "time": "2023-03-30T02:20:27Z"}, {"author": "Yoshitaka Aharen", "text": "server implementations need another ACL for new NOTIFYs in addition to existing ACL of NOTIFY(SOA) which typically allows to replicas
", "time": "2023-03-30T02:21:17Z"}, {"author": "Shane Kerr", "text": "Good point about UDP as a transport. If it's new, we could require non-UDP transports. :-)
", "time": "2023-03-30T02:21:49Z"}, {"author": "Peter Thomassen", "text": "@Shane, your XFR service comment: yes, ack
", "time": "2023-03-30T02:22:06Z"}, {"author": "Erik Nygren", "text": "I wonder if using SVCB records would make sense for specifying the NOTIFY endpoint, protocol, etc?
", "time": "2023-03-30T02:23:46Z"}, {"author": "David Lawrence", "text": "Zzzzz
", "time": "2023-03-30T02:30:07Z"}, {"author": "Alexander Clouter", "text": "over in dnssd they have published 'push notifications' for DNS (RFC 8765) and also draft-ietf-dnssd-update-lease-06 for self expiring records, which could be used for signally maybe more inbound?
", "time": "2023-03-30T02:30:08Z"}, {"author": "Chris Box", "text": "NOTIFY(LUNCHBREAK)
", "time": "2023-03-30T02:30:09Z"}, {"author": "Shane Kerr", "text": "@erik it might!
", "time": "2023-03-30T02:30:10Z"}, {"author": "Tim Wicinski", "text": "Thanks everyone for being here and big thanks to Lorenzo for helping us chairs out!
", "time": "2023-03-30T02:30:15Z"}, {"author": "Tommy Jensen", "text": "NOTIFY(DINNER)
", "time": "2023-03-30T02:30:23Z"}, {"author": "David Lawrence", "text": "See you in add @ 3:30 am! (tzset...)
", "time": "2023-03-30T02:30:29Z"}, {"author": "Alexander Clouter", "text": "NOTIFY(BED)
", "time": "2023-03-30T02:30:33Z"}, {"author": "Tim Wicinski", "text": "ZZZZzzzz
", "time": "2023-03-30T02:30:39Z"}]