<div dir="ltr"><div class="gmail_default" style="font-family:monospace">Thanks for this Shane</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">I sent you a pull request mapping some of the RFCs to part of your list.  There are definitely a few more - like Marco's suggest on the DNSSEC validating resolver draft now in WGLC in DNSOP</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">more text coming</div><div class="gmail_default" style="font-family:monospace"><br></div><div class="gmail_default" style="font-family:monospace">tim</div><div class="gmail_default" style="font-family:monospace"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 22, 2023 at 3:19 AM Shane Kerr <<a href="mailto:shane@time-travellers.org">shane@time-travellers.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Colleagues,<br>
<br>
I have no strong feelings about where a joint document should be <br>
authored, although I don't really think e-mailing around drafts of Word <br>
documents is the right solution. As a coder, I figured that of course <br>
GitHub is the simplest and most logical solution. 😉<br>
<br>
My thinking now is that we can proceed like this:<br>
<br>
* List everything that seems possibly appropriate.<br>
* Try to organize it into some sort of rough outline.<br>
* Dig into the details and discuss each of them as a group.<br>
* Assign people to do research about things that we need more knowledge <br>
about or just don't feel certain of.<br>
* Iterate until we're happy.<br>
* Champagne. 🍾<br>
<br>
To start that, I've put a brain-dump of random things that we may wish <br>
to consider in GitHub:<br>
<br>
<a href="https://github.com/DNS-Resolver-BCP-TF/Resolver-Recommendations" rel="noreferrer" target="_blank">https://github.com/DNS-Resolver-BCP-TF/Resolver-Recommendations</a><br>
<br>
My thinking right now is that anyone can make a pull request with <br>
suggested additional topics that might usefully fall under a RIPE BCP <br>
document, and we can add it to the list.<br>
<br>
I've already got a couple of issues for stuff that needs to be done <br>
based on Mattermost discussions; please don't hesitate to create an <br>
issue if you don't have time or energy to make a pull request with <br>
specific changes:<br>
<br>
<a href="https://github.com/DNS-Resolver-BCP-TF/Resolver-Recommendations/issues" rel="noreferrer" target="_blank">https://github.com/DNS-Resolver-BCP-TF/Resolver-Recommendations/issues</a><br>
<br>
Cheers,<br>
<br>
--<br>
Shane<br>
-- <br>
dns-resolver-tf mailing list<br>
<a href="mailto:dns-resolver-tf@ripe.net" target="_blank">dns-resolver-tf@ripe.net</a><br>
<a href="https://ripe.net/mailman/listinfo/dns-resolver-tf" rel="noreferrer" target="_blank">https://ripe.net/mailman/listinfo/dns-resolver-tf</a><br>
</blockquote></div>