IETF Logo Mail Archive

Re: [DNSOP] [iesg-secretary@ietf.org: Results of IETF-conflict review for draft-klensin-dns-function-considerations-04]

Warren Kumari <warren@kumari.net> Mon, 18 December 2017 21:23 UTC

Return-Path: <warren@kumari.net>
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 C796F12D946 for <dnsop@ietfa.amsl.com>; Mon, 18 Dec 2017 13:23:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level:
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.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 ALvnuKAAMnky for <dnsop@ietfa.amsl.com>; Mon, 18 Dec 2017 13:23:12 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 B180E12D950 for <dnsop@ietf.org>; Mon, 18 Dec 2017 13:23:11 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id n138so390726wmg.2 for <dnsop@ietf.org>; Mon, 18 Dec 2017 13:23:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yfewT0GBaCPzN2KetNStOvzrx0bf/VFz1Uxz3LWrMjs=; b=cghAHTXZ8vOcJbMEabM9FxepCKYSbdnDNB9E75H6YIvv9vCHP+YN8AyBL5W012tYw8 7eD6j+nhSEXC2BTIgdxo/fE34fP/93wLZmgHxdpt+PvOTisdUfPnnTnEBOXBOTPMsrGh 7fnwjSEj+jxQmmvNU4vGsJH85sm6vWN/oIgdHpVQf4Qhsbzb03S3H+aaeyA9f+MPCW97 sWXQcSTTJ1/p8ggCcZnqSWdA5eS+JJcR4dYhfVUa6jlFeKMRD7grMznLpF6Suiyxb+Bu ylIIlm1DlAV3KJefqRJEkgeOEwmxH8SqIZM0a78qxiIMR+7Vd3YSF8iWU4kb8O1wVohx e49A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yfewT0GBaCPzN2KetNStOvzrx0bf/VFz1Uxz3LWrMjs=; b=gdnnDmMrvODwQpg5XzMwsoGo0xXpTY5USnT1KFJ/VPrFIiOLfwkBCzXvnMuY9yV3Ua Uyfe9a0ooE4mxRXj6nOtpn2Ny8cT0MTzUlhp3VvO0iainmDgMDiqNO54c19fn5fcfB+n eDqr5zNRsZ230cS+Y4EGuwns21plEJNnf4kDu8iQtJL+60NHtRLmbDqu7X/OVtjKazfE mOV0dYrtijTpPb47bFvoNv3hq7wCr4ZKEd70lhcshLKOXLsFv0KKPI6byXlIEpa77pM9 +5ivfEpD9YAcMHU4t2z2/6N9BKiB7D0fxqbQQYbwFPvUn/m5AJ4ARkH4EtQA0o2wJSc5 XVdg==
X-Gm-Message-State: AKGB3mIEiWd0AcbxxBL5gdHazHvNwo2iSa8Q5jpBHdfeXCGgNf81q33Y zfJLf+WlTWJiy5292OwHUWZELCb7XO1WSNXsCvTixQ==
X-Google-Smtp-Source: ACJfBoviyGNGWFtGkYpVIKLMd7NGx73oMZUG6rHGAjEicHDU1wvQi/mVkJCsYMq8dyy0yK4QO3eDl/Ai/cRiFE3kJyI=
X-Received: by 10.28.207.130 with SMTP id f124mr593665wmg.132.1513632189836; Mon, 18 Dec 2017 13:23:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.160.149 with HTTP; Mon, 18 Dec 2017 13:22:29 -0800 (PST)
In-Reply-To: <20171218202311.expokhek6vpytdpo@sources.org>
References: <20171218191650.j5nq2gbfjuv335e2@nic.fr> <902EAAA3-81C5-4FAB-A00C-1A810C9B5951@vpnc.org> <20171218202311.expokhek6vpytdpo@sources.org>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 18 Dec 2017 16:22:29 -0500
Message-ID: <CAHw9_i+ua5qu-WzswVJu7tEeJQ3D-sCwixiGY5OxG=FRtJPoWA@mail.gmail.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, dnsop <dnsop@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/YPl9Nf3v9__HsS8CEOa9LLSj_i8>
Subject: Re: [DNSOP] [iesg-secretary@ietf.org: Results of IETF-conflict review for draft-klensin-dns-function-considerations-04]
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 18 Dec 2017 21:23:15 -0000

On Mon, Dec 18, 2017 at 3:23 PM, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> On Mon, Dec 18, 2017 at 11:31:11AM -0800,
>  Paul Hoffman <paul.hoffman@vpnc.org> wrote
>  a message of 17 lines which said:
>
>> > Probably relevant for this group.
>>
>> Surprisingly not. An IETF-conflict review is just the IESG's way of
>> giving input on a document that the Independent Submissions Editor
>> (ISE) might publish in the future.
>
> When I said "relevant", I was not speaking of the IETF-conflict review
> but of the document itself, which will probably be of interest for
> people here.
>

<no hats>

Yup -- I personally thought that this was a good read, and contained a
bunch of useful background.

For those readers who think if feels strangely familiar (from early
June 2017): https://mailarchive.ietf.org/arch/search/?email_list=dnsop&q=What+can+be+done+with+the+DNS+and+what+should+be+done+elsewhere+%5Bdraft-klensin-dns-function-considerations%5D

W
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop



-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf

v2.23.0 | Report a Bug | By Email