Yes.   I'm using it right now to implement draft-ietf-dnssd-mdns-relay, and
that implementation is working and interoperating.   I don't know of
another independent implementation yet, unfortunately.

On Tue, Jun 12, 2018 at 4:36 AM, Job Snijders <[email protected]> wrote:

> Hi all,
>
> Are there any implementations of this protocol extension?
>
> Kind regards,
>
> Job
>
> ---------- Forwarded message ----------
> From: The IESG <[email protected]>
> Date: Mon, Jun 11, 2018 at 6:20 PM
> Subject: [DNSOP] Last Call: <draft-ietf-dnsop-session-signal-10.txt>
> (DNS Stateful Operations) to Proposed Standard
> To: IETF-Announce <[email protected]>
> Cc: Tim Wicinski <[email protected]>, [email protected],
> [email protected], [email protected]
>
>
>
> The IESG has received a request from the Domain Name System Operations WG
> (dnsop) to consider the following document: - 'DNS Stateful Operations'
>   <draft-ietf-dnsop-session-signal-10.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> [email protected] mailing lists by 2018-06-25. Exceptionally, comments may be
> sent to [email protected] instead. In either case, please retain the
> beginning of
> the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document defines a new DNS OPCODE for DNS Stateful Operations
>    (DSO).  DSO messages communicate operations within persistent
>    stateful sessions, using type-length-value (TLV) syntax.  Three TLVs
>    are defined that manage session timeouts, termination, and encryption
>    padding, and a framework is defined for extensions to enable new
>    stateful operations.  This document updates RFC 1035 by adding a new
>    DNS header opcode and result code which has different message
>    semantics.  This document updates RFC 7766 by redefining a session,
>    providing new guidance on connection re-use, and providing a new
>    mechanism for handling session idle timeouts.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-session-signal/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-session-signal/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
> _______________________________________________
> DNSOP mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dnsop
>
> _______________________________________________
> DNSOP mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dnsop
>
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to