Re: [DNSOP] A quick update on draft-ietf-dnsop-attrleaf / draft-ietf-dnsop-attrleaf-fix

Warren Kumari <warren@kumari.net> Mon, 22 October 2018 14:01 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 9A6E3126BED for <dnsop@ietfa.amsl.com>; Mon, 22 Oct 2018 07:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level:
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=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 FCBaFrgDBceS for <dnsop@ietfa.amsl.com>; Mon, 22 Oct 2018 07:01:00 -0700 (PDT)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 0B6E11286E7 for <dnsop@ietf.org>; Mon, 22 Oct 2018 07:00:34 -0700 (PDT)
Received: by mail-wr1-x432.google.com with SMTP id d2-v6so45110764wro.7 for <dnsop@ietf.org>; Mon, 22 Oct 2018 07:00:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=aVck/1oL2uf1GYnVX/6sxwBemI/VvFcA4t9o7kme9yY=; b=HRgZ67ZqmQZIGWaLBsgmD+VpK64HNrxSflS1Gd3+r1Ce0dH1RrBhwGbt5Iua/8h9Nk MC9N7R+X4tnexu8kshoUUu85wGnU9j/w1tSBmf9yStAZDpY050jyftKRCpCPhuCRL4Gh uk9O+vsIpq+wM+Tht6x9MDzFkLcners7FZnFiiqDMUOsK6m+R9UUVs1cfPAkVaKC1N8U PwEB3ZRL8wpBDhhas0RlG/BPAnazS/YF4pTNgNxMAjPzLgZxOQVGPXpXHg5dH+9LfrHi 0Q3nQY7/OMDkabsIJG6KEy0uriggd3m6iixdta9jDoLadNG0XISzy7nyrWeTboYRLJjo tNyg==
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; bh=aVck/1oL2uf1GYnVX/6sxwBemI/VvFcA4t9o7kme9yY=; b=CyaMchx5YRUKi2RAWvRBB1Ex+OUZXZFAQJN4Yps6rE8xSahru4v8vKSdfqg0Dme9F5 H3HskhWOYWc4yqo6RV1NGWssTyVhhN1VN1ItddSANa+cXeXgnDAVHY3fYi8/E2a1aj0C yuRNkThh7gvo995muYFd2rFAFiMBlhTw1iw7euYwDB9PGZX/HDNpZ6m8I4ZPL+3Inr8H +h68jAsnnB0M3zobqdEXgDqEknQ0JUjruAzoVYXAjIYY519Tn0lWvdIPUO/ZuebR+ZVd MEEstexhuhnJqqtfYvS7ji3e7NKnQuSOCxxWZmWdijx++xsvSArPM0nQSrrR8ziK53AO ZZdg==
X-Gm-Message-State: ABuFfojJE48uBgsNKZhB+oapvSbupKx+fYJoduubmZ5NeEHAtuf2WpJf CekXS50xutStTeSsHCqlldaYHre8BoJwX5r8pYLtFk8bJuhIsw==
X-Google-Smtp-Source: ACcGV620a3FT55M6WtOKdno24nRmTDt1XNbX62m3zePwAFGZC+dTEyUdHVHd2ZE7BZ+8hd+U1vXv2Xqz5OWxn4zpBxk=
X-Received: by 2002:a5d:444c:: with SMTP id x12-v6mr25778732wrr.143.1540216831718; Mon, 22 Oct 2018 07:00:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAHw9_i+Hi_y2W+5sSLuZvtM0nLHVR=y5R--3D-UB2_W3TYJ8JA@mail.gmail.com> <CAHw9_i+OrDZPD7go_KHC0MWWv6Bn6=X7C2_Ps6SvxU8+BrdynQ@mail.gmail.com> <CAHw9_iJdTv4XmjhhSptZ0q9AjztqS+HzTww4OFX+tUB2ybqb6w@mail.gmail.com>
In-Reply-To: <CAHw9_iJdTv4XmjhhSptZ0q9AjztqS+HzTww4OFX+tUB2ybqb6w@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Mon, 22 Oct 2018 15:59:53 +0200
Message-ID: <CAHw9_iKXi=d+aHFqh04sFZi1isnLCNbM2gGRPExonZw17qsyDQ@mail.gmail.com>
To: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000021ccc60578d1ad0a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/IueAhKcR7Zi0hsQrMlTa2O7V9oU>
Subject: Re: [DNSOP] A quick update on draft-ietf-dnsop-attrleaf / draft-ietf-dnsop-attrleaf-fix
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Oct 2018 14:01:04 -0000

I believe that adding, at the end of Section 2.1.  TXT RRset Use

"Documents which fall into this category include:
RFC6763, RFC6120, RFC5518, RFC5617, RFC6376, RFC7208, and RFC7489"


and Section 2.2. (SRV RRset Use)

"Documents which fall into this category include:
RFC3263, RFC3529, RFC3620, RFC3832, RFC3887, RFC3958, RFC4120, RFC4227,
RFC4386, RFC4387, RFC4976, RFC5026, RFC5328, RFC5389, RFC5415, RFC5555,
RFC5679, RFC5766, RFC5780, RFC5804, RFC5864, RFC5928, RFC6186, RFC6733,
RFC6763, RFC6120. "

will cover this.

It seems that:
RFC3861, RFC3404, RFC6121 and RFC6011 should all be removed from the list.

I was not able to find any URI documents in the list - can anyone educate
me?

W

On Fri, Oct 19, 2018 at 11:49 AM Warren Kumari <warren@kumari.net> wrote:

>
>
> On Fri, Oct 19, 2018 at 9:34 AM Warren Kumari <warren@kumari.net> wrote:
>
>>
>>
>> On Thu, Oct 18, 2018 at 9:04 PM Warren Kumari <warren@kumari.net> wrote:
>>
>>> Hi there,
>>>
>>> Dave suggested I send this out.
>>>
>>> draft-ietf-dnsop-attrleaf and draft-ietf-dnsop-attrleaf-fix have
>>> completed IESG review.
>>> Alissa is holding a DISCUSS position on draft-ietf-dnsop-attrleaf-fix -
>>> this can be seen here:
>>> https://datatracker.ietf.org/doc/draft-ietf-dnsop-attrleaf-fix/ballot/
>>>
>>> Alissa (and a number of other ADs) feel that each of the (37!) updated
>>> documents should be classified into 2.1. (TXT RRset), 2.2. (SRV RRset)
>>> or 2.3. (URI RRset).
>>>
>>> Basically, we need to go through each document in draft-ietf-dnsop-attrleaf-fix,
>>> figure out which class it falls into (TXT, SRV, URI), and add it to a list.
>>> We then add a sentence to each of those sections saying "Documents in this
>>> category include RFCxxxx, RFCyyyy, RFCzzzz".
>>>
>>> Dave has stated that he is unwilling to do this work. Instead of having
>>> the WG document simply stall, Benno and I have agreed that we would split
>>> them between us. If anyone would like to volunteer to help out, we would
>>> not take it amiss.
>>>
>>> Please note that this is not a normal situation - in general we expect
>>> the authors to deal with IESG DISCUSS (and other ballots) - but we wanted
>>> to move this document along.
>>>
>>> So, if you would be willing to take a few documents to classify, please
>>> go to this spreadsheet:
>>> https://docs.google.com/spreadsheets/d/1oTs8ZJy6EZdSt4NXZJbcIRd771V9Rbg9TqddE5KlLGE/edit?usp=sharing
>>> [0]
>>>
>>> Change the reviewer from Benno or Warren to your name **before**
>>> starting the review (we really don't need multiple reviews of the same
>>> document!), and then update the spreadsheet with what "class" of update it
>>> is. Please have the review done by Wednesday Oct 24th.
>>>
>>> Review help would be appreciated, but if you are not able to (I know
>>> people are really busy before IETF week), Benno and I will manage...
>>>
>>
>>
>> ... and my plane was delayed by an hour, so I decided to take a start on
>> this - I’ve done ~20 so far, so please remember to check the spreadsheet
>> before starting any...
>>
>
>
> ... and I got basically all of the rest done on the flight.
>
> I have a few which I really cannot figure out what category they are, and
> so I’ll ask for your help figuring them out...
>
> W
>
>
>> W
>>
>>
>>> W
>>> [0]: Posting a public link to a spreadsheet.... what could *possibly* go
>>> wrong!?
>>>
>>> --
>>> 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
>>>
>> --
>> 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
>>
> --
> 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
>


-- 
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