[DNSOP] Moving forward with DNS Stateful Operations
Ted Lemon <mellon@fugue.com> Thu, 02 August 2018 15:32 UTC
Return-Path: <mellon@fugue.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 D2BBE130E9C for <dnsop@ietfa.amsl.com>; Thu, 2 Aug 2018 08:32:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 idVTlQpAkoXo for <dnsop@ietfa.amsl.com>; Thu, 2 Aug 2018 08:32:49 -0700 (PDT)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 E556F130DF4 for <dnsop@ietf.org>; Thu, 2 Aug 2018 08:32:48 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id d10-v6so3963300itj.5 for <dnsop@ietf.org>; Thu, 02 Aug 2018 08:32:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=jxi3sGUmqQn+srWSnB7F2PERV2ZNyCyDxChXGTBfIR0=; b=RucJacsyKEwTplWRATmIMyrjVh97ggdOXmkyp95VehNjgiL9jbBYgJjh65z+S8/D5f hOB33RtQcbwRhzrbHyKB9YHBW3R4JmstoqAhsSQG19W7LelOw5arKVwfvj1lxNZinXZT +gaertw9YOTLbc9ctQ/kBhTwtl/x4ej8lBxhexD6US+YOP/gxuGGqqfQ9fCBSlFM1otS y54OZc5fQqiWDUlNpEVdDwl/n++1o/zzIsLOkcTWDaH9WjYpCfwQFRl+ldkR1vikakxF kVH9Pox8N1fE5tuZZ/bxm0PwuE7GZtR5oAGqNQNa/WdhDMXlQytJDyN+MGT3eSFvplKv OLkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=jxi3sGUmqQn+srWSnB7F2PERV2ZNyCyDxChXGTBfIR0=; b=ji1g7dd6DK4Sf2H0qRUHTvV4oRldJsb71Jf/oTkUn6gAibyMHx4WVt3dMWPM8g7FCO 7xGjyBMcCcyOJXUP7kitayPZYFAK24HXlrwej+q9GFqovleeuc4hWIWdVIvvG23+CkWK aXa3yjx9YiyNLj7ro90vEnZ+Efscwdz5aqOYXAvwSmpv+MOt7gd5rlfk/y4aktmgU8XJ YEG3pADtdgbOWaqOD+R832K8LTwscIugDdiaCBqJunQolcdHDgmHTe3wmL74sH1ot7EO n/fFfXrdIE8xuRivZNxIDm46cWrnRtA4gHBJe6PFWM1gRLGXfcELEv3VKoc16+QHRAC/ Kk8A==
X-Gm-Message-State: AOUpUlF2v0d/BUp0RFx10IBi0MEO1P5Hv+eJgykRxRgcY76mf2vXdPRM csrk1CvCH0XCv2HticaoWsCTuBA/Buluq+4Fq5VfVA==
X-Google-Smtp-Source: AAOMgpf6+av1LCVFDlgA+H/YYiE6DxHCNe+5IAu+mLnPpO2pc5fIvOY07Ais0L3p9SIvi/aKRLqH6zhovhQEGhLNHUE=
X-Received: by 2002:a24:d485:: with SMTP id x127-v6mr3150512itg.82.1533223968148; Thu, 02 Aug 2018 08:32:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:b442:0:0:0:0:0 with HTTP; Thu, 2 Aug 2018 08:32:07 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 02 Aug 2018 11:32:07 -0400
Message-ID: <CAPt1N1n6nmPPnNUQxAw1g-kX_d+LTrdrCE900BPNOHKR5Jjc6g@mail.gmail.com>
To: draft-ietf-dnsop-session-signal@ietf.org
Cc: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fba5640572758556"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DydXGwCfXIrF12XXpY1PeOgX-q0>
Subject: [DNSOP] Moving forward with DNS Stateful Operations
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, 02 Aug 2018 15:32:51 -0000
We got some really good review during the IESG last call process. Thanks to the IESG members (bcc) who read the document thoroughly and gave so many thoughtful comments. I believe that we have addressed all of the comments that were made during the review adequately. However, this hasn't been thoroughly reviewed; we should do a thorough review of these changes. In order to facilitate that, I've submitted a -14 (on top of last night's -13), so the diffs to look at are between -12 and -14, not, e.g., just -13 and -14. You can get the diffs here: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-session-signal-14&url1=draft-ietf-dnsop-session-signal-12 Note that because I added an applicability section, all of the IESG comments about sections after 4 are off by one. The one remaining nit is that at least two and possibly three of the ADs commented that the terminology section has a lot of normative language in it and generally talks a lot about things that are really specification, not terminology. I responded to this by saying that we'd discussed this as a group, agreed it wasn't great, and decided it was more work to fix than it was worth. However, at the moment I actually have a lot of state on this document in my head, and I think I could fix this without it being too much work or introducing errors. But doing so would impose extra workload at least on the authors, and maybe on the working group, to review the changes I make and make sure I don't screw something up. Is there appetite for doing this? I think it would significantly improve the document, but I am mindful of the expense.
- [DNSOP] Moving forward with DNS Stateful Operatio… Ted Lemon
- Re: [DNSOP] Moving forward with DNS Stateful Oper… Tom Pusateri
- Re: [DNSOP] Moving forward with DNS Stateful Oper… Ted Lemon
- Re: [DNSOP] Moving forward with DNS Stateful Oper… Ray Bellis
- Re: [DNSOP] Moving forward with DNS Stateful Oper… Ted Lemon