Re: [Mops] Confirming adoption consensus Re: draft-ietf-mops-streaming-opcons

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 04 February 2020 02:27 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mops@ietfa.amsl.com
Delivered-To: mops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5C9412004A for <mops@ietfa.amsl.com>; Mon, 3 Feb 2020 18:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level:
X-Spam-Status: No, score=-1.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 ufTS5R4r7o8T for <mops@ietfa.amsl.com>; Mon, 3 Feb 2020 18:27:30 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 608E612004D for <mops@ietf.org>; Mon, 3 Feb 2020 18:27:29 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id b15so11147731lfc.4 for <mops@ietf.org>; Mon, 03 Feb 2020 18:27:29 -0800 (PST)
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=0wl+1BOpCABNbaRbnFL4VGOVc91UI0Kc+rFragv/ZtY=; b=j7UtVhHN1sUU6MX9a+/KBRco+AzbtXVByEj/DGBGfumgayzomKZ9Kp0wYGbcfhmlUv wL6Os0SBpIRdAMzOXDHuWv+lVoutEYj+9jPEAQHAeoyiZcbRLbskpyb6il56pQvz9L9l 6Sr19P/Y5YCkRi12GPQpE6P1c5IKOvFbek4SnVkhyYundr2YUCcy1PQfAh8BCTMMMP2/ 7KOfce4LH3MfAox0aL55A6nCnRoybTifcOm3bzsSigQu9g9n1w+tQNBKISwjB81Iz90e sgrrzPaXCVkMix2bJErdZOcxY6pq1ketkcwM/c8bFjsbzW3xMfJIv3Z73fDeH/ucOffY /F+g==
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=0wl+1BOpCABNbaRbnFL4VGOVc91UI0Kc+rFragv/ZtY=; b=a15d4Xw6WwiE4b0kKaojhKdAtBfLvpAw1gzWm03Fz6H4Z+4eZNcT8qaiyvmLbGZbCf NDPK7IExB5Wj3cp9935mSTNEnmwd1AME6D9ONGnXglbObTKNO+xJWBDUtamouG37mNdJ ZCDT7JnFvrbed5u+46PJ7+X/MaJ8C5GQEFI4XNcvz4DNywbwYazKOKxnq/aABeI6APuO ryYUMYUYPpJJWguB/iuydLyUfcAnuRMLHxfFUyi8tc1kUJlrZ6HhJYcXYJyZxjSno/VL ig5TTty8xniIOOeABdnUlkROW8vCJv9BexKVvaAx8mGbekimFFHPnEqFlGS5pMsj5d0K Ga6w==
X-Gm-Message-State: APjAAAWK45umjRQ6/cD9jqRVZpiQCn/H+SBb5Wb5kfmyfNWAMtLm2FrT tLg7Vgk9TcYOZIKFj9OYUb2DUBBBA4yj4mQKwxw=
X-Google-Smtp-Source: APXvYqxiaMNMgp1SCauJG1PUElFvMt0HVsYV9QY1heEKrOPyKrss6OKegMc5+vQ20Y+ukIHDOiULh6VDTm94vm0oaDE=
X-Received: by 2002:ac2:5e29:: with SMTP id o9mr13552741lfg.81.1580783247533; Mon, 03 Feb 2020 18:27:27 -0800 (PST)
MIME-Version: 1.0
References: <C6919186-0074-450C-8E0B-02F09E28574F@thinkingcat.com> <CACq2X+=qUDAumGhBP7k9+WQTo6OrjcKWaOy74ssHrPGRgRAQGw@mail.gmail.com> <CAKKJt-f5sR6X9U7CCRn-uBKc6H5MJEaaRU+Pt-vTF2+MfkfJcA@mail.gmail.com> <B72C34B4-1032-4F08-B5F4-B7CEC3AB8D42@thinkingcat.com> <CAKKJt-e6BeToRFWvOEOVurPo1k4cghDnkDeS4LkTjhKP32Oa7Q@mail.gmail.com> <CAJU8_nUj9UJhqRpHoa7qCxmnesvGF0WavGT1KCigUJ8E4G2dbA@mail.gmail.com>
In-Reply-To: <CAJU8_nUj9UJhqRpHoa7qCxmnesvGF0WavGT1KCigUJ8E4G2dbA@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 03 Feb 2020 20:27:01 -0600
Message-ID: <CAKKJt-e4N=qhBDqW=bLCv+vJx_JRjhobCSq=GZc5HUakHT+V+Q@mail.gmail.com>
To: Kyle Rose <krose@krose.org>
Cc: Leslie Daigle <ldaigle@thinkingcat.com>, Matt Stock <mstock@llnw.com>, mops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000efab9c059db6c7f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/V8dvhgbPm2zzrysQU6u51yWXRC4>
Subject: Re: [Mops] Confirming adoption consensus Re: draft-ietf-mops-streaming-opcons
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Media OPerationS <mops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mops>, <mailto:mops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mops/>
List-Post: <mailto:mops@ietf.org>
List-Help: <mailto:mops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mops>, <mailto:mops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Feb 2020 02:27:33 -0000

Hi, Kyle,

On Mon, Feb 3, 2020 at 4:01 PM Kyle Rose <krose@krose.org> wrote:

> I'll look into the right way to set this up. I'm not sure that the QUIC
> single-repo model makes sense here, but one or more official MOPS repos for
> adopted docs seems like a good idea.
>

