attachment

<html>

<head>

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">

<base href="https://www.rfc-editor.org/rfc/rfc9665.html">

</head>

<body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">

<base href="https://www.rfc-editor.org/rfc/rfc9665.html">

<div class="Apple-Mail-URLShareUserContentTopClass">Hi there,</div>

<div class="Apple-Mail-URLShareUserContentTopClass"><br>

</div>

<div class="Apple-Mail-URLShareUserContentTopClass">Not sure if this has slipped past everybody, but if the infrastructure is available on home / SMB networks, the protocol defined in this RFC provides a DNS-SD alternative to using mDNS, helping to mitigate

 some multicast reliability issues that have been observed for many years due to a variety of causes.</div>

<div class="Apple-Mail-URLShareUserContentTopClass"> </div>

<div class="Apple-Mail-URLShareWrapperClass" style="position: relative !important;">

<blockquote type="cite" style="border-left-style: none; color: inherit; padding: inherit; margin: inherit;">

<a href="https://www.rfc-editor.org/rfc/rfc9665.html">https://www.rfc-editor.org/rfc/rfc9665.html</a><br>

</blockquote>

</div>

<br>

Perhaps we need to consider adding this to IPP Everywhere 2.0? This is already being discussed in IoT framework environments.

<div><br>

<div>Smith<br>

<br>

/**<br>

    Smith Kennedy<br>

    HP Inc.<br>

*/ </div>

<br>

</div>

</body>

</html>