Re: [rfc-i] Informational...

"Andrew G. Malis" <agmalis@gmail.com> Thu, 11 June 2020 19:08 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D943A0486; Thu, 11 Jun 2020 12:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" 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 4pIqAnTcbCzC; Thu, 11 Jun 2020 12:08:26 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AD143A07C6; Thu, 11 Jun 2020 12:08:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8FFAAF40718; Thu, 11 Jun 2020 12:07:58 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 3E3BDF40718 for <rfc-interest@rfc-editor.org>; Thu, 11 Jun 2020 12:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJsvln9H8URG for <rfc-interest@rfc-editor.org>; Thu, 11 Jun 2020 12:07:53 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) by rfc-editor.org (Postfix) with ESMTPS id 1EE9BF406D7 for <rfc-interest@rfc-editor.org>; Thu, 11 Jun 2020 12:07:53 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id r16so3149932qvm.6 for <rfc-interest@rfc-editor.org>; Thu, 11 Jun 2020 12:08:19 -0700 (PDT)
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=l0j5sAM0lrX4dp+XVB/E9nsRQSO+iuKMoCTy+VwJpEM=; b=d02aGlb1jfqqUMHE7JAFWex6xdIiWh98Mh2XN23MtgoBOWpmyJwdLoBQ9yifH70h1r MLey7vk2QY7uMLl0+D/wGZM2Dwv1zf7POu8BEIaNFTKrywRY/lMpeyI9JWjS7vgxUI9S sgfMeLzPJPVIEOip1wEd5c6ndWWh5shC7MajUEehgmnEpbAuXnztePwfTqxsz+zh0ThB iH7Hc34DXTKT45pgVEqrVy3X/boKCTttxgsGvhe0+/H+CblmfpGwcJc/W/jmB0FS7dZz 2nxRFv/uXqfsi3+58FoWhS+uXPEKM/85LFcspDfIEMa/1nT3Sa89LlbPCPGMn19/lvV3 H/Zw==
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=l0j5sAM0lrX4dp+XVB/E9nsRQSO+iuKMoCTy+VwJpEM=; b=pRgValC0TIpUBAS6FP7czV6nvIjZBE2vRGMzAexTin7+zcLqyzS+ErSjOAVCv9t3VE s8QVHvYBzgaCIsWEzeKokqr61Kxe0jFdP+W69i7SgGEmdAJdbUUzn3SyzD5OXH3MyDWO xzZ+Jkhx6QKOunuQfbNkS0Xijng1qDg286Gt++ZF0T+OBLV/2REoFchzGyRdNfNsMp1s OzAoDHwUtwVf4nB4ApBKVRW9pyLvrndIt36rDbvYBCGERMpSdvpOPn6cHgBd6AgCeXaJ qXO70RHfm2E9YLNarE3X8bEaJ/6Mw1b956AXgv4h+1G2KRmKgAYdy1pob7MMnUoXiE4y 1UeA==
X-Gm-Message-State: AOAM5309Fxk/5uLRSAHtBbJ9sv5ViPrd+yhzDwm4IuuuB/rlaxFlqfjD GkH/YBW8/IutFYTJ4axBC0NWLieGp7jAX6WEr5mmyA==
X-Google-Smtp-Source: ABdhPJx7KwIibPHrY/6OEY/A0/29cm5wlwmbFyBPSBb7lZkr8DooiWbxoOmSWilpXNZz65rW/ZKc+S8uLRV5EN/mUOQ=
X-Received: by 2002:a0c:ba22:: with SMTP id w34mr9276379qvf.129.1591902497984; Thu, 11 Jun 2020 12:08:17 -0700 (PDT)
MIME-Version: 1.0
References: <021bfdfc-136c-ea07-e2d5-042d9e429522@nthpermutation.com> <CAA=duU2smrFwZy_mAm6c=dnQqD3z8ErmDA8bAzZLh87dpt4Q-g@mail.gmail.com> <c55c0b9d-dc92-4410-a6ec-489a52db0179@nthpermutation.com>
In-Reply-To: <c55c0b9d-dc92-4410-a6ec-489a52db0179@nthpermutation.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 11 Jun 2020 15:08:06 -0400
Message-ID: <CAA=duU3xkwbJHHEu+Uwp173Ayepx+q4xzd-WOH1x0QyVBKUvfQ@mail.gmail.com>
To: Michael StJohns <msj@nthpermutation.com>
Subject: Re: [rfc-i] Informational...
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: RFC Interest <rfc-interest@rfc-editor.org>
Content-Type: multipart/mixed; boundary="===============4444385906053655294=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

Mike,

That sounds good, or, if you want to be more wordy, "any RFC published by
an IETF Working Group that is not a standards-track or Experimental
specification."

Cheers,
Andy


On Thu, Jun 11, 2020 at 1:14 PM Michael StJohns <msj@nthpermutation.com>
wrote:

> On 6/9/2020 6:17 PM, Andrew G. Malis wrote:
>
> Mike,
>
> You left off what's probably the most common category, an IETF WG
> consensus document that doesn't contain protocol conformance language (e.g.
> architecture, framework, overall requirements, etc.), thus is not on the
> standards track.
>
> What - not "Other; Uncategorized"?
>
> Seriously though - I agree.   I'm wondering if there might be 2-4
> categories we could agree on to break these down.  Or maybe just one?
>
> Working Group Explanatory Material?
>
>
>
> Cheers,
> Andy
>
>
> On Tue, Jun 9, 2020 at 3:24 PM Michael StJohns <msj@nthpermutation.com>
> wrote:
>
>> Hi -
>>
>> I was looking at a document that's currently on last call for the third
>> time in the transport area with a proposed status of "Informational".
>> After reading it, I was wondering why it was being published by the
>> Transport area, as opposed to being an architectural discussion by the
>> IAB or even as a product of the IRTF?  In any event, it got me thinking
>> about the Informational category of documents and wondering what would
>> happen if we added a sub-header or sub-category for documents published
>> under this banner - here's a strawman list:
>>
>> IAB Architectural Note - applied to IAB consensus documents
>> IAB Policy Note -  ditto
>> IESG Policy Note - applied to IESG consensus documents
>> Community Policy Note - applied to community consensus documents
>> wherever originated
>> Technical Cross Publication - previously published documents where the
>> IETF will not gain change control
>> IRTF Pure Research
>> IRTF Applied Research
>> IETF Path Not Taken (applied to documents that weren't accepted as WG
>> items, but might have been  viable alternatives ISE or Area Director
>> sponsored)
>> Individual Technical Proposal or Opinion
>> Individual Policy Proposal or Opinion
>> Individual Architectural Proposal or Opinion
>> Individual Other
>> (IAB/IESG/IRTF/IETF) Workshop Report
>> Business Report
>> Other; Uncategorized.
>>
>> The Informational group is the least homogeneous of any of the
>> publication categories, and possible the one least understood by the
>> non-IETF crowd as to its role.  Perhaps providing some sub-text might
>> improve things slightly.
>>
>> This is a discussion topic - not so much a baked proposal.
>>
>> Enjoy - Mike
>>
>>
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest@rfc-editor.org
>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>>
>
>
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest