IETF Logo Mail Archive

Re: [dns-privacy] Status of draft-ietf-dprive-rfc7626-bis?

Rob Sayre <sayrer@gmail.com> Sat, 26 September 2020 02:07 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: dns-privacy@ietfa.amsl.com
Delivered-To: dns-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C42333A0E75 for <dns-privacy@ietfa.amsl.com>; Fri, 25 Sep 2020 19:07:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 B3vP-rslE1-E for <dns-privacy@ietfa.amsl.com>; Fri, 25 Sep 2020 19:07:44 -0700 (PDT)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A2843A0E70 for <dns-privacy@ietf.org>; Fri, 25 Sep 2020 19:07:44 -0700 (PDT)
Received: by mail-il1-x12f.google.com with SMTP id z5so4362853ilq.5 for <dns-privacy@ietf.org>; Fri, 25 Sep 2020 19:07:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rXfq2VhVd6KjsjEssx2e0WOabdAhFsK+lE52bgftrDw=; b=Q61vSa/Lks2vWLISJ17RfnrThH83B0CjdN8USd/Nrb7anl8Q5D+2IeeokMPCwO3lUj ogR+NPd0rY8qeoWyRx3UtSdznMF6YXflXxjd6fin65zg7zZX2hOq28X2bEgqpPrZvJdF eOK3PStYgUyKrnf2RRt0C9ydUyw+7CuPDfxUiQGZ7jztkh+nwbCduliniTqK41knjSPk aGRLdSg0y2S46N2IxTGv4c0iJHHdDbGm3LGR1RUu8VVFqs0Z5Gw9+UymoF4cWNq3NU7u 82pbU5cix+0qjrTe+leqMEJ6UVGg4/AmHDzXbkXztUrFjpCBrTDdlg4vqMkLNTGewqp0 DX2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rXfq2VhVd6KjsjEssx2e0WOabdAhFsK+lE52bgftrDw=; b=VKKPTRqB8hj034hoB9VNCzZ47mVEFRRnPjtVHo5T6ZKdJ92VdAyCSytAodlYRHT3Hk tWDikhHocxDPyuqATBpr4dE1yNmM5ZQ6ncnMbmkeb/1vzaQbzITqXmNZ32fUFr7PH+vy r2G/Jj1XNU6cjUypoBXBQKMdYKinK9hGBFnT8PjyJRrYDRCM+JMHsg+92LmU+sJGoxXL 0yUmc9ub9BRboBj37r/cijcMYtzBMgmQUZdaycf8MTCj2ieTI3GUXmCAV7KK2FCAA1Pz AVhm4fGzaXSGz6sPj37fxzFtD03qwHywbq9r8dPFzbZcL/fZSgsaInltdK9ekKPDw/jP 6jaw==
X-Gm-Message-State: AOAM530Foa8QKzV5kkPd6Yhpi7ED7SJiEj6eVJUlKuR4WI40kNxGDeaB r5e6r7JApaPHdEVHniYbnhPNCbAFyuSfOvql76k=
X-Google-Smtp-Source: ABdhPJwKXqQ9gM9en8yUN38g0U27LzeNdwv92T+NtNsvV2Sxq7Me51E6pVWyoE13jqaaAalIFrMPZhWdV6IXbu3w5Qc=
X-Received: by 2002:a05:6e02:ccf:: with SMTP id c15mr2573162ilj.257.1601086063463; Fri, 25 Sep 2020 19:07:43 -0700 (PDT)
MIME-Version: 1.0
References: <CAChr6SxQQACJrSQnxLVr+G14hfzXDkYurk+V_YFVPWVOCS=fyQ@mail.gmail.com> <81781e42-30f0-b9d1-bd9a-456b8ecc6d31@innovationslab.net>
In-Reply-To: <81781e42-30f0-b9d1-bd9a-456b8ecc6d31@innovationslab.net>
From: Rob Sayre <sayrer@gmail.com>
Date: Fri, 25 Sep 2020 19:07:31 -0700
Message-ID: <CAChr6Sz_Rei2hT4hLdhwevAM+E0qPGrph5r1EtdnmEtipmAASg@mail.gmail.com>
To: Brian Haberman <brian@innovationslab.net>
Cc: DNS Privacy Working Group <dns-privacy@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000011538905b02de677"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/Is5AA4q9uvBuXFGIKeKh2iYT89s>
Subject: Re: [dns-privacy] Status of draft-ietf-dprive-rfc7626-bis?
X-BeenThere: dns-privacy@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dns-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dns-privacy/>
List-Post: <mailto:dns-privacy@ietf.org>
List-Help: <mailto:dns-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dns-privacy>, <mailto:dns-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Sep 2020 02:07:46 -0000

On Wed, Sep 23, 2020 at 5:20 AM Brian Haberman <brian@innovationslab.net>
wrote:

> >
> > Other recent submissions have changed their references to RFC 7626. What
> > changes in the 7626-bis document are important to you?
> >
>
> The changes made to the BCP document were driven by feedback from IESG
> members who rightly pointed out that the BCP referred to text originally
> found in 7626 and that 7626-bis was in a state of churn.
>

That makes sense to me. I was only pointing out that the same tradeoff
might apply to Paul's document.

I personally don't understand what 7626-bis adds, and it doesn't seem like
completing the revision has been a pressing concern.

thanks,
Rob

v2.23.0 | Report a Bug | By Email