Re: [Doh] URI Template

4.1:

  Future specifications for new media types for DoH MUST define the
   variables used for URI Template processing with this protocol.

On Fri, Aug 31, 2018 at 3:10 PM, Star Brilliant <m13253@hotmail.com> wrote:

> On Fri, Aug 31, 2018 at 11:23 PM Daniel Stenberg <daniel@haxx.se> wrote:
> >
> > On Fri, 31 Aug 2018, Martin Thomson wrote:
> >
> > > For instance, DoH only defines what "dns" means, so you would take
> > > "https://example.org{?dns}{?x}" and just do
> > > "https://example.org?dns=<blah>".  Of course, an extension to DoH
> > > might define "x", and those clients that understand that extension
> > > could use that template with the extension.
> >
> > Ok I understand. If we in the future also adds 'x' as a variable that
> can be
> > used in DoH, a future template could look like "https://example.org
> {?dns}{?x}"
> > so if we want the current template parser to be future-proof it needs to
> > accept them all...
> >
> > Thanks!
>
> Hi,
>
> By the way, I remember we once had a "ct" parameter to specify the
> Content-Type, in case we will define another one in the future.
>
> But I can not find any information about "ct" in the latest draft. Is it
> removed?
> What should we do if we want another Content-Type in the future? (e.g.
> text-based, JSON-based, or session-based XFR)
>
>
> Best regards,
> StarBrilliant
> _______________________________________________
> Doh mailing list
> Doh@ietf.org
> https://www.ietf.org/mailman/listinfo/doh
>