Re: [dns-privacy] Datatracker State Update Notice: <draft-ietf-dprive-rfc7626-bis-04.txt>

Sara Dickinson <sara@sinodun.com> Fri, 24 January 2020 17:01 UTC

Return-Path: <sara@sinodun.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 19EB6120A9C for <dns-privacy@ietfa.amsl.com>; Fri, 24 Jan 2020 09:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sinodun.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 n9BR_WrgdLGI for <dns-privacy@ietfa.amsl.com>; Fri, 24 Jan 2020 09:01:27 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EA01120A8B for <dns-privacy@ietf.org>; Fri, 24 Jan 2020 09:01:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sinodun.com ; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=2ECC2FlOKV3BCaHhTJePCjpvpHZaEDgYPyMvSQsQuto=; b=UGDlqnw7JrMZBNGYxlkzxbj9bT zjMbC9SyAHvJTPJ6hTAi3/6NGn83Qr8ZF3LM9vWvFfbyaQfilpi46WSiceO1qsSHWiAlq0n6SbVNd 3vKS5YugxgMPws1tA8peWn2u1m4AogYtKAek5erq/RT18umcJS0ioUlQef6sNS+cJ6oEgipfnTmPB 2R1C4/KdS91J9NlnAmaIBR45WhywdllhoNe4wVCbJ+R1w8C/Hs1TALGxdeazRio/fE8yFz7RtEmRv rRPvErGqRv6kWVOMMpmgmqW5ygAAnnNlAfxDH+EUICxbihjmqV4GJRkj87WjXGvA2XwJV41e6amjg wWTVdUCg==;
Received: from [2a02:8010:6126:0:3906:dc5c:c2bd:8c46] (port=56855) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <sara@sinodun.com>) id 1iv2Kf-0000at-W2 for dns-privacy@ietf.org; Fri, 24 Jan 2020 17:01:26 +0000
From: Sara Dickinson <sara@sinodun.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 24 Jan 2020 17:01:21 +0000
References: <157955609351.1744.15099511006231348523.idtracker@ietfa.amsl.com> <417BE033-4DE5-452A-BE93-0657C83051BC@cisco.com>
To: "dns-privacy@ietf.org" <dns-privacy@ietf.org>
In-Reply-To: <417BE033-4DE5-452A-BE93-0657C83051BC@cisco.com>
Message-Id: <FDC33D24-8B9C-414C-AD63-51E64C6FD58D@sinodun.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/dns-privacy/FgrWHitMlXXu-3aNF-406_36-Nw>
Subject: Re: [dns-privacy] Datatracker State Update Notice: <draft-ietf-dprive-rfc7626-bis-04.txt>
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: Fri, 24 Jan 2020 17:01:30 -0000

Hi All, 

Please note that I will be out of the office next week and not reading email. I will continue to respond to IETF Last call comments on my return. 

Best regards

Sara. 

> On 20 Jan 2020, at 21:45, Eric Vyncke (evyncke) <evyncke@cisco.com>; wrote:
> 
> Thanks to Sara and Stéphane for the -04 revised I-D. 
> 
> After reading the -04, I think that most of the IETF Last Call comments are addressed (and consensus needs to be balanced -- even for informational document) and that the document sticks to facts.
> 
> But, as section 3.5.1 ("in the recursive resolvers") raised a lot of discussions during the first IETF Last Call, and as the authors reacted to those comments by deep changes in the text, let's have a new IETF Last Call before proceeding with IESG evaluation.
> 
> Again, thank you to the reviewers and the authors
> 
> Regards,
> 
> -éric
> 
> 
> On 20/01/2020, 22:34, "IETF Secretariat" <ietf-secretariat-reply@ietf.org>; wrote:
> 
>    IESG state changed:
> 
>    New State: Last Call Requested
> 
>    (The previous state was Waiting for AD Go-Ahead::AD Followup)
> 
>    The previous last call raised several points. The authors have worked on those points and this new informational IETF draft has substantive changes; enough to go trigger a new IETF Last Call.
> 
>    -éric
> 
>    Datatracker URL: https://datatracker.ietf.org/doc/draft-ietf-dprive-rfc7626-bis/
> 
> 
> 
> _______________________________________________
> dns-privacy mailing list
> dns-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/dns-privacy