[Doh] re original_transport indicator

Patrick McManus <pmcmanus@mozilla.com> Thu, 05 April 2018 20:53 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 236C012D7E8; Thu, 5 Apr 2018 13:53:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.101
X-Spam-Level: **
X-Spam-Status: No, score=2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_SBL_CSS=3.335, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id yHUDsb-2qXg8; Thu, 5 Apr 2018 13:53:53 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 4133912D7E4; Thu, 5 Apr 2018 13:53:53 -0700 (PDT)
Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com []) by linode64.ducksong.com (Postfix) with ESMTPSA id C5D093A081; Thu, 5 Apr 2018 16:53:52 -0400 (EDT)
Received: by mail-oi0-f52.google.com with SMTP id f63-v6so11827793oic.4; Thu, 05 Apr 2018 13:53:52 -0700 (PDT)
X-Gm-Message-State: AElRT7HC7PFBX2JeZICMNmjTO6v0tLFZp8DkZXJhCTulMOZHFhGhJsy4 a6dn49tqokrDJDW1zYdh8lz3cdIkPZ5+m+EkjK4=
X-Google-Smtp-Source: AIpwx4/rQIlqXgaggULd9UjCFcqDW4FW4tZYc1gFklxp/NIstIoURV0HTMFVJl2jQwgmaWMFNcclI54TNa9FJ3anuBE=
X-Received: by 2002:aca:cd42:: with SMTP id d63-v6mr14301227oig.213.1522961632395; Thu, 05 Apr 2018 13:53:52 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Thu, 5 Apr 2018 13:53:51 -0700 (PDT)
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Thu, 5 Apr 2018 16:53:51 -0400
X-Gmail-Original-Message-ID: <CAOdDvNrO0bbSdRn8dzWiFzMx4Wc33yAh0C6SWg+DR4b4XTEmHg@mail.gmail.com>
Message-ID: <CAOdDvNrO0bbSdRn8dzWiFzMx4Wc33yAh0C6SWg+DR4b4XTEmHg@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Paul Vixie <paul@redbarn.org>, dnsop <dnsop@ietf.org>, DoH WG <doh@ietf.org>, Ted Lemon <mellon@fugue.com>, Ray Bellis <ray@bellis.me.uk>
Content-Type: multipart/alternative; boundary="0000000000001b09ee0569202346"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/w7qTHihAdfnznZrBmXGuh23sfns>
Subject: [Doh] re original_transport indicator
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Apr 2018 20:53:55 -0000

Hi All,

We've had quite a thread re the -05 optional parameter to the
dns-udpwireformat registration.

The parameter is defined as having no meaning for DoH, but was included to
accommodate a use case the dnsop wg is considering. Future proofing, if you

Upon consideration (and a read of 6838), I think including this in doh is
premature because Media Type registrations can be updated by mechanisms
laid out in RFC6838 and in this case such an update could occur without
impacting existing DoH deployments. (i.e. it does not need to be future

Therefore the definition of the parameter should accompany the work that
makes use of it if a future standards document chooses to go down that
path. As a bonus we avoid unused clutter if it doesn't happen. I also get
the feeling that there isn't yet strong consensus on the anticipated use
case or the exact form it needs to take - we should let that process work
itself out separately before registration.

I've chatted with Paul, and our recommendation is to remove the
original_transport parameter from DoH and encourage dnsop to update the
registration if/when a different standard needs to make use of it.