DNS EDNS Tags
draft-bellis-dnsop-edns-tags-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2019-03-04
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DNSOP Working Group                                            R. Bellis
Internet-Draft                                                  A. Clegg
Intended status: Standards Track                                     ISC
Expires: September 5, 2019                                March 04, 2019

                             DNS EDNS Tags
                    draft-bellis-dnsop-edns-tags-00

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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 5, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Bellis & Clegg          Expires September 5, 2019               [Page 1]
Internet-Draft                DNS EDNS Tags                   March 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Description . . . . . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  Packet Validation Rules . . . . . . . . . . . . . . . . .   3
     3.2.  Error Handling  . . . . . . . . . . . . . . . . . . . . .   3
     3.3.  Wire Format . . . . . . . . . . . . . . . . . . . . . . .   3
       3.3.1.  EDNS-Client-Tag . . . . . . . . . . . . . . . . . . .   3
       3.3.2.  EDNS-Server-Tag . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Implementation status . . . . . . . . . . . . . . . . . . . .   4
   6.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   This document describes EDNS Tags, a mechanism by which DNS clients
   and servers [RFC1034] can transmit an opaque data field which has no
   defined semantic meaning other than as previously agreed between the
   client and server operators.

   The tag is a single 16 bit field stored within the RDATA of an
   EDNS(0) OPT RR as described in [RFC6891].

   Two EDNS options are defined to allow for the detection of servers
   that incorrectly echo responses verbatim.  The EDNS-Client-Tag option
   may only appear in client requests, and the EDNS-Server-Tag may only
   appear in responses from servers.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

3.  Description

   The values of the individual bits within a tag are not defined to
   have any semantic meaning in this specification.  Their
   interpretation is defined entirely by bi-lateral agreement between
   client and server operators.  The definitions for EDNS-Client-Tag and
   EDNS-Server-Tag values MAY be different.

Bellis & Clegg          Expires September 5, 2019               [Page 2]
Internet-Draft                DNS EDNS Tags                   March 2019

   Operators are free to partition the bits within that field as they
   see fit; for example it could be used to transmit up to 16 separate
   boolean flags, or perhaps to transmit a 10 bit numeric value combined
   a 2 bit value and four boolean flags.
Show full document text