Re: [Rswg] Issue Tracker/Filed Issues

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 03 October 2022 20:59 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE37C15257C for <rswg@ietfa.amsl.com>; Mon, 3 Oct 2022 13:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Level:
X-Spam-Status: No, score=-7.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ryc05B9zZsA for <rswg@ietfa.amsl.com>; Mon, 3 Oct 2022 13:59:50 -0700 (PDT)
Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01C49C15258A for <rswg@rfc-editor.org>; Mon, 3 Oct 2022 13:59:23 -0700 (PDT)
Received: by mail-pg1-x530.google.com with SMTP id f193so10714918pgc.0 for <rswg@rfc-editor.org>; Mon, 03 Oct 2022 13:59:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date; bh=9AegyYPTpLfkpy3Gcv1TZDH+WCIRtvlu1MzyGUVK+Qw=; b=a5/A9bxBh0tIQvoZzNdFFHY8xw3LVFwOHCIojoCKwXHOl7OcZq5K/V7bG7KriKl2B0 9d5DtujyKyz+0siidChPf0g4Z97/HvgU+k7ZA14x+TrxnVqRohsEm9hJ0rPNsQqlRGR9 tqHcNiWxaOrKa0QceS7+Kge1hYAhlPgEPISJq8PSUn6fPIK6HE10tLkmREkvBWyclNbz 9ifdMb8FEj2AMBpFli/+/+gES8Kun8boeS/JEwl5hSl3Fnf/9ur63nNUHNAcD9Pswqfp ggxFdYr/duv3oY2liE2EHchQOd2Aayu1BAJWdbgQxQnrffZHltvIAh/jPpJZoNXBGlaD CAuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date; bh=9AegyYPTpLfkpy3Gcv1TZDH+WCIRtvlu1MzyGUVK+Qw=; b=66ADd14W9hstjdpENqXUGtHl8fuHljfuWcI9h3teynmCW+MjvixkBNaY9djKwB8lFm pvE2OnfqDP222rmtDwIwwZZKs1uwRW0ljm9L11p9PeWlac4/jCKVF7aq/9GOxmWfkRTc 5C1v/cCI+YWmacaY56glmVKqlezpKlw9ZKJnsdZMuYWn/SoQih9f0DoFoHvMvkDSPxBz xo4tF7y0C0kEaZW8SIvJuUFFx3+ePY2yvRr+FwNCFaoFfHCw0sVi7kR3sSDJL4AeLaXt o4sxvCZvicuKwRmoOvlDcboRkqOTHZeAzVupqrjqi1WS0gf1TdlCkIPqguzdG6RfdaYs ZTGw==
X-Gm-Message-State: ACrzQf0ymVb1eNdupsoOmCBR6Fb4dBh5AFN0tGbzAEI3JSjC9ROSMlms zxtCMAtHEVhbO5+jrhQC11U8zLY07/MO5w==
X-Google-Smtp-Source: AMsMyM5TpY8a1tyuiv6+xQUuSdnbVae2vZnmWlASXzPn1ThwOC4JBjFPH4QhhW4KX2Kki215CxuXiQ==
X-Received: by 2002:a63:fa4f:0:b0:438:e26d:5ec with SMTP id g15-20020a63fa4f000000b00438e26d05ecmr20163997pgk.361.1664830763426; Mon, 03 Oct 2022 13:59:23 -0700 (PDT)
Received: from ?IPV6:2406:e003:1124:9301:80b2:5c79:2266:e431? ([2406:e003:1124:9301:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id t3-20020a17090a6a0300b0020a0571b354sm6246994pjj.57.2022.10.03.13.59.20 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 Oct 2022 13:59:22 -0700 (PDT)
Message-ID: <fa8d20ed-0138-441b-8860-3f9a44a7bd6e@gmail.com>
Date: Tue, 04 Oct 2022 09:59:18 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Eliot Lear <lear@lear.ch>, Eric Rescorla <ekr@rtfm.com>, rswg@rfc-editor.org
References: <CABcZeBN+qPVTo1Yn3tDSJSqFOajm3WX-y480Y++fSAEPgAUuyw@mail.gmail.com> <fa5a2585-51d5-0035-11b9-c3920a340066@lear.ch>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <fa5a2585-51d5-0035-11b9-c3920a340066@lear.ch>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/rswg/8Q7_1_YzB8zjwBFV_Qk8CZYHE60>
Subject: Re: [Rswg] Issue Tracker/Filed Issues
X-BeenThere: rswg@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RFC Series Working Group \(RSWG\)" <rswg.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rswg>, <mailto:rswg-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg/>
List-Post: <mailto:rswg@rfc-editor.org>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rswg>, <mailto:rswg-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2022 20:59:54 -0000

On 03-Oct-22 20:29, Eliot Lear wrote:
> Hi EKR,

Not ekr, but here are my thoughts:

> 
> I am pondering this issue list, and wondering how that shapes into an agenda.  I am also wondering at what pace we want to proceed.  Obviously one doesn't need to sort every issue in one meeting.  The predecessor to this group certainly didn't ;-)

Certainly not, and some of them can surely be handled without needing meeting time. Might I suggest that the chairs orchestrate a process of discussing issues one at a time, to see if there's a quick consensus or if a deep discussion is needed?

> 
> I am thinking that Issue #13 (Produce a real 7991bis) is something of an umbrella for other issues, but that we also need to decide how much energy to put into Issue #12, documenting what we have.  It's not like we've had a lot of energy on this list, and so I am a little concerned about trying to do both.

To what extent do we need more for #12 than what is in draft-irse-draft-irse-xml2rfcv3-implemented-02?

> With regard to Issue #9 about who gets to decide what, I have a simple suggestion, which is this: until this group decides to delegate format aspects that aren't otherwise already the province of the RPC, we continue to set'em up and knock'em down.  If someone brings a proposal for delegation that we like, let's of course consider it, but let's also not block our work on a lack of consensus over such a proposal.

I agree with that, but for the detailed work on #13 (7991bis) and #14 (SVG) it seems fairly clear to me that a design teams approach is appropriate. If we agreed on that too, we could close #9 soon.

Regards,
     Brian

> 
> Thoughts?
> 
> Eliot
> 
> On 27.09.22 19:43, Eric Rescorla wrote:
>> Hi folks,
>>
>> In Philadelphia we discussed setting up an issue tracker on GitHub
>> to track proposed new issues. I have now done so at:
>>
>> https://github.com/rfcseries-wg/new-topics/
>>
>> I have seeded the issues with the proposed topics I am aware of.
>> If I have missed any or described them inaccurately, please file
>> new issues, comment, etc. Pete is also giving it a scrub to
>> make sure we missed anything.
>>
>> Go ahead and file your new topic proposals. As discussed, any
>> substantive discussion of the issue beyond fleshing out what it's
>> about should be on the list.
>>
>> Note 1: This repo is just for new topics. Once we drafts, we may
>> create new repos for those.
>>
>> Note 2: I believe I have captured the right language for
>> CONTRIBUTING.md, but please file PRs/issues if you Think
>> something is wrong.
>>
>> -Ekr
>>
>>
>>
>