On Wed, Aug 31, 2022 at 01:39:32AM -0700, Brian Dickson wrote:
> Here are some proposed text changes, per Warren's invitation to send text:
>
> In section 1.2, change:
>
> 2. TargetName: The domain name of either the alias target (for
>AliasMode) or the alternative endpoint (for
On Wed, Aug 24, 2022 at 4:11 PM Eric Orth wrote:
>
>
> On Wed, Aug 24, 2022 at 4:58 PM Viktor Dukhovni
> wrote:
>
>> * When the initial SVCB (also HTTPS, ...) query returns an AliasMode
>> result, lookup failures in all subsequent SVCB/HTTPS queries are
>> "fatal"
>> even for
On Wed, Aug 24, 2022 at 07:11:16PM -0400, Eric Orth wrote:
> > Regarless, once AliasMode records are found, these MUST be used and
> > partial lookup failure along a non-empty (so far) alias chain needs
> > to be fatal.
>
> This would be a big non-editorial change from the current draft, and I
>
On Tue, Aug 23, 2022 at 02:51:33PM -0700, Brian Dickson wrote:
>- The problem is whether/when/how the DNS queries are considered
>failures, and whether/when/how some sort of fall-back procedure is followed
>in those cases.
Indeed "failure" may not be consistently defined.
- On the
Hiya,
On 23/08/2022 23:52, Martin Thomson wrote:
On Wed, Aug 24, 2022, at 08:30, Stephen Farrell wrote:
Currently chromium and firefox disagree on whether ECH is setup
correctly for one of my test pages
I'm fairly confident that that is a bug on the Firefox end. The
person looking into it
On Wed, Aug 24, 2022, at 08:30, Stephen Farrell wrote:
> Currently chromium and firefox disagree on whether ECH is
> setup correctly for one of my test pages
I'm fairly confident that that is a bug on the Firefox end. The person looking
into it has been on leave, but as far as I can tell the
Hiya,
On 23/08/2022 22:51, Brian Dickson wrote:
The differences in interpretation, and the client behavior under one of
those interpretations, are the problem.
I've seen a different client-behaviour issue related to ports
other than 443 and ECH, but I'm unsure if that's a problem
with this
On Sat, Aug 20, 2022 at 10:07 AM Warren Kumari wrote:
> Brian Dickson recently reached out to one of the DNSOP chairs to raise
> some technical concerns related to the AliasMode functionality in
> draft-ietf-dnsop-svcb-https.
>
> Although this document has already passed WGLC, IETF LC, IESG
Brian Dickson recently reached out to one of the DNSOP chairs to raise some
technical concerns related to the AliasMode functionality in
draft-ietf-dnsop-svcb-https.
Although this document has already passed WGLC, IETF LC, IESG Eval, and was
approved and sent to the RFC Editor, I want to make
