Hm, you seem to have left out a definition of what a "session" is. Do you mean a TCP connection? Are you referring to something that's already defined in a document that I have, lamentably, not read? (In which case, a reference would be helpful).
On Wed, Jul 6, 2016 at 3:24 PM, Ray Bellis <[email protected]> wrote: > I've just submitted this draft, which resulted from discussions in > Buenos Aires related to issues with using EDNS for persistent signalling > (c.f. RFC 7828), and also from an overlap with draft-ietf-dnssd-push and > its (mis-)use of the edns-tcp-keepalive option. > > The intention here is to split out session-related stateful options from > the dnssd-push draft into a more generic specification. > > Please note that the question of whether to use an alternate message > format for this OpCode (as it is currently specified) or whether to > shoe-horn the options into an RR lookalike (per EDNS) is still a matter > of some debate between the authors. With no consensus amongst us I felt > if important that the WG be able to weigh in on that debate. > > Ray > > -------- Forwarded Message -------- > Subject: New Version Notification for > draft-bellis-dnsop-session-signal-00.txt > > A new version of I-D, draft-bellis-dnsop-session-signal-00.txt > has been successfully submitted by Ray Bellis and posted to the > IETF repository. > > Name: draft-bellis-dnsop-session-signal > Revision: 00 > Title: DNS Session Signaling > Document date: 2016-07-06 > Group: Individual Submission > Pages: 10 > URL: > > https://www.ietf.org/internet-drafts/draft-bellis-dnsop-session-signal-00.txt > Status: > https://datatracker.ietf.org/doc/draft-bellis-dnsop-session-signal/ > Htmlized: > https://tools.ietf.org/html/draft-bellis-dnsop-session-signal-00 > > > Abstract: > The Extension Mechanisms for DNS (EDNS(0)) [RFC6891] is explicitly > defined to only have "per-message" semantics. This document defines > a new Session Signaling OpCode used to carry persistent "per-session" > type-length-values (TLVs), and defines an initial set of TLVs used to > handle feature negotiation and to manage session timeouts and > termination. > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop >
_______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