I'm certainly not the genius of Github at IETF, but I'd tend to agree - the
MOPS documents aren't likely to have the same tight linkages and
intersecting participant lists that the QUIC core protocol specifications
do. I'm recently co-chair of CELLAR, and that working group uses 4 repos
(see https://github.com/cellar-wg for details).

Best,

Spencer


>
> Kyle
>
> On Fri, Jan 31, 2020 at 1:17 PM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Hi, Leslie,
>>
>> On Fri, Jan 31, 2020 at 11:34 AM Leslie Daigle <ldaigle@thinkingcat.com>
>> wrote:
>>
>>> That’s a fair question.
>>>
>>> IMO, if people are generally interested in using GitHub for docs in this
>>> WG, we should. Kyle?
>>>
>>> There seems to be some leaning that way, given Jake & Ali’s use so far,
>>> but I, at least, would like to hear from others to know whether the
>>> interest in using GitHub for documents extends beyond the authors of that
>>> particular document?
>>>
>> I certainly am (I have a PR waiting for that particular document now, but
>> I don't know why we would not want to use Github for other docs).
>>
>> I'd also note that Ali has at least a few issues in Jake's repository
>> now, and I've been waiting to see if the repository would change upon
>> adoption before adding issues of my own.
>>
>> Best,
>>
>> Spencer
>>
>>> Leslie.
>>>
>>> On 30 Jan 2020, at 16:51, Spencer Dawkins at IETF wrote:
>>>
>>> Since we seem to be getting "support" e-mail and the 31st is tomorrow,
>>> is it too early to ask if the working group will have its own repository
>>> for working group drafts?
>>>
>>> Thanks,
>>>
>>> Spencer
>>>
>>> On Thu, Jan 30, 2020 at 3:25 PM Matt Stock <mstock@llnw.com> wrote:
>>>
>>>> I support the adoption of the draft.
>>>>
>>>> Matt
>>>>
>>>>
>>>> On Tue, Jan 21, 2020 at 2:45 PM Leslie Daigle <ldaigle@thinkingcat.com>
>>>> wrote:
>>>>
>>>>> Thanks, Jake, for putting together the follow ups from the IETF 106
>>>>> MOPS meeting.
>>>>>
>>>>> I’m happy to see others have already started chiming in with comments.
>>>>>
>>>>> We had pretty strong consensus in the room to take this on as a WG
>>>>> item, and I’m happy to formally follow that up on the list here and now.
>>>>>
>>>>> If anyone *objects* to adoption of the document (
>>>>> https://tools.ietf.org/html/draft-jholland-mops-taxonomy-01), please
>>>>> share your objection now.
>>>>>
>>>>> If there is no (unresolved) objection by the end of January 31, 2020,
>>>>> we will adopt this document as draft-ietf-mops-streaming-opcons ...
>>>>>
>>>>> Thanks,
>>>>> Leslie.
>>>>>
>>>>> On 17 Jan 2020, at 17:26, Holland, Jake wrote:
>>>>>
>>>>> Hi Mops,
>>>>>
>>>>> I'm finally writing to follow up on draft-jholland-mops-taxonomy.
>>>>>
>>>>> I did a quick review of the video from the IETF 106 mops meeting:
>>>>> https://www.youtube.com/watch?v=4_k340xT2jM
>>>>>
>>>>> I captured the comments I heard in a new notes section and
>>>>> updated the draft to -01, plus a few very minor editing tweaks.
>>>>> I was going to rename it to draft-ietf-mops-streaming-opcons, but
>>>>> I thought I'd wait until after the adoption call, to make sure it's
>>>>> confirmed on-list. (I think the data tracker is easier to use when
>>>>> you change names less often...)
>>>>> https://tools.ietf.org/html/draft-jholland-mops-taxonomy-01
>>>>>
>>>>> I also wanted to say thanks to the folks who volunteered to co-author
>>>>> this draft. You 3 are BCC'd, and your contributions are very welcome.
>>>>>
>>>>> I also wanted to ask whether there's any particular topics you'll be
>>>>> working on, so we don't get multiple people writing to the same points?
>>>>>
>>>>> Regardless, for the moment the current version is here and I'm
>>>>> accepting pull requests :) :
>>>>> https://github.com/GrumpyOldTroll/ietf-mops-drafts
>>>>>
>>>>> Assuming the adoption call starts soon and is successful, we maybe
>>>>> should move to a WG-owned repo, but that's where it is for now.
>>>>>
>>>>> Thanks and regards,
>>>>> Jake
>>>>>
>>>>> --
>>>>> Mops mailing list
>>>>> Mops@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mops
>>>>>
>>>>> --
>>>>> ------------------------------
>>>>>
>>>>> Leslie Daigle
>>>>> Principal, ThinkingCat Enterprises
>>>>> ldaigle@thinkingcat.com
>>>>> --
>>>>> Mops mailing list
>>>>> Mops@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mops
>>>>>
>>>>
>>>>
>>>> --
>>>> [image: Limelight Networks] <https://www.limelight.com>
>>>> Matt Stock* Principal Architect*
>>>> EXPERIENCE FIRST.
>>>> +1 716 949 0332 <+1+716+949+0332>
>>>> www.limelight.com
>>>> [image: Facebook] <https://www.facebook.com/LimelightNetworks>[image:
>>>> LinkedIn] <https://www.linkedin.com/company/limelight-networks>[image:
>>>> Twitter] <https://twitter.com/llnw>
>>>>
>>>> --
>>>> Mops mailing list
>>>> Mops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mops
>>>>
>>> --
>>> Mops mailing list
>>> Mops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mops
>>>
>>> --
>>> ------------------------------
>>>
>>> Leslie Daigle
>>> Principal, ThinkingCat Enterprises
>>> ldaigle@thinkingcat.com
>>>
>>