DNSOP,
This new draft describes a way for clients and servers to exchange a
limited amount of information where the semantics of that information
are completely unspecified, and therefore determined by bi-lateral
agreement between the client and server operators.
There are known cases where bespoke implementations are using
experimental EDNS option values for this purpose, for example for a
front-end load-balancer to tell the server whether an incoming
connection arrived over TCP or UDP (c.f. my XPF draft).
A goal of this draft is to assign a common EDNS code-point such that
popular OSS implementations can support similar features interoperably.
Ray
-------- Forwarded Message --------
Subject: New Version Notification for draft-bellis-dnsop-edns-tags-00.txt
Date: Mon, 04 Mar 2019 08:14:24 -0800
From: internet-dra...@ietf.org
To: Ray Bellis <r...@isc.org>, Alan Clegg <acl...@isc.org>
A new version of I-D, draft-bellis-dnsop-edns-tags-00.txt
has been successfully submitted by Ray Bellis and posted to the
IETF repository.
Name: draft-bellis-dnsop-edns-tags
Revision: 00
Title: DNS EDNS Tags
Document date: 2019-03-04
Group: Individual Submission
Pages: 6
URL:
https://www.ietf.org/internet-drafts/draft-bellis-dnsop-edns-tags-00.txt
Status:
https://datatracker.ietf.org/doc/draft-bellis-dnsop-edns-tags/
Htmlized: https://tools.ietf.org/html/draft-bellis-dnsop-edns-tags-00
Htmlized:
https://datatracker.ietf.org/doc/html/draft-bellis-dnsop-edns-tags
Abstract:
This document describes EDNS Tags, a mechanism by which DNS clients
and servers can transmit an opaque data field which has no defined
semantic meaning other than as previously agreed between the client
and server.
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
