IETF Logo Mail Archive

Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-rescorla-tls-esni-00.txt]

Patrick McManus <pmcmanus@mozilla.com> Thu, 19 July 2018 19:36 UTC

Return-Path: <pmcmanus@mozilla.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEACD130F75; Thu, 19 Jul 2018 12:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level:
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tbl3095GhtYD; Thu, 19 Jul 2018 12:36:10 -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 76CF7130EB2; Thu, 19 Jul 2018 12:36:10 -0700 (PDT)
Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by linode64.ducksong.com (Postfix) with ESMTPSA id 2943F3A04B; Thu, 19 Jul 2018 15:36:10 -0400 (EDT)
Received: by mail-oi0-f50.google.com with SMTP id k81-v6so17109200oib.4; Thu, 19 Jul 2018 12:36:10 -0700 (PDT)
X-Gm-Message-State: AOUpUlEHj8TG5CAueYYo0X5CYQQ161Vxroajpa/tbYKfjEFWdd5FkAzj u5zMUiOOmqVI3mr5mngaioVtF2evUOZiW0/16iA=
X-Google-Smtp-Source: AAOMgpeMGOEWVroM/SjILrWW3Zf0LhvELAcRAgyHxzJ4dkuaY5zRz5xqZcZwUc1V1q7zUfeiM+rJWwCQT7/rYytzbpE=
X-Received: by 2002:aca:d7c1:: with SMTP id o184-v6mr11524225oig.347.1532028969876; Thu, 19 Jul 2018 12:36:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:8a22:0:0:0:0:0 with HTTP; Thu, 19 Jul 2018 12:36:09 -0700 (PDT)
In-Reply-To: <CAOdDvNrMrz0Vx74xued7MrSR1jx5RpBmn1TsWcp-rOmg2H3J8w@mail.gmail.com>
References: <20180707191900.7jjaxklib3tlixgb@nic.fr> <CAM1xaJ_jcMunvfuqqgoe-5hTSE1t=A4ELWF1j0SBsztoZ_1S=w@mail.gmail.com> <CAOdDvNpWs3_+c3=pdYjxm+UrEfBUawcTKXY4ks0VbuGSts+q7Q@mail.gmail.com> <CADyWQ+HwNsvgs0BnQ3NqnEob6xZrcbmk_qVOX58UCW4rFrmahg@mail.gmail.com> <CAOdDvNq65kGho6oCX=mMw+qebHOqzJq6qJ7kAWdO53wAKeyj2A@mail.gmail.com> <CAM1xaJ8nsqreqBz7f2fG_HOaB6dc5JOS_S9Oxj5pyiOaPiyvsA@mail.gmail.com> <CAOdDvNrMrz0Vx74xued7MrSR1jx5RpBmn1TsWcp-rOmg2H3J8w@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Thu, 19 Jul 2018 15:36:09 -0400
X-Gmail-Original-Message-ID: <CAOdDvNpoTa_MFMTdM8jiWnaCQHhueji+ac_HqYHNXOJhHLEi=A@mail.gmail.com>
Message-ID: <CAOdDvNpoTa_MFMTdM8jiWnaCQHhueji+ac_HqYHNXOJhHLEi=A@mail.gmail.com>
To: Patrick McManus <pmcmanus@mozilla.com>
Cc: Jan Včelák <jv@fcelda.cz>, tjw ietf <tjw.ietf@gmail.com>, dnsop <dnsop@ietf.org>, draft-rescorla-tls-esni@ietf.org
Content-Type: multipart/alternative; boundary="00000000000089048405715f4a4b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/RuU535Y2updJLPglFwEV7NgJl8w>
Subject: Re: [DNSOP] [internet-drafts@ietf.org: I-D Action: draft-rescorla-tls-esni-00.txt]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2018 19:36:18 -0000

On Thu, Jul 19, 2018 at 3:07 PM, Patrick McManus <pmcmanus@mozilla.com>
wrote:

>
> Am I correct in saying that what you're getting at is not so much a wire
> issue as a convention among configuration and implementations? i.e.
> wildcards are synthesized - they aren't actually sent as responses that
> clients use in some kind of short-cut kind of way?
>
>
[replying to myself] I see now that the wildcards are part of things like
axfr which form an open definition for interoperability.. so they are a
wire protocol element of a sort. Thanks!

v2.23.0 | Report a Bug | By Email