Re: [Rfcplusplus] Conversation as metaphor

"Aaron Falk" <aaron.falk@gmail.com> Tue, 10 July 2018 21:29 UTC

Return-Path: <aaron.falk@gmail.com>
X-Original-To: rfcplusplus@ietfa.amsl.com
Delivered-To: rfcplusplus@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A4B41310FD for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 14:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_PASS=-0.001, 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 HxDg4p7-LHL5 for <rfcplusplus@ietfa.amsl.com>; Tue, 10 Jul 2018 14:29:47 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (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 0E14D130DE1 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 14:29:47 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id l10-v6so19704370qtj.0 for <rfcplusplus@ietf.org>; Tue, 10 Jul 2018 14:29:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version; bh=dc/L7hgbRH4gPCrujT8N72CAjLwRJAFFg3SNX45Y1FI=; b=sNZdrY5fvtlbIy1bhQ0cKeAQ5RzFV/YY6zp+mgLzlJsStvFSTD7dAvN1Mu+ZAhuB5G iWr2/XhMCNJvvmVQ2nAmga/RmhNpXauHzYApU9+4MMtkJIDtZp4EfQ3sHLYoX/nbBN5G afTXTSU3LcZlLY6BWS+Lr5yb3z9KIi/0BPLWlQkwMF2m6ZnFDK7ozLjhRYjQGSX462ma sNAIV5qeciDKlHX+Fcta2/jMniVUvaxPeMmHLNF64rwXYHsIw12q6n1wGPHP5DHwNFq/ uhaoe1Almd4XqBFN419eyaT2uIq4kbJaWRMYvb/dQcCSsTruPoxVhZUAyDbNCENkxd7+ tkWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version; bh=dc/L7hgbRH4gPCrujT8N72CAjLwRJAFFg3SNX45Y1FI=; b=LVLE9Tlrh22qa8R1hVLTRKNOJQmCKKjeor3Q7+gUdeUpMp9pDKlYLXU0dyLZGebiBx qCtX1WgVH3+CAitwL+MUhlMYVeudviF0DVsWoxpKPF/i/2jpa82QA9lDV8nhL+X643hv YBzt6hFdHhdQUUZv2u++V6Im+TcKbFBvuCJcxsMpt8ZGjUy4sFw4J5wVHRkVDhzfUZdV aSSD7hGcC8S4htJHUlh0eX11TrK0+Isi3FYpDirx0LgzUWUKphDN9s7O1wtqlypxRjWH Lw8/ooCQg4uEJ8kHAXBieGH99lbwDWlCjpn21eRKF1LfwPsecrNULeKL5hpojo2+yjce TjIw==
X-Gm-Message-State: APt69E2kbnKXSAEyokbrEfvNgxjK3PVL2QJbMOHtSPkHH2idPHjef3kw aRoVXj6l4fQwLAQ3W9jtHFm7rytc
X-Google-Smtp-Source: AAOMgpdQ9dTiWtoMKdcj8XBkIu52XevGD2ykm0t/aK6eeXaRaScjzjF8qNwacM1ky3MMt1TE25uMhQ==
X-Received: by 2002:a0c:95fa:: with SMTP id t55-v6mr23165080qvt.246.1531258185905; Tue, 10 Jul 2018 14:29:45 -0700 (PDT)
Received: from [172.19.33.154] ([2001:4878:a000:3000:f826:7a2c:984c:1004]) by smtp.gmail.com with ESMTPSA id b4-v6sm15568463qtb.64.2018.07.10.14.29.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jul 2018 14:29:45 -0700 (PDT)
From: Aaron Falk <aaron.falk@gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Eric C Rosen <erosen@juniper.net>, rfcplusplus@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
Date: Tue, 10 Jul 2018 17:29:43 -0400
X-Mailer: MailMate (1.11.2r5507)
Message-ID: <8517CAB5-EB55-4E1B-9FBE-01A965923901@gmail.com>
In-Reply-To: <6125AF9C-9112-4728-B4B3-E5CB06120B50@gmail.com>
References: <CA+9kkMBVC82qy0hbUbQKm=OsFPsaJUPndtVaxd782au6Qy0w6Q@mail.gmail.com> <a4b50286-5c54-e6cf-9087-7171030b7fca@juniper.net> <C9EBFF44-DB93-45E4-954D-2AC5E2F47D03@gmail.com> <20180710192810.GQ20282@mx4.yitter.info> <0e127473-902a-2421-6b5d-73f9e7f83286@juniper.net> <CA+9kkMDwOuLOJMzBSowqga-6s0GnO=03PBScOaHRcJT0+QYicw@mail.gmail.com> <1F7626CA-FB10-402A-BCF3-EA89526AC63C@gmail.com> <CA+9kkMAdth-wiCxMbmuXQKRY08FoPz0+0H=OLaNEyrYAymw7FQ@mail.gmail.com> <6125AF9C-9112-4728-B4B3-E5CB06120B50@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_575FB68F-C976-482D-B190-559015BD10B3_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfcplusplus/R1E_HF-hlTuauk_NdYiMx87X0tY>
Subject: Re: [Rfcplusplus] Conversation as metaphor
X-BeenThere: rfcplusplus@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: For discussion of the RFC++ BoF proposal and related ideas <rfcplusplus.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfcplusplus/>
List-Post: <mailto:rfcplusplus@ietf.org>
List-Help: <mailto:rfcplusplus-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfcplusplus>, <mailto:rfcplusplus-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 21:29:53 -0000


On 10 Jul 2018, at 17:24, Aaron Falk wrote:

> On 10 Jul 2018, at 17:13, Ted Hardie wrote:
>
>> On Tue, Jul 10, 2018 at 1:23 PM, Aaron Falk <aaron.falk@gmail.com> 
>> wrote:
>>
>>> IIRC, the copyrights for IRTF stream RFCs default to permit 
>>> publication
>>> elsewhere to allow for easy submission in more-recognized forums.
>>>
>>
>> Well, you're the author of the relevant doc, so I hesitate to cite it 
>> to
>> you, but the text is in RFC 5743 and in
>> https://trustee.ietf.org/docs/IETF-Trust-License-Policy.pdf.  
>> Basically,
>> though, the individuals retain their own copyright (along with the 
>> Trust
>> Copyright, managed by the IETF Trust at the request of the IRTF).  
>> They can
>> re-submit.
>
> Thanks for confirming my memory is still of some use. ;)
>
>>
>>> Finally, I haven't seen anyone present that helping IRTF output get 
>>> more
>>> recognition is a goal of this activity. Is someone asking for this?
>>>
>>
>> It's been a discussion between IRTF folk and the IAB for some time.  
>> It
>> could, of course, be a separate activity from this experiment.
>>
>
> Indeed.  I think it is separate for the reason in my last message you 
> chose not to cite:
>
>>  an important reason for RGs to publish RFCs is the same reason that 
>> they are RGs in the first place: to have their work be adjacent, 
>> influence, and possibly migrate to the IETF. Of course, that is not 
>> the only reason we have RGs but it is a good reason to have 
>> non-standards track output in similar format & repositories as the 
>> IETF.
>
> To be explicit: while there might be value in creating a peer-reviewed 
> "IRTF Journal" or somesuch (and it has been proposed many times), many 
> IRTF documents would

*not* (sigh)

> be candidates for it.  Compared the IRTF RFC Stream, the criteria for 
> publication would be quite different.
>
> --aaron