<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
This is not a good survey... </div>
<ol start="1" data-editing-info="{"applyListStyleFromLevel":false,"orderedStyleType":3}">
<li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0); list-style-type: "1) ";">
<div class="elementToProof">The 2025 US Executive orders point to a dead links. Use the Federal Registrar link as it should be there long-term.
<span style="font-size: 18.6667px; background-color: rgb(255, 255, 255);"><a href="https://public-inspection.federalregister.gov/2025-01470.pdf" target="_blank" id="LPlnk" class="OWAAutoLink" title="https://public-inspection.federalregister.gov/2025-01470.pdf" rel="noopener noreferrer" data-olk-copy-source="MessageBody" data-linkindex="0" data-auth="NotApplicable" style="margin: 0px; background-color: rgb(255, 255, 255); text-align: left;">2025-01470.pdf</a>
CISA <a href="https://www.federalregister.gov/documents/2021/05/17/2021-10460/improving-the-nations-cybersecurity" id="LPlnk" class="OWAAutoLink" style="background-color: rgb(255, 255, 255);">Federal Register :: Improving the Nation's Cybersecurity</a></span></div>
<div class="_Entity _EType_OWALinkPreview _EId_OWALinkPreview_1 _EReadonly_1">
<div id="LPBorder_GTaHR0cHM6Ly93d3cuZmVkZXJhbHJlZ2lzdGVyLmdvdi9kb2N1bWVudHMvMjAyMS8wNS8xNy8yMDIxLTEwNDYwL2ltcHJvdmluZy10aGUtbmF0aW9ucy1jeWJlcnNlY3VyaXR5" class="LPBorder318533" style="width: 100%; margin-top: 16px; margin-bottom: 16px; position: relative; max-width: 800px; min-width: 424px;">
<table id="LPContainer318533" role="presentation" style="padding: 12px 36px 12px 12px; width: 100%; border-width: 1px; border-style: solid; border-color: rgb(200, 200, 200); border-radius: 2px;">
<tbody>
<tr valign="top" style="border-spacing: 0px;">
<td>
<div id="LPImageContainer318533" style="position: relative; margin-right: 12px; height: 57.6923px; overflow: hidden; width: 240px;">
<a target="_blank" id="LPImageAnchor318533" href="https://www.federalregister.gov/documents/2021/05/17/2021-10460/improving-the-nations-cybersecurity"><img id="LPThumbnailImageId318533" alt="" height="57" style="display: block;" width="240" src="https://www.federalregister.gov/assets/open_graph_site_banner.png"></a></div>
</td>
<td style="width: 100%;">
<div id="LPTitle318533" style="font-size: 21px; font-weight: 300; margin-right: 8px; font-family: wf_segoe-ui_light, "Segoe UI Light", "Segoe WP Light", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px;">
<a target="_blank" id="LPUrlAnchor318533" href="https://www.federalregister.gov/documents/2021/05/17/2021-10460/improving-the-nations-cybersecurity" style="text-decoration: none; color: var(--themePrimary);">Federal Register :: Improving the Nation's Cybersecurity</a></div>
<div id="LPDescription318533" style="font-size: 14px; max-height: 100px; color: rgb(102, 102, 102); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px; margin-right: 8px; overflow: hidden;">
This site displays a prototype of a “Web 2.0” version of the daily Federal Register. It is not an official legal edition of the Federal Register, and does not replace the official print version or the official electronic version on GPO’s govinfo.gov.</div>
<div id="LPMetadata318533" style="font-size: 14px; font-weight: 400; color: rgb(166, 166, 166); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif;">
www.federalregister.gov</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div><br>
</div>
<div class="_Entity _EType_OWALinkPreview _EId_OWALinkPreview _EReadonly_1">
<div id="LPBorder_GTaHR0cHM6Ly9wdWJsaWMtaW5zcGVjdGlvbi5mZWRlcmFscmVnaXN0ZXIuZ292LzIwMjUtMDE0NzAucGRm" class="LPBorder123120" style="width: 100%; margin-top: 16px; margin-bottom: 16px; position: relative; max-width: 800px; min-width: 424px;">
<table id="LPContainer123120" role="presentation" style="padding: 12px 36px 12px 12px; width: 100%; border-width: 1px; border-style: solid; border-color: rgb(200, 200, 200); border-radius: 2px;">
<tbody>
<tr valign="top" style="border-spacing: 0px;">
<td style="width: 100%;">
<div id="LPTitle123120" style="font-size: 21px; font-weight: 300; margin-right: 8px; font-family: wf_segoe-ui_light, "Segoe UI Light", "Segoe WP Light", "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px;">
<a target="_blank" id="LPUrlAnchor123120" href="https://public-inspection.federalregister.gov/2025-01470.pdf" style="text-decoration: none; color: var(--themePrimary);">Federal Register on 01/17/2025 and available online at Nationality Act of 1952 (8 U.S.C.
1182(f)), and section 301 of https://federalregister.gov/d/2025-01470 EXECUTIVE ORDER U.S.C. 1601 et seq. 14144</a></div>
<div id="LPDescription123120" style="font-size: 14px; max-height: 100px; color: rgb(102, 102, 102); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; margin-bottom: 12px; margin-right: 8px; overflow: hidden;">
6 develop and publish a preliminary update to the SSDF. This update shall include practices, procedures, controls, and implementation examples regarding the</div>
<div id="LPMetadata123120" style="font-size: 14px; font-weight: 400; color: rgb(166, 166, 166); font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif;">
public-inspection.federalregister.gov</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div><br>
</div>
</li><li style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0); list-style-type: "2) ";">
<div class="elementToProof">How can one determine the impact of unknown regulations??</div>
</li></ol>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
FYI - If the EU took it upon themselves to analyze every bit of software and provide a free rating - that may have one outcome. However, if everyone producing open- source software was required to pay some large sum to get their software tested (and face fines
if they didn't), that would have a different outcome.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
Regulations can be a carrot or stick approach.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
Software can be buggy but still be very useful/helpful. Malicious software can be well written (no obvious bugs). </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 14pt; color: rgb(0, 0, 0);">
RW<br>
</div>
<div class="elementToProof" id="Signature">
<div style="font-size:14pt;color:#000000;font-family:Calibri,Helvetica,sans-serif" dir="ltr" id="divtagdefaultwrapper">
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> bind-users <bind-users-bounces@lists.isc.org> on behalf of Marc <Marc@f1-outsourcing.eu><br>
<b>Sent:</b> Tuesday, January 28, 2025 3:27 PM<br>
<b>To:</b> Victoria Risk <vicky@isc.org>; BIND Users <bind-users@lists.isc.org>; 'CNECT-F3@ec.europa.eu' <CNECT-F3@ec.europa.eu><br>
<b>Subject:</b> RE: Survey on the impact of software regulation on DNS systems</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">This email originated from outside of TESLA<br>
<br>
Do not click links or open attachments unless you recognize the sender and know the content is safe.<br>
<br>
><br>
> Did you know that there is significant momentum building to regulate<br>
> software, including open source, in at least Europe and the US (and<br>
> possibly elsewhere as well), in order to improve cybersecurity? Do you<br>
> think this regulation will improve cybersecurity for your operations?<br>
> What are the opportunities and pitfalls you can envision?<br>
><br>
><br>
<br>
What about regulating standards? What is the point of regulation open source, when companies like apple and microsoft sabotage third party software/connectivity by not implementing software according to standards. Their upgrades miraculously only break third
parties implementations and not their own.<br>
Think eg. of auto provisioning.<br>
<br>
<br>
--<br>
Visit <a href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a> to unsubscribe from this list<br>
<br>
ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://www.isc.org/contact/">https://www.isc.org/contact/</a> for more information.<br>
<br>
<br>
bind-users mailing list<br>
bind-users@lists.isc.org<br>
<a href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a><br>
</div>
</span></font></div>
</body>
</html>