[{"author": "\u00c9ric Vyncke", "text": "Is Benno's voice OK on remote ?<br/>", "time": "2022-03-24T13:32:03Z"}, {"author": "Joey Salazar", "text": "it is<br/>", "time": "2022-03-24T13:32:14Z"}, {"author": "\u00c9ric Vyncke", "text": "thanks<br/>", "time": "2022-03-24T13:32:27Z"}, {"author": "Glenn Deen", "text": "is there a reason most of the in room local people are one side of the room?<br/>", "time": "2022-03-24T13:32:44Z"}, {"author": "Chris Box", "text": "I can move if it makes you feel better Glenn<br/>", "time": "2022-03-24T13:33:34Z"}, {"author": "Andrew Campling", "text": "@Gllenn totally random<br/>", "time": "2022-03-24T13:33:53Z"}, {"author": "Tim Wicinski", "text": "Minutes kept at <a href=\"https://notes.ietf.org/notes-ietf-113-add?edit\" rel=\"nofollow\">https://notes.ietf.org/notes-ietf-113-add?edit</a><br/>", "time": "2022-03-24T13:33:57Z"}, {"author": "Peter van Dijk", "text": "there are some high-value authoritatives with 853 out there already - like for facebook.com<br/>", "time": "2022-03-24T13:42:06Z"}, {"author": "Glenn Deen", "text": "@Chris - just wanted to keep it visually balanced for the recording.<br/>", "time": "2022-03-24T13:42:18Z"}, {"author": "Jim Reid", "text": "If someone tilts the camera, people might shift to the other side of the room Glenn.<br/>", "time": "2022-03-24T13:43:50Z"}, {"author": "Ted Hardie", "text": "I'm always a bit squicked by MUST NOTs like this in 3.3; \"such a server MUST NOT serve resource records that differ based on SNI (or on the lack of SNI) provided by the client,\".&nbsp;&nbsp;Is there any reasonable way for the client to tell this?&nbsp;&nbsp;Or is this&nbsp;&nbsp;a \"don't do this, but we know you will\"?<br/>", "time": "2022-03-24T13:44:59Z"}, {"author": "\u00c9ric Vyncke", "text": "@Jim: prefix your wish with meetecho ;-)<br/>", "time": "2022-03-24T13:45:18Z"}, {"author": "Christopher Inacio", "text": "@dkg - are you using the issues in gitlab to track issues?<br/>", "time": "2022-03-24T13:45:19Z"}, {"author": "Benjamin Schwartz", "text": "Ted: Varying server behavior based on SNI is not trivial to implement, so it's unlikely to happen by accident.<br/>", "time": "2022-03-24T13:45:35Z"}, {"author": "Ted Hardie", "text": "@Benjamin Schwartz I agree that it is not likely to be an accident.<br/>", "time": "2022-03-24T13:45:57Z"}, {"author": "Joey Salazar", "text": "@Christopher Inacio yes we are<br/>", "time": "2022-03-24T13:46:08Z"}, {"author": "Joey Salazar", "text": "<a href=\"https://gitlab.com/dkg/dprive-unilateral-probing\" rel=\"nofollow\">https://gitlab.com/dkg/dprive-unilateral-probing</a><br/>", "time": "2022-03-24T13:46:26Z"}, {"author": "Benjamin Schwartz", "text": "Ted: It may not be detectable by the client (i.e. resolver), but it will break resolution so it will be detectable by the zone's helpdesk.<br/>", "time": "2022-03-24T13:46:53Z"}, {"author": "dkg", "text": "fully agreed with mapping mailing list issues to the issue tracker<br/>", "time": "2022-03-24T13:47:02Z"}, {"author": "Christopher Inacio", "text": "@joey thanks - looking at it now, just comparing against the fixme's<br/>", "time": "2022-03-24T13:47:04Z"}, {"author": "Joey Salazar", "text": "we encourage ml reviews that include/summarize the created gitlab issues<br/>", "time": "2022-03-24T13:47:10Z"}, {"author": "Christopher Inacio", "text": "@joey, dkg - ack<br/>", "time": "2022-03-24T13:47:22Z"}, {"author": "Peter van Dijk", "text": "+1 to dkg's answers here<br/>", "time": "2022-03-24T13:51:41Z"}, {"author": "Christian Huitema", "text": "The bar should be, \"as good or better than DNS cookies\". I think it is met.<br/>", "time": "2022-03-24T13:52:44Z"}, {"author": "Jim Reid", "text": "+1 Christian<br/>", "time": "2022-03-24T13:53:04Z"}, {"author": "Brian Haberman", "text": "@ekr May be worth creating two issues so we can track them in the WG discussion of the draft.<br/>", "time": "2022-03-24T13:58:00Z"}, {"author": "ekr@jabber.org", "text": "It's worth noting that as bemasc points out, self-signed certs are very slightly a move towards the direction of DANE<br/>", "time": "2022-03-24T14:00:36Z"}, {"author": "Benjamin Schwartz", "text": "ekr: I do think that's pretty slight.&nbsp;&nbsp;For anyone who wants to use WebPKI, there's no barrier in this draft.<br/>", "time": "2022-03-24T14:01:44Z"}, {"author": "ekr@jabber.org", "text": "@bemasc: yes, I agree with that as well.<br/>", "time": "2022-03-24T14:01:56Z"}, {"author": "Christian Huitema", "text": "In practice, the easy alternative are let's encrypt and self signed. LE is probably slightly easier, so I predict it will see deployment<br/>", "time": "2022-03-24T14:02:10Z"}, {"author": "Wes Hardaker", "text": "grumpy view ha ha: there have definitely been documents in the IETF that were designed to get in the way of future things :-/<br/>", "time": "2022-03-24T14:02:20Z"}, {"author": "Peter van Dijk", "text": "I have a non-exhaustive list, even ;)<br/>", "time": "2022-03-24T14:02:48Z"}, {"author": "Christian Huitema", "text": "Unilateral subsumes \"unauthenticated\".<br/>", "time": "2022-03-24T14:03:35Z"}, {"author": "Chris Box", "text": "Paul's \"let's use obviously wrong self-signed certs\" makes sense to me. For example CN = i-am-an-authoritative-DNS-server<br/>", "time": "2022-03-24T14:03:52Z"}, {"author": "Christian Huitema", "text": "You could do that. Or you could host a tiny web server for the purpose of making let's Encrypt work, use the resulting cert in DoQ/DoT, and see it work with most TLS stacks...<br/>", "time": "2022-03-24T14:05:24Z"}, {"author": "Kevin Fleming", "text": "i use LE certs without any web server at all (using the DNS challenge method, although that could be a chicken-and-egg issue here)<br/>", "time": "2022-03-24T14:06:01Z"}, {"author": "Christian Huitema", "text": "It absolutely has a chicken-and-egg issue. That's what should drive the further work, eventually.<br/>", "time": "2022-03-24T14:06:45Z"}, {"author": "\u00c9ric Vyncke", "text": "@Paul I agree for intended status, let's explore how can be done w/o too many efforts<br/>", "time": "2022-03-24T14:07:50Z"}, {"author": "Tim Wicinski", "text": "Thanks all for working with us <br/>", "time": "2022-03-24T14:10:44Z"}, {"author": "\u00c9ric Vyncke", "text": "Thank you Brian &amp; Tim !<br/>", "time": "2022-03-24T14:10:47Z"}, {"author": "Tommy Pauly", "text": "If only this was the first session to get up for...<br/>", "time": "2022-03-24T14:14:40Z"}, {"author": "Wes Hardaker", "text": "then why did I get up at 01:30?<br/>", "time": "2022-03-24T14:14:48Z"}, {"author": "Glenn Deen", "text": "----- ADD Session from here -----<br/>", "time": "2022-03-24T14:14:57Z"}, {"author": "Tommy Pauly", "text": "I'm just being silly =) lack of sleep<br/>", "time": "2022-03-24T14:15:29Z"}, {"author": "dkg", "text": "DPRIVE holdover: i just opened <a href=\"https://gitlab.com/dkg/dprive-unilateral-probing/-/issues/11\" rel=\"nofollow\">https://gitlab.com/dkg/dprive-unilateral-probing/-/issues/11</a> to record suggestions about draft framing that came up in the meeting just now<br/>", "time": "2022-03-24T14:15:30Z"}, {"author": "dkg", "text": "sorry for the delay in the slide upload<br/>", "time": "2022-03-24T14:16:29Z"}, {"author": "Tommy Jensen", "text": "\"You can see the sun?\" -- live from Redmond<br/>", "time": "2022-03-24T14:17:15Z"}, {"author": "dkg", "text": "David, there are 111 people here.&nbsp;&nbsp;please don't leave newcomers in the dark.<br/>", "time": "2022-03-24T14:18:01Z"}, {"author": "David Lawrence", "text": "Mixed precip here in Vermont on top of the worst mud season we've had in years and years.<br/>", "time": "2022-03-24T14:18:03Z"}, {"author": "\u00c9ric Vyncke", "text": ":-(<br/>", "time": "2022-03-24T14:18:27Z"}, {"author": "dkg", "text": "saying \"everyone already knows me\" can make a newcomer feel unwelcome and left out, and it doesn't hurt to just do a reintroduction even if everyone does already know you.<br/>", "time": "2022-03-24T14:18:44Z"}, {"author": "David Lawrence", "text": "Apologies, I didn't mean to sounds as flippant there as I ended up sounding.&nbsp;&nbsp; You're right, dkg, I should be mindful that there are always new people coming in.&nbsp;&nbsp;We hope.<br/>", "time": "2022-03-24T14:18:52Z"}, {"author": "dkg", "text": "that's the goal :)<br/>", "time": "2022-03-24T14:19:03Z"}, {"author": "\u00c9ric Vyncke", "text": "Thanks for the 2 notes indeed<br/>", "time": "2022-03-24T14:19:17Z"}, {"author": "David Lawrence", "text": "So for anyone who is new and wants to know more about me (or Glenn), please feel free to say hi and I'll be happy to talk.<br/>", "time": "2022-03-24T14:19:43Z"}, {"author": "ekr@jabber.org", "text": "What if I'm not new and wants to know more about you<br/>", "time": "2022-03-24T14:19:59Z"}, {"author": "David Lawrence", "text": "(Tired here.&nbsp;&nbsp;Long week of getting up at 4am for IETF.)<br/>", "time": "2022-03-24T14:20:00Z"}, {"author": "Andrew Campling", "text": "@Dave, dkg: based on co-hosting the newcomers\u2019 breakfast this morning, there are indeed newcomers so being mindful of them is much appreciated<br/>", "time": "2022-03-24T14:20:24Z"}, {"author": "David Lawrence", "text": "I'll be happy to talk with you too, ekr. :)<br/>", "time": "2022-03-24T14:20:30Z"}, {"author": "Kevin Fleming", "text": "the initialisms for the work in this group are most excellent and have so many meanings :-)<br/>", "time": "2022-03-24T14:20:55Z"}, {"author": "David Lawrence", "text": "DDR *always* makes me think of Dance Dance Revolution.<br/>", "time": "2022-03-24T14:21:20Z"}, {"author": "Kevin Fleming", "text": "yes<br/>", "time": "2022-03-24T14:21:26Z"}, {"author": "David Lawrence", "text": "and DNR has some sad medical overtones<br/>", "time": "2022-03-24T14:21:47Z"}, {"author": "Tommy Jensen", "text": "My coworkers remind me DDR has other meaning in the context of Europe, but I too think of the game.<br/>", "time": "2022-03-24T14:22:14Z"}, {"author": "Eric Orth", "text": "Didn't the DDR slides at the last IETF have a bunch of Dance Dance Revolution imagery?<br/>", "time": "2022-03-24T14:22:51Z"}, {"author": "Andrew Campling", "text": "@meetecho comments from the in-room mic into the room seem pretty quiet<br/>", "time": "2022-03-24T14:23:03Z"}, {"author": "Meetecho", "text": "Andrew: do you mean quiet for local participants, or remote?<br/>", "time": "2022-03-24T14:23:46Z"}, {"author": "Meetecho", "text": "And just that mic, or all of them?<br/>", "time": "2022-03-24T14:24:07Z"}, {"author": "Andrew Campling", "text": "@meetecho quiet for local participants<br/>", "time": "2022-03-24T14:24:32Z"}, {"author": "Chris Box", "text": "Chair mike sounds quiet to me in the room too<br/>", "time": "2022-03-24T14:24:46Z"}, {"author": "Andrew Campling", "text": "+1 to the chair mike too<br/>", "time": "2022-03-24T14:25:12Z"}, {"author": "Vicky Risk", "text": "I can see the agenda deck above the rest of the slides. The agenda is also in the note taking pad<br/>", "time": "2022-03-24T14:26:22Z"}, {"author": "Meetecho", "text": "Since we're using the ADD working group for the room, we only pull materials from there<br/>", "time": "2022-03-24T14:27:11Z"}, {"author": "Meetecho", "text": "So the DPRIVE slides won't be available in the slide share feature<br/>", "time": "2022-03-24T14:27:24Z"}, {"author": "Meetecho", "text": "From settings / manage slides, though, you can also upload PDF files manually<br/>", "time": "2022-03-24T14:27:56Z"}, {"author": "Benjamin Schwartz", "text": "Wow<br/>", "time": "2022-03-24T14:29:01Z"}, {"author": "Eric Orth", "text": "My eyes hurt.<br/>", "time": "2022-03-24T14:29:08Z"}, {"author": "Andrew Campling", "text": "A new encoding option?<br/>", "time": "2022-03-24T14:29:23Z"}, {"author": "Tommy Jensen", "text": "DNS over Cuneiform<br/>", "time": "2022-03-24T14:29:39Z"}, {"author": "Christian Huitema", "text": "The new ComicSans!<br/>", "time": "2022-03-24T14:29:41Z"}, {"author": "Vicky Risk", "text": "readable <a href=\"https://datatracker.ietf.org/meeting/113/materials/slides-113-add-i-noticed-these-arent-posted-yet-split-horizon-dns-configuration/\" rel=\"nofollow\">https://datatracker.ietf.org/meeting/113/materials/slides-113-add-i-noticed-these-arent-posted-yet-split-horizon-dns-configuration/</a><br/>", "time": "2022-03-24T14:29:46Z"}, {"author": "David Lawrence", "text": "Cuneiform<br/>", "time": "2022-03-24T14:29:52Z"}, {"author": "Erik Nygren", "text": "Or some alien font.&nbsp;&nbsp;Split event horizon.<br/>", "time": "2022-03-24T14:30:10Z"}, {"author": "David Lawrence", "text": "Oops, Tommy beat me to it<br/>", "time": "2022-03-24T14:30:10Z"}, {"author": "Chris Box", "text": "Thanks Vicky. And I like \"Verified Split Horizon\" as a title.<br/>", "time": "2022-03-24T14:30:41Z"}, {"author": "Tommy Jensen", "text": "Dave I'm grateful you confirmed my spelling which I did not check<br/>", "time": "2022-03-24T14:31:24Z"}, {"author": "Tommy Jensen", "text": "(I like the scope clarification, thanks for the updates Dan)<br/>", "time": "2022-03-24T14:32:07Z"}, {"author": "Chris Box", "text": "Ben's title also works, and has the benefit of being more precise, but I wonder whether keeping \"split horizon\" in the title will help people find it?<br/>", "time": "2022-03-24T14:33:32Z"}, {"author": "dkg", "text": "does anyone else hear helicopters whenever Dan Wing talks?<br/>", "time": "2022-03-24T14:35:12Z"}, {"author": "Benjamin Schwartz", "text": "It was better before<br/>", "time": "2022-03-24T14:35:21Z"}, {"author": "Andrew Campling", "text": "Definitely some background crackle<br/>", "time": "2022-03-24T14:35:31Z"}, {"author": "dkg", "text": "better helicopters or better non-helicopters?<br/>", "time": "2022-03-24T14:35:43Z"}, {"author": "David Lawrence", "text": "Just crackle distortion, no choppers<br/>", "time": "2022-03-24T14:36:21Z"}, {"author": "Kevin Fleming", "text": "@dkg: i was hearing the same distortion during the DPRIVE session, but then it went away<br/>", "time": "2022-03-24T14:36:40Z"}, {"author": "Vicky Risk", "text": "+1 'split' or 'split horizon' is helpful in the name<br/>", "time": "2022-03-24T14:37:45Z"}, {"author": "Wes Hardaker", "text": "it might be helpful for Dan to mute and then unmute -- that can fix problems like that.<br/>", "time": "2022-03-24T14:39:32Z"}, {"author": "Wes Hardaker", "text": "(sometimes)<br/>", "time": "2022-03-24T14:39:36Z"}, {"author": "Andrew Campling", "text": "+1 on keeping a reference to split in the title<br/>", "time": "2022-03-24T14:39:58Z"}, {"author": "\u00c9ric Vyncke", "text": "++<br/>", "time": "2022-03-24T14:41:27Z"}, {"author": "Benjamin Schwartz", "text": "ekr: The internal one can probably just act as a recursive resolver for all the public names<br/>", "time": "2022-03-24T14:41:50Z"}, {"author": "David Lawrence", "text": "split-horizon probably helps best for SEO-type issues, as Chris suggested<br/>", "time": "2022-03-24T14:42:44Z"}, {"author": "\u00c9ric Vyncke", "text": "typing noisein the background...<br/>", "time": "2022-03-24T14:42:45Z"}, {"author": "Chris Box", "text": "Perhaps Dan?<br/>", "time": "2022-03-24T14:42:55Z"}, {"author": "Tommy Pauly", "text": "@dan is that you typing?<br/>", "time": "2022-03-24T14:42:57Z"}, {"author": "Glenn Deen", "text": "is chair audio still low for those in the room?<br/>", "time": "2022-03-24T14:43:52Z"}, {"author": "\u00c9ric Vyncke", "text": "Your audio is fine Glenn<br/>", "time": "2022-03-24T14:44:26Z"}, {"author": "Chris Box", "text": "Your audio was never a problem, it was audio from the mics in the room; and no-one has spoken into those recently<br/>", "time": "2022-03-24T14:44:34Z"}, {"author": "dkg", "text": "are there any other PvD attributes that claim some sort of exclusive access?<br/>", "time": "2022-03-24T14:47:15Z"}, {"author": "Tommy Pauly", "text": "No, there aren't any existing ones<br/>", "time": "2022-03-24T14:48:10Z"}, {"author": "dkg", "text": "that makes it very odd semantically<br/>", "time": "2022-03-24T14:48:26Z"}, {"author": "Eric Orth", "text": "+1 to Tommy's point.&nbsp;&nbsp;I think most non-network-managed clients are going to ignore any similar flags unless they run into adversarial interference so good to make things more explicitly around that.<br/>", "time": "2022-03-24T14:49:07Z"}, {"author": "Tommy Jensen", "text": "+1 as well, describing network behavior seems to be more productive than prescribing client behavior and in line with previous discussions near this point.<br/>", "time": "2022-03-24T14:50:02Z"}, {"author": "dkg", "text": "+1 as well<br/>", "time": "2022-03-24T14:50:19Z"}, {"author": "Christian Huitema", "text": "+1<br/>", "time": "2022-03-24T14:50:26Z"}, {"author": "Christian Huitema", "text": "Basic problem is the network does control the Wi-Fi network, does not control cellular connection. The device in theory could always run DNS over cellular, and unless the devic eis fully controlled there is no way to block that.<br/>", "time": "2022-03-24T14:51:49Z"}, {"author": "dkg", "text": "and you cannot know that, as the network operator<br/>", "time": "2022-03-24T14:52:40Z"}, {"author": "dkg", "text": "it's pretty hard to not characterize this as \"when i block the user from using the network as they choose, they get confused and frustrated\"<br/>", "time": "2022-03-24T14:53:12Z"}, {"author": "Christian Huitema", "text": ":-)<br/>", "time": "2022-03-24T14:53:38Z"}, {"author": "Christian Huitema", "text": "Should we have an IETF position on not endorsing perimeter based security?<br/>", "time": "2022-03-24T14:54:27Z"}, {"author": "dkg", "text": "\"the user is willing to agree\" is a tough interpretaton of the usual UI/UX modal interruption<br/>", "time": "2022-03-24T14:54:39Z"}, {"author": "dkg", "text": "most users see such an interruption as \"to get your work done, blah blah blah [OK] [cancel]\"<br/>", "time": "2022-03-24T14:55:02Z"}, {"author": "Peter Hessler", "text": "aka, the ssl warning click-through<br/>", "time": "2022-03-24T14:55:34Z"}, {"author": "dkg", "text": "among many others<br/>", "time": "2022-03-24T14:56:06Z"}, {"author": "Tommy Jensen", "text": "@christian: that would be lovely<br/>", "time": "2022-03-24T14:56:16Z"}, {"author": "Christian Huitema", "text": "Perimeter security belongs to the old \"inadequate but marketable\" legacy...<br/>", "time": "2022-03-24T14:56:48Z"}, {"author": "Andrew Campling", "text": "@Christian I image malware developers would welcome such a move, ditto surveillance capitalists and others<br/>", "time": "2022-03-24T14:58:22Z"}, {"author": "Christian Huitema", "text": "@andrew look at zero trust for the actual security response. Or at various ransomware attacks for the inadequacy of perimeter security.<br/>", "time": "2022-03-24T14:59:48Z"}, {"author": "Chris Box", "text": "In the spirit of bind.version, perhaps we should add to RESINFO response a list of CVEs to which this resolver is currently vulnerable. :-)<br/>", "time": "2022-03-24T15:01:14Z"}, {"author": "Andrew Campling", "text": "@Christian: not suggesting using it in isolation<br/>", "time": "2022-03-24T15:01:24Z"}, {"author": "Brett Carr", "text": "I've not read this draft (disclosure), but instead of a new record could we use HINFO (Shows my age)<br/>", "time": "2022-03-24T15:02:45Z"}, {"author": "Tommy Jensen", "text": "@chris if it claims vulnerability to a CVE that it was already patched for, is that legally misleading the user?<br/>", "time": "2022-03-24T15:03:35Z"}, {"author": "Chris Box", "text": "Sounds like a honeypot<br/>", "time": "2022-03-24T15:04:26Z"}, {"author": "Tommy Pauly", "text": "I don't see us using this info in the UI<br/>", "time": "2022-03-24T15:04:29Z"}, {"author": "Tommy Jensen", "text": "Neither does the other Tommy<br/>", "time": "2022-03-24T15:04:45Z"}, {"author": "dkg", "text": "the binding ekr is talking about needs to go in the opposite direction<br/>", "time": "2022-03-24T15:05:02Z"}, {"author": "Benjamin Schwartz", "text": "I really think about this as just for debugging.&nbsp;&nbsp;That might point toward it being less machine-readable.<br/>", "time": "2022-03-24T15:05:11Z"}, {"author": "Eric Orth", "text": "I can't think of any use for this directly in Chrome.&nbsp;&nbsp;All I can come up with is that it might be useful for manually debugging/querying.<br/>", "time": "2022-03-24T15:05:32Z"}, {"author": "Jim Reid", "text": "@ Brett, is HINFO still a thing?<br/>", "time": "2022-03-24T15:05:53Z"}, {"author": "Brett Carr", "text": "efforts to increase ease of dns debugging are very much a good idea :)<br/>", "time": "2022-03-24T15:05:57Z"}, {"author": "dkg", "text": "+1 for debugging info<br/>", "time": "2022-03-24T15:06:25Z"}, {"author": "ekr@jabber.org", "text": "@dkg: yeah, what I'm saying is that I join the network, it says \"go over here to find my policies\". What we would need is if the client shows that information it needs to validate that the person asserting the policies asserts that this server is its own<br/>", "time": "2022-03-24T15:06:34Z"}, {"author": "Tommy Jensen", "text": "+1 to ekr, now there's a whole new chain of trust to build.<br/>", "time": "2022-03-24T15:07:01Z"}, {"author": "dkg", "text": "and another round trip, probably<br/>", "time": "2022-03-24T15:07:14Z"}, {"author": "Brett Carr", "text": "@Jim still exists as a record type AFAIK but is never used hence my suggestion of re-using ut instead of inventing a new one<br/>", "time": "2022-03-24T15:07:37Z"}, {"author": "dkg", "text": "Brett Carr: does \"never used\" mean never published or never queried?<br/>", "time": "2022-03-24T15:08:29Z"}, {"author": "\u00c9ric Vyncke", "text": "I should read the I-D but is it relevant for IPv6 only&nbsp;&nbsp;network ?<br/>", "time": "2022-03-24T15:10:17Z"}, {"author": "Eric Orth", "text": "I have expressed support for adoption of this before, and I still support it.&nbsp;&nbsp;I don't have much else to say.<br/>", "time": "2022-03-24T15:11:04Z"}, {"author": "Jim Reid", "text": "The RESINFO's JSON goop will likely be much richer than anything HINFO can do.<br/>", "time": "2022-03-24T15:11:33Z"}, {"author": "Erik Nygren", "text": "@\u00c9ric: I worry that DDR is a big problem for IPv6-only networks with forwarders.&nbsp;&nbsp;I think we may need a solution there.&nbsp;&nbsp;For example, if we adopt this draft should it also apply to resolvers on the same (/64?) as the client.<br/>", "time": "2022-03-24T15:14:30Z"}, {"author": "\u00c9ric Vyncke", "text": "@Erik good Q indeed<br/>", "time": "2022-03-24T15:14:55Z"}, {"author": "Peter Hessler", "text": "@Erik anecdotal data, but my ISP gives me an IPv6 resolver that happens to have the same IP address as the gateway; so that would be helpful in this case<br/>", "time": "2022-03-24T15:16:23Z"}, {"author": "Erik Nygren", "text": "@Peter: is that a global address?<br/>", "time": "2022-03-24T15:19:27Z"}, {"author": "Peter Hessler", "text": "yes it is<br/>", "time": "2022-03-24T15:19:46Z"}, {"author": "Peter Hessler", "text": "sorry, meant to say that<br/>", "time": "2022-03-24T15:19:54Z"}, {"author": "Nicolai Leymann", "text": "We use a link local IPv6 Address for address resolution in the local network for residential customers.<br/>", "time": "2022-03-24T15:19:59Z"}, {"author": "Erik Nygren", "text": "Nicolai: how does that work interface scope-wise?<br/>", "time": "2022-03-24T15:20:58Z"}, {"author": "Peter Hessler", "text": "the client knows what interface they received the slaac or dhcpv6 announcement on, so they can use that when configuring dns information.&nbsp;&nbsp;or, if it was added manually, then the host admin will need to add that by hand.<br/>", "time": "2022-03-24T15:22:34Z"}, {"author": "Erik Nygren", "text": "permissions issues, I think<br/>", "time": "2022-03-24T15:24:27Z"}, {"author": "\u00c9ric Vyncke", "text": "As the AD, I am interested to know whether putting ADD/DPRIVE in the same slot is interesting (time efficiency and agenda conflict reduction). Over email preferred (unicast or mailing list).<br/>", "time": "2022-03-24T15:25:09Z"}, {"author": "Glenn Deen", "text": "@EV - only would work again if the tools supported splitting better.<br/>", "time": "2022-03-24T15:26:03Z"}, {"author": "Kevin Fleming", "text": "as a relative newcomer who had just started lurking in DPRIVE and was not aware of ADD at all, this worked out quite well for me and I'll now start lurking in ADD as well<br/>", "time": "2022-03-24T15:26:07Z"}, {"author": "Tim Wicinski", "text": "all lurkers welcome!<br/>", "time": "2022-03-24T15:26:31Z"}, {"author": "Tommy Jensen", "text": "Excellent; welcome, Kevin! Not too long ago I too lurked.<br/>", "time": "2022-03-24T15:26:54Z"}, {"author": "Glenn Deen", "text": "that should be an IETF shirt - Lurkers most welcome<br/>", "time": "2022-03-24T15:26:58Z"}, {"author": "Kevin Fleming", "text": "probably shouldn't use the word 'public' here, but 'global scope' instead?<br/>", "time": "2022-03-24T15:27:23Z"}, {"author": "Tommy Jensen", "text": "+1 to what Ben exactly just said: \"closeness\" is not a metric I want to rely on<br/>", "time": "2022-03-24T15:27:43Z"}, {"author": "Tommy Jensen", "text": "@glenn I'd wear that, presuming I ever get to attend in person to show it off to anyone but my dog :(<br/>", "time": "2022-03-24T15:28:23Z"}, {"author": "Peter Hessler", "text": "scope is trivial for clients.&nbsp;&nbsp;they have to know the interface they learned it from<br/>", "time": "2022-03-24T15:28:40Z"}, {"author": "Kevin Fleming", "text": "weirdos like me use global-scope IPv6 addresses as *anycast* to reach in-network resolvers, so link-local-scope would not work there<br/>", "time": "2022-03-24T15:28:48Z"}, {"author": "Tim Wicinski", "text": "Gold Stars all around!<br/>", "time": "2022-03-24T15:30:04Z"}, {"author": "\u00c9ric Vyncke", "text": "Thanks to the chairs &amp; delegates<br/>", "time": "2022-03-24T15:30:15Z"}, {"author": "Tommy Jensen", "text": "Thanks, take care!<br/>", "time": "2022-03-24T15:30:19Z"}, {"author": "Peter Hessler", "text": "thanks all!<br/>", "time": "2022-03-24T15:30:20Z"}, {"author": "Andrew Campling", "text": "Thanks co-chairs<br/>", "time": "2022-03-24T15:30:23Z"}]